Finance domain map
The domain map is the shared mental model for the entire Finance curriculum. It shows responsibility and evidence boundaries, not merely menu hierarchy.
Audience: bursars, accountants, administrators, auditors, implementers and support analysts
Learning time: 25 minutes
Learning outcomes
You will be able to:
- describe the main Finance subdomains;
- identify which records originate inside or outside Makronexus;
- trace dependencies from configuration to reporting;
- recognise where controls cross multiple workspaces;
- identify relationships that remain configuration-dependent.
Domain responsibility map
Subdomain boundaries
Configuration
Configuration answers how the school intends Finance to operate.
It includes:
- fee structures and payment plans;
- accounting books and Chart of Accounts;
- bank accounts and payment providers;
- process setup and approval matrices;
- receipt templates and numbering;
- posting policy, rules, mappings and readiness controls.
Configuration changes can affect future transactions and, depending on the field, reporting or integration. P2 documents the dependency order.
Billing
Billing answers what a student or responsible payer owes.
The verified billing model includes:
- fees as pricing configuration;
- billing runs as bulk invoice operations;
- invoices and line items;
- invoice payment state and amount outstanding;
- discounts and credit notes;
- student financial summaries.
Collections
Collections answers what money Makronexus records as received and how it is applied.
The verified collection model includes:
- payment attempts for provider-oriented state;
- payments for recorded funds;
- allocations across invoices;
- receipts as proof documents;
- cashier, cash-up, custody and deposit control workspaces.
Accounting
Accounting answers how the economic event is classified and reported.
The verified internal GL includes:
- tenant-default and school-specific accounts;
- manual and operationally sourced journal entries;
draft,postedandreversedjournal states;- trial balance, income statement, balance sheet and cash flow;
- ledger exports for packaging and external handoff.
Payments and banking
This subdomain connects Makronexus records to providers, banks and settlement evidence.
It includes:
- bank settings;
- Stripe, PayNow, InnBucks, mobile-money and bank-transfer workspaces;
- payment attempts;
- bank statements;
- reconciliation;
- webhooks and posting exceptions.
A route’s existence does not prove that the provider is enabled for every school.
Controls and assurance
Controls answer who may act, who reviewed the action, and whether evidence is complete.
It includes:
- exact abilities;
- approval matrices and requests;
- posting controls;
- validation and business rules;
- audit events;
- readiness checks;
- access-control scans and independent certification;
- reconciliation and close evidence.
Object relationship model
Relationship notes
- A school fee can price multiple invoice lines.
- An invoice contains one or more line items.
- A payment currently carries an anchor invoice and can also carry manual allocations across invoices.
- A receipt is issued for a source payment and includes invoice-allocation evidence.
- A journal entry uses one debit and one credit account in the current GL API model.
- Operational records can be journal sources when posting is configured.
- A bank statement line and a payment can be related through reconciliation evidence.
- Approval and audit evidence are separate from the economic object.
Internal versus external truth
| Evidence | Owner | What it proves | What it does not prove alone |
|---|---|---|---|
| Invoice | Makronexus | recorded obligation | money received |
| Payment | Makronexus | recorded incoming funds | external settlement |
| Receipt | Makronexus | proof document issued | bank settlement or reconciliation |
| Journal entry | Makronexus GL | accounting classification | bank settlement |
| Provider callback | provider and integration | provider-side event delivered | final bank statement match |
| Bank statement line | bank | bank-side movement | correct student allocation |
| Reconciliation record | Makronexus control process | reviewed relationship or difference | approval of unrelated actions |
| Audit event | Makronexus | actor/action trace | correctness of the business decision |
Dependency order
The order is a conceptual readiness sequence. P2 verifies the exact configuration procedure and which dependencies are mandatory for each feature.
Mupfure scenario trace
Mupfure bills Tariro for tuition and receives a bank transfer.
| Domain | Object or evidence |
|---|---|
| Configuration | USD tuition fee, school bank account, receipt template, GL mapping |
| Billing | invoice and line item |
| Collection | bank-transfer payment and allocation |
| Evidence | receipt and audit event |
| Accounting | sourced journal entry and GL balance |
| External | bank statement line |
| Control | payment verification and bank reconciliation |
A missing item does not automatically mean failure. It may mean the workflow stage is not complete, the feature is not configured, or the evidence is not applicable. The reviewer must distinguish those cases.
Boundary decisions
The following claims remain deliberately limited in P1:
| Topic | P1 statement |
|---|---|
| Automatic posting for every object | configuration-dependent; do not assume |
| Exact journal mapping for tuition or cash | configured mapping; examples remain illustrative until P5 |
| Provider availability | school/provider configuration-dependent |
| Tax and statutory treatment | external policy and country-pack dependent |
| Universal student-account ledger table | not claimed; the workspace combines verified Finance records |
| One approval lifecycle for every object | not claimed; each object has its own states and permissions |
| Every navigation permission matching API permission exactly | not claimed; backend remains authoritative |
Practice
Place each item in its primary subdomain:
financial_payment:reconcile- receipt template
- credit note
- journal reversal
- PayNow callback
- trial balance
- access-control certification
Answer: payments/banking control; configuration; billing; accounting; external integration; accounting/reporting; controls/assurance.