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.
- Invoice Factoring Platform
- Features
- Cash reconciliation
Cash reconciliation
Match provider cash events to confirmed instructions and dated balances.
OverviewCash matching exceptions×
Invoice Factoring Platform · Cash reconciliation
New
Cash matching exceptions
Cash applications
| Provider event ID | Occurred at | Amount USD | State | Account | Matched instruction | |
|---|---|---|---|---|---|---|
| PEI-604 | 26 Oct | 870 | Unmatched | LA-120 | AD-28733 | |
| PEI-656 | 23 Oct | 390 | Exception | LA-110 | AD-44927 | |
| PEI-602 | 17 Oct | 100 | Unmatched | LA-150 | AD-81956 | |
| PEI-360 | 20 Oct | 240 | Exception | LA-110 | AD-87179 | |
| PEI-449 | 13 Oct | 370 | Unmatched | LA-140 | AD-90078 |
6 of 6 records
PEI-604Cash applications · CA-92205
UnmatchedOccurred at26 Oct
Amount USD870
AccountLA-120
Matched instructionAD-28733
What you can do
Reconcile what the provider recorded
The cash application identifies a provider event, its occurrence date, amount and ledger account. The Accounting Reviewer compares it with a confirmed banking instruction and the account on its journal lines. An exact amount and the occurrence date in verified provider evidence are required for a match. A different amount or date remains unmatched or becomes an exception for investigation. This keeps a nearby payment from being treated as the expected settlement merely because its amount looks familiar.
Dated account snapshots give the reviewer a second check. They show provider ledger and available balances for an account as of a particular day. Journal lines set out the debit and credit account scopes of an instruction. Together, the instruction, provider event, journal lines and snapshot let treasury trace the expected movement and the observed balance without conflating requested and confirmed money.
How the work is organized
- Event identity. Each provider movement retains its source event identifier, date, amount and account.
- Exact match. The reviewer checks the amount, date, confirmed instruction and account together before marking a cash application Matched.
- Balance check. Account snapshots and signed confirmed journal lines support a dated reconciliation; unresolved differences stay visible.
What to agree during setup
Agree how provider balance snapshots and cash events arrive, which account identifiers map to the account register and who validates that mapping. Set the close window and the time zone used to compare occurrence dates. A local request date should not be substituted for a provider confirmed date. Decide who investigates an exception and how the team records its resolution while preserving the original event identifier.
The provider may report available balance separately from ledger balance. Keep that distinction in review. If a bank correction arrives later, retain the earlier provider line and link the correction to its instruction. Reconciliation should be repeatable from source events and dated snapshots, rather than a manually adjusted total with no underlying movement.
Check the handoff on an actual case
Take a confirmed instruction with a debit and credit journal scope. Import the provider movement for its ledger account and date. The Accounting Reviewer checks the event identifier, amount, account and date on the verified provider line, then marks the cash application Matched when all conditions agree. Compare the account snapshot before and after the movement with signed confirmed journal lines and inspect any balance difference.
Try the same amount on a different date and a different amount on the same date. Neither event should be forced into a match. Place the discrepancy in the exception view with its provider event identifier intact, so the next reviewer can continue from the source evidence rather than restart the investigation.
What your team sees
- Cash matching exceptions — Unmatched movements and exceptions by account and provider event.
- Confirmed instructions — The confirmed instruction population used to trace expected effects.
- Active provider accounts — Current accounts and their external identifiers for scope checks.
Follow the work through
See cash reconciliation and provider confirmation.
What it keeps track of
Data model- Cash applications
- Source-identified provider movements matched against banking instructions.
- Account snapshots
- Dated provider balance snapshots for a financial account.
- Ledger accounts
- Provider-held financial accounts owned by a counterparty.
- Accounting documents
- Typed banking instructions moving through authorization, submission and confirmation.
- Journal lines
- Debit and credit account scopes that make an instruction balanced.
- Document lines
- Provider statements, confirmations, settlement notices and corrections for an instruction.
Who uses it
Permissions- Accounting Reviewer
- Reconciles provider events and balances.
- Accounting Preparer
- Supplies instruction context and follows operational exceptions.
- Auditor
- Reads the matched and unresolved evidence.
Set up Invoice Factoring Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.