Import corrections and overlap
Review changed exports, map row identities, and apply full or partial corrections without double counting.
Browse documentation
On this page
Use /imports when incoming evidence revises or overlaps an earlier export. The comparison shows rows and calculated financial effects before approval.
Prepare the sources
Review the incoming document’s identity and evidence first. New or corrected activity needs a reviewed posting proposal. Select the incoming source and, where relevant, the earlier source it should be compared with.
Do not compare unrelated exports solely because their amounts look similar. Identity, accounting lineage and statement scope matter.
Choose the correction scope
| Mode | Required scope | What absent earlier rows mean |
|---|---|---|
| Full statement replacement | Same account, entity, currency and exact statement period | Removed rows reverse their earlier postings |
| Partial update | Same account, entity and currency, with overlapping dated statements | Earlier rows are retained |
A partial file may contain only a corrected transaction. Absence from that file is not evidence that other transactions disappeared.
Map changed identifiers
Preview once to load the rows. Expand the identity mapping controls when an incoming export uses changed row identifiers. Select the earlier transaction represented by each incoming row, then preview again.
Mappings must be one-to-one, refer to rows in the selected company and imports, and stay within the supported limit. Partial corrections require explicit mapping even when the export key stayed the same. Equal, stable keys can identify equal normalized rows; unmatched incoming identities are treated as new and require overlap review.
Amounts or dates alone do not establish identity. Ambiguous repeated identities and already superseded earlier rows block approval.
Inspect financial effects
The preview classifies new, duplicate, corrected, removed, retained and ambiguous rows as applicable. It runs the normal posting, recurrence and settlement controls in a rolled-back transaction. Previewing retains no temporary journals.
Inspect proposed reversals, new postings, month-end cash, goal effects, starting-cash controls and limitations. A duplicate retains its active earlier posting. Corrections reverse the supported prior journal and post the reviewed replacement.
Save or apply
Save an evaluation even when approval is blocked to preserve the comparison. To apply effects, give a name and reason, acknowledge the scope and limitations, and approve the current preview.
Approval repeats the validation and commits the effects, source dispositions, audit, receipt and recalculation request atomically. A changed source invalidates the preview. Retrying an identical request key returns the saved receipt rather than posting again.
A full replacement supersedes the old statement scope. A partial update preserves both documents and only supersedes the corrected rows. Conflicting balance evidence may therefore still need separate reconciliation.
Bounds
One review supports up to 2,000 normalized rows across the selected sources, 100 explicit mappings and 200 journal effects. Partial mappings require dated transaction rows; balance evidence cannot be replaced piecemeal. Unsupported FX, missing provenance and closed-period controls remain approval blockers.
See Troubleshooting for stale previews and unavailable financial effects.