Skip to main content

Understanding Vouchers

For: Business Users, Managers, Clients
Purpose: Explain what vouchers are and why they're essential for accounting
Reading Time: 6 minutes

What is a Voucher?​

A voucher is a unique reference number assigned to a group of related accounting entries. Think of it as a "transaction ID" that ties together all the debits and credits that make up a single business transaction.

Real-World Analogy​

Imagine you're buying groceries:

Your Receipt Shows:

  • Receipt Number: 12345
  • Item 1: Milk ($4)
  • Item 2: Bread ($3)
  • Item 3: Eggs ($5)
  • Total: $12

The receipt number (12345) groups all your purchases together. If you need to return the milk, you reference receipt 12345.

In accounting, a voucher works the same way:

  • Voucher Number: V-2025-0042
  • Debit: Cash $1,000
  • Credit: Revenue $1,000
  • Balanced Transaction

If you need to reverse this entry, you reference voucher V-2025-0042.

Why Do Vouchers Matter?​

Single Transaction, Multiple Lines:

Without Vouchers:

Entry 1: Debit Cash $1,000
Entry 2: Credit Revenue $800
Entry 3: Credit Sales Tax $200

Question: Which entries belong together?
Answer: Unclear! You have to guess.

With Vouchers:

Voucher V-001:
  Entry 1: Debit Cash $1,000
  Entry 2: Credit Revenue $800
  Entry 3: Credit Sales Tax $200

Question: Which entries belong together?
Answer: Clear! All entries with voucher V-001.

2. Enable Easy Reversals​

Business Scenario: You record a sale on Monday:

Voucher V-001:
  Debit: Accounts Receivable $5,000
  Credit: Revenue $5,000

On Tuesday, customer cancels the order. You need to reverse it:

Voucher V-002 (Reverses V-001):
  Debit: Revenue $5,000
  Credit: Accounts Receivable $5,000

The voucher makes it clear:

  • V-002 reverses V-001
  • Both transactions are linked
  • Complete audit trail maintained

3. Maintain Audit Trail​

Auditor Questions:

  • "Show me the journal entry for invoice SI-2025-0042"
  • "What voucher was used?"
  • "Has this been reversed?"
  • "When was it posted?"

With proper voucher numbering, you can answer instantly:

  • Voucher: V-2025-0042
  • Posted: January 15, 2025
  • Reversed: No
  • Related Document: Invoice SI-2025-0042

4. Ensure Transaction Balance​

A fundamental accounting rule: Every voucher must balance.

Debits = Credits

Valid Voucher (Balanced):

Voucher V-001:
  Debit: Cash $1,000
  Credit: Revenue $1,000
  Balance: $0 ✓ (Balanced)

Invalid Voucher (Unbalanced):

Voucher V-001:
  Debit: Cash $1,000
  Credit: Revenue $800
  Balance: $200 ✗ (Unbalanced - System rejects!)

The system uses vouchers to enforce this rule - you cannot post an unbalanced voucher.

Voucher Numbering Strategies​

Your ERP system can generate voucher numbers in three different ways, depending on your business needs.

Strategy 1: In Connection with Balance​

How it works:

  • System generates a new voucher when entries balance
  • Unbalanced entries reuse the last voucher
  • Multiple balanced sets = multiple vouchers

Example: Daily General Journal

User enters Entry 1: Debit Cash $1,000
  → System: Unbalanced, generates Voucher V-001
  → Debit total: $1,000 | Credit total: $0

User enters Entry 2: Credit Revenue $1,000
  → System: Now balanced, KEEPS Voucher V-001
  → Debit total: $1,000 | Credit total: $1,000 ✓

User enters Entry 3: Debit Expense $500
  → System: Unbalanced again, generates NEW Voucher V-002
  → Debit total: $500 | Credit total: $0

User enters Entry 4: Credit Cash $500
  → System: Balanced, KEEPS Voucher V-002
  → Debit total: $500 | Credit total: $500 ✓

Final Result:

  • Voucher V-001: Cash + Revenue (balanced)
  • Voucher V-002: Expense + Cash (balanced)

Best For:

  • Daily adjusting entries
  • Multiple small transactions
  • General purpose journals

Business Benefit: Each balanced transaction gets its own voucher, making it easy to reverse individual transactions.

Strategy 2: One Voucher Number Only​

How it works:

  • Entire journal batch gets ONE voucher number
  • All entries, regardless of how many, share this voucher
  • Used when the whole batch represents one logical transaction

Example: Opening Balances

Voucher OB-2025-001:
  Entry 1: Debit Asset Account 1 $10,000
  Entry 2: Debit Asset Account 2 $5,000
  Entry 3: Debit Asset Account 3 $8,000
  Entry 4: Credit Equity Account $23,000

Total Debit: $23,000 | Total Credit: $23,000 ✓
All 4 entries share Voucher OB-2025-001

Example: Monthly Payroll

Voucher PAY-JAN-2025:
  Entry 1: Debit Salary Expense - Employee A $5,000
  Entry 2: Debit Salary Expense - Employee B $4,500
  Entry 3: Debit Salary Expense - Employee C $6,000
  ...
  Entry 50: Credit Payroll Clearing Account $155,500

Total Debit: $155,500 | Total Credit: $155,500 ✓
All 50 entries share Voucher PAY-JAN-2025

Best For:

  • Opening balances (migration from old system)
  • Payroll batches (entire month is one transaction)
  • Batch imports
  • Consolidated entries

Business Benefit:

  • Easy to reverse the entire batch with one command
  • Clearly shows that all entries are part of one logical transaction
  • Simplifies auditing of batch operations

Strategy 3: Manual Entry​

How it works:

  • System does NOT generate voucher numbers
  • User must type the voucher number manually
  • Full control but more work

Example: Data Migration

When importing data from an old system where vouchers already exist:

Old System Voucher: OldSys-4532
User manually enters: OldSys-4532
System accepts manual entry

Best For:

  • Data migration from legacy systems
  • Matching external voucher numbers
  • Special cases requiring specific numbering

Business Benefit: Maintains continuity when moving from another system.

Drawback: More prone to errors (typos, duplicates if user not careful).

How Vouchers Work in Different Scenarios​

Scenario 1: Recording a Sale​

Business Transaction: Customer purchases goods for $1,000 on credit.

Accounting Entry (Voucher V-001):

Voucher: V-001
Date: January 15, 2025
Reference: Invoice SI-2025-0042

  Debit: Accounts Receivable $1,000
  Credit: Sales Revenue $1,000

Total Debit: $1,000 | Total Credit: $1,000 ✓ Balanced

Key Points:

  • Single voucher groups both entries
  • Voucher references the source invoice
  • Easy to find later: "Show me voucher for invoice SI-2025-0042"

Scenario 2: Recording a Complex Sale with Tax​

Business Transaction: Customer purchases goods for $1,000 plus $200 sales tax, pays cash.

Accounting Entry (Voucher V-002):

Voucher: V-002
Date: January 16, 2025
Reference: Invoice SI-2025-0043

  Debit: Cash $1,200
  Credit: Sales Revenue $1,000
  Credit: Sales Tax Payable $200

Total Debit: $1,200 | Total Credit: $1,200 ✓ Balanced

Key Points:

  • One voucher for three accounting lines
  • All entries tied to the same business transaction
  • Clear tax tracking for reporting

Scenario 3: Reversing an Entry​

Original Transaction (Monday):

Voucher: V-050
Date: January 20, 2025
Reference: Accrued Expense - Rent

  Debit: Rent Expense $2,000
  Credit: Accrued Expenses $2,000

Reversal (Tuesday - realized error):

Voucher: V-051
Date: January 21, 2025
Reference: Reversal of V-050

  Debit: Accrued Expenses $2,000
  Credit: Rent Expense $2,000

Reversal Link: Original Voucher V-050

Key Points:

  • Reversal voucher mirrors original (debits become credits, credits become debits)
  • Clear link between original and reversal
  • Both vouchers remain in system (audit trail preserved)
  • Net effect after reversal: zero impact

Scenario 4: Payment to Vendor​

Business Transaction: Pay vendor for three separate invoices totaling $5,000.

Accounting Entry (Voucher V-075):

Voucher: V-075
Date: January 25, 2025
Reference: Check #12345 - Vendor ABC

  Debit: Accounts Payable - Invoice PI-001 $2,000
  Debit: Accounts Payable - Invoice PI-002 $1,500
  Debit: Accounts Payable - Invoice PI-003 $1,500
  Credit: Bank - Main Account $5,000

Total Debit: $5,000 | Total Credit: $5,000 ✓ Balanced

Key Points:

  • One payment (one check) = one voucher
  • Multiple invoice payoffs grouped together
  • Clear reference to payment method (check number)
  • Bank reconciliation made easier

Voucher Lifecycle​

Stage 1: Creation​

When: User enters accounting transactions

What Happens:

  1. System assigns voucher number (or user enters manually)
  2. Entries are linked to this voucher
  3. Voucher remains "open" (not posted)

Status: Draft - Can still be modified or deleted

Stage 2: Validation​

Before Posting, System Checks:

  • ✓ All entries have a voucher number
  • ✓ Voucher is balanced (Debits = Credits)
  • ✓ All required fields completed
  • ✓ Transaction date is valid (not in closed period)
  • ✓ Accounts exist and are active

If Validation Fails: User must fix issues before posting

Stage 3: Posting​

When: User clicks "Post Journal"

What Happens:

  1. All voucher entries are written to the general ledger
  2. Voucher marked as "Posted"
  3. Account balances updated
  4. Posted date recorded

Status: Posted - Cannot be modified (immutable)

Stage 4: Reversal (Optional)​

When: Need to undo a posted voucher

What Happens:

  1. System creates a new voucher (reversal voucher)
  2. New voucher mirrors original (opposite debits/credits)
  3. Both vouchers remain in system
  4. Link created between original and reversal

Status:

  • Original voucher: Posted (Reversed)
  • Reversal voucher: Posted

Important: Original voucher is NOT deleted - audit trail preserved!

Voucher Numbering and Number Sequences​

Vouchers are automatically numbered using Number Sequences.

Connection to Number Sequences​

Each Journal Name is configured with a Number Sequence for vouchers:

Journal NameVoucher Number SequenceFormat
Daily General JournalGeneral VouchersV-####
Payment JournalPayment VouchersPAY-####
Payroll JournalPayroll VouchersPR-####-{Month}

How it works:

  1. User creates journal using "Payment Journal" name
  2. System looks up: What voucher sequence does Payment Journal use?
  3. Answer: "Payment Vouchers" sequence with format PAY-####
  4. System generates: PAY-0001, PAY-0002, etc.

Why separate sequences:

  • Different voucher series for different purposes
  • Easy to identify voucher type from number
  • Cleaner audit trail

Related Concept: See "Understanding Number Sequences" for more details

Best Practices​

1. Don't Manually Override Vouchers​

Why:

  • Creates risk of duplicates
  • Breaks audit trail
  • Can cause system issues

Instead: Let the system generate automatically

2. Include References​

Always include:

  • Source document number (invoice, payment, etc.)
  • Description of transaction
  • Any relevant external reference

Example:

Voucher: V-042
Reference: Invoice SI-2025-0100 - Customer ABC Corp
Description: Sale of office supplies

Benefit: Anyone can understand what the voucher represents

3. Don't Post Unfinished Journals​

Problem:

  • Generate voucher
  • Leave journal half-complete
  • Voucher number "wasted"

Better:

  • Complete all entries
  • Validate before posting
  • Post only when ready

4. Reverse Properly​

Wrong Way: Delete the original entry ❌

Right Way:

  1. Create reversal entry
  2. Link to original voucher
  3. Post reversal
  4. Both entries remain in system

Why: Maintains complete audit trail

5. Use Descriptive References​

Poor Reference:

Voucher: V-001
Description: Entry
Reference: (blank)

Good Reference:

Voucher: V-001
Description: January rent expense accrual
Reference: Invoice from ABC Properties - Inv #45678

Common Mistakes to Avoid​

Mistake 1: Posting Unbalanced Vouchers​

Problem: Trying to post when Debits ≠ Credits

System Response: Rejects posting with error message

Solution: Review all entries, find the imbalance, correct it

Mistake 2: Using Same Voucher for Unrelated Transactions​

Problem:

Voucher V-001:
  Customer sale
  Vendor payment
  Rent expense
  Payroll entry
(All unrelated transactions under one voucher!)

Why it's bad:

  • Impossible to reverse individually
  • Confusing audit trail
  • Violates accounting principles

Solution: Use separate vouchers for separate business transactions

Mistake 3: Not Documenting Reversals​

Problem:

  • Post voucher V-050
  • Reverse it with V-051
  • No note linking them

Why it's bad:

  • Future users don't know V-051 reversed V-050
  • Audit trail unclear

Solution:

  • Always reference original voucher in reversal
  • System should create automatic link

Mistake 4: Deleting Posted Vouchers​

Problem: "I made a mistake, let me just delete it"

Why it's bad:

  • Breaks audit trail
  • May violate regulations
  • Can cause data integrity issues

Solution: Never delete - always reverse

Understanding Voucher Reports​

Voucher Listing Report​

Shows:

  • All vouchers in a date range
  • Posted vs. unposted status
  • Reversed vouchers
  • Associated journal and document references

Use For:

  • Audit trail review
  • Finding specific transactions
  • Reconciliation

Voucher Detail Report​

Shows:

  • All accounting lines for a specific voucher
  • Account numbers and names
  • Debit and credit amounts
  • Transaction dates
  • References

Use For:

  • Understanding a specific transaction
  • Investigating errors
  • Supporting documentation for audits

Reversed Vouchers Report​

Shows:

  • Original vouchers and their reversals
  • Links between them
  • Dates of original and reversal
  • Reasons for reversal (if documented)

Use For:

  • Tracking corrections
  • Audit compliance
  • Error analysis

Frequently Asked Questions​

Can I change a voucher after it's posted?​

No. Posted vouchers are immutable (cannot be changed).

Reason: Maintains audit trail integrity

If you need to correct: Create a reversal voucher, then post the correct entry

Why do I see gaps in voucher numbers?​

Common Causes:

  • User generated voucher but didn't post journal
  • System error during creation
  • Transaction cancelled after number assigned

Is this a problem?

  • Small gaps (1-2%): Normal and acceptable
  • Large gaps: May indicate process issues worth investigating

Can different journals share the same voucher series?​

Yes!

Example:

  • Daily General Journal → Uses "General Vouchers" (V-####)
  • Adjusting Journal → Uses "General Vouchers" (V-####)
  • Both share the same number sequence

Benefit: Unified numbering across related journals

What's the difference between a voucher and an invoice number?​

Invoice Number:

  • External document given to customer
  • Example: SI-2025-0042

Voucher Number:

  • Internal accounting reference
  • Example: V-2025-0042

They often match (SI-2025-0042 might use voucher V-2025-0042), but they serve different purposes:

  • Invoice: Business document
  • Voucher: Accounting transaction group

Can I reverse only part of a voucher?​

No. Reversals must reverse the entire voucher.

If you need partial reversal:

  1. Reverse entire voucher
  2. Post correct version with proper amounts
  3. Net effect = partial adjustment

Do all accounting systems use vouchers?​

Most professional accounting systems do.

Why:

  • Required for proper audit trails
  • Essential for transaction grouping
  • Standard accounting practice
  • Regulatory compliance

Small business software might not - they often use simplified approaches.

Summary​

Vouchers are unique reference numbers that:

  • Group related accounting entries together
  • Ensure transactions balance (Debits = Credits)
  • Enable easy reversals and corrections
  • Provide clear audit trails
  • Link accounting entries to source documents

Key Principles:

  • One business transaction = One voucher
  • All entries in a voucher must balance
  • Posted vouchers cannot be modified
  • Reversals preserve the original voucher
  • System generates voucher numbers automatically

Key Takeaway: Vouchers are the foundation of proper accounting transaction management. They ensure that every transaction is balanced, traceable, and properly documented - essential for both day-to-day operations and regulatory compliance.

Business Concepts:

  • Understanding Journal Names (configures voucher numbering)
  • Understanding Number Sequences (generates voucher numbers)
  • Understanding Reversals (how to undo vouchers)

User Guides:

  • How to Create a Journal Entry (using vouchers)
  • How to Post a Journal (finalizing vouchers)
  • How to Reverse a Journal Entry (voucher reversal process)

For Developers/Architects:

  • Voucher Generation Strategies (technical implementation)
  • Journal Posting Lifecycle (technical workflow)

This guide is part of the ERP Business Concepts series, designed to help business users understand key financial concepts without technical jargon.