Introduction
Use this article when the validation report contains the error inconsistentCalculationUsingRounding. This error indicates that the calculation performed by the iXBRL engine does not match the reported total or subtotal.
Summary
After following this article, you will understand the most common causes of calculation inconsistencies and how to investigate and resolve them.
Overview
The inconsistentCalculationUsingRounding error occurs when the validation engine calculates a different result than the value reported in a total or subtotal.
This means there is a difference between:
- The calculated result based on the tagged facts.
- The reported value of the total or subtotal fact.
In many cases the difference is small, but it should always be investigated.
Common causes
Cause 1: The calculation is incorrect
The most common cause is that the reported total does not match the underlying values.
For example:
| Line item | Value |
|---|---|
| Item A | 100 |
| Item B | 200 |
| Total | 250 |
In this example, the reported total should be 300 rather than 250.
To investigate:
- Locate the affected total or subtotal in the report.
- Open the source file.
- Verify the calculation in the source data.
- Correct the reported values if necessary.
- Generate a new iXBRL package.
Cause 2: Incorrect sign configuration
A calculation inconsistency can also occur when one or more concepts are reported with the wrong sign.
For example, an expense concept that should contribute positively to the XBRL calculation may be reported as a negative fact value.
This causes the validation engine to calculate a different result than expected.
To investigate:
- Open the validation report.
- Locate the affected concept.
- Open the inline viewer.
- Review the concept details and fact values.
- Verify that the sign configuration is correct.
More information can be found in this article: Resolve sign-related validation inconsistencies
Cause 3: Rounding differences
Sometimes the underlying calculation is correct, but rounding causes a small difference between the displayed values and the calculated result.
For example:
| Line item | Actual value | Displayed value |
|---|---|---|
| Item A | 100.4 | 100 |
| Item B | 100.4 | 100 |
| Total | 200.8 | 201 |
The displayed values may appear correct to the reader, while the validation engine performs its calculation using the underlying reported facts.
Depending on the taxonomy and filing requirements, these small differences may still trigger a validation message.
Always consult your auditor regarding acceptable rounding differences.
Investigate the inconsistency
- Open the validation report.
- Locate the reported total or subtotal.
- Open the inline viewer.
- Review the calculation relationships for the affected concept.
- Compare the reported value with the contributing facts.
- Verify:
- The reported values.
- The calculation in the source file.
- The sign configuration of the contributing concepts.
- Any potential rounding differences.
Expected Result
The reported total or subtotal matches the calculation performed by the iXBRL engine and the validation message no longer appears after generating a new iXBRL package.
Remarks
- Always verify the calculation in the source data before making changes to the iXBRL tagging.
- Calculation inconsistencies are often caused by incorrect sign configuration rather than incorrect totals.
- The inline viewer can be used to inspect the calculation relationships of the affected concept.
- Small rounding differences can also trigger this validation message.
- After making corrections, regenerate the iXBRL package and review the validation report again.
Was this article helpful?
Articles in this section
- The XBRL button not visible
- message:positive - Reported value is below 0
- inconsistentDuplicateNumericFactInInlineXbrlDocument
- inconsistentCalculationUsingRounding
- incorrectNamingConventionReportPackageReportFile
- message valueFinancialReportingPeriod
- extensionTaxonomyWrongFilesStructure - Each linkbase type MUST be provided in a separate linkbase file: cal linkbase has no calculationLink element
- missingMandatoryMarkups