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
Customer confirms 900,000.00 while AR shows 965,000.00. Invoice 115,000.00 sent before close not recorded by customer, and transfer 50,000.00 reached bank but is unapplied. Overall subledger differs from control by 15,000.00 due manual journal and interface. Build two reconciliations without plug.
Entity customer statement explains what books claim; customer confirmation, portal or statement explains what customer acknowledges. Equal totals alone do not prove documents correct, and difference does not automatically mean error. Invoice may be sent but not entered, transfer received but unapplied, note in one system, or cut-off between dates. A good reconciliation does not compare two numbers and label difference. It fixes date, currency and equal population, matches movements or homogeneous groups, and names every difference, owner and closure evidence. Unexplained amount is not 'timing' until event and expected clearing date are proven.
Define comparison. 'Balance at 30/09/2026' means same end of day, legal entity, currency and posting cut-off. If customer statement is 28/09 and AR list 30/09, isolate two days invoices/receipts before declaring difference. Define sign convention: debit in your books may be credit in customer records as its liability, so compare magnitudes after understanding direction rather than doubling difference through sign error. For foreign currency, match transaction currency first, then explain functional-currency revaluation; early conversion hides agreement on 100,000 USD with only FX difference.
Use strong keys: invoice/note number, PO/contract, transfer reference, date, currency and amount. Matching 115,000.00 alone is insufficient when two invoices share value. Start one-to-one, then one-to-many or many-to-one only where remittance explains one transfer paying several invoices or note covering lines. Preserve links; do not delete matched movements, mark matched so reviewer sees full population. Fuzzy name/date matching proposes, not decides. Every proposal needs validation, especially repeated periodic invoice values or customer using different internal numbers.
Classify differences by source. Invoice in transit is a valid pre-date invoice not yet recorded by customer, supported by transmission or portal. Cash in transit means customer sent funds before date but bank does not yet show them, requiring transfer advice and later bank statement—not an entry on promise. Unapplied cash reached bank and books but lacks invoice link. An advance for a new order is not an application difference: link it to order and prepayment invoice, separating net contract liability from output VAT. A pending credit note may be issued by entity but not applied by customer, or requested without approved cause. Dispute concerns right, price or quantity, not timing. Wrong account, duplicate and cut-off error require correction and cannot remain reconciling items forever.
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
Receipt 50,000.00 arrived and identified to INV-4408.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Cash | 50,000.00 | |
| Trade receivables | 50,000.00 | |
| Total (SAR) | 50,000.00 | 50,000.00 |
Treatment and financial effect
Bank and remittance close cash difference and apply item.
Reperformance starts from this case's own facts: Receipt 50,000.00 arrived and identified to INV-4408. Obtain the original source that proves this event. The training drawings Customer balance reconciliation, AR subledger to control reconciliation 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 (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 50,000.00 and total credits 50,000.00. Debit detail: Cash for 50,000.00. Credit detail: Trade receivables 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: AR and income are each overstated 50,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.
Customer open items and billing/clearing documents extract at key date; matching ID retained for pairs/groups. Difference reason codes cannot close without evidence attachment. Control reconciliation compares subledger with GL and prevents/reports manual control posting. Rerun after correction is part of closure.
Match 18 movements between customer statement and AR, classify/own differences, then build AR-to-GL reconciliation and rerun after entries.
Work output: A reconciliation workpaper
These are yours once downloaded, and need no account. Fill them with your own figures and keep them in your portfolio.
Recalculate customer exposure after applying 50,000.00 and decide whether reconciliation difference changes credit decision.
Reconcile customer statement then connect result to control account.
What you haveCustomer statement 28/09; AR 30/09.
The arithmetic in this case runs in the tool itself, which is open to you any time with your own figures.
Log wrong basis, key or difference class, then owner, closure evidence and rerun effect on both reconciliations.
This is not sent anywhere and not stored here. Write it down for yourself — in the workpaper you downloaded, or on paper.
Align date, currency and sign, match identity, name/own differences, reconcile customer to AR and AR to GL, then rerun.
Customer confirms 65,000.00 below books. How prove it is 115,000.00 invoice in transit less 50,000.00 unapplied cash?
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 customer statement beside AR, align date/sign, link 115,000.00 invoice and 50,000.00 receipt with evidence, reach 965,000.00, then move total to control reconciliation and expose 25,000.00 journal and 10,000.00 interface before rerun.
No difference posts to AR or revenue until event, account and document are evidenced.
Ownership shortens close. Billing owns invoice transmission and price correction; cash application owns unapplied transfers; sales owns contract/discount; operations owns delivery/acceptance; tax owns note effect; customer owns remittance/rejection reason. Record item ID, amount, age, cause, owner, follow-up date and expected closure evidence. 'With sales' without person/date is inadequate. When item transfers owners, retain history and reason instead of new ID. Age reconciling items; invoice in transit three months is not normal timing but transmission/acceptance failure.
Customer confirmation is not substitute for ledger reconciliation. Customer may confirm 900,000.00 while books show 950,000.00 because 50,000.00 receipt reached but unapplied. After application they agree, but customer totals in subledger must also equal GL control. Manual entry to control can make GL differ while statements all correct. Build two connected reconciliations: external customer-to-AR and control AR-to-GL. External difference maps to document/cash/dispute; internal maps to interface/journal/wrong account. Neither covers the other.
For confirmation, control address, recipient, dispatch and response so request does not pass through person preparing balance or unverified address they supplied. Positive confirmation requests response whether agree/disagree and is stronger for large/risky balances. Negative asks only on disagreement, gives less evidence and requires suitable conditions. Non-response is not agreement; perform alternatives such as subsequent cash, invoices, delivery and correspondence. If customer says zero, do not reverse AR immediately; compare records and identify legal-entity, portal, dispute or real error.
Inspect subsequent events because they close timing items and expose false labels. Bank receipt 02/10 matching transfer advice 30/09 may support cash in transit; customer recording invoice 04/10 with receipt stamp 29/09 may close invoice in transit. A document newly created after date does not prove pre-date existence. Retain version/date, and do not mark item matched without ending evidence. For entry-required difference, state accounts, amount, period and approver, rerun reconciliation after posting. Difference closed by correspondence alone returns next month if system unchanged.
Dispute in reconciliation does not equal accepting no debt. Compare basis: rejected undelivered quantity questions supply and may require note/revenue/tax correction; accepted supply but rejected price goes to contract/change. Claimed payment needs transfer number traced in bank/suspense. Customer deduction needs legal set-off right or remains unauthorised. Record undisputed portion and continue collection. Do not label every undocumented difference customer dispute; code turns internal ignorance into claim against customer and distorts billing/collection quality metrics.
Close package retains raw statements, match version/rules, total bridge, open/closed differences, closure evidence, AR-to-GL reconciliation and independent preparation/review. Totals: customer balance ± explained items = books, then total books = control after explained internal items. 'Immaterial residual' requires approved threshold and qualitative assessment; small repeated or related-party difference may matter. After close analyse causes and feed process owners. Reconciliation repeating same invoice-in-transit monthly is not resolution; it is archive of failure.
Facts and supporting evidence
Transfer 30,000.00 appears in bank without customer/remittance.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Cash | 30,000.00 | |
| Unapplied receipts | 30,000.00 | |
| Total (SAR) | 30,000.00 | 30,000.00 |
Treatment and financial effect
Cash is recorded but difference remains owned until application identity.
Reperformance starts from this case's own facts: Transfer 30,000.00 appears in bank without customer/remittance. Obtain the original source that proves this event. The training drawings Customer balance reconciliation, AR subledger to control reconciliation 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 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 30,000.00 and total credits 30,000.00. Debit detail: Cash for 30,000.00. Credit detail: Unapplied receipts 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: Wrong customer under 30,000.00 while true item remains over. 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
Valid dispute results in note net 10,000.00 and VAT 1,500.00.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Sales reduction | 10,000.00 | |
| Output VAT | 1,500.00 | |
| Trade receivables | 11,500.00 | |
| Total (SAR) | 11,500.00 | 11,500.00 |
Treatment and financial effect
Correction closes difference in customer, tax and revenue.
Reperformance starts from this case's own facts: Valid dispute results in note net 10,000.00 and VAT 1,500.00. Obtain the original source that proves this event. The training drawings Customer balance reconciliation, AR subledger to control reconciliation 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 reduction, 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 11,500.00 and total credits 11,500.00. Debit detail: Sales reduction for 10,000.00; Output VAT for 1,500.00. Credit detail: Trade receivables 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 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/tax over 10,000.00/1,500.00 with undefined expense. 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
A VAT-inclusive 34,500.00 advance concerns a new standard-rated order, not old invoices.
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
It stays outside old invoice matching and links to order and prepayment invoice with net liability separate from VAT.
Reperformance starts from this case's own facts: A VAT-inclusive 34,500.00 advance concerns a new standard-rated order, not old invoices. Obtain the original source that proves this event. The training drawings Customer balance reconciliation, AR subledger to control reconciliation 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 under 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.