What Is a Payment Voucher? Format, Example, and AP Flow

A payment voucher is an internal accounting record that brings together the payee, amount, account coding, supporting documents, and approval for a disbursement. It may be created before money leaves the business, then updated afterward with a cheque number, bank-transfer reference, payment date, and paid status.

In accounts payable, the voucher does not replace the supplier invoice or the evidence that goods or services were received. It organizes those records into a traceable basis for checking, authorizing, recording, and later verifying the payment.

The terminology is not universal. Payment voucher, accounts payable voucher, and disbursement voucher frequently describe the same internal record. In one organization, the voucher is a form attached to the supporting documents; in another, it means the entire supporting packet; in an accounting system, it may exist only as an electronic transaction record.

Context matters because the term has other meanings. A tax authority may call a remittance slip a payment voucher, while a retailer may issue a gift or service voucher to a customer. Those documents are not the internal AP record described here.

How a payment voucher moves through the AP lifecycle

A voucher changes as the payment moves through the accounts payable process. Its sequence usually looks like this:

1. Source documents arrive. AP receives the supplier invoice or expense claim. A purchase order, contract, goods receipt, service confirmation, or other evidence may support the amount and business purpose.

2. The voucher is prepared and coded. An AP clerk or bookkeeper records the payee, amount, source references, general-ledger account, cost centre, and proposed payment method. The voucher is still a payment request at this point, not proof that funds have moved.

3. The record is checked. A reviewer confirms that the payee and amount agree with the source documents, the coding is appropriate, required evidence is attached, and the same obligation has not already been paid.

4. An authorized person approves release. Approval records who accepted the payment and when. Depending on the organization's size and risk, preparation, checking, and approval may belong to separate people or be combined under compensating review controls.

5. Payment details are added. After a bank transfer, cheque, card payment, or other disbursement is released, the record receives its payment date and transaction reference. Its status moves from approved to paid.

6. The voucher is closed and retained. AP reconciles the payment to the bank or cash record, resolves exceptions, and keeps the voucher with its linked evidence according to the organization's retention policy.

A voucher system in accounting is the controlled method behind this sequence. It creates a traceable route from the original liability or claim to approval and settlement. The voucher may be paper, electronic, or a combination of both; its function depends on the evidence and state history it preserves, not its physical format.

---

A practical payment voucher format and field schema

A useful payment voucher format makes four things traceable: what is being paid, why it is payable, who authorized it, and whether payment was completed. The field names below can be copied into spreadsheet columns or adapted to a paper or system form.

Field	Purpose	Typical control treatment
Voucher number	Gives the record a unique identifier	Usually core
Voucher date	Shows when the record was created	Usually core
Payee name and ID	Identifies the supplier, employee, or other recipient	Usually core
Source document type	Identifies an invoice, expense claim, refund request, or other basis	Usually core
Source document reference	Links the voucher to an invoice number or claim ID	Usually core
Description or payment purpose	Explains the obligation in business terms	Usually core
Amount and currency	States the value proposed for payment	Usually core
GL account	Records the general-ledger classification	Usually core
Cost centre, project, or department	Assigns responsibility or reporting ownership	Varies by organization
Prepared by and date	Identifies who assembled and coded the record	Usually core
Checked by and date	Records the independent check where the workflow requires one	Varies by control design
Approved by and date	Records authorization under the applicable approval limit	Usually core
Status	Distinguishes draft, checked, approved, paid, voided, and closed records	Usually core
Supporting attachments	Points to the invoice, purchase evidence, receipt, or other support	Usually core
Payment method	Identifies transfer, cheque, card, cash, or another channel	Varies by payment method
Payment reference	Links the voucher to the bank transaction, cheque, or payment run	Usually core after payment
Payment or close date	Shows when the disbursement occurred or the record was closed	Usually core after payment

Some fields exist only in particular settings. A cash-payment form might include recipient acknowledgement; a tax payment may need a taxpayer or assessment reference; a project business may require job codes; and a regulated entity may record a retention category. Bank account details should appear only where operationally necessary and should be protected by appropriate access controls.

The timing of field completion is part of the format. Source references, amount, coding, and approval evidence should be available before release. A bank reference or cheque number cannot be completed until the payment is created, and the closed status should follow reconciliation or the organization's final review step. A template that treats every field as complete at preparation obscures that lifecycle.

Payment voucher example from invoice to closed record

Suppose Northwind Office Services sends invoice INV-8472 for USD 2,480 of printer maintenance. The buyer's records include purchase order PO-1936 and a service confirmation dated August 4, 2026. AP creates voucher PV-2026-0418 on August 6.

State	Information added or checked	What the record proves at that point
Prepared	Payee: Northwind Office Services; invoice: INV-8472; PO: PO-1936; amount: USD 2,480; GL account: Repairs and maintenance; cost centre: Operations	AP has identified the proposed payment, its source, and its accounting destination
Checked	Invoice agrees with the PO and service confirmation; supplier and duplicate checks completed by the AP reviewer on August 7	The payment packet has passed the required documentary checks
Approved	Finance manager approval recorded on August 8 within the manager's authority	An authorized person has released the disbursement for processing
Paid	Bank transfer reference TRX-625190 added on August 9	Funds were sent through the stated payment channel
Closed	Voucher marked closed after the bank transaction was reconciled on August 12	The payment and accounting record have been tied back to settlement evidence

Each document has a different job. The supplier invoice states the amount claimed. The purchase order and service confirmation support why the buyer accepts that claim. The voucher records coding, checks, and authorization. The bank reference shows that the approved payment was executed.

The journal entry depends on when the organization recognized the liability. If the invoice was posted earlier, settlement commonly debits accounts payable and credits cash or bank. If the expense is recognized only when payment is recorded, the debit may instead go directly to the relevant expense or asset account. The voucher supports the entry but does not determine one universal debit-and-credit treatment.

---

Payment voucher vs invoice, receipt voucher, and related documents

Documents in the same transaction chain are not interchangeable. The clearest way to distinguish them is to ask who creates the record, when it exists, and what it proves.

Document	Usual creator	Timing	What it proves or communicates
Payment or AP voucher	The paying organization's AP or finance team	Prepared before payment, then updated through settlement and closure	Internal coding, review, authorization, and the traceable payment record
Supplier invoice	The supplier	After supplying goods or services, according to the commercial arrangement	The supplier's request for payment and transaction details
Purchase order	The buyer	Before purchase or delivery	The buyer's authorized order and agreed terms
Receiving or service evidence	The buyer's receiving team or service owner	When goods arrive or services are accepted	What the buyer received or accepted
Proof-of-payment receipt	The recipient or payment provider	At or after payment	That money was received or the transaction was executed
Remittance advice	The payer	With or after payment	Which invoices, credit notes, or balances the payment is intended to settle
Receipt voucher	The receiving organization's finance team	When money comes in	Internal evidence of a cash or bank receipt
Tax payment voucher	A tax authority or taxpayer using its prescribed form	When remitting a tax amount	The taxpayer, period, tax type, and amount accompanying or identifying the remittance
Gift or service voucher	A retailer or service provider	Before redemption	A customer's right to goods, services, or stored value

In a payment voucher vs invoice comparison, direction and ownership are decisive. The supplier creates the invoice to state what the customer owes. The customer creates the payment voucher to organize its internal basis for approving and recording settlement of that obligation.

For payment voucher vs receipt voucher, the usual distinction is cash flow direction: a payment voucher records money going out, while a receipt voucher records money coming in. An organization's own chart of forms may use different labels, so the fields and workflow are more reliable identifiers than the title alone.

A proof-of-payment receipt confirms execution or receipt of funds, but it does not show the payer's full internal approval trail. Similarly, remittance advice helps the supplier apply a payment to the correct invoices; it is not the payer's authorization record. A tax payment voucher belongs to a prescribed remittance process, not to the supplier-payment workflow, even though it shares the name.

Controls that make a voucher record useful

A voucher is useful control evidence only when its links remain intact. The source invoice or claim, accounting classification, review history, approval, payment reference, status, and later corrections should be preserved as one record or as a reliably linked packet. A voucher number on an isolated form proves little by itself.

Control design should match the organization's size, payment risk, and systems. Common measures include checking for duplicate invoice and voucher references, separating preparation from approval where proportionate, enforcing approval limits, restricting changes after approval, and recording any void or reissue without erasing the history. Reconciliation connects the paid voucher to the bank or cash record, while retention keeps the evidence available for later review.

Official procedures provide concrete illustrations. NASA's payment voucher requirements state that vouchers and supporting documents must be marked electronically or manually to prevent duplicate payment processing, and that payment records must carry accounting classification references. These are requirements for NASA's process, not universal private-sector rules, but they show why duplicate controls and coding belong inside the voucher record rather than in informal side notes.

An accounts payable control framework places those checks alongside supplier validation, access controls, approval authority, payment security, and monitoring. A voucher supports that framework by preserving evidence; it does not eliminate fraud, guarantee that a payment is correct, or create a measurable reduction in errors on its own.