Nexus

A premium-financed policy has two lifecycles running against each other. The policy has its own states — quoted, issued, endorsed, renewed, lapsed. The loan has its own — applied, approved, disbursed, in repayment, in arrears. When those live in separate systems, every question that matters sits in the gap between them: is this policy still on risk if the borrower has stopped paying, and who is carrying the exposure right now?

• 01 Approval limits and referral rules that exist in policy documents rather than in the system enforcing them
• 02 Disbursement reconciled to the policy after the fact, in a monthly manual match
• 03 Arrears visible to the lender but not to the team servicing the policy
• 04 No audit trail tying a decision to the person and the limit that authorised it

One record holding the cover and the credit together. The authority thresholds the lender already works to become rules the platform applies, so a referral is triggered by the limit rather than by recollection. Settlement posts against the policy that generated the premium, which is what lets the books close without a manual match.

• 01 A single record spanning issuance through renewal, shared with the credit against it
• 02 Financing application, routing, drawdown and instalment schedules inside that same flow
• 03 Underwriting authority expressed as configured thresholds, with each decision recorded against its rule
• 04 Mobile money and card settlement posted to the originating policy as it arrives
• 05 Claims handled against the same record, including on cover still under finance
• 06 Portfolio reporting drawn from operational data rather than a separate extract

What the business can do that it could not before.