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.
- Treasury Management
- Features
- Bank reconciliation
Bank reconciliation
Follow released payments to a recorded bank outcome.
OverviewPayment Requests Past Due×
Treasury Management · Bank reconciliation
New
Payment Requests Past Due
Payment requests
| Payment request number | Counterparty | Due date | Balance due | Status | |
|---|---|---|---|---|---|
| PR-77307 | CNT-45244 | 05 Oct | BD-620 | Draft | |
| PR-93697 | CNT-37365 | 06 Oct | BD-425 | Pending Approval | |
| PR-27632 | CNT-51597 | 04 Oct | BD-807 | Approved | |
| PR-70612 | CNT-32977 | 11 Oct | BD-546 | Scheduled | |
| PR-64922 | CNT-22463 | 05 Oct | BD-875 | Paid |
6 of 6 records
BD-620Payment requests · PR-77307
DraftCounterpartyCNT-45244
Due date05 Oct
What you can do
Compare a payment with bank evidence
Bank follow-up begins after a payment has a release result. The payment register shows its direction, date, amount, method, status and bank reference. Treasury Analyst uses those details to compare the internal record with the bank’s outcome. A Reconciled status is the final recorded match; a Failed status sends the payment back for investigation.
How the work is organized
- Collect released items. The waiting list focuses attention on payments whose status is Released.
- Compare the bank result. Treasury Analyst checks direction, amount and reference against the statement or other bank evidence.
- Record the outcome. The team captures the reference and resulting status, then keeps supporting material with the record.
What to agree during setup
Choose the banking source the team will use for each payment method and decide who enters a bank reference. Define how often released items are checked and who resolves a mismatch. A bank statement can be retained as record attachments evidence. Agree how treasury distinguishes a bank rejection from an internal release failure and how it informs AP Specialist or AR Specialist when an originating obligation or invoice needs correction.
Check the handoff on an actual case
Take a released outbound payment whose request link and amount are known. Compare it with a bank entry of the same amount and direction. Record the bank reference and confirm the payment as Reconciled when the match has been reviewed. Preserve the supporting statement in the attachment record. Controller can inspect the payment, its request and the release receipt to see both the internal action and the later bank outcome.
Now rehearse a bank rejection. Keep the payment visible as Failed, retain the bank reference and explain the result in the payment memo. The team should examine the original request before deciding whether to schedule a replacement. A status change alone should never be used to erase the release receipt or the bank’s reported failure.
For an inbound payment, start from its invoice link; for an outbound payment, start from its payment request. Those links let Treasury Analyst investigate a difference without guessing which obligation the bank entry belongs to. Record the bank reference on the payment and keep the statement attachment tied to the right parent record, then show Controller the unresolved item.
What your team sees
- Payments Awaiting Bank Reconciliation — Find Released payments that need a comparison with bank evidence.
- Treasury Payment Register — Check payment direction, amount, method, reference and recorded outcome.
- Payment Pipeline — See Scheduled, Released, Reconciled and Failed payments by status.
Follow the work through
See the related process for the operating sequence. Use the data model to map source identifiers before import and implementation to rehearse the handoff with your team.
What it keeps track of
Data model- Payments
- Money movement in and out of the business, matched to a bill or invoice and reconciled to the bank.
- Operation receipts
- Evidence that an operation actually ran: who triggered it, when, with what result and where the output lives.
- Record attachments
- Parent-agnostic evidence files attached to any business record in this app.
- Payment requests
- Outbound payment requests awaiting approval and scheduling, matched to the counterparty and organization that settles them.
- Receivable invoices
- Incoming receivable invoices issued to a remitter, tracked from issue through collection.
Who uses it
Permissions- Treasury Analyst
- Compares the payment with bank evidence and records the outcome.
- Controller
- Reviews failed matches and the related request or invoice.
Set up Treasury Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.