Premium billing

From bound to banked.

Binding a policy derives its installment schedule, issues the down payment and posts written premium. Every endorsement after that revises what has not been billed yet.

Premium billing examples

The schedule follows the policy. Billing reacts to the lifecycle you already configured, so nothing is keyed twice and there is no second system to reconcile at month end.

[01]

Pinned, not copied.

A schedule points at the exact plan version the policy was sold under. Change the plan tomorrow and this term keeps billing the way it was quoted.

[02]

Derived at bind.

The premium is split, the first invoice goes out, and written premium posts to the ledger the moment the policy binds.

[03]

Revised, not reissued.

A mid-term endorsement lands on the installments that have not gone out. Invoices already sent stay as they were sent, and a credit memo covers the rest.

[04]

Earned to the day.

Cancel mid-term and the schedule earns what the policy was on risk for. Whatever the payer paid beyond that comes back as return premium.

“An endorsement used to mean rebuilding the whole schedule by hand. Now it moves the installments that have not gone out and leaves the rest alone.”
Billing managerProgram carrier · 12 states

Billing your way. A payment plan is a short list of decisions you make per program. Author it in settings, version it like everything else you configure, and attach it to the products that use it.

The down payment

Decide what the payer hands over at bind, as a share of the term premium. Take the whole term on a single invoice, or take a slice and spread the balance.

One ledger, no cached balances. What an invoice has been paid is a sum over the rows that paid it, so nothing can quietly drift out of agreement with the money.

A premium subledger

Written, endorsed, audited and cancelled premium all post as signed rows against the bound term.

Append-only by design

A correction is a linked reversal row. Nothing in the money tables is edited away or deleted.

Four eyes on money out

A refund or a payout needs an approval from someone other than whoever requested it.

Collections that run on a timer. Billing carries its own state, so a policy can be in force and past due at once without either side of the house misreading the other.

Past due.

An installment passes its due date and the schedule says so. The policy does not move: being late is a billing fact, and billing acts on it alone.

The grace window closes.

The plan decides how many days a payer gets. When they run out a delinquency case opens against the invoice, and there is never more than one live case per invoice.

Cured, or escalated.

Payment clears and the case closes. Nothing arrives and billing fires the non-payment event the plan named, which on the shipped plans lapses the policy with reinstatement as the way back.

The money desk, in one place. Cash in, cash out and what is still owed, all read from the same rows rather than from three exports that agreed last Tuesday.

Money that arrived.

Cards, bank debits, checks and wires in one queue. Collection sits behind a single interface, so the processor you settle through is a configuration choice.

Money owed onward.

Producer commission and carrier remittance stay open as obligations until a disbursement settles them, in full or in part.

Receivables at a glance.

Outstanding, past due, collected in the last thirty days, unapplied cash and the aging buckets behind them.

Bill one of your programs live.

Bring a payment plan you actually sell and the endorsement that always breaks the schedule. We will derive it on the call.

Usually 30 minutes, with an underwriter on the call.