Reconciliation for payments teams
Know exactly why your books don't balance.
AnselIQ matches processor, bank and internal ledger data automatically. When something doesn't tie out, it shows you the difference, the movements behind it, and the fix, with every step recorded.
Now onboarding a small group of design partners.
Cash balance
$1,284.50
Unreconciled
$1,940.00
14 movements
In progress
-$15.50
5 reconciliations
Mismatched
-$640.00
4 reconciliations
Cash balance = unreconciled + in progress + mismatched. Final reconciliations net to zero.
The problem
Reconciliation breaks quietly.
A balance with no explanation
The clearing account is off by a few hundred dollars and nobody can say which payouts, fees or deposits make up the gap.
Exceptions without context
A mismatch lands in a spreadsheet or a ticket, separated from the transactions that caused it and from whoever is meant to fix it.
Fixes with no trail
Write-offs and corrections get edited in place, so months later no one can show what changed, when, or why.
How it works
From raw files to a balance you can explain.
-
01
Ingest every source
File feeds pick up processor, bank and internal ledger files as they land in S3, and parse CSV, BAI2 and JSON into movements on a double-entry ledger.
-
02
Match with rules
Define how two sides relate, one-to-one or one-to-many, and which attributes and dates must agree, including offsets like "settles two days later."
-
03
Explain every difference
Every balance breaks down into unreconciled, in-progress and mismatched amounts, and each mismatch shows what came in, what went out, and what it matched on.
-
04
Resolve with a record
Write off, unmatch or wait for the missing movement. Each fix posts a ledger entry, closes its exception automatically, and can itself be reversed.
Mismatches, explained
The answer is on the screen, not in a spreadsheet.
When a payout and its bank deposit don't agree, AnselIQ shows the two totals, the difference, and the exact value they were matched on. The exception that tracks it sits beside the movements, with the actions to resolve it.
- Exceptions are raised automatically when something mismatches or a file goes missing.
- They close themselves when the underlying problem is fixed, so the queue never lies.
- Assignment, status and discussion live on the exception's own thread.
Why it doesn't balance
In
$5,000.00
Out
$5,031.20
Difference
-$31.20
Matched on
payout_id = bank_reference
po_9f3a2c71
Capabilities
Built around how money actually moves.
One-to-one and one-to-many
Match a payout to its deposit, or one settlement to many card transactions. Partial groups wait for the rest to arrive, then get flagged once they've aged past your limit.
Rules on any attribute
Combine string and date attributes from each side, with constants and date offsets, and see which values each reconciliation was matched on.
File feeds with a test bench
Configure CSV, BAI2 or JSON parsing, try it against a sample file before going live, and get an exception when an expected file doesn't arrive.
Built for volume
Ingestion and reconciliation run in resumable batches, so a large file or a long backlog picks up where it left off instead of starting over.
Corrections, never edits
Bad ingests are reversed, not deleted. Write-offs post adjustment entries, and reversing one posts another, so the ledger always shows what happened.
Exceptions that close themselves
Mismatches and missing files resolve automatically when the real fix happens. People handle the judgment calls, with assignment and a discussion thread.
Early access
Become a design partner.
We're onboarding a small number of payments teams to shape AnselIQ with us. Design partners get hands-on onboarding, a direct line to the people building it, and a say in what comes next.
- 1Tell us what you reconcile and where it hurts.
- 2We walk through AnselIQ against a sample of your files.
- 3If it's a fit, we set up your feeds and rules together.