These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Accounting Document and Account Reconciliation
- Features
- Account reconciliation
Account reconciliation
Compare source-identified provider movements with confirmed documents on an account.
OverviewReconciliation exceptions×
Accounting Document and Account Reconciliation · Account reconciliation
New
Reconciliation exceptions
Reconciliation items
| Provider event ID | Occurred at | Amount USD | State | Account | Matched document | |
|---|---|---|---|---|---|---|
| PEI-947 | 24 Oct | 190 | Unmatched | LA-120 | AD-94388 | |
| PEI-208 | 17 Oct | 70 | Exception | LA-150 | AD-22049 | |
| PEI-804 | 18 Oct | 240 | Unmatched | LA-110 | AD-37927 | |
| PEI-780 | 03 Oct | 130 | Exception | LA-120 | AD-13181 | |
| PEI-203 | 05 Oct | 490 | Unmatched | LA-140 | AD-85779 |
6 of 6 records
PEI-947Reconciliation items · RI-78352
UnmatchedOccurred at24 Oct
Amount USD190
AccountLA-120
Matched documentAD-94388
What you can do
Work from the provider movement
A reconciliation item identifies a provider movement by event identifier, occurrence date, amount and ledger account. It also points to a matched accounting document. This gives the reviewer a concrete starting point: which external movement occurred, which financial account it affected and which confirmed instruction might explain it. The item’s state distinguishes an unmatched movement, a matched one and an exception.
The match rule is deliberately strict. The amount and confirmed occurrence date must agree exactly with a confirmed instruction linked to the same account. A difference in amount or date remains open or becomes an exception. An operator should not resolve a difference by forcing a match. Instead, the reviewer identifies whether the provider event, document or account assignment requires investigation.
How the work is organized
- Source movement. Provider event identity, amount and date establish the item being reconciled.
- Candidate document. The linked accounting document and its account lines show the proposed financial explanation.
- Disposition. Matched, unmatched and exception states keep unresolved items separate from supported matches.
What to agree during setup
Agree the provider source, event identifier format and date convention before importing movements. Choose how the finance team handles a provider event that arrives after the document, or a document whose outcome is still pending. Define which account a movement belongs to and make sure document lines use the same account identity. The reviewer needs access to the provider evidence that supports the comparison.
The team should rehearse duplicate provider events as well as mismatches. One event identifier should not create two independent matches. A correction should retain the original source item and the reason for changing its disposition. An auditor must be able to follow the link from movement to account, document and provider evidence.
Check the handoff on an actual case
A supplier-related instruction has a confirmed provider outcome on an account. A provider movement arrives with the same amount and occurrence date. The reviewer checks the account link and the source event identifier, then marks the movement matched against the document. A second movement arrives with the same amount but the next day’s date. It remains unmatched or is marked an exception; matching the amount alone is insufficient. A third event with a different amount also remains open. The reviewer can use the exception list to determine whether the cause is a provider correction, wrong account or wrong candidate document.
The matched population should be understandable without hiding open items. The team can group exceptions by account and date, then return to the underlying source record. Keep the provider event identifier visible in reports so an external statement can be compared with the local record.
What your team sees
- Reconciliation exceptions — Examine open movements with account, amount and occurrence date.
- Matched movements — Trace accepted links from a provider event to its confirmed document.
Follow the work through
What it keeps track of
Data model- Reconciliation items
- Source-identified provider movements matched against banking instructions.
- Accounting documents
- Accounting documents prepared, reviewed and linked to provider outcomes.
- Document lines
- Line-level amounts recorded against an accounting document.
- Ledger accounts
- Ledger accounts referenced by document lines and posted journals.
- Cash receipts
- Provider event evidence linked to accounting documents.
Who uses it
Permissions- Accounting Reviewer
- Investigates and resolves account movements.
- Accounting Preparer
- Supplies document context.
- Auditor
- Checks the resulting evidence.
- Admin
- Manages access to the finance records.
Set up Accounting Document and Account Reconciliation your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.