Premium Settlement Reconciliation Agent
Reconciles card and direct debit premium settlements to the premium ledger.
- Industry
- Insure AI
- Department
- Finance
- Team
- Accounting Operations
- Kind
- Investigator
- Approver
- Treasury Operations Manager
- Code
- FIN-17
It reconciles each premium settlement run from the card and direct debit processors to the premium ledger, policy by policy. It explains shortfalls from chargebacks, returned debits, processor fees, refunds netted in the run and cutoff timing, and reopens collection on policies whose payment reversed. **The problem it solves:** Why the settlement run differs from the premium ledger: chargebacks, returned debits, fees, netted refunds or cutoff timing.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the payments platform: the settlement file and the premium receipts expected in the run..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Treasury Operations Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the general ledger: it posts fee entries and records the reconciliation; reopens collection on reversed payments. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The settlement reconciliation procedure, processor fee schedules, settlement cutoffs, chargeback and return reason codes and the premium ledger rules.
Reads from
the payments platform: the settlement file and the premium receipts expected in the run.
Acts in
the general ledger: it posts fee entries and records the reconciliation; reopens collection on reversed payments.
Hands back
An object with run_id, matched_amount, differences (a list, each with policy_number, amount, cause and action) and status (reconciled, explained or open).
Asks a person when
A run stays unreconciled past 24 hours, or the difference is not explained by fees, timing or reversals.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Run tolerance (USD) | 10 | A run differing by less is reconciled. |
| Cutoff grace (minutes) | 30 | Payments this close to cutoff may fall into the next run. |
| Post processor fees below (USD) | 100 | Smaller fee differences post themselves. |
| Escalate after (hours) | 24 | An unreconciled run this old goes to the approver. |
| Expected runs a day | 2 | Fewer runs means a missing file. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Reconcile a run when it differs by less than 10.
- Treat payments within 30 minutes of cutoff as timing until the next run shows them.
- Post processor fee differences below 100.
- A chargeback or returned debit reopens collection on the policy and never stays as a ledger difference.
- Flag a missing run when fewer than 2 arrive, and escalate runs unreconciled after 24 hours.
See the Premium Settlement Reconciliation Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.