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
- Payment execution
Payment execution
Schedule and release outbound money movement.
OverviewPayments Awaiting Bank Reconciliation×
Treasury Management · Payment execution
New
Payments Awaiting Bank Reconciliation
Payments
| Payment number | Direction | Payment date | Amount | Bank reference | Status | |
|---|---|---|---|---|---|---|
| PYM-99071 | Inbound | 05 Oct | 750 | BR-847 | Released | |
| PYM-74813 | Outbound | 08 Oct | 510 | BR-112 | Released | |
| PYM-49206 | Inbound | 02 Oct | 200 | BR-493 | Released | |
| PYM-56452 | Outbound | 05 Oct | 90 | BR-171 | Released | |
| PYM-75464 | Inbound | 13 Oct | 810 | BR-478 | Released |
6 of 6 records
BR-847Payments · PYM-99071
InboundPayment date05 Oct
Amount750
StatusReleased
What you can do
Move an approved request into the payment register
Payment execution follows an approved obligation into a scheduled payment record. Treasury Analyst records the payment date, amount, method and the request it relates to. The record can carry a counterparty and a bank reference. Its status distinguishes a scheduled instruction from a released payment and from a later bank reconciliation outcome.
How the work is organized
- Schedule with a source. Treasury Analyst relates each outbound payment to its originating request and confirms amount and method.
- Release through the action. A scheduled payment is released by the native action, which guards the status change and records an operation receipt.
- Watch the outcome. Treasury Analyst follows released and failed records through the payment register and bank follow-up queue.
What to agree during setup
Decide which treasury staff may prepare a payment and who may invoke release. Match the payment method to the actual operating channel, and agree how a bank reference is entered after an external bank response. Define who investigates a Failed payment and how the originating request is updated after a confirmed result. A payment record is the team’s operating evidence; it should be checked against the banking channel before someone treats Released as cleared cash.
Check the handoff on an actual case
Start with an approved payment request for a utilities counterparty. Create an outbound payment with the request link, payment date, amount and ACH method. Confirm that it is Scheduled. Treasury Analyst uses the release action, then checks that the payment is Released and that a Payment Release operation receipt names the result and actor. Follow the payment in the register while waiting for its bank reference and reconciliation outcome. If the bank reports a failure, record the Failed outcome and keep the original request visible for follow-up.
A second rehearsal should try to release a payment that is already Released. The action’s guard should prevent another successful release. The team should inspect the operation history to determine what happened, rather than creating another payment to make the queue look clear.
Check the approved request and its linked payment together. A matching amount and counterparty give the Controller a clear trail from obligation to internal release. If a payment is marked Failed after a bank response, Treasury Analyst retains that original record and asks AP Specialist to check the source request before another payment is scheduled.
What your team sees
- Payment Pipeline — See scheduled payments alongside released and failed items.
- Treasury Payment Register — Check the linked amount, method, date and bank reference.
- Payments Awaiting Bank Reconciliation — Find Released payments that need bank follow-up.
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.
- Payment requests
- Outbound payment requests awaiting approval and scheduling, matched to the counterparty and organization that settles them.
- Counterparties
- Counterparties treasury pays: payee master data with settlement terms, remit-to details and contact information.
- Operation receipts
- Evidence that an operation actually ran: who triggered it, when, with what result and where the output lives.
Who uses it
Permissions- Treasury Analyst
- Prepares and releases the payment record.
- Controller
- Compares the approval, release receipt and later bank evidence; AP Specialist resolves questions about the source request.
Set up Treasury Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.