iRecon
IngestMatchTies
iRecon
Capabilities

One engine for every account you reconcile.

LegsMatchingGhost entriesReal timeWorkbenchSources and hand-overGoing live
Who it's for

Wherever money moves, iRecon keeps it balanced.

CorporatesBank statements, payment gateways, intercompany, fixed assets.Banks and credit unionsSuspense, accruals, nostro, cards and switch, inter-branch, real-time rails.Payments and fintechGateway settlements, wallets, payouts, real-time rails.InsurancePremium collection, broker accounts, claims payments.Telecom and utilitiesCollection channels, agent float, billing against the bank.Retail and e-commerceStore cash, gateway settlements, marketplace payouts.Shared service centresMany entities, many banks, many currencies.
How it works

Six stages.
You appear in one.

iRecon runs on a schedule you set, or continuously as entries arrive. Each run does the same six things, and the only output that needs a person is the review queue.

Stage 1 of 6 Automatic

Ingest

  • Bank statements, ledger and sub-ledger extracts, files, APIs and database connections.
  • Each source has an expected arrival time, so a missing statement is noticed in the morning, not at month-end.
What your team does here: Nothing, once each source is connected.
Book a session
Stage 2 of 6 Automatic

Normalise

  • Dates, debit and credit signs, currency codes and references are made comparable.
  • A rule written once works across every source.
What your team does here: Nothing. Mapping is set up once per source.
Stage 3 of 6 Automatic

Match

  • Rules run in the order you set: exact first, then within your tolerances.
  • Full or partial matches, across one, two or four legs.
What your team does here: Nothing. Rules are agreed once and changed under control.
Stage 4 of 6 Automatic

Hand over

  • Differences inside tolerance become ghost entries, handed to your core system by API or file.
  • iRecon never writes to your books. Your system stays the record.
What your team does here: Nothing. You chose the accounts when you set up the reconciliation.
Stage 5 of 6 Your team works here

Review

  • Everything no rule could clear arrives in one queue, with the reason it failed and how long it has been open.
  • Match, split or adjust by hand, within the tolerance your role allows.
Your team works here: Only on the items that need judgement.
Stage 6 of 6 Automatic

Evidence

  • A reconciliation statement per account, per run, with ageing and SLA status.
  • The trail shows what matched, on which rule, and who reviewed it.
What your team does here: Sign off. The statement is already built.
Book a session
Automatic
01 / 06 · Ingest
Stage 1 of 6 Automatic

Ingest

  • Bank statements, ledger and sub-ledger extracts, files, APIs and database connections.
  • Each source has an expected arrival time, so a missing statement is noticed in the morning, not at month-end.
What your team does here: Nothing, once each source is connected.
Book a session
Automatic
01 / 06 · Ingest
Stage 2 of 6 Automatic

Normalise

  • Dates, debit and credit signs, currency codes and references are made comparable.
  • A rule written once works across every source.
What your team does here: Nothing. Mapping is set up once per source.
Automatic
02 / 06 · Normalise
Stage 3 of 6 Automatic

Match

  • Rules run in the order you set: exact first, then within your tolerances.
  • Full or partial matches, across one, two or four legs.
What your team does here: Nothing. Rules are agreed once and changed under control.
Automatic
03 / 06 · Match
Stage 4 of 6 Automatic

Hand over

  • Differences inside tolerance become ghost entries, handed to your core system by API or file.
  • iRecon never writes to your books. Your system stays the record.
What your team does here: Nothing. You chose the accounts when you set up the reconciliation.
Automatic
04 / 06 · Hand over
Stage 5 of 6 Your team works here

Review

  • Everything no rule could clear arrives in one queue, with the reason it failed and how long it has been open.
  • Match, split or adjust by hand, within the tolerance your role allows.
Your team works here: Only on the items that need judgement.
Your team works here
05 / 06 · Review
Stage 6 of 6 Automatic

Evidence

  • A reconciliation statement per account, per run, with ageing and SLA status.
  • The trail shows what matched, on which rule, and who reviewed it.
What your team does here: Sign off. The statement is already built.
Book a session
Automatic
06 / 06 · Evidence

See your own run.

Bring one account and we will take it through all six stages with you.

Book a session