1. Accounting with GST/Tax
  2. Features
  3. Payments and reconciliation
Feature · Payments and reconciliation

Payments and reconciliation

Follow scheduled payments through release and compare the recorded movement with bank evidence.

OverviewPurchase Bills Settled
Accounting with GST/Tax · Payments and reconciliation

Purchase Bills Settled

Purchase bills

New
Bill numberVendorOrganizationInvoice dateTotal amountAmount paid
PB-85105VND-064ORG-5202004 Oct620200
PB-24611VND-219ORG-3827007 Oct710140
PB-87537VND-093ORG-9740703 Oct630770
PB-45185VND-023ORG-4361303 Oct240760
PB-77734VND-114ORG-5018713 Oct330110
6 of 6 records
BD-800Purchase bills · PB-85105
Paid
VendorVND-064
OrganizationORG-52020
Invoice date04 Oct
Total amount620
Amount paid200
Example screen with sample data

What you can do

Know which payment stage the team has reached

Treasury Analyst works from a payment record with a direction, amount, date and method. The linked bill or invoice explains why the money is moving. Scheduled, Released, Reconciled and Failed distinguish the stages that require attention. The bank reference and supporting evidence help the team explain whether a released payment has reached the expected outcome.

Payment release is an operating action with its own receipt. A successful action moves a scheduled payment to Released. The reconciliation review then compares that record with the bank’s evidence. Keep the distinction clear when a supplier asks whether a payment has arrived or when AR Specialist is deciding which customer invoice to update.

How the work is organized

  • Prepare the movement. Select the correct direction and counterparty, then link the payment to the intended bill or invoice. Check the amount and date against the document’s current balance.
  • Release within authority. Treasury Analyst uses the payment release action within the customer’s agreed access policy. Inspect the operation outcome before moving to the next task.
  • Reconcile the evidence. Match the released movement to the bank reference and retain the supporting statement or remittance evidence. Resolve failed or unmatched items before treating the source document as settled.

What to agree during setup

Controller and Treasury Analyst agree who may prepare and release payments. Set the review process for a change of amount or destination before the release action is used. Check the selected methods against the bank procedures the business actually operates. A method name on a record should lead the operator to the appropriate agreed bank process.

Define the owner of bank evidence and the way it reaches the team. Bank feeds or payment provider connections are connections to configure. Agree how partial payments update the linked document and who verifies the remaining amount. Retain a failed release receipt so that a later successful attempt does not conceal the original problem or encourage a duplicate instruction.

Check the handoff on an actual case

A vendor bill has an approved outstanding amount of 800. Treasury Analyst prepares an outbound payment for 500 and links it to that bill. After the release action completes, the record becomes Released and carries an operation receipt. The bill still requires a balance check; the release alone is insufficient evidence that the vendor received the money.

When bank evidence confirms the movement, Treasury Analyst records the reference and completes the reconciliation review. AP Specialist checks the amount paid against the bill and retains the remaining 300 for later payment. Rehearse an unmatched bank reference as well. Leave that case visible for investigation until the team can identify the destination and source obligation reliably.

What your team sees

  • Treasury Payment Register — Compare payment dates, amounts and bank references with the linked bill or invoice.
  • Payment Pipeline — Separate scheduled work from released, reconciled and failed movements.
  • Payments Awaiting Reconciliation — Follow released payments that still need a bank evidence review.

Follow the work through

Use payment release to reconciliation and carry unresolved items into the tax period review. Agree the evidence handoff in implementation.

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.
Purchase bills
Accounts payable header: a vendor invoice received, approved and scheduled for payment.
Tax invoices
Accounts receivable header: a customer invoice issued, sent and collected.
Vendors
Supplier master: who we owe money to, on what payment terms and in what lifecycle state.
Customers
Customer master: who owes us money, on what invoice terms and in what lifecycle state.
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.
Review decisions
Approval trail: who approved, rejected or returned a bill, invoice, payment or journal entry, when and under what conditions.

Who uses it

Permissions
Treasury Analyst
, AP Specialist, AR Specialist, Controller, External Auditor, Admin.
Treasury Analyst
Owns the payment evidence.
AP Specialist
And AR Specialist check the affected document balance within their responsibilities.

Set up Accounting with GST/Tax your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started