Accounting Vouchers: The Professional Guide from Receipt and Payment to Journal Vouchers

An accounting voucher is the formal document that evidences a financial transaction and provides the objective basis on which the accountant records the journal entry. Without a voucher there is no entry; without an entry there are no reliable financial statements. The golden rule “No Voucher, No Entry” is not a procedural tradition; it is a legal and control pillar grounded in the International Standards on Auditing and in ZATCA regulations in the Kingdom of Saudi Arabia.

This guide examines accounting vouchers from a comprehensive professional perspective: their primary types, their legal and accounting components, their lifecycle inside an ERP, and their impact on internal control and tax compliance.

1) What is a voucher and why does it matter?

An accounting voucher is a written document (paper or electronic) that evidences a specific financial transaction, identifies the parties, the amount, the date, and the purpose, and is signed or approved by authorized individuals. The voucher is the supporting evidence in audit terminology, and it is the foundation on which a journal entry rests.

• Control dimension: proves that the transaction occurred and was authorized, protecting the organization from fraud.
• Legal dimension: the evidence presentable before judicial and regulatory authorities.
• Tax dimension: ZATCA requires supporting vouchers to be retained for at least six years.

2) Receipt voucher

A receipt voucher evidences the receipt of cash, cheque, or bank transfer—from a customer, employee, or third party. The typical accounting effect:

Types:

• Cash receipts — require strict controls and daily deposits.
• Cheque receipts — require status tracking (deposited, in clearing, cleared, bounced).
• Bank transfers — reconciled directly with bank statements.
• Electronic receipts — POS, digital wallets, payment gateways.

A proper voucher carries a unique sequential number, the recipient and payer signatures, and proper allocation of the amount against outstanding invoices. Poor allocation distorts customer accounts and corrupts aging reports.

3) Payment voucher

A payment voucher evidences cash outflow to an external or internal party. Typical effect:

Types:

• Supplier payments — must follow three-way match with PO and GRN.
• Direct expense payments (rent, utilities, transportation).
• Employee advances — require subsequent settlement.
• Payroll payments via WPS.
• Tax remittances — VAT, Zakat, withholding tax to ZATCA.

A professional payment voucher requires an original supporting document, multi-tier approvals by amount, budget availability verification, and—for purchase invoices—Fatoora platform UUID validation.

4) Journal voucher

A journal voucher records transactions without direct cash movement: adjustments, depreciation, provisions, corrections, and reclassifications. It is the documentary counterpart of a manual journal entry.

Required attachments depend on its nature: depreciation schedule, inventory valuation report, provision calculation memo, or CFO approval for a reclassification. Without proper attachment, the voucher loses credibility before the auditor.

5) Other supporting vouchers

• Goods Receipt Note (GRN) — evidence of goods received before approving the supplier invoice.
• Issue voucher — evidence of stock leaving the warehouse.
• Transfer voucher — movement of value between branches or cost centers.
• Debit / Credit note — adjusts the value of a previously issued invoice.
• Adjustment voucher — records stock-count variances or reconciliation differences.

6) Mandatory components

• Unique sequential number generated by the system.
• Voucher date and transaction date (may differ).
• Parties: name and commercial registration of the recipient/payer.
• Amount in figures and words, with currency.
• Purpose / narration linking to invoices or contracts.
• Identities and signatures of preparer, reviewer, approver.
• Supporting attachments (invoice, contract, approval, report).
• Affected accounts and analytical dimensions (cost center, project).

7) Voucher lifecycle in ERP

1. Request — payment or receipt request from the requesting party.
2. Preparation — voucher created with data and attachments.
3. Review — completeness and account accuracy checked.
4. Approval — tiered workflow by amount and type.
5. Execution — actual payment or receipt processed.
6. Posting — linked journal entry generated automatically.
7. Archiving — voucher digitally retained with all supporting files.

8) Tax and legal compliance

Under Saudi VAT regulations, all supporting documents must be retained for at least six years from the end of the relevant tax period, extending to eleven years for vouchers related to real estate. E-invoicing rules additionally require that payment vouchers for purchase invoices link to valid e-invoices issued through the Fatoora platform.

Legally, a signed and approved voucher constitutes conclusive evidence before commercial courts; its absence may forfeit the right to claim outstanding balances or saddle the company with unjustified obligations.

9) Voucher governance

• System-controlled sequential numbering with no human interference.
• Segregation of duties between preparer, approver, and executor.
• Authority matrix by value.
• Mandatory attachments before save.
• Budget availability check before payment.
• Complete audit log of every modification or cancellation.
• Internal audit sampling reviews monthly.

10) Segregation of duties in the voucher cycle

Effective internal control is not achieved by writing policies on paper but by configuring an RBAC system inside ERP that technically prevents any one person from controlling the full cycle:

11) Worked examples

a) Supplier payment with three-way match

Procurement requests payment of a supplier invoice for SAR 57,500 (50,000 + 7,500 VAT):

1. Verify an approved purchase order (PO).
2. Verify matching goods receipt note (GRN).
3. Verify e-invoice and UUID on the Fatoora platform.
4. Match quantities, prices, and VAT terms (3-way match).
5. Generate the payment voucher linked to all three documents.
6. Tiered approval (procurement manager + CFO).
7. Execute bank transfer and lock the voucher as Paid.

b) Partial customer receipt with allocation

A customer has four outstanding invoices totaling SAR 80,000 and remits SAR 30,000 by bank transfer:

1. Receive bank deposit confirmation.
2. Create receipt voucher for SAR 30,000.
3. Allocate against invoices per the customer’s written instruction (default FIFO).
4. Track remaining balance per invoice in the customer subledger.

c) Credit note for a volume rebate

Granting a customer a 3% volume rebate on quarterly sales of SAR 200,000 (SAR 6,000 + 900 VAT):

12) Vouchers in the e-invoicing era (Phase 2)

• Direct integration with Fatoora: every e-invoice and credit/debit note must be transmitted to ZATCA in real time to receive a cryptographic stamp and UUID.
• Payment voucher for a rejected invoice: blocked by the system until the supplier corrects it.
• Digital archiving in approved XML for retrieval during any tax audit.
• Certified electronic signature on every tax voucher, verified through a trusted certificate.
• Linking voucher number to the paid invoice number for seamless ZATCA matching.

Key performance indicators

FAQ