Ageing and collections worklists

An ageing worklist groups positive student balances by how long they are overdue and adds operational priority. It tells a credit controller whom to review and contact; it does not record a payment, issue a receipt, waive a debt or prove collectability.

Audience: credit controllers, bursars, school leaders, reviewers, and support analysts
Learning time: 35–45 minutes
Primary routes: /finance/student-summaries, /finance/analytics, /finance/invoices

Learning outcomes

You will be able to:

• explain ageing buckets and balance statuses;
• build a reproducible worklist from filters;
• distinguish overdue from arrears;
• review disputes, credits and stale summaries before contact;
• document reminders and escalation without altering financial records;
• hand cases safely to P4 collections.

Prerequisites

Requirement	Verification
Fresh summaries	recalculation time acceptable
Correct scope	school, year, currency, as-of date
Approved invoices	obligation is valid and not cancelled
Due dates	present and accurate
Contact policy	authorised guardian/contact channel
Dispute process	owner and escalation route known
Access	summary statistics/list/read/export and invoice read/send as applicable
Privacy	least-data principle and authorised worklist recipients

Roles and exact permissions

• student_financial_summary:list
• student_financial_summary:read
• student_financial_summary:statistics
• student_financial_summary:export
• student_financial_summary:recalculate
• financial_invoice:list
• financial_invoice:read
• financial_invoice:send
• financial_invoice:statistics
• financial_credit_note:list
• financial_payment:list
• scholarship_award:list

Ageing and priority model

Balance-status interpretation

Status	Meaning	Default action
credit	balance below zero	investigate allocation/refund; do not demand payment
balanced	zero	no collection action
positive current	due but not overdue	monitor or pre-due reminder policy
overdue	positive and an overdue bucket exists	contact under policy
arrears	positive with 90+ balance	higher-priority escalation

Arrears is a subset of serious overdue exposure, not a moral judgement about a family.

Build a controlled worklist

Guided procedure

1. Set school, academic year, currency and as-of date.
2. Confirm summaries are fresh enough for the worklist cycle.
3. Filter balanceStatus=overdue or arrears, or a specific agedBucket.
4. Sort by policy—age, amount, prior contact or risk. Document the method.
5. Open each high-value/high-age case and trace the balance to invoices, credits, payments and scholarships.
6. Place cases on review hold when a dispute, pending adjustment, missing allocation or stale summary exists.
7. Export only the minimum fields required for authorised staff.
8. Record contact date, channel, authorised recipient, outcome, promised action and next review date in the approved operational system.
9. Do not change invoice totals merely to remove a worklist item.
10. When payment arrives, transfer to P4 procedures for capture, verification, allocation and receipt.
11. Rebuild the worklist after material corrections or at the next cycle.

Worked scenario

The 90+ worklist shows a learner owing USD 700. Detail review finds a USD 200 approved scholarship award not yet reflected in the latest summary and a USD 100 payment recorded but unallocated. The credit controller does not demand USD 700. The case is held; the scholarship/application and payment allocation are resolved under their workflows; the summary is recalculated; the remaining valid receivable becomes USD 400. The contact record states the corrected amount and evidence date.

Communications boundary

Invoice send/reminder fields store sent_to_parent, sent date, method, reminder count and last reminder. They do not prove delivery/read status unless the downstream communication provider supplies that evidence. A reminder must not disclose another student’s data or include unsupported threats, penalties or statutory claims.

Accounting and balance effects

Creating or exporting a worklist has no accounting effect. Contacting a guardian has no accounting effect. A valid credit, payment allocation, refund or invoice correction changes source records and may change accounting evidence under configured mappings.

Controls and audit evidence

Store filter scope, as-of date, export job ID, worklist version, account review evidence, holds, owner, contact channel/date/outcome and escalation decision. Protect exports as confidential financial data and delete according to retention policy.

Failure modes

Symptom	Likely cause	Evidence	Safe action	Escalate when
Worklist includes paid student	stale summary/unallocated payment	payment and recalculation timestamps	resolve source and rebuild	source is correct but balance remains
Large credit appears	overpayment/duplicate adjustment	payment/credit records	investigate; no collection	unsupported negative balance
Wrong ageing bucket	due date/as-of error	invoice due dates	correct source or date	bucket logic violates contract
Same family contacted repeatedly	no shared contact log	communication history	coordinate and set next action	harassment/privacy risk
Export shared broadly	access-control failure	download/share audit	revoke and incident process	confidential disclosure
Arrears amount changes mid-cycle	new transaction/correction	source audit history	refresh before action	unexplained change

Verification checklist

• Worklist scope and as-of date are explicit.
• Summaries are fresh.
• Credit/zero accounts are excluded from demands.
• Material balances trace to sources.
• Disputed/pending-correction cases are on hold.
• Contact recipients and channels are authorised.
• Worklist/export access is restricted.
• No balance was edited to improve worklist metrics.
• Payments hand off to P4.
• Escalation follows school policy, not undocumented operator judgement.

Practice and knowledge check

Guided practice

Use a non-production test school and the Mupfure Learning Academy scenario. Record the selected school, academic year, term, currency, fee, operator, reviewer, and timestamps. Capture the before-state, action evidence, after-state, and any exception IDs. Do not mark the exercise complete from a success toast alone.

Knowledge check

1. What record proves the student obligation?
2. Which status dimension answers whether the invoice is authorised?
3. Which status dimension answers how much remains unpaid?
4. What evidence proves the selected student population was correct?
5. Which action requires a separate reviewer in your school policy?
6. What should be inspected before retrying a failed or partial operation?
7. Which later phase owns payment collection and receipt procedures?

Answer rubric: a complete answer names the exact Makronexus record, status, permission or evidence source. Role names alone are insufficient.

P3 completion gate

P3 is complete when an independent reviewer can:

1. prove the fee-to-student population decision;
2. reproduce dry and live billing runs;
3. reconcile run counters and invoices;
4. explain each invoice status dimension and total;
5. perform an authorised credit correction;
6. trace student summary and ageing to source records;
7. produce a controlled receivables worklist;
8. identify the exact point where P4 collection procedures begin.

Next phase

Continue to P4 when published: payment capture, allocation, receipts, cash controls, bank transfer, mobile money/card, refunds, reversals and collection exceptions.