Why matching is hard

Nothing ever
matches exactly.

Brokers quote last year’s policy number. Pay short by six dollars. Send the wrong commission. Name the insured five different ways across five systems.

Seven real examples of what comes through our pipeline — and what we do with them.

scroll

First, it’s really hard to get the data out of remittances.

Every broker management system spits out a different shape of PDF. Six real samples — same week, six different formats:

Remittance PDF sample
Remittance PDF sample
Remittance PDF sample
Remittance PDF sample
Remittance PDF sample
Remittance PDF sample

Second, the data on the remittance rarely matches the data in your underwriting systems.

The past 20,000 matches · real production data
97.6%
cleared without a human keystroke
14.8%
had every field agree exactly

Only 1 in 7 receipts arrived clean. The other six needed the AI to bridge a gap somewhere — a stale policy number, a name variant, an off-by-a-few-dollars amount. Here is what those look like.

Example 01 / 07 Matched

When everything lines up.

Broker sent We have on file
Insured
Mainline Freight Co Pty Ltd
Insured
Mainline Freight Co Pty Ltd
Policy
P0306452PR2026AU2
Policy
P0306452PR2026AU2
Amount
$2,212.79
Amount
$2,212.79

Every field agrees. About 1 in 7 incoming receipts looks like this — they resolve in milliseconds without ever touching a person. The rest are below.

Example 02 / 07 Matched

No policy yet — just “TBA”.

Broker sent We have on file
Insured
Eastpoint Joinery P/L
Insured
Eastpoint Joinery Pty Ltd
Policy
TBA
Policy
P0218543PR2026AU0
Amount
$3,487.16
Amount
$3,487.16

The broker bound the policy yesterday and paid for it today — before they had a policy number to quote. We matched on the insured name and the exact amount. The policy number on file gets attached to the receipt automatically.

Example 03 / 07 Matched · split

One payment, two policies.

Broker sent We have on file
Insured
Sandstone Consulting
Insured
Sandstone Consulting Pty Ltd
Sandstone Consulting Pty Ltd
Policy
P0245187PR2026AU0
Policy
P0245187PR2026AU0
professional indemnity
CYB089412PR2026AU0
cyber
Amount
$4,820.00
Amount
$3,247.50
$1,572.50
sums to $4,820.00

The insured carries professional indemnity and cyber under two policy numbers, and the broker pays for both in one line — quoting only the PI policy. The two invoice amounts sum exactly to what has been paid, so the system splits the allocation across both.

Example 04 / 07 Matched · written off

Six dollars short on five thousand.

Broker sent We have on file
Insured
Brackenridge Plant Hire Limited
Insured
Brackenridge Plant Hire Pty Ltd
Policy
P0392641PR2026AU3
Policy
P0392641PR2026AU3
Amount
$4,840.96
Amount
$4,847.20
$6.24 short

Six dollars and twenty-four cents short on a five-thousand-dollar receipt. Inside the ten-dollar write-off threshold, so the variance is written off and the receipt clears straight through. The threshold is set by you, not by us.

Example 05 / 07 Matched

Three open invoices, one match.

Broker sent We have on file
Insured
Granite Civil Group
Insured
Granite Civil Group Pty Ltd
Granite Civil Group Pty Ltd
Granite Civil Group Pty Ltd
Effective date
21 Feb 2026
Effective date
21 Feb 2026
match — same date
15 Jan 2026
21 Mar 2026
Policy
Policy
P0162009PR2026AU0
P0181437PR2026AU0
P0194250PR2026AU0
Amount
$37,612.40
Amount
$37,612.40
$23,140.00
$51,902.15

One payment, three open invoices for the same insured. Without an effective date the matcher would have to guess between them. With one, the right invoice falls out — same date, same amount to the cent. Auto-matched.

Example 06 / 07 Eventual match

The invoice doesn’t exist yet.

Broker sent We have on file
Insured
Risk Counsel Australia (broker ref.)
Insured
Policy
ICA047192634
Policy
no invoice on file
Amount
$41,892.50
Amount

The payment arrived before the underwriter bound the policy. The system flags the underwriter to bind it — and the moment the invoice appears, the receipt auto-matches against it. Today it sits in the queue; in a day or two it resolves itself with no human keystroke. We call this an eventual match.

The 2.4 % — when a human looks at it

So what isn’t auto-matched?

Mostly over- and under-payments that fall outside the write-off threshold your finance team set. They hold for human review — and from the same screen the operator can query the broker or notify the underwriter in a single click.

Example 07 / 07 Held for review

The broker over-paid by twenty-two dollars.

Broker sent We have on file
Insured
Hartford Group P/L
Insured
Hartford Group Pty Ltd
Policy
P0203814PR2026AU0
Policy
P0203814PR2026AU0
Amount
$1,012.30
Amount
$989.66
$22.64 over expected

The broker withheld less commission than expected, so they over-paid by twenty-two dollars. That is above the ten-dollar write-off threshold your finance team set, so the receipt holds for a human to decide rather than be over-allocated to the wrong policy.

This is what AI matching actually has to do.

Not pattern recognition. Judgement under ambiguity — knowing when to match, when to write off, and when to refuse to guess.

See how it works