Each document has a different job
A quotation proposes a transaction. A sales invoice records an amount charged. A delivery note supports evidence of delivery. A receipt acknowledges payment. A credit note adjusts a previous charge. Treating these as interchangeable can cause duplicate income, unpaid balances disappearing or a customer being chased for money already received.
Assign a unique document reference and cross-reference the related order, delivery and payment. If an invoice is corrected, retain the original and record the adjustment. A neat PDF is not proof that a document meets Zimbabwe tax requirements.
Build a useful invoice workflow
Before issuing an invoice, confirm the customer identity, agreed goods or services, quantities, prices, currency and payment terms. State the supplier details consistently. Where a purchase order is required by the customer, obtain and record it before supply rather than discovering the requirement when payment is overdue.
For a non-tax teaching invoice, include the invoice number, issue date, customer, description, quantity, amount, currency, total and payment reference. Tax and fiscal invoices have additional rules. Do not add VAT simply because another business does; ZIMRA states that an unregistered operator must not unlawfully charge VAT.
Zimbabwe-specific checks
ZIMRA's fiscalisation guidance explains the recording and transmission of sales information through the fiscalisation system. Its fiscal-tax-invoice guidance identifies details used to support invoice validity. Use the current official requirements applicable to the operator and its approved fiscalisation arrangement, rather than copying an old internet template.
When assessing a purchase invoice, check the supplier and customer particulars, transaction currency, description, tax treatment and verification details required by the current system. Investigate discrepancies with the supplier before relying on the document for a tax claim. A payment screenshot is not a substitute for a valid fiscal document where one is required.
A worked document trail
A workshop accepts an order for 10 items at 20 currency units each. It receives a deposit of 60 and later invoices a total of 200. Link the deposit to the customer balance so that only 140 remains payable. When a defective item is accepted as a return and credited at 20, the outstanding balance becomes 120, subject to the agreed treatment and any applicable tax adjustments.
The exact posting depends on when the sale is recognised and how deposits are treated. The control lesson is consistent: record the order, advance payment, final invoice and return as connected events, not unrelated sales.
Retention, access and security
ZIMRA's published VAT guidance identifies record retention obligations, including a six-year period for relevant records. Confirm how current legislation and any ongoing enquiry affect a particular file. A retention policy should also explain who can retrieve records when a bookkeeper leaves or a computer fails.
- Keep documents readable, searchable and linked to the ledger.
- Separate approved originals from working drafts.
- Back up records somewhere independent of the everyday device.
- Limit access to customer IDs, bank details and other personal information.
- Check the applicable legal retention period before deleting records.
Sources & further reading
Use these references to check the underlying guidance and any current local requirements. Practical worksheets and illustrative examples in this guide are original educational material.
- ZIMRA: fiscal tax invoices
- ZIMRA: fiscalisation explained
- ZIMRA: valid fiscal tax invoices and VAT input claims
- ZIMRA: VAT mechanics and registered-operator obligations
This guide is general information. Source notes are not a claim of independent professional review.