Credit notes and adjustments

A credit note is a controlled record that reduces an invoice obligation. It has its own amount, remaining balance, reason, approval history and application evidence. It is not money paid to the guardian and it is not a deletion of the invoice.

The original invoice, line items, approval history and related payment evidence remain available after a credit is applied. A credit does not prove that cash moved, a bank account was debited, a receipt was cancelled, or a refund was authorised. Those are separate controlled records and procedures.

Audience: bursars, credit controllers, approvers, accountants, auditors, and support analysts
Learning time: 35–45 minutes
Primary route: /finance/invoices credit-note actions

Learning outcomes

You will be able to:

• choose credit, cancellation, fee adjustment or refund correctly;
• explain credit-note states and balances;
• create, approve and apply credits with exact permissions;
• prevent over-application and wrong-student/wrong-currency errors;
• verify invoice and student-summary effects;
• preserve append-only correction evidence.

Prerequisites

Requirement	Verification
Original invoice	correct student/school/currency and remaining obligation
Reason/evidence	authorised policy, supporting document and reviewer
Amount	positive and no greater than intended reduction
Credit state	draft for edit, approved for application
Available balance	remaining_amount supports application
Access	exact credit-note abilities
Accounting policy	configured correction mapping understood
Refund boundary	no cash-out claim is being made

Roles and exact permissions

• financial_credit_note:create
• financial_credit_note:list
• financial_credit_note:read
• financial_credit_note:update
• financial_credit_note:delete
• financial_credit_note:approve
• financial_credit_note:reject
• financial_credit_note:apply
• financial_invoice:read
• financial_invoice:update
• student_financial_summary:read
• student_financial_summary:recalculate

Correction decision

State and amount model

The stored status vocabulary is typically draft, pending, approved, rejected; partial/full application is derived from applied_amount and remaining_amount.

Field	Rule
amount	positive total credit
applied_amount	starts at 0 and increases on application
remaining_amount	amount − applied; never negative
invoice_id	optional at creation, explicit on apply
reason_code	required classifier
approval_status	only draft is editable; approved is applicable
credit_note_reference	invoice retains applied reference(s)

Guided procedure

1. Open the original invoice and establish the exact erroneous amount.
2. Decide whether the case is full cancellation, partial credit, future fee change or cash refund.
3. Create credit note with student, school, optional invoice, date, reason code, description, positive amount and currency.
4. Attach/record supporting evidence according to policy.
5. Review while draft; only draft notes are editable.
6. Submit for independent approval.
7. Approver verifies invoice, amount, reason, currency, prior credits and segregation.
8. Apply an approved credit to the intended invoice. The amount must not exceed remaining credit or valid invoice outstanding.
9. Refresh both returned credit note and invoice.
10. Recalculate or refresh the student summary and verify ageing movement.
11. Verify any configured accounting adjustment separately.
12. Preserve rejected/unused notes according to archive policy; do not reuse a rejected reason silently.

Worked scenario

A student is billed USD 500 tuition. The school later approves a USD 100 bursary adjustment that is not cash. A credit note for USD 100 is created, reviewed and approved. Applying USD 100 changes the invoice outstanding from USD 500 to USD 400, increases the note’s applied amount to USD 100 and reduces remaining to zero. The student summary moves USD 100 out of outstanding receivables. No refund or receipt is created.

Accounting and balance effects

Action	Invoice	Student summary	Cash	Accounting
Create draft credit	no change	no change	no change	none
Approve credit	no amount change until apply	no change	no change	policy-dependent
Apply credit	outstanding decreases	adjusted/outstanding changes after refresh	no change	configured correcting entry may post
Refund payment	separate P4 process	refunded/balance may change	cash outflow	separate posting
Cancel invoice	obligation cancelled	invoiced/outstanding aggregates change	no change	configuration-dependent reversal/correction

Controls and audit evidence

Require original invoice ID, credit ID/number, reason code, supporting decision, creator, approver, amount/currency, application amount, pre/post invoice values, pre/post credit balances, request ID and summary refresh timestamp.

Failure modes

Symptom	Likely cause	Evidence	Safe action	Escalate when
Credit cannot update	not draft	approval state	create authorised correction path	state unexpectedly changed
Credit cannot apply	not approved	approval history	obtain approval	approval exists but service rejects
Insufficient remaining	prior application consumed balance	applied/remaining history	reduce amount or use correct note	history inconsistent
Wrong invoice/student	selection error	IDs and student context	stop before apply; recreate correctly	application already persisted
Balance not reduced	stale summary or failed application	API response and summary timestamp	refresh/recalculate	source invoice changed but summary does not
User expects cash refund	concept confusion	payment/refund records	use P4 refund flow	money already returned outside system

Verification checklist

• Correction type was chosen correctly.
• Credit amount and currency are correct.
• Creator and approver are appropriately separated.
• Credit was approved before application.
• Applied amount does not exceed remaining credit.
• Invoice pre/post outstanding is recorded.
• Student summary was refreshed.
• No payment, receipt or refund was invented.
• Accounting evidence was checked where configured.
• Original invoice remains traceable.

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.

Next lesson

Continue to Student accounts and statements.