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.
- ATM Management System
- Features
- Settlement reconciliation
Settlement reconciliation
Match provider movements and balance snapshots to confirmed instructions.
OverviewUnmatched provider movements×
ATM Management System · Settlement reconciliation
New
Unmatched provider movements
Reconciliation items
| Provider event ID | Occurred at | Amount USD | State | Account | Matched work order | |
|---|---|---|---|---|---|---|
| PEI-454 | 11 Oct | 200 | Unmatched | FA-110 | WO-75334 | |
| PEI-448 | 23 Oct | 900 | Exception | FA-130 | WO-61177 | |
| PEI-721 | 11 Oct | 480 | Unmatched | FA-150 | WO-91307 | |
| PEI-740 | 27 Oct | 480 | Exception | FA-110 | WO-64957 | |
| PEI-804 | 15 Oct | 100 | Unmatched | FA-130 | WO-19956 |
6 of 6 records
PEI-454Reconciliation items · RI-99313
UnmatchedOccurred at11 Oct
Amount USD200
AccountFA-110
Matched work orderWO-75334
What you can do
Settlement reconciliation in daily work
Match provider movements and balance snapshots to confirmed instructions. A provider sends a movement for an account after a confirmed instruction. The analyst compares the provider event identifier, amount and occurrence date with the confirmed work linked to that account. Matching the amount against a different date or account is insufficient. The item stays unmatched or is marked as an exception for investigation. The provider event ID identifies the movement and the snapshot ID identifies the dated balance. Agree how each account maps to provider records before matching movements or investigating balance differences.
How the work is organized
- Preparation. Maintenance Preparer records the assigned work and supporting context for the organization.
- Decision. Independent Maintenance Approver checks the current revision and records a decision when authority is required.
- Verification. Operations Analyst compares recorded effects with provider evidence; Auditor can inspect the retained history within assigned scope.
What to agree during setup
The dated provider snapshot gives a ledger and available balance at a specific point in time. Compare the opening ledger balance and signed confirmed movements with the closing provider balance. Preserve both snapshots and source movement IDs; a later balance refresh must not erase the evidence used for the earlier reconciliation. Agree the provider identifier that the team will use for follow-up and the evidence type that distinguishes a request from a confirmation. Set organization membership before giving anyone access to a record. Test a disabled person, another organization’s record and a stale revision. A read-only audit path should show the old decision as well as the current state.
Check the handoff on an actual case
Start with a dated provider snapshot and a source-identified movement for one financial account. Find a Confirmed instruction whose work order accounts include that same account. Compare the movement amount and occurrence date exactly with confirmed work. Mark it Matched only when all of those agree. Use a second movement with the right amount but the wrong date; leave it Unmatched or Exception.
Compare the opening provider ledger balance plus signed confirmed movements with the closing provider snapshot. Preserve both provider snapshot IDs and the movement’s event ID. An unexplained difference stays visible for the Independent Maintenance Approver to inspect; the Auditor can retrace the source entries and matching instruction.
What your team sees
- Unmatched provider movements — Unmatched and Exception movements with source event, date, amount and account.
- Provider snapshot history — Dated ledger and available balances with the provider snapshot ID for comparison.
Follow the work through
Follow the instruction cycle and use the implementation guide to rehearse it with your provider references. The data model shows the record links that carry each handoff.
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.
- Financial accounts
- Provider-held financial accounts owned by a counterparty.
- Work orders
- Typed banking instructions moving through authorization, submission and confirmation.
- Work order accounts
- Debit and credit account scopes that make an instruction balanced.
Who uses it
Permissions- Maintenance Preparer
- Prepares assigned work.
- Independent Maintenance Approver
- Decides the reviewed revision.
- Operations Analyst
- Investigates differences and verifies effects.
- Auditor
- Reads the authorized record; App Administrator maintains organization access.
Set up ATM Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.