--- title: "Automated Reconciliation That Closes the Loop | Fynex" description: "Every payment and payout posts back to Xero or QuickBooks as a journal entry, scored for confidence. PSP deposits broken out, exceptions flagged." url: "/uk/features/reconciliation" --- # 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. *Reconciliation.* ## 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. | | | |---|---| | Auto-matched | 1,284 | | Journals posted | £312,400 | | Needs review | 11 | ## 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. - Reference-match first, with a heuristic fallback on amount, date and payee - A confidence score on every match, so low-certainty pairs surface for review - PSP settlements broken out into individual orders and journal entries - Diagnostic reasoning on every unmatched item, so a human resolves it fast - Duplicate and anomaly detection across payments, refunds and fees ## The same job, with the leaks closed Point tools solve part of it. Fynex runs the whole thing on one platform. | The problem | Other platforms (An AP automation tool + spreadsheets) | Fynex | |---|---|---| | Tie a payment to its order | You match by hand, line by line. | Reference-matched, then scored. | | A PSP pays one lump sum | One line in, hundreds owed out. | Split back into every order. | | Get it into the accounting system | Re-keyed, or a flat CSV import. | Posted as a proper journal entry. | | Something doesn't reconcile | You hunt for the reason. | Flagged with the reason attached. | ## The money in, the books it posts to PSPs and rails on one side, your accounting system kept in sync on the other. Integrates with: Revolut, Wise, Mercury, Brex, Airwallex, Ramp, Bluevine, Bank of America, American Express, Stripe, Xero, QuickBooks, FreshBooks, WooCommerce, monday.com. ## 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. > One recent diagnostic found €2M in hidden fees across 10 processors for a proptech client. ## Questions, answered ### How does Fynex match a payment to an order? It matches on reference first — invoice number, order ID, payment reference. When there's no clean reference, it falls back to heuristics on amount, date and payee, and scores the match so you can see how certain it is. ### What happens to a bulk PSP deposit? Fynex breaks [one settlement](/docs/payouts/what-is-a-settlement-statement-and-how-do-i-read-it/) — say a single Stripe payout — back out into the individual orders behind it, nets off the fees, and posts each as its own journal entry. ### Where do the journal entries go? Straight into your accounting system. Fynex posts to Xero and [QuickBooks](/docs/integrations/how-does-the-quickbooks-connection-work-and-what-syncs/) as proper journal entries, not a flat CSV import you have to re-key. ### What does a confidence score mean? It's how certain Fynex is about a match. High-confidence matches post automatically; anything below your threshold is held for a human to confirm. ### What happens when something can't be matched? It's flagged as needs review with diagnostic reasoning — no matching order reference, amount mismatch, possible duplicate — so a person resolves it in seconds rather than hunting. ### Can it allocate costs to a project or matter? Yes. Entries can be tagged to a project, matter or client, so studios and agencies reconcile and allocate in one pass. ## Close the loop. *Every payment, back in your books* --- The AI finance layer for platforms and operators. It runs the money chain and keeps more of it in your business. One platform instead of a dozen. © 2026 Fynex