Dates, periods, currencies and dependencies

A correct amount in the wrong school, currency, date or period is still wrong. Finance users must state context explicitly.

Audience: every Finance role
Learning time: 25 minutes

Learning outcomes

You will be able to:

• distinguish tenant, school, academic and financial context;
• identify the date that controls an object or statement;
• recognise currency and exchange-rate dependencies;
• explain why a closed or unconfigured period can block downstream work;
• collect complete context when comparing balances.

Scope hierarchy

A tenant can contain multiple schools. School-scoped Finance requests use the selected school, an X-School-Id header or equivalent session context. APIs enforce tenant isolation.

Context types

Context	What it controls	Example
Tenant	organisational data-isolation boundary	Mupfure Education Group
School	operational and accounting scope	Mupfure Learning Academy
Academic year	teaching/billing year reference	2026 academic year
Term	optional billing and due-date context	Term 2
Financial year	accounting reference where configured	FY2026
Financial period	posting and close window	May 2026
Currency	monetary unit on the record	USD
Timezone	interpretation of timestamps and cut-offs	school or deployment timezone

Academic and financial calendars can overlap, but they answer different questions.

Date fields by object

School fee

Field	Meaning
academic_year_id	academic year the pricing belongs to
term_id	optional term; null can represent annual pricing
financial_year_id	optional accounting reference
due_date	expected payment date
payment_deadline	hard deadline when configured
effective_from	date the fee becomes effective
effective_until	optional end of validity
early_payment_discount_deadline	deadline for configured early discount
refund_deadline	policy deadline where configured

Current fee creation can default academic year, term, due date or effective date from school context. Review the resolved values instead of assuming the default was correct.

Invoice

Field	Meaning
invoice_date	billing issue date
billing_period_start / billing_period_end	service/charge coverage
due_date	payment deadline
sent_date	communication evidence
late_fee_date	date late fee was applied
adjustment_date	manual adjustment date
refund_date	invoice refund metadata date where used
approved_at	approval timestamp

Invoice date, billing period and due date are separate facts.

Payment

Field	Meaning
payment_date	date funds were recorded as received
created_at	system creation timestamp
verified_at	internal verification time
reconciled_at	reconciliation time
cheque date	method-specific instrument date
refund metadata	refund control time and reference

A backdated payment date and a current creation timestamp can both be valid, but the difference must be visible and authorised.

Receipt

Field	Meaning
receipt_date	issuance date
created_at	system creation timestamp
sent_date	most recent delivery timestamp
cancelled_at	cancellation timestamp
template version dates	document design lifecycle

Journal and statements

Object	Date basis
Journal entry	entryDate
Trial balance	as-of date
Balance sheet	as-of date
Income statement	from/to period
Cash flow	from/to period

Date decision flow

Currency on core objects

Object	Currency behaviour
School fee	required currency; API does not universally normalise case
Invoice	required ISO code plus optional base/foreign amount and exchange-rate metadata
Payment	required currency; current contract enumerates USD, ZWG, ZAR, EUR and GBP
Allocation	carries currency
Receipt	required currency, with settings fallback when applicable
GL journal	carries currency
Statement	accepts a currency filter
Bank statement line	external currency evidence

Do not silently convert

Never change an amount’s currency merely to make totals agree. Record or use an authorised exchange rate, its source and effective date where the workflow supports it.

Exchange-rate questions

Before using a rate, identify:

• source;
• quote direction;
• effective date and time;
• base and transaction currency;
• approval or certification requirement;
• rounding rule;
• whether the rate is for operational capture, accounting posting, settlement or presentation;
• whether manual rate use requires a separate permission or approval.

P1 does not declare one universal rate source.

Multi-currency example

Mupfure issues a USD invoice and receives a configured local-currency payment.

The workflow may require:

1. source invoice amount and currency;
2. payment amount and currency;
3. exchange rate and source;
4. converted/base amount where supported;
5. allocation rule;
6. journal currency and mapping;
7. provider or bank settlement currency;
8. reconciliation difference and rounding evidence;
9. approval for manual or exceptional rates.

The exact procedure is published in later phases after each route is verified.

Period controls

A financial period is a control boundary for accounting activity.

Possible controls include:

• open/closed state;
• allowed posting dates;
• required tie-outs;
• unresolved posting exceptions;
• approval completion;
• reconciliation readiness;
• certification evidence.

The Period Close workspace and controls-readiness pages indicate that close is more than choosing a date. P5 documents the exact close procedure.

Configuration dependencies

Not every feature requires every node, but a downstream error can originate in upstream configuration.

Compare reports safely

When comparing two figures, record:

Comparison dimension	Example
Tenant	Mupfure Education Group
School	Mupfure Learning Academy
Statement/report	trial balance
As-of or date range	31 May 2026
Currency	USD
Status population	posted journals only
Included schools/accounts	school plus tenant defaults
Generated time	1 June 2026 08:15
Exceptions	two unresolved posting exceptions

Without the dimensions, “the totals differ” is not reproducible.

Localisation boundary

Makronexus fields can support:

• country-specific currency;
• regulator or ministry references;
• tax metadata;
• statutory receipt/invoice numbers;
• local providers;
• retention or reporting configuration.

A field is not compliance assurance. The school must confirm local requirements with qualified advisers and the applicable provider or regulator.

Troubleshooting table

Symptom	Likely cause	Evidence to inspect	Safe action
Record appears in wrong school	stale or incorrect school context	selected school, header, record school ID	stop and escalate before further mutation
Totals differ by currency	mixed currencies or rate basis	object currencies, rate, source and date	compare like-for-like or use authorised conversion
Statement differs from dashboard	different date/status/source population	report parameters and posting state	align scope and regenerate
Posting date rejected	period or date control	period state, entry date, readiness exception	request authorised period resolution
Fee defaults unexpected term	current school calendar default	resolved academic year/term fields	correct before billing
Bank line cannot match	currency/date/reference mismatch	statement line and payment evidence	investigate; do not force a false match

Verification checklist

• Correct tenant
• Correct school
• Correct academic year and term
• Correct financial year and period
• Correct operational date
• Correct accounting date
• Correct amount and currency
• Correct rate, source and effective date where applicable
• Correct timezone interpretation
• Correct report parameters
• Correct period and approval state

Knowledge check

1. Is invoice date the same as due date?
2. Does a USD payment automatically settle a local-currency invoice without rate evidence?
3. Which statement types use an as-of date?
4. Why can creation time differ from payment date?
5. Does a tax field prove local compliance?

Answer guide

1. No.
2. No.
3. Trial balance and balance sheet.
4. The economic date can be backdated while system capture occurs later.
5. No.