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
One day remains before the deadline. The prior return file contains final numbers without a map, a new tax code used on 46 invoices is absent from the report, and a 4,000.00 manual output-VAT journal has no reference. The manager wants to copy last month's boxes and adjust the total. You must lock population and period, map codes, explain the journal and produce a version another reviewer can reperform before filing.
A good return begins before its portal is opened. If an accountant copies totals from the ledger into boxes with no reference to invoice register, classification or period, the result cannot be reperformed. A sound return starts with complete populations of sales, purchases, notes and adjustments, maps every category to its route, reperforms net and VAT, reconciles to the ledger, and only then transfers approved figures to the return. The order matters: the form does not create correct data; it exposes whether the preceding system is organised. Any box whose source cannot be explained through a clear schedule is unfinished however plausible its number looks.
Period scope is locked first. Businesses with annual taxable supplies above SAR 40 million file monthly; the standard frequency for others is quarterly, with a route to apply for monthly filing subject to ZATCA approval. Filing and payment are due by the last day of the following month. The applicability file records frequency basis, period dates, due date and any application, approval or notice. Revisit frequency when activity or notice changes. Mixing monthly populations into a quarterly file without month boundaries breaks ledger comparison even if the quarter total is right.
Before aggregation, map system tax codes to return categories. Standard sales, zero-rated, exempt and outside-scope do not share one route merely because several can show 0.00 VAT. Deductible, held and ineligible purchases do not collapse into one input column. The map has version, effective date and owner, and an unmapped code appears as an error rather than zero. A code introduced mid-period cannot disappear because last month's list did not include it. Completeness reporting starts with every code actually used and proves each found a route or a documented exclusion.
| Source | What it proves | What it does not prove |
|---|---|---|
| Sales register | Output invoices and notes | That every journal reached the ledger |
| Purchase register |
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
Output VAT is 150,000.00 and supported input VAT 90,000.00; net payable is 60,000.00.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Output VAT | 150,000.00 | |
| Input VAT | 90,000.00 | |
| VAT payable | 60,000.00 | |
| Total (SAR) | 150,000.00 | 150,000.00 |
Treatment and financial effect
Transit accounts close to net settlement after map and reconciliations are approved.
Reperformance starts from this case's own facts: Output VAT is 150,000.00 and supported input VAT 90,000.00; net payable is 60,000.00. Obtain the original source that proves this event. The training drawings Return map from registers, Filing control sheet 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 (Output VAT) and the credit side (Input VAT, VAT payable). 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 150,000.00 and total credits 150,000.00. Debit detail: Output VAT for 150,000.00. Credit detail: Input VAT for 90,000.00; VAT payable for 60,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: Expense is overstated by 60,000.00 and both tax accounts retain balances that do not explain settlement. 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.
The ERP should produce a stable-field period register, versioned tax-code map, manual-journal report and exceptions. A return is not extracted from one account balance; subledgers are aggregated and reconciled. Tax-map editing and period reopening are separated from return preparation, and the approved version locks before filing.
Build a teaching return from sales and purchase registers, map every code, reconcile ledger, write settlement journal, then lock a filing version with a synthetic receipt.
Work output: A workbook
These are yours once downloaded, and need no account. Fill them with your own figures and keep them in your portfolio.
Test an inclusive invoice before it enters the population, noting the tool does not determine box, period or input entitlement.
A return file arrives incomplete, then codes, journals and adjustments emerge. Do not move a figure into a box before evidencing its source.
What you haveMonthly period 01–30/09/2026 is evidenced in the applicability file.
The arithmetic in this case runs in the tool itself, which is open to you any time with your own figures.
Write the box you started from instead of the source, the population or code omitted, and the version that changed. Rebuild from the register and log later discoveries separately.
This is not sent anywhere and not stored here. Write it down for yourself — in the workpaper you downloaded, or on paper.
Lock period and population, map every code, reconcile registers to ledger, separate adjustments, then post settlement and lock the filing version with its receipt.
How do you move from output/input VAT ledger balances to a reperformable return, and what do you lock before filing?
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 begin with a blank return and close it. Instead I open sales register, purchase register and tax-code map. I total output 150,000.00 and supported input 90,000.00, reconcile both to ledger, and derive 60,000.00 net. After review I stamp V3 locked, transfer boxes and link the submission receipt to that exact version.
| Input invoices and notes |
| Entitlement of every amount |
| General ledger | Final accounting consequence | Document type and status |
|---|
| Exception register | Held items, differences and owner | That a described difference is resolved |
|---|
The sales register leads output VAT and the purchase register leads input VAT, but both reconcile to the ledger. A successful invoice may exist in the register without a journal, or a manual tax-account journal may have no invoice. Reconciliation starts with opening balance, adds register movements, separately identifies notes, adjustments and manual journals, and reaches closing balance. Categories then map to the return. A difference is not forced to zero with a lump-sum journal; it is resolved to invoice, code, period or duplication. A genuine timing difference remains visible with description, amount and expected reversal date rather than hidden in another box.
Settlement converts output and input accounts into net payable, refundable or carried balance under approved treatment. If output VAT is 150,000.00 and supported input VAT 90,000.00, net liability is 60,000.00. Inputs do not become expense and outputs do not become revenue; both transit accounts close against net settlement. If inputs exceed outputs, a corresponding balance explains its origin rather than appearing as a negative sign in payables. The journal follows the approved return workpaper, carries period and version reference, and is not posted before review lest the journal amount dictate the workpaper result.
When an error in a prior return understated net VAT, measure the full effect and record original period, cause and discovery date, then add the missing amount through the Corrections section of the return for the period in which the error is discovered under the current treatment. The former SAR 5,000 threshold is not part of this operating route; no amount is an ignore tolerance and a difference is not split to alter its description. The ledger correction remains distinct from the return correction: one fixes the account, the other carries its tax effect with original-period reference. Reconcile the portal correction to journal and cause schedule so Corrections does not become a general difference bucket.
Credit and debit notes enter from their registers and links to original documents, not manual journals to tax accounts. Large, late or unlinked notes are reviewed because they can move return net without a new sale. Non-invoice adjustments also remain separate, each with basis, approver and box consequence. A general adjustments box without analysis becomes a hiding place for multi-year differences and grows harder to explain with every return. The reviewer therefore reads the adjustment list line by line even when not recomputing every invoice.
Final review runs both ways. Top-down, take each box to map, register and document. Bottom-up, select sales, purchase and note documents and confirm they entered the correct period, category and account. The first direction tests existence and explanation; the second tests completeness. A box-only sample may miss an invoice excluded from the population, while a document-only sample may miss a manual journal changing the box. Combining both makes return sign-off more than a visual review of final totals.
Cut-off needs a separate test around period end. Review the last invoices and notes before close and the first after it, comparing supply, payment or document dates to the tax point used under policy. September register can agree perfectly to the ledger because both pulled an October invoice into September under the same code; population agrees while timing is wrong. A credit note arriving after close may relate to an earlier event and needs an evidenced route rather than random placement in whichever box reduces payment. Cut-off tests not only the date but why it was selected: contract, delivery, acceptance, payment and invoice. Deferred cases retain amount, proposed period, evidence needed and owner so deferrals do not become a permanent balance moving from return to return.
The filing file retains submitted return, submission receipt, payment reference where applicable, settlement workpaper, box map, reconciliations, exceptions and preparer/reviewer sign-offs. The accountant does not submit and then edit the workpaper until it matches the submitted copy; the filing version is locked first and later discoveries begin a separate log. Versioning prevents a dangerous later question: is this table the basis of the filed return or a copy changed afterwards? Name and date alone are not enough; version number, locked status and receipt link make the answer clear.
Facts and supporting evidence
Output VAT is 60,000.00 and supported input VAT 90,000.00; settlement is a 30,000.00 debit balance.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Output VAT | 60,000.00 | |
| VAT settlement balance | 30,000.00 | |
| Input VAT | 90,000.00 | |
| Total (SAR) | 90,000.00 | 90,000.00 |
Treatment and financial effect
The difference becomes a settlement balance with supporting file, not a negative payable.
Reperformance starts from this case's own facts: Output VAT is 60,000.00 and supported input VAT 90,000.00; settlement is a 30,000.00 debit balance. Obtain the original source that proves this event. The training drawings Return map from registers, Filing control sheet 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 (Output VAT, VAT settlement balance) and the credit side (Input 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 90,000.00 and total credits 90,000.00. Debit detail: Output VAT for 60,000.00; VAT settlement balance for 30,000.00. Credit detail: Input VAT for 90,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: The 30,000.00 may be netted into other liabilities and lose its recovery or carry-forward trail. 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 reduces an earlier sale: net 10,000.00, VAT 1,500.00 and customer gross 11,500.00.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Sales returns | 10,000.00 | |
| Output VAT | 1,500.00 | |
| Accounts receivable | 11,500.00 | |
| Total (SAR) | 11,500.00 | 11,500.00 |
Treatment and financial effect
The note enters from its register and mapping into the period, linked to its invoice rather than an opaque adjustment.
Reperformance starts from this case's own facts: A credit note reduces an earlier sale: net 10,000.00, VAT 1,500.00 and customer gross 11,500.00. Obtain the original source that proves this event. The training drawings Return map from registers, Filing control sheet 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). 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 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: The return moves by 1,500.00 while subledger and customer do not reflect the return. 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 prior 4,000.00 output-VAT understatement is found because the amount was posted to revenue; the account is corrected and the effect enters Corrections in the discovery-period return.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Sales revenue | 4,000.00 | |
| Output VAT | 4,000.00 | |
| Total (SAR) | 4,000.00 | 4,000.00 |
Treatment and financial effect
The correction fixes the source, records original period and discovery date, then ties the 4,000.00 journal to the Corrections-section line.
Reperformance starts from this case's own facts: A prior 4,000.00 output-VAT understatement is found because the amount was posted to revenue; the account is corrected and the effect enters Corrections in the discovery-period return. Obtain the original source that proves this event. The training drawings Return map from registers, Filing control sheet 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 revenue) and the credit side (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 4,000.00 and total credits 4,000.00. Debit detail: Sales revenue for 4,000.00. Credit detail: Output VAT for 4,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: The understatement doubles to 8,000.00 across the original and wrong correction. 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.