Every payment, back in your books
Fynex posts each payment and payout to your accounting as a proper journal entry, scored for confidence — and breaks a PSP deposit back out into the orders behind it.
How reconciliation runs on Fynex
Three steps from setup to settled — then it runs itself.
- 1
Ingest the money
Payments and PSP deposits land in Fynex with every reference attached, so nothing arrives without context.
- 2
Match and score
Fynex matches on reference first, falls back to heuristics on amount, date and payee, and scores how certain each match is.
- 3
Post the journal
Each match posts to Xero or QuickBooks as a journal entry. Anything below your threshold is flagged for review with the reason attached.
The loop, closed
From a bulk PSP deposit to a booked journal entry, with reasoning on anything it can't match.
Reference-match first
Fynex matches each payment to its order on reference before anything else.
Heuristic fallback, scored
No clean reference? Fynex matches on amount, date and payee, and scores it.
PSP deposit, broken out
Fynex splits one settlement into the individual orders and journal entries behind it.
Exceptions explained
Anything unmatched comes with diagnostic reasoning so a human resolves it in seconds.
This morning's reconciliation, already done
Fynex matched every payment it could, broke out the PSP deposit and posted the journals — leaving only what a human needs to see.
The intelligence behind the match
Fynex reads every reference, amount and date, scores how sure it is, and explains anything it can't tie out, so one bulk deposit lands in your books as the hundred lines it really was, and a human only sees what truly needs a human.
The same job, with the leaks closed
Point tools solve part of it. Fynex runs the whole thing on one platform.
The money in, the books it posts to
PSPs and rails on one side, your accounting system kept in sync on the other.
Find what you're leaking, for free
Send us your setup. We run a free diagnostic and show you what your payment stack costs you today.