Reconcile period, unit and movements before publishing an equity statement
Keep equity-statement arithmetic checks separate from accounting judgment and specialised ESEF validation.
Narrative and numeric checks differ
A financial report can explain geopolitical risk carefully while still mixing periods or units in its equity statement. Narrative adequacy and numeric reconciliation require different checks. Truthound can validate a prepared arithmetic contract; it should not approve accounting judgments or an electronic filing.
The 2026 priorities
ESMA published its 2026 common enforcement priorities on October 13, 2026. They distinguish geopolitical uncertainty, restructuring matters, connected sustainability information and common ESEF errors in statements of changes in equity. The announcement is not a finding against a particular issuer.
Connect balances within one scope
Preserve equity item, consolidation scope, period, currency, display unit, opening balance, movement category and closing balance in the extract. The owner defines how the previous close connects to the current opening. Entity and group figures, or current and comparative periods, should not share an ambiguous key.
Find the sign and unit boundary
Check sign conventions even where labels match. One table may express a decrease as negative; another may put a positive amount in a deduction column. Thousands and millions also need separate units. Establish rounding policy before accepting a small residual as harmless rather than letting the observed difference choose the tolerance.
The arithmetic supplied to Truthound
Truthound Core Python SDK 3.3.4, operating on a prepared Polars table, provides ExpressionValidator for caller-defined Polars row expressions and ColumnPairValidator for specified comparisons of non-null fields. Accounting owners supply arithmetic, null treatment and rounding bounds. A failed relation should initiate investigation, not an automatic balance adjustment.
Compare the existing predicate
An existing Pandera 0.35.0 pandas predicate can retain the same arithmetic. Compare it with a prepared Truthound path using a wrong-period opening, a differently scaled movement and an omitted component. Documented support for custom expressions does not establish identical filing acceptance.
Leave format validation to its tools
Specialised tools and procedures still handle ESEF tags, contexts, extensions and XBRL rules. Correct extracted arithmetic can coexist with incorrect tagging in the report. Preserve the scope and result of both checks so the team knows which boundary revealed the problem.
Record how a difference was resolved
When a difference appears, record the item, period and unit involved. Assign responsibility for distinguishing extraction error, presentation convention and underlying accounting content. Preserve an approved adjustment and its basis alongside the source rather than losing the reason before the next reporting cycle.
Give the reporting review its evidence
The useful review artifact is a reconciled table with unresolved differences, not one pass label. Explain the scope of numeric validation before combining it with narrative judgment. A repeatable comparison gives later reviewers a concrete basis for checking the next report.
Conditions
Use an extract with owner-confirmed accounting scope, units, arithmetic and rounding policy.
Alternatives
Keep existing Pandera 0.35.0 pandas arithmetic predicates under the same definitions.
Limitations
Arithmetic checks do not replace accounting judgment or complete ESEF/XBRL validation.
Evidence
- Event checked
- Subject checked
- Modified
