break-trace

To trace a reconciliation break, you cross-compare the originating GL entry against the matching subledger transaction by diffing posting dates, FX rates, accounts, and sign conventions to identify the mismatch. This isolates the exact differing element that caused the break.

The best way to identify a GL subledger break is to fetch both the journal entry and the matching subledger transaction, then diff attributes like posting date, FX rate, account mapping, and amount signs. This comparison highlights the specific field discrepancy driving the reconciliation break.

You find the mismatch by tracing the break row to its source GL entry and subledger transaction, then cross-comparing attributes like posting dates, FX rate dates, and quantity signs. The diff reveals the exact data entry or mapping discrepancy causing the reconciliation break.

Yes, after identifying a reconciliation break, the process produces a structured JSON output containing a concise root-cause sentence and a compiled recommended remediation action. This provides clear, actionable steps to resolve the specific GL and subledger mismatch.

When auditing a reconciliation break, you need to compare posting dates, FX rates and dates, account mappings, and both quantity and amount sign conventions. Differing values in these specific fields between the GL entry and subledger transaction typically reveal the break's origin.