Commission
Staff & Access
Who can sign in, from which approved devices, and what each role may do.
Staff sign-in, devices and sessions are managed by the owner only; every change is
authorised on the server and recorded in the audit log.
Role assignments
Grant or revoke staff access. The owner account is protected; you cannot change your own roles.
SMS / Non-payment
Pick an arrears bucket and draw the non-payment file. Drawing produces the
CSV/Excel and records each policy as “drawn & sent”. The system never sends the SMS —
you send the file through your own SMS provider.
3-stage non-payment cadence (assessed on the 20th)
From the shared payment ledger: Stage 1
(1 month in arrears), Stage 2 (2 months — pending lapse), Stage 3
(lapsed). The monthly 20th job records a warning per policy, lapses Stage-3 policies automatically and —
while the auto-send gate is on — sends the SMS to clients itself. Preview is read-only.
Cadence pipeline monitor — epoch, stage toggles, next-run preview & audit
Arrears are counted from the arrears epoch
onward — earlier months are never counted as missed. Each stage can be toggled on/off; Stage 3 has
separate controls for its message and its lapse action. Whatever the toggles, a policy is
never lapsed without a prior recorded warning. The preview is a true dry-run of the
next scheduled run (the 20th, 08:00): nothing is saved, sent or lapsed.
Open this drawer to load the cadence settings…
Communications
Every member message in one place — non-payment, premium-correction and re-rate
notices, welcome/lapse and ad-hoc — each with its live delivery status. The notice queue
surfaces issues found at payment import: review the member, optionally call first, then send the
SMS. Sends are always staff-initiated — the system drafts, a human sends. Numbers are masked; full numbers
live only in the vault and the provider.
Debit-order worklist
Every member moved from employer payroll to the Voluntary group, and where each
one is in the switch: Awaiting banking → Mandate signed → Debit order active.
Tracking only — no grace: each policy's lapse clock runs exactly as for the rest of the book.
Database Export
Export the whole book of record as a faithful POL360-shape file (one row per
life — main member, every dependent/extended life, and the nominated beneficiary). This is the
highest-PII export in the system: admin/ops-manager only, every export is a single logged
disclosure event, and the file is delivered by a short-lived link to a private store that
auto-deletes within 24 hours. Banking is not included.
Approvals
Pending senior maker-checker change requests for high-risk fields
(inception, agent/employer, identity, beneficiary, clawback waiver). You are the second pair of
eyes — you cannot approve a request you raised, and the database enforces it.
Every decision is recorded in the hash-chained audit log.
Reconciliation
Reconciliation exceptions
Only the payment lines that need a person — ambiguous, overpayment,
underpayment and unmatched. Everything that auto-matched cleanly is hidden. Assign the correct
policy, accept the engine's recommendation, or dismiss the line. Every action is audited; a
resolved line drops off the list. The Shortfalls to reconcile worklist (part-paid
months, oldest first, with Add slice) sits below the table.
Operations
Run the engines: draw billing, import payments and record a manual receipt.
Every run is authorised on the server and written to the audit log. The engines never
move money — they produce, match and record; a human executes payment.
Billing Delivery
Who each employer's monthly deduction file goes to, whether it sends by hand
(Manual) or on a schedule (Automatic), and — per draw cycle — whether every file truly went out.
The run day drives draw + inception lock + send as one event. The system never moves money —
it emails the deduction request file; the employer deducts.
Employer Registry
The master roster of every employer. Each Employer Card holds the employer's
details, canonical code, payroll format, billing-delivery config, and signed agreement. Edit and
onboarding are admin/ops-manager; finance is view-only. Every change is server-authorised and
audited. The system never moves money.
