Reinsurance Payment Run: Control Every Outgoing Payment
On this page
- Reinsurance Payment Run: Controlling Claim and Premium Payments to Reinsurers and Cedents
- Key Takeaways
- What Is a Reinsurance Payment Run?
- Why Do Reinsurance Payment Runs Go Wrong?
- Which Items Should Enter the Payment Run?
- What Changes When Payments Go Through a Broker?
- How Should Netting Work in a Payment Run?
- How Do You Run a Controlled Payment Run?
- Who Should Approve and Release Payments?
- Why Do Bank Detail Changes Need Special Care?
- How Do Cut-Off Times and Currency Affect the Run?
- Where Does Automation Help?
- Do Market Standards Help Payment Runs?
- Which Metrics Show a Payment Run Is Under Control?
- What Should Heads of Settlements Do Next?
- Key Terms
- Sources
- Frequently Asked Questions
Reinsurance Payment Run: Controlling Claim and Premium Payments to Reinsurers and Cedents
Last reviewed: November 2026
Most reinsurance payment errors are not fraud. They are a correct amount sent too early, to the wrong account, or for a balance the counterparty never agreed.
Short answer: A reinsurance payment run is controlled by letting only agreed, reconciled and due items in, and by separating who prepares, approves and releases it. Every held item needs a recorded reason, and every released item needs bank confirmation.
Key Takeaways
- Gate the run, not just the release. Wrong items are cheaper to stop at proposal than at the bank.
- Separate the roles. The preparer, approver and releaser should be different people.
- Treat bank detail changes as high risk. Verify them by a separate channel before any payment.
- Software checks, people authorise. Reconciliation tools flag issues, but money moves only on human approval.
What Is a Reinsurance Payment Run?
A reinsurance payment run is a scheduled batch of outgoing payments under reinsurance contracts. For a reinsurer, it typically covers claims to cedents, return premiums and premiums to retrocessionaires.
Many payments go through brokers rather than directly. That adds a party, a bank account and a timing step to every item.
Why Do Reinsurance Payment Runs Go Wrong?
Reinsurance payment runs go wrong when items enter the run before they are ready. The payment system then faithfully pays an amount nobody should have released.
Which failures are most common?
The most common failures are unagreed balances, unreconciled amounts and stale bank details. Each one looks normal in a payment file.
- Unagreed balance. The counterparty has queried the statement, but the item still sits in the payable list.
- Unreconciled amount. The payable differs from the treaty calculation, and nobody has checked why.
- Not yet due. Settlement terms allow more time, but the item is paid early and cash leaves too soon.
- Changed bank details. A new account was accepted by email and never verified.
Which Items Should Enter the Payment Run?
Only items that are agreed, reconciled, due and payable to verified details should enter the run. Everything else is held with a reason.
| Item status | Include in run? | Action |
|---|---|---|
| Agreed, reconciled, due, verified details | Yes | Propose for approval |
| Reconciled but counterparty query open | No | Hold until the query is closed |
| Agreed but variance against treaty calculation | No | Investigate the variance first |
| Agreed and reconciled, not yet due | No | Schedule for the run before the due date |
| Bank details changed since last payment | No | Verify by a separate channel, then release |
| Payee or beneficiary not screened | No | Complete sanctions screening |
Held items should not disappear. A held-items report each run shows what is waiting and for how long.
What does the gate look like in practice?
The gate works by testing each candidate item against every rule before approval. Here is an illustrative weekly run for a reinsurer.
| Candidate items | Count | Amount (USD) |
|---|---|---|
| Payables proposed from the ledger | 48 | 21,400,000 |
| Held: counterparty query open | 5 | 2,100,000 |
| Held: variance against treaty calculation | 3 | 1,350,000 |
| Held: not yet due under settlement terms | 6 | 3,900,000 |
| Held: bank details changed, not verified | 1 | 2,800,000 |
| Released after approval | 33 | 11,250,000 |
Nearly half the value was held, and each hold had a reason. The single unverified bank change was the largest item in the run.
What Changes When Payments Go Through a Broker?
Payments through a broker add a party, an account and a timing step. The reinsurer pays the broker, and the broker pays the cedent or retrocessionaire.
Confirm in the broker terms when payment to the broker counts as payment to the counterparty. Then track broker-held items as open until onward payment is confirmed.
Broker remittances often bundle several treaties. Ask for item-level remittance details, or matching on the other side becomes a manual exercise.
How Should Netting Work in a Payment Run?
Netting should follow the treaty settlement terms or an agreed statement, not convenience. Where netting is allowed, record the gross items behind each net payment.
Netting across treaties, counterparties or currencies without that basis creates trouble. Disputed items get buried, and later reconciliation of each balance becomes guesswork.
Netting rights also change if a counterparty fails. Our guide to the reinsurance offset clause explains when netting holds and when it does not.
How Do You Run a Controlled Payment Run?
You run a controlled payment run as a fixed sequence with evidence at each stage. It works in six steps.
- Propose. Select items that are agreed, reconciled and due, and attach the statement reference to each.
- Validate. Check bank details against the verified record, screen payees and confirm currency and cut-off.
- Review held items. List every excluded item with its reason and owner.
- Approve. An approver independent of the preparer signs off within a documented authority limit.
- Release. A separate user releases the approved file to the bank, without the ability to edit it.
- Confirm and close. Match bank confirmations, send remittance details, update open items and chase rejections.
Step six is often treated as optional. Yet a returned payment that nobody chases becomes an aged item and an unhappy counterparty.
Who Should Approve and Release Payments?
Payments should be approved and released by people who did not prepare them. The IAIS expects segregation of duties and clear policies on who can commit the insurer, and for what amounts.
The IAIS also cites the practice of key decisions taken by at least two people, and double signatures. In a payment run, that means two independent approvals above a set threshold.
| Role | Can do | Cannot do |
|---|---|---|
| Preparer | Propose items, attach evidence | Approve or release |
| Approver | Approve within authority limit | Edit payment details or release |
| Releaser | Send the approved file to the bank | Change amounts or payees |
| Bank detail administrator | Record verified changes | Approve payments to the changed account |
System-enforced roles beat policy documents. If one user can do all four, the control exists only on paper.
Why Do Bank Detail Changes Need Special Care?
Bank detail changes need special care because one altered account can divert a large claim payment. Reinsurance amounts are large and counterparties change banks rarely, which makes a change stand out.
Verify every change through a known contact, using a channel other than the one that requested it. Then hold the first payment to the new account for an extra review.
Keep a log of every change request, including the ones you reject. Repeated requests for the same counterparty can be an early warning worth escalating.
How Do Cut-Off Times and Currency Affect the Run?
Cut-off times decide whether a payment settles today or later. A run released after the bank or currency cut-off can miss the due date despite being approved on time.
Plan the run calendar backwards from the cut-offs for each currency. Our guide to cross-border reinsurance settlement explains the credit exposure late settlement creates.
Sanctions checks belong before approval, not after release. See sanctions screening for reinsurance for why a valid claim can still be unpayable.
Where Does Automation Help?
Automation helps most before the run, by proving which items are ready to pay. It does not approve payments or move money.
Bordereaux calculation and reconciliation calculates reinsurer-wise premium and claim shares and net amounts. It reconciles them against bordereaux, master data, premium, claims and settlement records.
Each reinsurer gets a reconciliation status, showing whether records match or need investigation. Finance can use that status as the gate for the payment proposal.
The platform identifies the difference; finance teams determine the cause. Payment approval, release and bank controls stay with your people and banking systems.
Do Market Standards Help Payment Runs?
Market standards help by linking payments to the accounts they settle. ACORD's EBOT standards use Technical Account and Financial Account messages for back-office accounting and settlement.
ACORD's ECOT standards use the Claims Movement message and link with EBOT to complete claims-related payments. Where counterparties exchange these messages, matching payments to items becomes far easier.
Which Metrics Show a Payment Run Is Under Control?
The best metrics show what was held, what went late and what came back. Track them for every run.
| Metric | What it tells you |
|---|---|
| Items held back, by reason | Where upstream processes fail |
| Payments released after cut-off | Whether the run calendar works |
| Bank detail changes awaiting verification | Exposure to diversion |
| Days from agreement to payment | How fast counterparties are paid |
| Rejected or returned payments | Quality of payee data |
| Payments recalled after release | Whether validation caught enough |
What Should Heads of Settlements Do Next?
Heads of settlements should tighten the gate and the roles before adding new tools. These four actions can start with the next run.
- Write the entry rules for the run and publish them to finance and claims.
- Remove any user's ability to prepare, approve and release the same run.
- Require separate-channel verification for every bank detail change.
- Produce a held-items report with reasons for every run.
Key Terms
- Payment run: A scheduled batch of outgoing payments prepared, approved and released together.
- Held item: A payable excluded from a run, with a recorded reason and owner.
- Segregation of duties: Splitting preparation, approval and release between different people.
- Cut-off time: The latest time a bank accepts a payment for same-day settlement in a currency.
- Remittance details: The information sent to a payee showing which items a payment settles.
- Financial Account: An ACORD message used for settlement details between counterparties.
Sources
- IAIS: ICP 8 Risk Management and Internal Controls
- ACORD: Ruschlikon FAQ
- Insurnest: Bordereaux Calculation & Reconciliation
Frequently Asked Questions
What is a reinsurance payment run?
A reinsurance payment run is a scheduled batch of outgoing payments, such as claims to cedents, return premiums and premiums to reinsurers or retrocessionaires. A controlled payment run moves each item through proposal, validation, approval and release, with evidence kept at every stage.
Which items should be included in a reinsurance payment run?
A reinsurance payment run should include only items that are agreed with the counterparty, reconciled to the treaty calculation, due under the settlement terms and paid to verified bank details. Disputed, unreconciled or unverified items should be held back with a recorded reason.
Who should approve a reinsurance payment run?
A reinsurance payment run should be approved by someone other than the person who prepared it, within a documented authority limit. Larger runs or individual payments above a threshold should need a second approver, and approvers should not be able to edit payment details.
Why is bank detail verification important in reinsurance payments?
Bank detail verification is important in reinsurance payments because a changed account number can divert a large claim or premium payment. Changes should be confirmed through a known contact by a separate channel and approved by someone independent before the next payment run.
Should reinsurance payments be netted?
Reinsurance payments should be netted only where the treaty settlement terms or an agreed statement allow it. Netting across treaties, counterparties or currencies without that basis can hide disputed items and make later reconciliation of each balance much harder.
How do cut-off times affect a reinsurance payment run?
Cut-off times affect a reinsurance payment run because a payment released after the bank or currency cut-off may settle a day or more later. Late settlement can breach treaty or claims payment timelines and extend credit exposure on both sides.
What should happen after a reinsurance payment run is released?
After a reinsurance payment run is released, finance should match bank confirmations to each payment, update open items, send remittance details to counterparties and investigate any rejected or returned payments. The run is complete only when every item is confirmed or resolved.
Which metrics show a reinsurance payment run is under control?
Useful payment run metrics include items held back and their reasons, payments released after cut-off, unverified bank detail changes, time from agreement to payment, rejected or returned payments, and payments recalled after release. Trends across runs matter more than any single figure.

Hitul Mistry
CEO, Insurnest
An InsurTech leader with more than a decade of experience across insurance and technology, focused on solving business problems with the help of technology. Has worked with brokers, insurance carriers, and reinsurance firms across the India, UAE, and US markets.
View LinkedIn profile →