Finance
Makronexus Finance is the school’s controlled system for defining charges, billing students, recording money received, allocating value, issuing proof of payment, posting balanced accounting evidence, closing periods, reconciling external activity and producing financial evidence.
Audience: school owners, administrators, bursars, accountants, cashiers, credit controllers, treasury officers, auditors, implementers and support analysts
Published curriculum: P1 foundations, P2 configuration, P3 student billing and receivables, P4 collections and receipts, P5 accounting operations, and P6 banking and reconciliation
Current boundary: dashboards, management reporting, statutory reporting, evidence exports and consolidated reporting begin in P7.
Learn the domain, prove configuration, bill the correct population, collect with controlled evidence, post balanced journals, close internal periods, and then reconcile external evidence. A provider success, printed receipt, completed bank import, match score, balanced trial balance or green dashboard is not proof that every financial record is complete and correct.
Published learning path
P1 — Foundations
Start with Choose your learning path. P1 teaches terminology, objects, workspaces, lifecycle dimensions, the internal General Ledger, dates, currencies, exact permissions, approvals and segregation.
P2 — Foundation configuration
P2 verifies readiness, fiscal periods, currencies, Chart of Accounts, posting mappings, fees, concessions, providers, bank accounts, templates, approvals and posting controls. Start at Readiness and dependency order.
P3 — Student billing and receivables
P3 converts verified configuration into controlled obligations. Start at Student billing lifecycle.
P4 — Collections and receipts
P4 converts verified receivables into controlled incoming-funds evidence. Start at Collection lifecycle.
P5 — Accounting operations
P5 converts eligible Finance events into balanced, traceable accounting evidence and controlled close packages. Start at Posting model.
P6 — Banking and reconciliation
P6 connects external bank and provider evidence to Makronexus operational and accounting records:
- Bank statement lifecycle
- Import bank statements
- Match and reconcile
- Settlement and provider reconciliation
- Reconciliation exceptions
- Bank webhooks and operational monitoring
P6 ends when an independent reviewer can reproduce imported statement evidence, match every external amount or explain its exception, reconcile provider gross activity to net bank payout, verify webhook lineage, operate continuous exception controls and prove the separation between internal posting and external reconciliation.
Domain flow
Core record distinctions
| Record | What it proves |
|---|---|
| Fee | reusable pricing and audience configuration |
| Invoice | student-specific obligation |
| Payment Attempt | pre-Payment provider/channel lifecycle |
| Payment | incoming funds recorded by Makronexus |
| Allocation | where Payment value was applied |
| Receipt | numbered evidence issued for a saved Payment |
| Journal document | balanced accounting evidence with source and currency identity |
| Trial balance | server-computed debit/credit equality as of a date |
| Tie-out run | internal ledger-versus-source comparison and review evidence |
| Bank statement import | external statement identity, balances, source and file evidence |
| Bank statement transaction | one external bank movement |
| Reconciliation batch | controlled comparison container |
| Reconciliation item | one external/internal matching unit |
| Provider report | provider’s external transaction or payout evidence |
| Webhook event | received and processed provider message |
| Continuous snapshot | immutable subledger evidence for an as-of date |
| Continuous exception | owned variance or missing-evidence work item |
| Bank payout match | link between expected settlement and external bank credit |
| Financial statement | server-computed GL view for performance, position or cash movement |
A Payment Attempt is not a Payment. A Payment is not bank settlement. A webhook event is not a Payment. A completed statement import is not reconciliation. A match is not period close. A balanced trial balance is not external reconciliation.
P6 control path
Choose the right path
| Responsibility | Recommended path |
|---|---|
| Treasury preparer | bank statement lifecycle → import statements |
| Reconciliation analyst | import → match and reconcile → exceptions |
| Payment operations | provider settlement → webhook monitoring → exceptions |
| Accountant | P5 journals/tie-outs → P6 bank/provider reconciliation |
| Bursar/controller | P6 lifecycle → exceptions → review and close |
| Auditor | provenance → match evidence → gross-to-net → continuous certification |
| Support analyst | import diagnostics → webhook failures → exception lineage |
| Implementer | P2 bank/provider setup → P4 test Payments → P5 postings → all P6 labs |
Mupfure Learning Academy scenario
The curriculum uses a fictional multi-campus school with USD and a configured local currency, bank statement files, mobile-money and gateway reports, delayed settlement, provider fees, refunds, chargebacks, bank-originated charges, webhook retries and continuous control-account comparisons. Bank-specific layouts, provider settlement calendars, country rules and statutory retention remain configuration- or external-policy dependent.
Curriculum status
| Phase | Status | Coverage |
|---|---|---|
| P1 — Foundations | Published | language, objects, lifecycle, GL model, permissions, dates and currencies |
| P2 — Configuration | Published | readiness, periods, accounts, fees, banks, templates, approvals and posting controls |
| P3 — Student billing | Published | applicability, billing runs, invoices, credits, summaries and ageing |
| P4 — Collections | Published | attempts, Payment capture, verification, allocation, receipts, cash controls, returns and exceptions |
| P5 — Accounting operations | Published | posting model, journals, source/GL traceability, controls, trial balance, period close and statements |
| P6 — Banking and reconciliation | Published | statements, provenance, matching, provider settlement, exceptions, webhooks and continuous controls |
| P7 — Reporting and analytics | Next | dashboards, revenue, collections, receivables, cash flow, accounting/statutory reports and evidence exports |
| P8–P11 | Not yet published | governance, operating playbooks, implementation, labs and certification |
P6 proves external bank/provider comparison and exception control. It does not define every management KPI, statutory filing, consolidation rule or board report. Continue to P7 when published.
Start now
- New to Finance: Choose your learning path
- Ready to bill: Student billing lifecycle
- Ready to collect: Collection lifecycle
- Ready to post: Posting model
- Importing a statement: Import bank statements
- Matching bank/provider evidence: Match and reconcile
- Investigating a difference: Reconciliation exceptions
- Monitoring callbacks: Bank webhooks and operational monitoring