Skip to main content
For business neobanks

The money arrived. Did the invoice get paid?

Your invoicing system, the account or wallet that received it, the provider that moved it, and the destination each hold one piece of the answer. Recon Layer puts them in one case.

Read access only. We don't move funds or write to your ledger.

How it works

What we read, and what we return.

01

Intent

The invoice: amount, currency, payer, due date, and where the money is meant to end up.

02

Receipt

Where the money first landed - virtual account, wallet, or both. Amount, sender, reference, timestamp.

03

Transit

What happened on the way: conversion rate, transfers, fees, transaction hash. Sometimes nothing happens here, and that's a valid answer.

04

Settlement

Whether what landed matches what you invoiced, and where the difference went.

Example case

Invoice #INV-2041 $12,000 sent, $11,958 landed.

A single case shows where the payment entered, what changed on the way, and why the final amount landed short.

Two receipts. Two route outcomes. One explained delta.

iIllustrative example, not a production customer case.

Invoice reconciliation case

INV-2041
Needs review
Invoice intent$12,000.00
Combined receipts$11,964 equiv.
Final settlement11,958 USDC
IntentInvoicing system

$12,000 USD, ref INV-2041 · virtual account or wallet accepted

Receipt2 source records
Virtual account
Fiat

$6,964 USD

Northwind Ltd · ref INV-2041
Wire fee −$36

Wallet
On-chain

5,000 USDC

Northwind Ltd · memo INV-2041
Receipt confirmed

Matched to one invoice
Transit2 route outcomes
Swap path
Bridge

$6,964 → 6,958 USDC

Network fee −$6
tx 0x7a3f…c412

Direct path
No swap

5,000 USDC unchanged

No conversion or provider hop required

Combined at settlement
SettlementOn-chain

11,958 USDC combined and confirmed at the intended address

Needs review - $42 short of intent.

Both deductions are accounted for: a $36 wire fee and a $6 network fee.

The $42 isn't the problem. Not knowing where it went is.

What we don't do

Nothing changes about how your money moves.

Recon Layer reads records your systems already produce. It doesn't issue invoices, hold funds, execute payments, or write to your ledger.

01

No migration.

Your payment flow stays as it is. No new rails, no re-platforming.

02

Read access only.

We pull from the systems you already use. Nothing is written back.

03

Delivered your way.

Outcomes show up in the case view, or by API and webhook.

FAQ

Questions we hear before the first call.

For the first step, usually. A reference tells you which invoice a credit belongs to. What it doesn't tell you is whether the full amount reached the destination after the wire fee, the conversion spread, and the network fee. If your references already cover that, you don't need us.
It shows its own leg, accurately. Bridge knows what Bridge did; your bank knows what it received. Neither can tell you the invoice settled, because neither can see the other half.
Bridge today, BVNK next. If you're on something else, tell us. We'd rather know what to build than guess.
Neither are we, yet. That's what the call is for.
Bring one invoice

Close the month with
payments you can explain.

Recon Layer turns payment records into review-ready outcomes with explainable matches, complete traceability, and audit-ready evidence.

Explainable matching

See which records matched, and why they matched.

Evidence trail

Keep references, payloads, and notes on the same case.

Exception review

Surface short-paid, duplicate, and unmatched outcomes fast.