Reconciliation Variance Root Cause in Reinsurance

Reconciliation Variance Root Cause: Finding Why Reinsurance Numbers Don't Match, Faster

Last reviewed: November 2026

The same 48,312 difference appears for the third quarter running. Each time someone clears it with a journal, and nobody writes down why.

Short answer: Finding a reconciliation variance root cause means tracing a mismatch to the process or data fault behind it. Narrow the scope, read the variance pattern, test one cause at a time, then fix it at source.

Key Takeaways

• A variance is a symptom. Clearing it with a journal treats the symptom and guarantees a repeat.
• The shape of the number is a clue. Size, sign and behaviour over time often point straight to the cause.
• Fix at the source. A correction in the ledger does not fix a wrong rate in the treaty set-up.
• Code every cause. A coded log shows which processes and counterparties generate most breaks.

What Is a Reconciliation Variance Root Cause?

A reconciliation variance root cause is the underlying reason two reinsurance figures disagree. The variance is what you see, while the root cause is the fault that created it.

Two levels are worth separating. The immediate cause might be a missing claim row, while the root cause is a cedent extract that drops claims paid after a cut-off time.

Why Do Reinsurance Numbers Fail to Match?

Reinsurance numbers fail to match because the same transaction passes through several parties, systems and periods. Each handoff can change timing, scope, rate or currency.

Many of these begin before accounting sees the data. Our article on hidden data conflicts in reinsurance shows how underwriting, claims and finance can hold different versions of the same figure.

How Does the Shape of a Variance Point to Its Cause?

The shape of a variance often points to its cause before anyone opens a file. Check the size, the sign and how it behaves next period.

The divisible-by-nine test is an old accounting rule that still works. Swapping two adjacent digits always creates a difference that nine divides exactly.

The sign test matters too. ACORD's GRLC standards require a reversal technical account to carry the original amounts with the sign reversed, so a missed sign flip doubles the error.

What Does Root-Cause Decomposition Look Like?

Root-cause decomposition splits one total variance into its separate causes. A single number rarely has a single cause (illustrative figures below).

The ledger shows 26,450 more owed to a quota share reinsurer than the bordereau does. Investigation splits it three ways.

Only the first component needs a permanent fix. The timing item reverses next quarter, and the rounding needs an agreed rule and a small tolerance.

How Do You Find the Root Cause Step by Step?

You find the root cause by narrowing scope before you read detail. The process works in six steps.

1. Size and sign it. Record the amount, which side is higher, and whether it existed last period.
2. Narrow the scope. Break the total by reinsurer, contract, section, underwriting year and currency until it sits in one cell.
3. Read the shape. Compare the remaining variance with the pattern table above.
4. Test one hypothesis. Check the single most likely cause against the source document, then move to the next.
5. Fix at the source. Correct the treaty set-up, the extract or the booking rule, not just the balance.
6. Code and log it. Record cause code, amount, owner and fix date in a shared log.

Step two does most of the work. A variance that is unexplained at portfolio level is often obvious once isolated to one section and one year.

Why Do Plug Journals Make Variances Worse?

Plug journals make variances worse because they hide the fault while leaving it in place. The reconciliation balances, but the true position with the reinsurer stays wrong.

They also destroy the evidence. Next quarter, nobody can tell a new variance from the old one returning.

If a temporary adjustment is unavoidable at close, label it with a cause code and an owner. Then reverse it once the source is fixed.

How Do You Tell a Timing Difference From a Real Error?

A timing difference reverses in full in the next period, while a real error persists or grows. Track each variance across at least two periods before closing it.

Set a rule for how long a timing label can stand. If the item has not reversed after one further period, reclassify it and investigate.

Watch for partial reversals. A timing item that only half reverses is usually hiding a smaller real error underneath.

Who Should Own Each Root Cause?

Each root cause should be owned by the team that controls its source. Accounting finds the break, but it often cannot fix it alone.

Rekeying causes deserve special attention. Our article on duplicate data entry between underwriting and accounting explains why removing the second entry beats checking it.

Where Does Automation Help?

Automation helps by finding and locating differences quickly, so people spend their time on causes. It does not diagnose the cause for you.

Reinsurance bordereaux reconciliation reconciles bordereaux, master data, premium, claims and settlement. It identifies variances and mismatches and shows reconciliation status for each reinsurer.

That covers steps one and two of the process above. The platform identifies the difference, and your finance team determines the cause and the fix.

Standard messaging also reduces breaks at source. ACORD reports that PartnerRe maps 91% of financial account items automatically to the corresponding technical balance.

For the wider multi-cedent picture, see manual bordereaux reconciliation across cedents.

Which Metrics Show Root-Cause Work Is Paying Off?

The right metrics show whether variances are being eliminated, not just cleared. Track them each quarter.

What Should Heads of Reinsurance Accounting Do Next?

Heads of reinsurance accounting should make root cause a required field, not an optional note. Start with the variances that recur every quarter.

• Agree a short list of cause codes and use it for every variance.
• Ban uncoded plug journals at quarter close.
• Assign permanent fixes to the team that owns the source.
• Review the cause log with treaty operations every quarter.

Key Terms

• Variance: The difference between two figures that should agree, such as a bordereau and the ledger.
• Root cause: The process or data fault that produced a variance and will reproduce it unless fixed.
• Timing difference: A variance caused by two sides booking one transaction in different periods.
• Plug journal: A balancing entry posted to clear a variance without correcting its cause.
• Cause code: A standard label recording why a variance occurred.
• Transposition error: Two digits swapped during entry, creating a difference divisible by nine.

Sources

• ACORD: GRLC FAQs on technical accounts and corrections
• ACORD: PartnerRe's Tangible Benefits with Ruschlikon Messaging (29 September 2022)
• Insurnest: Reinsurance Bordereaux Calculation and Reconciliation