Finance in plain language

Finance answers five different questions:

1. What should the school charge?
2. What does a student or responsible payer owe?
3. What money did the school receive?
4. How is the event represented in the accounts?
5. What external or audit evidence confirms it?

Those questions require different records. Combining them into one “transaction” would make corrections, approvals, reconciliation and audit unreliable.

Audience: all Finance users
Learning time: 20 minutes

Learning outcomes

You will be able to:

• explain the difference between a fee, invoice, payment, allocation, receipt and journal entry;
• describe the normal flow from pricing to reporting;
• distinguish internal Makronexus evidence from bank or provider evidence;
• identify where approval, verification and reconciliation occur;
• recognise why a success message is not the final proof of completion.

The five layers

Layer	Plain-language purpose	Examples
Configuration	defines how Finance should operate	fee structures, payment plans, bank settings, receipt templates, accounting books, posting rules
Obligation	records what is owed	invoice, invoice line, credit note, outstanding amount
Collection	records money received and where it is applied	payment, payment allocation, receipt
Accounting	classifies financial effect	GL account, journal entry, trial balance
Settlement and evidence	confirms external movement and control	payment attempt, bank statement line, reconciliation match, approval history, audit event

The basic student-finance story

The sequence shows responsibilities, not a guarantee that every integration is synchronous. A provider can remain pending; posting can be blocked by configuration; reconciliation can occur later.

Exact meanings

Fee structure

A fee structure is configuration that describes a charge, such as tuition or boarding. It can contain amount, currency, frequency, audience, due-date rules, discount or installment settings, accounting codes and approval metadata.

A fee structure is not proof that a specific student owes money. The obligation is represented by an invoice or another supported billing record.

Invoice

An invoice is a student billing record. It identifies the billed student, billing period, line items, total amount, amount paid, amount outstanding, currency, due date, communication state and approval state.

An invoice is not proof that money was received.

Payment

A payment records incoming funds in Makronexus. It includes an amount, currency, method, date, student, anchor invoice, references, status, verification state, reconciliation state and refund state.

A payment is not the printable proof-of-payment document and is not automatically the same as a bank settlement.

Payment allocation

A payment allocation states how much of a payment is assigned to an invoice. One payment can be distributed across multiple invoices where supported. Allocation explains why an invoice balance changed.

An unallocated or partially allocated payment can exist even though money was recorded.

Receipt

A receipt is the official or configured proof-of-payment document issued from a payment. It has its own number, date, type, delivery state, cancellation state and links to invoice allocations.

Cancelling a receipt does not mean the same thing as refunding the payment. The receipt API unlinks the cancelled receipt from the payment; the payment’s monetary correction is a separate controlled action.

Credit note

A credit note reduces an invoice obligation when approved and applied. It carries its own amount, remaining amount, reason and approval state.

A credit note is not a cash refund. It changes what is owed; a refund changes money retained from a payment.

Journal entry

A journal entry is the double-entry accounting record. It has a debit account, credit account, amount, entry date, source and status.

Posted history is corrected by an offsetting reversal, not by destructive editing.

Bank statement line

A bank statement line is external bank-side evidence. It does not by itself prove which student or invoice the movement belongs to.

Reconciliation

Reconciliation is the control that links or compares external activity with Makronexus records and investigates differences.

Reconciliation is not payment creation and is not the same as verifying that a cashier entered the correct details.

One event through the layers

Mupfure Learning Academy bills Tariro USD 500 tuition. A guardian pays USD 300 by bank transfer.

Step	Record	Result
1	Fee structure	tuition pricing and policy exist
2	Invoice	Tariro owes USD 500
3	Payment	Makronexus records USD 300 received by bank transfer
4	Allocation	USD 300 is applied to Tariro’s invoice
5	Invoice balance	amount paid becomes USD 300; amount outstanding becomes USD 200
6	Receipt	proof of the USD 300 payment is issued if the receipt workflow is completed
7	Journal	accounting evidence is created when configured posting succeeds
8	Bank statement	the external USD 300 movement appears when bank evidence is available
9	Reconciliation	the bank movement and Makronexus records are matched and reviewed

Controls that users often confuse

Control	Question it answers	Typical evidence
Validation	Is the submitted data structurally and logically acceptable?	field error, rejected request, business-rule message
Approval	Did an authorised reviewer accept the request or object?	approval status, history, approver and timestamp
Verification	Was a payment checked according to the payment verification workflow?	is_verified, verifier and verification timestamp
Posting	Was the operational event classified in the internal GL?	journal entry, source type, source ID and posting status
Reconciliation	Does Makronexus agree with bank/provider or control data?	reconciliation status, bank line, batch or match reference
Certification	Did an independent actor certify an exact control state?	scan, fingerprint, certifier and certification timestamp
Audit logging	Who performed or attempted a mutation?	actor, action, resource, request/response evidence and time

Why status matters

A record’s status determines what can happen next.

Examples supported by current contracts include:

• invoices with approval states such as draft, pending, approved, rejected and cancelled;
• invoice payment states pending, partial and paid;
• payments draft, pending, processing, completed, failed, cancelled, refunded, reversed or partially_refunded;
• journal entries draft, posted or reversed;
• receipt templates draft, published or archived.

Do not assume similar words have identical meaning across objects. A pending payment, pending receipt approval and pending invoice approval are separate states.

What “complete” means

A Finance task is complete only after the evidence appropriate to that task is checked.

Task	Minimum verification
Create pricing configuration	active/effective state, amount, currency, scope, approval and accounting mapping where required
Bill a student	invoice exists, line totals reconcile, due date is correct, approval and communication state are understood
Record a payment	amount, currency, method, student, invoice reference, payment number and status are correct
Allocate payment	allocation total is valid and invoice outstanding amount changed as expected
Issue receipt	receipt number, amount, invoice allocations, delivery and cancellation state are correct
Post accounting	journal is balanced by construction, source is traceable, accounts are valid and status is posted
Reconcile	external evidence, internal record, amount, currency, date/reference and exception outcome agree

Never use the receipt alone to prove settlement

A receipt proves that Makronexus issued a document for a recorded payment. Bank or provider settlement and reconciliation require their own evidence.

Knowledge check

1. Does a fee structure mean every student owes the fee?
2. Can a payment exist before it is reconciled?
3. Is cancelling a receipt the same as refunding a payment?
4. Which object reduces an invoice without representing cash returned?
5. Which object is the internal accounting source?
6. Why can one amount appear on a payment, receipt, invoice and bank statement?

Answer guide

1. No. Billing creates the student obligation.
2. Yes. Payments default to unreconciled.
3. No. They are separate controlled actions.
4. A credit note.
5. The General Ledger and its journal entries.
6. Each record answers a different operational or control question.

Continue

• Glossary
• Domain map
• Core objects and relationships