A customer transfers money and an employee records it as sales, although the sales invoice was already posted. Revenue doubles for one transaction. This happens when an invoice and a receipt are treated as interchangeable. An invoice describes a claim connected with a supply; a receipt records money collected that needs allocation. Cash may arrive before a sale or cover several invoices. Understanding that relationship prevents duplicate revenue and makes partial settlements, advances and returns understandable in the customer account.
What does each document explain?
An invoice describes the transaction for which the customer is being charged, including items, quantities, prices, discounts, totals and relevant details. A payment receipt records money received from an identified party, with its date, payment method, reference and allocation. One invoice may be paid in instalments, and one receipt may cover several invoices. Their document counts therefore need not match.
| Document | Question it answers | Useful review reference |
|---|---|---|
| Invoice | What items and amount are being charged? | Customer and transaction date |
| Payment receipt | What amount was received? | Bank or cash account and payment reference |
| Payment allocation | Which balances does the payment cover? | Invoice numbers and allocated amounts |
| Customer statement | What movements and balance remain? | Reporting period and linked documents |
Why is a receipt not always revenue?
A business may receive an advance before delivering a service, a deposit held as security or payment of an old balance. The contract and purpose determine how the transaction should be described. The IFRS Foundation's IFRS 15 overview links revenue recognition to satisfying performance obligations through transferring goods or services under the standard. A transfer date or document date alone does not resolve every accounting treatment.
A quotation or preliminary document may also exist before a sale is completed. Do not automatically treat it as an approved invoice or evidence of cash received. Agree on document names, statuses and approval responsibilities within the business. Clear distinctions make it less likely that a valid document will be used for the wrong purpose during follow-up or reporting.
A clear partial-payment example
Assume an illustrative invoice total of SAR 10,000, without a tax breakdown. The customer pays SAR 4,000 initially and SAR 3,500 later. Each receipt is recorded once and allocated to the invoice. Total payment becomes SAR 7,500, leaving SAR 2,500 outstanding. Revenue does not become SAR 17,500 by recording the collections: in this example, payment settles a receivable rather than creating another sale.
Before allocating the second receipt, check the customer, reference, amount and bank value date under the agreed reconciliation procedure. The customer might have intended another invoice of the same value. A confirmed remittance reference or clarification makes later questions easier to resolve. If a receipt lacks sufficient information, identify it before allocating it arbitrarily to make a statement appear settled.
Checks before closing an outstanding balance
- Match the actual payment to supported bank or cash records.
- Confirm the customer and the invoices identified by the remittance.
- Record the receipt once and check for duplicate payment references.
- Allocate the amount and verify the balance remaining on each invoice.
- Process discounts and returns through approved documents rather than hiding them in a payment.
- Retain review evidence when correcting an allocation or reversing an incorrect action.
Electronic invoicing in Saudi Arabia
ZATCA describes electronic invoicing as issuing invoices and notes through an electronic process in a structured format using an electronic solution. A bank transfer receipt or a document image alone therefore does not establish that tax-invoice requirements have been met. Use the official source to check requirements relevant to the transaction and implementation phase, separately from internal evidence of payment.
This example explains document relationships and collections. It does not determine a tax point or the tax treatment of advance payments. Those details depend on the transaction and the official requirements applicable to it.
Make the customer's history understandable
Start an inquiry with the customer statement, then follow the invoice, receipt and bank reference. If balances disagree, identify when the difference first appeared and investigate the underlying movement. Re-entering the invoice or receipt without checking can double the problem. Always state the reporting date so today's balance is not accidentally compared with a statement from last week.
During a Wali ERP demonstration, use a defined sale and two partial payments. Discuss how your team reviews the remaining balance and handles a payment allocated incorrectly. The scenario shows the relationship between sales and accounts and clarifies the required workflow more effectively than a printed document alone. Implementation details and permissions remain part of the agreed scope.
Sources & further reading
Visit the original source to explore the concept and its wider context.
General educational content. Appropriate treatment depends on your business and accounting policies; consult your accounting professional when applying it to business records.
