We are restoring the requested view from its saved state. Your account and work remain unchanged while you wait.
Back to the track — Value Added Tax Specialist
Sales issued a SAR 115,000.00 invoice marked VAT-inclusive, then a week later asked to reduce it by 23,000.00 for a partial return. The system posted the whole invoice as revenue, and a colleague entered a manual reduction before the credit note arrived. Your job is to rebuild the chain: net, tax, date, and the document that reverses the return exactly once.
When a business issues an invoice for SAR 115,000.00 including VAT, not everything it will collect is revenue. One part pays for the goods or service; another was collected from the customer for settlement with the authority. The accountant therefore starts before multiplying a number by a rate: what supply occurred, who is the customer, where did it occur, when did consideration become due, and what evidence supports each answer? Starting with the gross and splitting it mechanically can produce correct arithmetic for a wrongly classified supply. The entry balances and the invoice looks orderly, yet both the return liability and revenue are wrong. The professional order is evidence, treatment, calculation and posting.
The first distinction is between revenue and output VAT. For a tax-exclusive price, the net sale is revenue, VAT is a separate liability, and the gross is receivable or cash. For a tax-inclusive price, VAT is not found by multiplying the gross by 15%, because tax is already inside it. Divide by 1.15 to obtain net and take the difference as output VAT. On SAR 115,000.00, net is 100,000.00 and VAT is 15,000.00. Multiplying gross by 15% gives 17,250.00, overstating the liability and understating revenue. The tool performs the arithmetic; the contract, quotation or invoice tells you whether the amount is inclusive.
Not every sale is standard-rated. A supply may be standard-rated, zero-rated, exempt, or outside scope. The numerical result may be zero in the last three cases, but their accounting and tax meanings differ, so they must not be collapsed into one code called zero. A zero-rated supply remains taxable and follows its own return route; an exempt supply is not zero because of a commercial discount but because its treatment differs; outside scope means the event is not a taxable supply in this context. The distinction affects input deduction, return mapping and the explanation of customer movements. The accountant does not infer treatment from a product name alone; classification evidence is retained and the exact code used.
| Treatment | Output VAT | Evidence to retain |
|---|
The treatment starts from these documents. Follow the numbers to identify recognition date, amount, counterparty, reference and approval evidence before preparing the entry.
Facts and supporting evidence
A domestic sale at 100,000.00 exclusive; VAT is 15,000.00 and gross receivable 115,000.00.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Accounts receivable — customer | 115,000.00 | |
| Sales revenue | 100,000.00 | |
| Output VAT | 15,000.00 | |
| Total (SAR) | 115,000.00 | 115,000.00 |
Treatment and financial effect
The customer owes the gross, but 15,000.00 is not revenue; it is a liability collected from the customer. Revenue remains the net earned by the business.
Reperformance starts from this case's own facts: A domestic sale at 100,000.00 exclusive; VAT is 15,000.00 and gross receivable 115,000.00. Obtain the original source that proves this event. The training drawings Tax invoice — domestic sale, Credit note linked to the invoice explain field shape and reading order; they do not replace the case document or transfer their figures into it. Match entity, period, currency, reference and version to the tax invoice, supply evidence, tax point and counterparty status, then confirm that the source supports the debit side (Accounts receivable — customer) and the credit side (Sales revenue, Output VAT). Missing ownership, date, reference or approval remains an open exception; a balancing journal or undocumented assumption does not cure it.
Remeasure from the facts before reading the proposed journal, then add it independently: total debits 115,000.00 and total credits 115,000.00. Debit detail: Accounts receivable — customer for 115,000.00. Credit detail: Sales revenue for 100,000.00; Output VAT for 15,000.00. Link every line to the recognition or measurement rule explained in the lecture, then trace its reference and posting date. After posting, test the output and input VAT ledgers and return bridge. Equal sides prove arithmetic only, not the correct account, period or classification.
In an ERP, the sales entry normally flows from the invoice tax code: customer at gross, revenue at net, and output VAT to a configured settlement account. Risk sits less in arithmetic than in master data, code and date. Customer and material code changes are reviewed, manual postings to tax accounts are restricted and approved, and credit notes link to original invoices so the system cannot reverse tax twice.
Complete the workpaper for four transactions: exclusive sale, inclusive sale, advance, and credit note. Evidence classification and date, write the correct entry, and compare it with a balanced wrong entry.
Work output: A journal entry
These are yours once downloaded, and need no account. Fill them with your own figures and keep them in your portfolio.
Split the inclusive invoice, then switch to exclusive basis and observe how the meaning of the amount changes, not only the result.
One sales invoice whose facts unfold step by step. Decide before the next fact is revealed.
What you haveThe quotation says 115,000.00 VAT-inclusive.
The arithmetic in this case runs in the tool itself, which is open to you any time with your own figures.
Write three lines: the event you classified, the evidence you missed, and the account or period your error changed. Then recompute from the document, not the answer.
This is not sent anywhere and not stored here. Write it down for yourself — in the workpaper you downloaded, or on paper.
Evidence the supply, classify it, determine timing, then separate net from VAT. Do not delete invoices or plug the tax account; link every correction to its original document.
A 115,000.00 VAT-inclusive invoice was posted entirely to revenue. What is the correct entry, and how do you handle a later 23,000.00 return?
Answer every question. Getting them all right records this lesson; you may retry as often as you need.
Reading alone records nothing.
The complete applied walkthrough is available below while the recording is prepared.
I place a 115,000.00 invoice before the camera. Dividing gross by 1.15 reveals 100,000.00, then I place 15,000.00 on a separate output-VAT card. Next I overlay a 23,000.00 credit note and draw a line between their references: no deletion and no parallel journal, just a new document reversing 20,000.00 of revenue and 3,000.00 of VAT once.
| Standard-rated | Calculated at the applied rate | Invoice, classification and tax point |
|---|---|---|
| Zero-rated | 0.00 while the supply remains taxable | Basis for applying zero rate |
| Exempt | 0.00 because of exemption | Evidence for exemption |
| Outside scope | Not treated as supply VAT | Why the event is outside scope |
Timing matters as much as amount. A beginner may assume VAT arises only when an invoice is collected and defer the liability to payment. Output VAT is not a cash book; the tax point must be determined from the supply facts and supporting documents. Invoice date, delivery or service completion, and an advance payment are not interchangeable fields, and any may affect the period in which VAT appears. A workpaper therefore records all three dates and explains why one governs, rather than merely filling a tax-date field. A system may propose a date, but it cannot see a contract that changed scope or an acceptance certificate delayed after invoicing. A reviewer needs the reason, not only the resulting date.
An advance payment exposes weak treatment faster than an ordinary sale. If the business receives cash before performing and credits all of it to revenue, it recognises revenue too early and mixes the contract liability with the tax liability. Accounting separates what has become revenue through performance from what remains an advance, while tax treatment considers receipt and invoicing based on the facts. One entry can therefore contain cash, output VAT and a contract liability without revenue. That prevents the receipt month from appearing profitable before anything was delivered. The payment is linked to the contract, invoice and later performance evidence so the correct part moves from liability to revenue without charging VAT twice on the final invoice.
When goods are returned or a post-invoice reduction is granted, the original invoice is not deleted or silently edited. The new event needs a credit note linked to the original invoice, showing net and VAT reversed. Under the current amendment, a required credit or debit note is issued within fifteen days following the end of the month in which the triggering event occurred; the file therefore records event date, issue deadline and actual issue date. A manual receivable reduction may correct the ledger while leaving the return wrong, or reduce VAT twice when the note later arrives. If a defect is descriptive and changes neither amount nor VAT, follow the documentary-correction route instead of inventing a financial movement.
In the general ledger, the output VAT balance should be rebuildable from the invoice register. Begin with any opening balance, add tax on standard-rated invoices, subtract tax on credit notes, isolate manual journals, and finish at a balance that maps to the return. If it does not, do not post a lump-sum tax adjustment merely to close the month. Find the invoice, credit note, tax code or timing difference that created the gap, because a plug removes the signal and retains the cause. Any manual entry to output VAT needs an owner, rationale, document and approval; an account designed to receive system invoices becomes high risk as soon as free posting is permitted.
A good review does not manually recompute every invoice. It builds tests that show where review time is worth spending: compare taxable sales with expected output VAT, separate zero-rated, exempt and outside-scope codes, look for negative invoices without credit notes, manual journals, tax dates far from delivery, and customers whose codes change repeatedly. These are indicators, not conclusions. An expected rate does not prove treatment correct, and a lower rate is not an error until the sales mix is analysed. The test turns thousands of lines into a small exception list, then each exception returns to its document. Arithmetic serves the search rather than replacing evidence.
At close, the output VAT file is complete when another reviewer can start from the return figure and drill down to the invoice register, or start from one invoice and move through the entry to its return box, without asking what you did. They should see the invoice, supply classification, tax point, account and linked credit note. That is a reperformance trail. A file containing screenshots and a final total without a map proves someone saw numbers; it does not prove how the number was formed. Quality is not the number of attachments but an unbroken short chain from event to document, decision, calculation and final consequence.
Before close, compare the correct treatment with the common alternative and record its specific effect: Revenue is overstated by 15,000.00 and the tax liability understated by the same amount. Do not close until the journal agrees with return boxes, general ledger and ZATCA evidence pack and an independent reviewer can move from balance to account, reference and this event's own source. Keep the calculation, source version, journal identifier, reconciliation result and unresolved exceptions in the same workpaper. An attached file without a stated conclusion is not review evidence.
Facts and supporting evidence
A cash sale of 57,500.00 VAT-inclusive. Net is 50,000.00 and VAT embedded in the price is 7,500.00.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Cash | 57,500.00 | |
| Sales revenue | 50,000.00 | |
| Output VAT | 7,500.00 | |
| Total (SAR) | 57,500.00 | 57,500.00 |
Treatment and financial effect
Divide the gross by 1.15 to obtain net; do not multiply gross by 15% because tax is already inside it.
Reperformance starts from this case's own facts: A cash sale of 57,500.00 VAT-inclusive. Net is 50,000.00 and VAT embedded in the price is 7,500.00. Obtain the original source that proves this event. The training drawings Tax invoice — domestic sale, Credit note linked to the invoice explain field shape and reading order; they do not replace the case document or transfer their figures into it. Match entity, period, currency, reference and version to the tax invoice, supply evidence, tax point and counterparty status, then confirm that the source supports the debit side (Cash) and the credit side (Sales revenue, Output VAT). Missing ownership, date, reference or approval remains an open exception; a balancing journal or undocumented assumption does not cure it.
Remeasure from the facts before reading the proposed journal, then add it independently: total debits 57,500.00 and total credits 57,500.00. Debit detail: Cash for 57,500.00. Credit detail: Sales revenue for 50,000.00; Output VAT for 7,500.00. Link every line to the recognition or measurement rule explained in the lecture, then trace its reference and posting date. After posting, test the output and input VAT ledgers and return bridge. Equal sides prove arithmetic only, not the correct account, period or classification.
Before close, compare the correct treatment with the common alternative and record its specific effect: VAT is overstated by 1,125.00 and revenue understated by 1,125.00, while the entry still balances. Do not close until the journal agrees with return boxes, general ledger and ZATCA evidence pack and an independent reviewer can move from balance to account, reference and this event's own source. Keep the calculation, source version, journal identifier, reconciliation result and unresolved exceptions in the same workpaper. An attached file without a stated conclusion is not review evidence.
Facts and supporting evidence
A 23,000.00 inclusive advance before the service is performed; net advance is 20,000.00 and VAT 3,000.00.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Cash | 23,000.00 | |
| Contract liability — advances | 20,000.00 | |
| Output VAT | 3,000.00 | |
| Total (SAR) | 23,000.00 | 23,000.00 |
Treatment and financial effect
Receipt does not prove performance, so the net remains a contract liability until delivery, with the tax effect separated according to the payment event.
Reperformance starts from this case's own facts: A 23,000.00 inclusive advance before the service is performed; net advance is 20,000.00 and VAT 3,000.00. Obtain the original source that proves this event. The training drawings Tax invoice — domestic sale, Credit note linked to the invoice explain field shape and reading order; they do not replace the case document or transfer their figures into it. Match entity, period, currency, reference and version to the tax invoice, supply evidence, tax point and counterparty status, then confirm that the source supports the debit side (Cash) and the credit side (Contract liability — advances, Output VAT). Missing ownership, date, reference or approval remains an open exception; a balancing journal or undocumented assumption does not cure it.
Remeasure from the facts before reading the proposed journal, then add it independently: total debits 23,000.00 and total credits 23,000.00. Debit detail: Cash for 23,000.00. Credit detail: Contract liability — advances for 20,000.00; Output VAT for 3,000.00. Link every line to the recognition or measurement rule explained in the lecture, then trace its reference and posting date. After posting, test the output and input VAT ledgers and return bridge. Equal sides prove arithmetic only, not the correct account, period or classification.
Before close, compare the correct treatment with the common alternative and record its specific effect: Period profit is overstated by 20,000.00 and the contract liability is missing. Do not close until the journal agrees with return boxes, general ledger and ZATCA evidence pack and an independent reviewer can move from balance to account, reference and this event's own source. Keep the calculation, source version, journal identifier, reconciliation result and unresolved exceptions in the same workpaper. An attached file without a stated conclusion is not review evidence.
Facts and supporting evidence
A credit note issued within the statutory window for part of an earlier sale: net 10,000.00, VAT 1,500.00 and gross 11,500.00.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Sales returns | 10,000.00 | |
| Output VAT | 1,500.00 | |
| Accounts receivable — customer | 11,500.00 | |
| Total (SAR) | 11,500.00 | 11,500.00 |
Treatment and financial effect
The credit note reverses net and VAT separately, links to the original invoice and records event and issue timing, reducing customer gross once.
Reperformance starts from this case's own facts: A credit note issued within the statutory window for part of an earlier sale: net 10,000.00, VAT 1,500.00 and gross 11,500.00. Obtain the original source that proves this event. The training drawings Tax invoice — domestic sale, Credit note linked to the invoice explain field shape and reading order; they do not replace the case document or transfer their figures into it. Match entity, period, currency, reference and version to the tax invoice, supply evidence, tax point and counterparty status, then confirm that the source supports the debit side (Sales returns, Output VAT) and the credit side (Accounts receivable — customer). Missing ownership, date, reference or approval remains an open exception; a balancing journal or undocumented assumption does not cure it.
Remeasure from the facts before reading the proposed journal, then add it independently: total debits 11,500.00 and total credits 11,500.00. Debit detail: Sales returns for 10,000.00; Output VAT for 1,500.00. Credit detail: Accounts receivable — customer for 11,500.00. Link every line to the recognition or measurement rule explained in the lecture, then trace its reference and posting date. After posting, test the output and input VAT ledgers and return bridge. Equal sides prove arithmetic only, not the correct account, period or classification.
Before close, compare the correct treatment with the common alternative and record its specific effect: Sales returns are overstated by 1,500.00 and the tax liability is too high by the same amount. Do not close until the journal agrees with return boxes, general ledger and ZATCA evidence pack and an independent reviewer can move from balance to account, reference and this event's own source. Keep the calculation, source version, journal identifier, reconciliation result and unresolved exceptions in the same workpaper. An attached file without a stated conclusion is not review evidence.