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.
- Fund Accounting
- Features
- Payments and cash
Payments and cash
Release scheduled payments and examine cash evidence before reconciliation.
OverviewPayments Awaiting Reconciliation×
Fund Accounting · Payments and cash
New
Payments Awaiting Reconciliation
Payments
| Payment number | Payment date | Amount | Bank reference | Accounting document | Invoice | |
|---|---|---|---|---|---|---|
| PYM-97699 | 11 Oct | 450 | BR-613 | AD-64138 | INV-23489 | |
| PYM-49238 | 10 Oct | 830 | BR-733 | AD-12792 | INV-14225 | |
| PYM-11054 | 03 Oct | 730 | BR-198 | AD-78937 | INV-33575 | |
| PYM-47546 | 04 Oct | 520 | BR-649 | AD-81127 | INV-75020 | |
| PYM-86635 | 01 Oct | 70 | BR-172 | AD-46350 | INV-90028 |
6 of 6 records
BR-613Payments · PYM-97699
ReleasedPayment date11 Oct
Amount450
Accounting documentAD-64138
InvoiceINV-23489
What you can do
Follow money movement from schedule to evidence
A payment record identifies its direction, amount, date, method and status. It can link to a business partner or donor and to the accounting document or invoice that explains why money moved. Treasury Analyst uses that link to distinguish an outbound partner payment from an inbound donor collection. The bank reference helps the team compare the internal payment with an external bank outcome.
The native payment release action applies to a scheduled payment. It guards the transition, records an operation receipt and marks the payment Released. The finance team can then compare the external result and change the payment to Reconciled through its operating review. A released payment tells the team the action ran; reconciliation answers whether the money movement can be matched to supporting evidence.
How the work is organized
- Payment pipeline. Scheduled, released, reconciled and failed items stay visible by status and direction.
- Money evidence. Bank references and operation results help Treasury investigate an expected transfer.
- Receipt matching. Verified cash receipts and their applications retain receipt amounts, dates and links to accounting documents.
What to agree during setup
Define who can schedule a payment, who can run the release action and what independent review is required under the organization’s policy. Agree which payment methods the team actually uses and how bank references arrive. A payment may be linked to a partner bill or donor invoice; make that connection before release so the eventual reconciliation has a source to inspect.
For receipts, decide how the provider event ID is kept unique during import and how staff verify the cash amount. The receipt application record links a verified receipt to an accounting document and records the applied amount and time. A reversal date lets staff identify corrected applications without erasing the original. Reconcile the source receipt, its applications and the remaining document balance together.
Check the handoff on an actual case
Use an approved bill with a scheduled outbound payment. Treasury Analyst checks the linked document, amount and method, then uses the release action. Inspect the operation result and the new Released status. Compare the bank reference on the payment with external evidence and mark it reconciled only after the match is checked. If release fails, inspect the operation result and current payment status before investigating; the failed action is not a settlement.
For an inbound case, follow the donor invoice, its payment record and the expected amount received. Review the balance after a partial collection. For an imported cash receipt, compare the provider event ID and amount with the receipt applications. This keeps a bank event, a payment record and a receivable or payable from being mistaken for the same evidence.
What your team sees
- Treasury Payment Register — Dated payments with direction, method, amount and bank reference.
- Payments Awaiting Reconciliation — Released items awaiting the final cash check.
- Payment Pipeline — A board for scheduled, released, reconciled and failed work.
Follow the work through
Follow payment release to reconciliation and donor collection.
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.
- Accounting documents
- Payables header for a fund: a business partner invoice received, approved and scheduled for payment out of fund cash.
- Invoices
- Contributions receivable header: a donor invoice issued, sent and collected into the fund.
- Cash receipts
- Verified cash receipts imported from the provider, used to reconcile fund cash.
- Cash applications
- Applications of verified cash receipts against posted accounting documents.
- Business partners
- Supplier master: who we owe money to, on what payment terms and in what lifecycle state.
- Donors
- 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.
Who uses it
Permissions- Treasury Analyst
- Schedules, releases and reconciles payments.
- Controller
- Reviews exceptions.
- AP Specialist
- And AR Specialist follow the linked bill or invoice.
- External Auditor
- Examines the recorded operation and source.
Set up Fund Accounting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.