How ReconIQ Works

Files arrive — nobody touches them

When a custodian or counterparty file lands, ReconIQ picks it up automatically. It checks whether it has seen the file before — duplicates are set aside, never processed twice — reads it according to the format configured for that source, and loads the data. Malformed files are flagged, never silently skipped.

The matching engine pairs everything it confidently can

Matching runs in passes, from strictest to most flexible. First, records that agree exactly. Then sensible tolerances: small amount differences, near-identical descriptions, aggregated postings that roll up to one line on the other side. Your team's own matching rules for known situations run alongside. The large majority of records pair off here without anyone lifting a finger.

The noise filter sets aside what isn't a problem

Postings that always settle a day later. Small accruals that self-clear. Recurring quirks of a particular custodian file. ReconIQ recognises these known artifacts and sets them aside automatically, each one labelled with the reason — “timing, settles next run”, “accrual below threshold”.

They are not deleted and not hidden. A counter shows how many items were set aside; one click shows exactly what and why; one click brings any of them back — and the system learns from that.

AI suggests matches for what's left

For genuinely unmatched items, the AI looks for the pairings a person would spot: similar security, amounts that fit, dates that line up. Every suggestion carries a confidence score and a written reason. High-confidence suggestions can be applied automatically with a full record of why; everything else waits in a review queue where your team accepts or rejects — and the threshold between the two is yours to set.

The AI never clears a break on its own judgment. It pairs records, and only when the evidence is strong.

Real breaks arrive with context, not just a flag

Where ReconIQ can explain a break — a dividend, a stock split, a trade that hasn't settled yet — it attaches that explanation to the row. Your investigation starts with the likely cause in front of you, not a bare difference.

Your team decides, and every decision is recorded

Matching manually, unmatching, commenting, signing off — every action is written to a permanent audit trail: who, what, when, and why. Sign-off follows a maker-checker pattern, so completed reconciliations carry a second pair of eyes. Nothing the system or a person does is invisible after the fact.

Breaks that persist are tracked, not forgotten

Open items are aged automatically. Recurring breaks are fingerprinted, so “we've seen this exact break for nine days running” is something the dashboard tells you — not something anyone has to remember.