Accounts receivable subsystem (internal)
Internal 3 credits Subsidiary ledger Aged debtors Bad debts Discount allowed Internal controlThe standard names two strands, side by side: PROCESSING financial information (subsidiary ledger, schedule of accounts receivable, aged debtors report — Achieved; bad debts/sundry charges — Merit; discount allowed/a transposition error — Excellence), and DESCRIBING/EXPLAINING/JUSTIFYING the subsystem's elements.
1 Reading the notation
Two parallel strands — processing, and describing/explaining/justifying elements.📖 Terms the schedule grades you on
4 terms- Processing (Achieved)
- Subsidiary ledger, schedule of accounts receivable, aged debtors report.
- Processing, detailed (Merit)
- Adds bad debts and/or sundry charges to debtors.
- Processing, complex (Excellence)
- Adds discount allowed and/or a transposition error between debtors.
- Elements (describe → explain → justify)
- Credit checking, authorisation, document control, subsidiary ledger, statements, aged debtors report, reconciliation.
2 Processing financial information
Subsidiary ledger and reports, then bad debts/discount, then a transposition error. Worked Correcting a transposition error between two debtors A $450 receipt from Debtor A was mistakenly posted as $540 to Debtor B's account. Reverse the incorrect entry from Debtor B: DR Debtor B $540 (restoring the balance that was wrongly reduced). Post the correct receipt to Debtor A: CR Debtor A $450 (the actual amount they paid). The $90 difference (540 − 450) must also be accounted for — check whether it was a genuine transposition (4 and 5 swapped) or a separate error. Reconcile: the subsidiary ledger total must again equal the control account after both corrections. ✓ A transposition error between debtors touches TWO customer accounts, which is what makes it complex — a single-account fix is not enough.3 Describing, explaining and justifying the elements
The standard's own closed list of seven elements.Structure that earns the top band
- Describe how the entity's subsystem actually works, document by document.
- Identify a specific weakness — with evidence from the entity, not a textbook list.
- Explain the consequence, followed through to cash and profit.
- Justify a recommended control, and say why THIS entity needs it specifically.
4 Internal controls, and the consequences of weak ones
Beyond the standard's own named list — the practical controls, and what failure looks like.The chain a report is marked on
- Weak control (e.g. no credit checking, no separation of duties).
- Slower collection — a rising age of receivables.
- A cash shortage despite profitable trading on paper.
- More bad debts, and reliance on an overdraft with its interest cost.
Practice
Recall it first, then use it — testing yourself builds the memory, where rereading the notes above only feels easier.
Recall and application shuffled together — you have to work out what each item wants before you can answer it, which is the part the exam actually tests. Both kinds feed the same spacing schedule, so anything you miss comes back sooner.
Say the answer out loud before flipping — that attempt is where the learning happens, even when you get it wrong.
Exam-style only. Instant feedback, shuffled each attempt, best score saved on this device.