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
- Accounting documents
Accounting documents
Review coded partner bills and carry approved balances toward payment.
OverviewOverdue Accounting Documents×
Fund Accounting · Accounting documents
New
Overdue Accounting Documents
Accounting documents
| Record number | Counterparty | Due date | Gross amount USD | Amount paid | Status | |
|---|---|---|---|---|---|---|
| AD-77914 | BP-8694 | 06 Oct | 560 | 870 | Draft | |
| AD-50183 | BP-2727 | 12 Oct | 20 | 430 | Pending Approval | |
| AD-94738 | BP-2294 | 04 Oct | 710 | 220 | Approved | |
| AD-58971 | BP-2093 | 11 Oct | 860 | 250 | Scheduled | |
| AD-36888 | BP-6850 | 08 Oct | 60 | 150 | Paid |
6 of 6 records
BP-8694Accounting documents · AD-77914
DraftDue date06 Oct
Gross amount USD560
Amount paid870
What you can do
Put each partner bill in a reviewable state
An accounting document is the payable that the finance team can review, approve, schedule and settle. It belongs to a business partner and an organization. Its dates, gross amount, amount paid and status give AP Specialist and Treasury a common record while they carry out different jobs. Coded document lines point to ledger accounts; attachments keep the invoice and supporting papers near the decision.
The Accounting Documents Control Desk brings documents still needing a decision into a ranked queue. Stage segments, organization and status filters let a reviewer narrow the work, then open the native document record. The desk is especially useful when several partner bills are nearing their due dates but only some are ready for approval. The Controller should reach the source bill and its lines before deciding.
How the work is organized
- Intake. AP Specialist records the counterparty reference, document date, due date, amounts and organization.
- Coding. Each document line carries its description, quantity, price, tax code and ledger account.
- Decision. The native approval action moves an eligible document to Approved and records a review decision and operation result.
What to agree during setup
Agree which partner information must be checked before a bill enters review. Partner payment terms and lifecycle state are visible on the master record, while the bill has its own due date and amount. Agree who can edit the coded lines after a review begins, and how the team handles a disputed bill. The statuses distinguish draft, pending approval, approved, scheduled, paid and disputed work; define an owner for each queue.
A controller and AP Specialist should also decide what evidence is required for different spend categories. An invoice PDF may be enough for a routine utility bill; a contract or purchase order may matter for a larger service bill. The attachment record holds the evidence type and uploader. The approval decision holds the reviewer, reason and conditions. These records should tell the same story.
Check the handoff on an actual case
Use a partner bill with several coded lines. The AP Specialist checks that the line total agrees with the document amount and links the right organization. If the expense relates to a restricted fund, the Controller examines the fund decision before the bill decision. Move the bill into the review queue. The Controller opens the native document, checks the source file and lines, then approves it through the document action. Verify that the decision and operation result point back to the same bill.
The Treasury Analyst can then create a scheduled payment linked to that accounting document. AP Specialist should continue to see the bill and amount paid, while Treasury Analyst follows release and reconciliation on the payment. If the bill remains disputed, its status should make that clear in the board and the overdue list.
What your team sees
- AP Bills Worklist — Draft and progressing bills with due dates and amounts for daily AP work.
- Accounting Documents Awaiting Review — Bills waiting for the Controller’s decision.
- Bills by Status — A board for the payable stages, including disputed work.
Follow the work through
See bill review to payment and payment release.
What it keeps track of
Data model- Accounting documents
- Payables header for a fund: a business partner invoice received, approved and scheduled for payment out of fund cash.
- Document lines
- Coded expense and asset lines that make up a vendor bill.
- Business partners
- Supplier master: who we owe money to, on what payment terms and in what lifecycle state.
- Ledger accounts
- Chart of accounts: the coded account structure every bill line, invoice line and journal line posts into.
- Fund restrictions
- Restricted-fund extension records supporting approval of an eligible restricted-fund posting.
- 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.
- Operation receipts
- Evidence that an operation actually ran: who triggered it, when, with what result and where the output lives.
Who uses it
Permissions- AP Specialist
- Prepares bills and coded lines.
- Controller
- Owns the approval decision.
- Treasury Analyst
- Uses approved bills for payment planning.
- External Auditor
- Follows the source and decision trail.
Set up Fund Accounting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.