We are restoring the requested view from its saved state. Your account and work remain unchanged while you wait.
Back to the track — Accounts Receivable Accountant
A package with net consideration of SAR 450,000.00 includes equipment, maintenance and training, with VAT of 67,500.00. Equipment transferred on 30/09/2026; training and maintenance have not begun, while sales billed gross 517,500.00 and asks to recognise all net revenue before close. Separate promises, allocate consideration, and determine revenue, contract liability, output VAT and the correct receivable.
Revenue recognition begins before the ledger, with a contract whose rights and obligations are understandable, has commercial substance, specifies payment terms, and has probable collection of consideration for goods or services to be transferred. An internal sales order, quotation or bank receipt does not satisfy those conditions by itself. For SAR 460,000.00 of equipment, a salesperson's signed quote is insufficient: the customer must accept the terms, both sides must have authority, the promises must be identifiable, and collectability must support accounting for a contract. If those conditions are absent, do not begin the recognition model and repair the defect later; keep cash received as a liability until facts change.
After establishing a contract, separate the promises into distinct performance obligations. One contract line may contain a machine, installation, training and a year of maintenance. The question is not how the invoice labels them, but whether the customer can benefit from each good or service on its own or with readily available resources, and whether each promise is separate in the contract context. Routine installation available from another contractor may be distinct; design and integration of components that do not function until the system is complete may form one combined output. This judgement determines when revenue appears and is documented before delivery. Splitting the contract after seeing the monthly result turns the standard into earnings management rather than a description of performance.
Determine the transaction price from the consideration the entity expects to be entitled to, not the highest possible outcome. Fixed price is direct, but annual rebates, delay penalties, performance bonuses, returns and volume discounts make consideration variable. Use expected value or the most likely amount according to the uncertainty, then constrain it to the amount for which a significant reversal is not highly probable when uncertainty resolves. A nominal SAR 500,000.00 sale with an expected SAR 20,000.00 penalty does not automatically begin with SAR 500,000.00 of revenue. Nor may management invent a reserve whenever it wants lower revenue; every estimate is tied to a contract clause, evidence and a documented reversal risk.
When a contract has several performance obligations, allocate transaction price in proportion to stand-alone selling prices at contract inception. If equipment normally sells for SAR 420,000.00, maintenance for 60,000.00 and training for 20,000.00, while the package is SAR 450,000.00, do not push the whole discount into maintenance to recognise most revenue on delivery. Stand-alone prices total SAR 500,000.00, so equipment receives 84%, maintenance 12% and training 4%, unless evidence shows the discount relates specifically to one promise. A stand-alone selling price may be observable or a disciplined market/cost-and-margin estimate. Estimate changes need reasons, not a desire to move revenue across months.
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 package with net 450,000.00 and VAT 67,500.00 was billed; transferred equipment carries 378,000.00 while 72,000.00 of maintenance and training remain unperformed.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Trade receivables | 517,500.00 | |
| Equipment revenue | 378,000.00 | |
| Contract liability | 72,000.00 | |
| Output VAT | 67,500.00 | |
| Total (SAR) | 517,500.00 | 517,500.00 |
Treatment and financial effect
Billing creates a gross claim and output VAT, but net revenue follows only the portion whose control transferred.
Reperformance starts from this case's own facts: A package with net 450,000.00 and VAT 67,500.00 was billed; transferred equipment carries 378,000.00 while 72,000.00 of maintenance and training remain unperformed. Obtain the original source that proves this event. The training drawings Performance and acceptance certificate, Recognition judgement memo 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 contract, performance or delivery evidence, invoice and collection advice, then confirm that the source supports the debit side (Trade receivables) and the credit side (Equipment revenue, Contract liability, 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 517,500.00 and total credits 517,500.00. Debit detail: Trade receivables for 517,500.00. Credit detail: Equipment revenue for 378,000.00; Contract liability for 72,000.00; Output VAT for 67,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 receivables control account, customer subledger and receipt allocation. Equal sides prove arithmetic only, not the correct account, period or classification.
ERP links contract, sales order, performance obligations, billing plan, delivery and acceptance certificates. Stand-alone prices, contract versions and modification reasons are retained, while billed remains separate from fulfilled. A manual revenue entry without performance reference breaks the AR-to-contract reconciliation and repeats every close.
Analyse four contracts: identify contract, promises, transaction price, allocation and performance evidence, then write the balance, entry and judgement reference.
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 whether consideration fits the credit limit before accepting the contract, then remember that clearing the limit does not prove performance.
A package contract arrives in stages; build the recognition judgement before allowing billing to lead it.
What you haveQuote signed internally with no customer acceptance.
The arithmetic in this case runs in the tool itself, which is open to you any time with your own figures.
Log the fact that misled you—invoicing, cash, internal signature or progress percentage—then record independent evidence, judgement and corrected balance.
This is not sent anywhere and not stored here. Write it down for yourself — in the workpaper you downloaded, or on paper.
Contract establishes promises and consideration; performance establishes transfer of control. Invoice and cash affect balance, not revenue by themselves.
A contract is fully billed but half the service is performed at close. How do you separate revenue, receivable and contract liability, and what evidence do you request?
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 the contract at the top, split three promise cards, allocate 450,000.00 by stand-alone prices, and flip only equipment to performed. Revenue becomes 378,000.00 and the rest contract liability, then I contrast the wrong entry that made the whole invoice revenue.
Recognise revenue when or as a performance obligation is satisfied by transferring control. For goods transferred at a point in time, examine present right to payment, legal title, physical possession, transfer of significant risks and rewards, and customer acceptance. No single indicator controls every contract. A signed delivery note may be strong evidence, but not if goods remain at the seller with no qualifying bill-and-hold request, or acceptance depends on a substantive test not yet passed. Conversely, an invoice delayed two days does not delay revenue when control and evidence are complete; a contract asset or unbilled receivable is recognised according to the existing right instead of waiting for an administrative document.
A service may be recognised over time when the customer simultaneously receives benefits, controls an asset as it is created, or when the asset has no alternative use and the entity has an enforceable right to payment for work completed. Do not mechanically divide contract value by months. Select a progress measure that depicts performance: accepted outputs, units delivered, labour hours or performance-related costs, excluding inputs that do not represent progress, such as a major uninstalled material that would overstate completion. At each month end, update progress and outcome and retain source data. A 60% completion figure with no operational basis is not measurement; it is a convenient target.
Separate trade receivable, contract asset and contract liability. A receivable is an unconditional right to consideration requiring only passage of time; a contract asset remains conditional on further performance or another condition. If an entity completes a SAR 180,000.00 milestone but cannot bill unconditionally until the next milestone is accepted, it records a contract asset, not a receivable. If a registered entity receives a VAT-inclusive 115,000.00 before a standard-rated service, debit cash 115,000.00 and credit a net contract liability 100,000.00 plus output VAT 15,000.00; receipt creates no revenue, but it creates a tax point and a prepayment invoice. The distinction matters to collection and disclosure. Collection staff do not chase a contract asset as an overdue invoice, and a reviewer does not accept a net advance hidden in revenue or its VAT deferred until service.
At close, do not begin with invoices and search for revenue to add. Begin with open contracts, performance obligations, delivery or acceptance evidence, modifications and post-period returns. Test cut-off around the final and first days: goods invoiced on 29/09/2026 but delivered on 03/10/2026 are not September revenue merely because billing came first; goods delivered on 30/09/2026 and billed on 02/10/2026 do not vanish from September when right and performance are established. Link entries to independent evidence so invoice date is not both premise and conclusion. A sound review runs both directions: invoice to delivery and delivery to ledger.
Modification, cancellation and return do not erase the old contract. Compare additions or cancellations with stand-alone prices and decide whether the modification is a separate contract, termination and prospective new contract, or a cumulative catch-up to one over-time obligation. Retain version, date, approval, and effects on revenue, tax and receivable. Weak collection does not automatically reverse valid revenue; once contract and performance are established, collection risk usually moves to expected credit losses, unless facts show the contract criteria were never met. This distinction prevents AR using a credit note to disguise a bad debt or an impairment allowance to hide revenue never earned.
A defensible recognition file does not end with 'per IFRS 15'. It forms a short chain: enforceable contract, distinct promises, transaction price including variability, allocation basis, evidence of control transfer or progress measure, then linkage to entry and receivable, contract asset or contract liability. It names assumptions, approvers and possible changes, and reconciles opening to closing movement. Another accountant can reproduce the result from documents without calling the file owner. This is the handoff to billing: a correct invoice is issued because a right arose in an explainable amount, not because invoicing is the fastest way to manufacture the requested sales figure.
Before close, compare the correct treatment with the common alternative and record its specific effect: Revenue is overstated by 72,000.00 and contract liability is missing by the same amount despite correct gross receivable and VAT. Do not close until the journal agrees with revenue, output VAT and receivables ageing 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
Customer paid a VAT-inclusive 115,000.00 advance for a standard-rated service starting next month: net consideration is 100,000.00 and output VAT 15,000.00, with no performance at close.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Cash | 115,000.00 | |
| Contract liability | 100,000.00 | |
| Output VAT | 15,000.00 | |
| Total (SAR) | 115,000.00 | 115,000.00 |
Treatment and financial effect
Receipt triggers output VAT and a prepayment invoice, while the net amount evidences a duty to perform or refund and is not profit before fulfilment.
Reperformance starts from this case's own facts: Customer paid a VAT-inclusive 115,000.00 advance for a standard-rated service starting next month: net consideration is 100,000.00 and output VAT 15,000.00, with no performance at close. Obtain the original source that proves this event. The training drawings Performance and acceptance certificate, Recognition judgement memo 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 contract, performance or delivery evidence, invoice and collection advice, then confirm that the source supports the debit side (Cash) and the credit side (Contract liability, 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: Cash for 115,000.00. Credit detail: Contract liability 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 receivables control account, customer subledger and receipt allocation. 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: Revenue and profit are overstated 100,000.00 and contract liability understated 100,000.00. Do not close until the journal agrees with revenue, output VAT and receivables ageing 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
An over-time service is priced at 600,000.00 and supported progress is 40%.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Contract asset | 240,000.00 | |
| Service revenue | 240,000.00 | |
| Total (SAR) | 240,000.00 | 240,000.00 |
Treatment and financial effect
Supported performance is 240,000.00; the right remains conditional on a later milestone.
Reperformance starts from this case's own facts: An over-time service is priced at 600,000.00 and supported progress is 40%. Obtain the original source that proves this event. The training drawings Performance and acceptance certificate, Recognition judgement memo 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 contract, performance or delivery evidence, invoice and collection advice, then confirm that the source supports the debit side (Contract asset) and the credit side (Service revenue). 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 240,000.00 and total credits 240,000.00. Debit detail: Contract asset for 240,000.00. Credit detail: Service revenue for 240,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 receivables control account, customer subledger and receipt allocation. 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: Revenue is overstated 360,000.00, receivable 600,000.00 and the proper contract asset is absent. Do not close until the journal agrees with revenue, output VAT and receivables ageing 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
An invoice with net 200,000.00 and VAT 30,000.00 was issued on 29/09/2026 for goods transferred on 03/10/2026.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Trade receivables | 230,000.00 | |
| Contract liability | 200,000.00 | |
| Output VAT | 30,000.00 | |
| Total (SAR) | 230,000.00 | 230,000.00 |
Treatment and financial effect
If billing becomes unconditional before performance, VAT is due but net consideration remains a contract liability until October.
Reperformance starts from this case's own facts: An invoice with net 200,000.00 and VAT 30,000.00 was issued on 29/09/2026 for goods transferred on 03/10/2026. Obtain the original source that proves this event. The training drawings Performance and acceptance certificate, Recognition judgement memo 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 contract, performance or delivery evidence, invoice and collection advice, then confirm that the source supports the debit side (Trade receivables) and the credit side (Contract liability, 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 230,000.00 and total credits 230,000.00. Debit detail: Trade receivables for 230,000.00. Credit detail: Contract liability for 200,000.00; Output VAT for 30,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 receivables control account, customer subledger and receipt allocation. 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: September revenue is overstated 200,000.00 and contract liability understated equally. Do not close until the journal agrees with revenue, output VAT and receivables ageing 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.