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
At 30/09/2026 a report places customer net 330,000.00 in over-90 bucket, but customer holds 300,000.00 current, 40,000.00 overdue and 10,000.00 unapplied credit note. A 70,000.00 receipt also arrived with no reference. Rebuild items rather than accept customer net and bucket.
A receivables ageing is not a ranking of customer names from worst to best. It reconstructs every amount still owed at a defined date. Its unit is the open item: invoice, debit note or unapplied receipt with legal customer, number, document and due dates, currency, residual balance and dispute status. One customer can hold 300,000.00 not yet due, 40,000.00 forty-five days overdue and a 10,000.00 unallocated credit note. Putting net 330,000.00 into one bucket erases item behaviour and distorts collection and allowance decisions. Build from open-item detail, then aggregate by customer and segment; do not begin with total and guess composition.
Fix report date before calculating. 'Invoice age today' moves every morning and cannot be reperformed after close. Choose 30/09/2026 and freeze items open at that date, including September documents posted in October after cut-off testing and receipts arriving before close but not yet applied. Then choose ageing date: delinquency usually runs from due date derived from payment terms, not issue date. An invoice dated 01/09 with thirty-day terms is not overdue on 15/09 despite document age of fourteen days. Mixing document age with days past due triggers premature collection and puts a valid balance in a higher loss-rate bucket without cause.
Define buckets once with non-overlapping limits: not yet due, 1–30, 31–60, 61–90 and over 90 days past due. Day zero is due today, not overdue; day 30 remains 1–30 and day 31 moves to 31–60. A greater-than-or-equal mistake can drop or duplicate a day and make bucket total differ from subledger. Test boundaries on small items before full population, then prove every item appears once and bucket sum equals open items in functional currency. If management changes buckets, retain each definition version so monthly comparison remains fair.
Age residual balance, not original amount. A 115,000.00 invoice with 70,000.00 paid leaves 45,000.00 in its bucket; keeping original and showing receipt in separate column can double exposure if wrong column is totalled. Application needs remittance or approved rule. Do not automatically allocate 70,000.00 to oldest invoice when customer named a newer one, and do not use it to beautify oldest bucket. Unapplied receipt remains a customer credit or liability until reference is known and appears in exception report rather than negative balance reducing an unrelated bucket. Application is an evidence decision, not a DSO-reduction technique.
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
Received 50,000.00 from customer with no invoice reference at close.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Cash | 50,000.00 | |
| Unapplied customer receipts | 50,000.00 | |
| Total (SAR) | 50,000.00 | 50,000.00 |
Treatment and financial effect
Credit remains separate until application is evidenced; it does not automatically reduce oldest item.
Reperformance starts from this case's own facts: Received 50,000.00 from customer with no invoice reference at close. Obtain the original source that proves this event. The training drawings Receivables ageing schedule, Customer open-item card 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 (Unapplied customer receipts). 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 50,000.00 and total credits 50,000.00. Debit detail: Cash for 50,000.00. Credit detail: Unapplied customer receipts for 50,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: Old bucket is understated 50,000.00 and unapplied credit hidden. 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.
ERP ages open items at key date using payment terms and baseline date, not customer net. Partial clearing leaves residual item; unapplied receipts and notes have distinct document types. Report variant, buckets and currencies are versioned, and due-date rewrite requires workflow and trail.
Build ageing for 20 items from dates and residuals, separate disputes and credits, and reconcile buckets to ledger.
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.
Combine current and overdue and test how moving balance changes allowance while total stays.
Clean a mixed customer file, then place each item in its bucket and action.
What you haveReport date 30/09/2026.
The arithmetic in this case runs in the tool itself, which is open to you any time with your own figures.
Open the tool itself — Receivables ageing and expected credit loss
Log item, key date, due date, residual and wrong bucket, then record application or correction evidence.
This is not sent anywhere and not stored here. Write it down for yourself — in the workpaper you downloaded, or on paper.
Freeze date, age each residual once from due date, separate dispute and credit, then reconcile and act.
Why can a customer net 330,000.00 mislead ageing, and how do you rebuild from open items?
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 split customer net 330,000.00 into three items, calculate days from due date, apply 70,000.00 only to referenced invoice, place unreferenced receipt and unapplied note in exception box, and agree buckets to ledger.
A dispute does not leave ageing; it changes action route and possibly loss estimate. Record reason code, disputed portion, opened date, owner and decision due date, while undisputed portion continues collection. 'Customer reviewing' is not manageable status. Is dispute 5,000.00 price on a 115,000.00 invoice or whole supply? Does it need credit note, delivery evidence or documented rejection? A 90-day invoice delayed by internal pricing error is not only customer credit evidence; it signals billing quality. Do not move it to current because sales promised resolution, and do not remove it until correction document is issued and applied.
Credit balances need separate explanation: unapplied note, overpayment, advance, duplicate or wrong-customer posting. Netting against debit invoices can make an overdue customer look healthy while credit belongs elsewhere and may be refundable. Show gross debit balances, gross credit balances and customer net, then determine legally and operationally valid offset. If a 34,500.00 receipt includes VAT for a new standard-rated supply, do not call it unapplied cash or book all of it as liability: link the prepayment invoice and separate contract liability 30,000.00 from output VAT 4,500.00. Do not transfer Customer A credit to Customer B merely because both share a group without reference, agreement and approved treatment. An old customer credit is not automatic income; it remains liability or open item until policy-backed settlement.
One month snapshot says where balances stand; movement explains why. Compare item migration from current to 1–30 and 31–60, receipts, notes and kept promises, not only bucket totals. Over-90 may fall because a major invoice was written off rather than collected; current may rise on month-end sales while commercial performance remains sound. Build roll-forward: opening + invoices/debit notes − receipts/credit notes − write-offs = closing, and explain time-based reclassification. If bridge fails, do not trust DSO, collection rate or allowance matrix built on it.
Read concentration with age. SAR 2,000,000.00 across two hundred customers differs from same balance among three, even with identical buckets. Show top ten customers, segments, regions, currencies, disputed share and exposure above credit limit. Treat government entities or long-approval customers using their data, not generic impression, and do not soften loss rate merely for name. Also watch many small invoices: one hundred overdue 2,000.00 invoices may expose transmission or portal failure and consume more collection time than one 200,000.00 invoice. Both value and item count drive action.
An ageing becomes execution list only with owner, action, due date and evidence. For 1–30, statement and receipt check may suffice; 31–60 needs call and dated promise; 61–90 escalates dispute or exposure to credit manager; over 90 may enter legal route or revised trading terms. Age does not replace judgement: unsupported promise tomorrow is not lower risk merely because promised, while delay from undelivered invoice needs channel repair, not threat. Record promise-to-pay amount, date and speaker, then test fulfilment. Broken promises are stronger evidence than polite wording in last call.
Closed version carries report date, ageing basis, bucket definitions, source, FX rate, ledger reconciliation, exception log and preparer/reviewer sign-off. Do not replace it after meeting with a 'cleaner' unversioned file; retain corrections and causes because due-date or receipt-application changes rewrite KPIs and allowance. Reviewer can sample any bucket and reach invoice, due date, residual balance, receipt or dispute. At that point ageing becomes decision map: who needs follow-up, where billing failed, which exposure threatens cash, and what data feeds expected-loss matrix later.
Facts and supporting evidence
Approved linked credit note net 20,000.00 and VAT 3,000.00.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Sales returns | 20,000.00 | |
| Output VAT | 3,000.00 | |
| Trade receivables | 23,000.00 | |
| Total (SAR) | 23,000.00 | 23,000.00 |
Treatment and financial effect
After posting and application, residual of same item falls.
Reperformance starts from this case's own facts: Approved linked credit note net 20,000.00 and VAT 3,000.00. Obtain the original source that proves this event. The training drawings Receivables ageing schedule, Customer open-item card 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 (Sales returns, Output VAT) and the credit side (Trade receivables). 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: Sales returns for 20,000.00; Output VAT for 3,000.00. Credit detail: Trade receivables for 23,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 VAT are over 20,000.00 and 3,000.00 with false expense 23,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
Approved matrix requires closing allowance 42,000.00; existing allowance is 30,000.00.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Credit loss expense | 12,000.00 | |
| Loss allowance | 12,000.00 | |
| Total (SAR) | 12,000.00 | 12,000.00 |
Treatment and financial effect
Ageing feeds measurement, but entry increases allowance only by difference.
Reperformance starts from this case's own facts: Approved matrix requires closing allowance 42,000.00; existing allowance is 30,000.00. Obtain the original source that proves this event. The training drawings Receivables ageing schedule, Customer open-item card 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 (Credit loss expense) and the credit side (Loss allowance). 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 12,000.00 and total credits 12,000.00. Debit detail: Credit loss expense for 12,000.00. Credit detail: Loss allowance for 12,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: Expense is over 30,000.00, AR under 42,000.00 and old allowance remains. 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 34,500.00 advance for a new standard-rated supply, with no final sales invoice or performance at close.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Cash | 34,500.00 | |
| Customer advances | 30,000.00 | |
| Output VAT | 4,500.00 | |
| Total (SAR) | 34,500.00 | 34,500.00 |
Treatment and financial effect
A prepayment invoice is issued; its net is liability and VAT is separate, while gross does not become negative AR reducing other invoices.
Reperformance starts from this case's own facts: Customer paid a VAT-inclusive 34,500.00 advance for a new standard-rated supply, with no final sales invoice or performance at close. Obtain the original source that proves this event. The training drawings Receivables ageing schedule, Customer open-item card 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 (Customer 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 34,500.00 and total credits 34,500.00. Debit detail: Cash for 34,500.00. Credit detail: Customer advances for 30,000.00; Output VAT for 4,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.
Before close, compare the correct treatment with the common alternative and record its specific effect: AR is understated 34,500.00, advance liability 30,000.00 and output VAT 4,500.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.