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.
- Legal Billing & Time Tracking
- Features
- Reconciliation
Reconciliation
Compare movements, dates and snapshots before marking a match.
OverviewReconciliation exceptions×
Legal Billing & Time Tracking · Reconciliation
New
Reconciliation exceptions
Reconciliation items
| Provider event ID | Occurred at | Amount USD | State | Account | Matched document | |
|---|---|---|---|---|---|---|
| PEI-775 | 27 Oct | 560 | Unmatched | LA-140 | AD-72621 | |
| PEI-925 | 18 Oct | 70 | Exception | LA-150 | AD-18677 | |
| PEI-373 | 15 Oct | 920 | Unmatched | LA-120 | AD-45140 | |
| PEI-533 | 09 Oct | 630 | Exception | LA-130 | AD-13272 | |
| PEI-991 | 12 Oct | 640 | Unmatched | LA-140 | AD-47267 |
6 of 6 records
PEI-775Reconciliation items · RI-42138
UnmatchedOccurred at27 Oct
Amount USD560
AccountLA-140
Matched documentAD-72621
What you can do
Reconciliation in practice
Reconciliation starts with a provider movement identified by its event key, date, amount and ledger account. The linked accounting document gives the expected instruction. A movement becomes matched only when the amount is exact, the confirmed occurrence date is exact and the document belongs to the same account. A differing amount or date remains unmatched or becomes an exception; there is no forced match to make a report look clean.
Dated account snapshots retain both recorded ledger and available balances and the provider snapshot identifier. The finance lead can compare those amounts with the movements applied during the period. Keep the source event key stable so the same event is not counted twice. A difference between provider availability and recorded ledger balance deserves investigation with the underlying document and event, rather than a manual status change.
How the work is organized
- Identify the movement. The Finance Lead keeps the provider event identifier with its account and date.
- Check the match. Compare the linked document, account, amount and confirmed occurrence date.
- Retain exceptions. Leave a mismatch open with its original source record.
What to agree during setup
Agree the account and provider feed identifiers and the time zone used for the confirmed occurrence date. Define who receives unmatched and exception work. Import a known opening snapshot before a pilot period, then collect the closing snapshot from the same account. Decide how to document a correction while preserving verified original lines and decisions.
Check the handoff on an actual case
Use one confirmed document and a movement on its account with exactly the expected amount and date. Verify the item is matched. Repeat with a different date, then with a different amount, and inspect the exception view to ensure both stay open. Compare the account snapshot before and after the period. An auditor should be able to see the source event, the matched document and the snapshot used in the comparison.
The handoff should show who made each decision and which record changed. Ask a preparer and reviewer to repeat the case from their own access. Confirm the auditor can reconstruct the sequence without changing the source records. If a provider result is involved, compare the external reference and persisted effect before closing the case.
What your team sees
- Reconciliation exceptions — Investigate unmatched or exception movements by account and source event.
- Account snapshot history — Compare dated recorded and available balances for an account.
Follow the work through
Continue through document preparation, independent review and reconciliation. Use the data model to confirm the record links before an import.
What it keeps track of
Data model- Reconciliation items
- Source-identified provider movements matched against banking instructions.
- Account snapshots
- Dated provider balance snapshots for a financial account.
- Ledger accounts
- Ledger accounts available to accounting documents and journal lines, with account code, currency and active flag.
- Accounting documents
- Central accounting document: readable record number, subject, lifecycle status, business date, gross amount USD, revision and counterparty.
Who uses it
Permissions- Finance Lead
- Investigates and reconciles.
- Accounting Reviewer
- Checks evidence; Auditor inspects the outcome.
Set up Legal Billing & Time Tracking your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.