# VAT on Advance Payments Saudi Arabia: Entries and Timing

> VAT on advance payments Saudi Arabia: work through SAR examples, record customer advances, reconcile the final invoice, and practise the tax timing decisions.

- Canonical page: https://accountery.app/learn/vat-advance-payments-saudi-arabia
- Language: English (en)
- Category: journal-entries
- Estimated reading time: 11 minutes
- Published: 2026-09-07
- Updated: 2026-09-07

## How does VAT on advance payments Saudi Arabia work?

VAT on advance payments Saudi Arabia becomes much easier to follow when you give the tax calculation and the sales calculation separate working papers. A customer can pay for goods before receiving them. That receipt can create output VAT while the amount belonging to the business remains a customer advance.

The bank movement, tax liability, and earned revenue answer different questions.

This guide works through ordinary domestic sales by a VAT-registered supplier, using the standard 15% rate and the normal VAT accounting basis. The businesses and transactions below are fictional training cases. They exclude continuous supplies, government procurement contracts, cash accounting, cancellations, and changes in the tax rate. Those facts can change the analysis and need their own checks.

Start by reading the contract amount carefully. Is the payment stated before VAT, or does the amount arriving in the bank already include VAT? Then draw a short timeline showing the payment, any actual tax invoice, and the supply. Finally, establish when control of the goods passes for revenue purposes. A single spreadsheet date cannot reliably do all three jobs.

If you need a refresher on output and input tax accounts, read the [Saudi VAT accounting guide](/learn/vat-accounting-saudi-arabia). Here the focus is narrower: carrying one advance through the records without losing its tax history or recording the sale twice.

## Which date matters for VAT on advance payments Saudi Arabia?

For the ordinary cases covered here, compare the supply date with any earlier invoice or payment. ZATCA's [digital economy guideline, section 4.3](https://zatca.gov.sa/ar/HelpCenter/guidelines/Documents/Guideline-For-the-Digital-Economy-Sector-under-VAT-Provisions.pdf) explains this timing rule; its May 2026 edition also confirms the standard 15% rate. An advance can therefore put VAT in a reporting period before delivery.

The amount matters alongside the date. ZATCA's [e-invoicing guideline, section 8](https://zatca.gov.sa/en/E-Invoicing/Introduction/Guidelines/Documents/E-Invoicing_Detailed__Guideline.pdf) addresses advance invoices and the adjustment of previously taxed amounts in subsequent invoices. For the partial advance assumed below, track the tax on the advance separately from the remaining consideration so that the final invoice can account for it correctly.

Before solving a question, write down what each document actually is. An order confirmation and a bank receipt tell you useful things, but they do not mean that an actual tax invoice for the whole sale was issued. Conversely, if the facts expressly say that the supplier issued such an invoice earlier, you must include that event when deciding the tax timing.

For each receipt, your working paper should show the gross amount, the taxable amount, the VAT amount, and the date that supports recognition. Put the invoice reference beside the payment reference. If the customer pays in several stages, use separate rows. This makes the eventual reconciliation possible even when the salesperson, treasury team, and accountant use different reference numbers.

Keep special cases separate. ZATCA has a [specific timing mechanism for qualifying government contracts](https://zatca.gov.sa/en/MediaCenter/News/Pages/New-VAT-Mechanism-for-Gov.aspx). A government customer, an ongoing service, or a stated cash-accounting basis is a reason to check the applicable rule before copying either example below.

## Why can a customer advance remain outside revenue?

Revenue follows the performance obligation. The [IFRS Foundation's IFRS 15 overview](https://www.ifrs.org/issued-standards/list-of-standards/ifrs-15-revenue-from-contracts-with-customers/) explains recognition when the promised goods or services transfer to the customer. For the point-in-time sales assumed below, revenue arises when control passes under the stated contract facts.

Before that happens, the net customer advance is a contract liability. IFRS 15 paragraph 106 addresses consideration paid or due before transfer; the [AASB's published equivalent paragraph](https://standards.aasb.gov.au/node/3026) provides the corresponding presentation requirement. A familiar bookkeeping description is [unearned revenue](/glossary#unearned-revenue), although the account title should make the nature of the customer obligation clear.

For practice, keep two separate questions on your page: how much of the sale has been performed, and how much VAT has already arisen? A correct answer to one does not prove the other. In the first example, the company has received cash and owes goods to the customer at the end of September. In October, the sale is completed and that customer obligation is cleared.

Use the [revenue recognition guide](/learn/ifrs-revenue-recognition) if the contract contains several promises or delivery terms that need closer analysis. The examples here deliberately state when control passes. In a real file, support that conclusion with the contract and delivery evidence rather than assuming every dispatch date is also the revenue date.

## Worked example 1: a partial advance before a later sale

Assume Najd Office Supplies sells equipment to a business customer for SAR 40,000 before VAT. The customer will collect the equipment in October, when control passes. On 28 September, Najd receives an advance of SAR 11,500, including VAT, and issues an invoice for that advance only. No earlier tax invoice or supply has occurred. Najd files quarterly VAT returns in this training case.

Separate the receipt first: SAR 11,500 divided by 1.15 gives SAR 10,000 before VAT. The difference is SAR 1,500 output VAT. The full contract, meanwhile, is SAR 40,000 plus SAR 6,000 VAT, or SAR 46,000 gross.

Keep these two sets of numbers visible: the first describes the receipt; the second describes the completed sale.

The receipt [journal entry](/glossary#journal-entry) is:

| Account | Debit SAR | Credit SAR |
|---|---|---|
| Bank | 11,500 | 0 |
| Customer advances, contract liability | 0 | 10,000 |
| Output VAT payable | 0 | 1,500 |

At 30 September, the contract liability is SAR 10,000 and revenue from this contract is zero. The SAR 1,500 output VAT belongs in the quarter ending September under the stated facts. The advance's taxable base is SAR 10,000. That tax reporting base can differ from revenue for the same period; your working paper should explain the difference.

On 12 October, the customer collects the equipment, the final invoice is issued, and control passes. The invoice reconciliation starts with SAR 46,000 gross, applies SAR 11,500 already paid, and leaves SAR 34,500 due. Additional output VAT is SAR 4,500, bringing the transaction's total to SAR 6,000.

One combined accounting entry for completion is:

| Account | Debit SAR | Credit SAR |
|---|---|---|
| Customer advances, contract liability | 10,000 | 0 |
| Trade receivables | 34,500 | 0 |
| Sales revenue | 0 | 40,000 |
| Output VAT payable, remaining portion | 0 | 4,500 |

The entry balances at SAR 44,500 on each side. The gross invoice reconciliation totals SAR 46,000 because it also includes the SAR 1,500 VAT recorded earlier. This difference is expected: the combined completion entry records what changes on 12 October. Inventory and cost-of-sales entries are outside this timing illustration.

When the remaining SAR 34,500 arrives, debit bank and credit trade receivables for that amount. There is no additional sale or output VAT from collecting this existing balance. Across both periods, cash receipts total SAR 46,000, revenue totals SAR 40,000, and output VAT totals SAR 6,000. Reperform all three checks before moving on.

## Worked example 2: a fully paid order crosses month-end

Assume Dammam Display Trading accepts an online order for standard-rated display units. The agreed price is SAR 23,000 including VAT. On 30 November, the customer pays the full amount and receives the advance invoice. The units remain with the seller. Dispatch and transfer of control both take place on 5 December under this example's contract. The seller files monthly VAT returns, and no earlier tax point exists.

The payment contains SAR 20,000 for the units and SAR 3,000 VAT. You can verify this in either direction: 23,000 divided by 1.15 equals 20,000; 20,000 multiplied by 15% equals 3,000. Multiplying the gross SAR 23,000 by 15% would incorrectly produce SAR 3,450. Write whether a figure is gross or net beside it before choosing the calculation.

On 30 November, debit bank SAR 23,000, credit customer advances SAR 20,000, and credit output VAT payable SAR 3,000. The November closing file should retain the advance invoice and payment evidence. Revenue from the order is zero because the stipulated transfer has not happened, while the output VAT for this transaction is SAR 3,000.

On 5 December, debit customer advances SAR 20,000 and credit sales revenue SAR 20,000. All the sale's VAT has already been recorded. The final document reconciliation is SAR 23,000 total less SAR 23,000 previously paid, leaving zero payable. A software-generated document must still account for the earlier advance correctly; the bookkeeping entry alone is not a specification for electronic invoice fields.

Look at the [general ledger](/glossary#general-ledger) after posting. The contract liability for this order should be zero. Revenue should show SAR 20,000 in December. The transaction contributes SAR 3,000 output VAT in November and no additional output VAT in December. Settlement of the overall VAT return is a separate process involving all transactions in that period.

Now compare this case with Najd's order. The full payment changes the remaining balance and the VAT left to recognize, but both cases still need a documented revenue date. For revision, hide the entries and reconstruct the November and December positions from the timeline. You should be able to explain each balance without relying on the order in which the example presented it.

## How do you reconcile the final invoice and the advance?

Build a transaction schedule that another accountant can follow without asking you what the numbers mean. Give each contract one reference, then attach the separate invoice and receipt references to it. Carry forward both the net advance and the VAT recognized on that advance. Keeping only the gross receipt makes it harder to identify a duplicated tax posting later.

Use Najd's numbers to test the schedule:

| Check | Calculation | Result SAR |
|---|---|---|
| Total contract including VAT | 40,000 + 6,000 | 46,000 |
| Remaining customer balance | 46,000 minus 11,500 | 34,500 |
| Remaining taxable base | 40,000 minus 10,000 | 30,000 |
| Additional VAT at completion | 6,000 minus 1,500 | 4,500 |

These are accounting control totals, not a replacement for the required invoice format. Your invoicing system must preserve the appropriate references and represent the advance correctly. Reconcile its output to the schedule before posting. If the system books the full invoice and a separate advance-clearing document, examine their combined effect rather than adding another copy of the combined entry shown above.

For month-end review, select orders with advances that remain open. Check whether delivery evidence exists, whether the customer balance agrees to the commercial records, and whether the same VAT has appeared in more than one period. Record the explanation beside every difference.

A useful reconciliation lets the next reviewer trace an amount from bank receipt to invoice, posting, and reporting period.

## What common mistakes should you check for?

The most useful review comments identify the incorrect decision and the evidence that would have corrected it. Start with these recurring errors when marking your own work:

- **Applying 15% to a VAT-inclusive receipt.** Separate the net amount first. In Dammam's case, the correct VAT is SAR 3,000; the gross amount already contains that tax.
- **Recognizing revenue immediately on collection.** Locate the stated transfer of control and explain the remaining obligation before posting the sales account.
- **Charging the advance VAT again at completion.** Compare total output VAT for the transaction with the VAT on the agreed total price.
- **Treating an unpaid final balance as a new sale when collected.** Trace the receipt to the existing receivable and check that revenue was already recorded.
- **Ignoring an earlier actual invoice.** The payment date alone is insufficient if another tax-triggering event has already occurred.
- **Copying a training entry into the invoicing system without reconciliation.** Confirm how the system clears advances and carries their tax references.

Also read what the word deposit means in the contract. A payment toward an identified sale and money held under separate security conditions require an analysis of their actual terms. These examples assume consideration for the sale throughout. Where that assumption does not hold, record the missing fact and check the applicable treatment before computing tax.

Keep corrections specific. Write which amount you misread, which date you overlooked, or which account you duplicated. That note gives your next practice session a concrete task.

## How can you practise the advance-to-invoice workflow?

Rework Najd's case on a blank page with a SAR 23,000 gross advance instead of SAR 11,500. Keep the SAR 40,000 net contract price and the same dates. Calculate the September net advance, the September VAT, the October remaining receivable, and the additional October VAT before preparing the entries.

Your control totals are SAR 20,000 net advance, SAR 3,000 September output VAT, SAR 23,000 remaining receivable, and SAR 3,000 additional October output VAT. Revenue on completion remains SAR 40,000. If your result differs, start with the gross-to-net calculation and then inspect the advance-clearing line.

Next, explain the result aloud as if handing the file to a colleague: what was received, what remained owed to the customer, what changed on delivery, and which VAT had already been recorded. Use the [journal-entry walkthrough](/learn/how-to-record-journal-entries) to revisit debit and credit structure when needed. Then repeat the exercise a day later using different amounts and no visible answer.

If you are applying this topic in certificate study, Accountery's [VAT Specialist exam preparation](/prep/socpa/vat-specialist) provides a relevant next place to practise and review alongside your course and official materials. Keep this article's transaction schedule beside your error log: it helps you separate a timing mistake from an arithmetic mistake and choose what to work on next.

---

Educational content from Accountery. Verify current standards, regulations, and authoritative sources before professional use.