Stablecoin Close Desk · for payout and payroll platforms

Every stablecoin dollar, tied out.
Every break, explained.

Chain, provider, bank and books, matched daily inside your own cloud. Close in days, and have the answer when your partner bank calls.

Book a discovery call See a sample break report

Runs in your own cloud
Read-only keys
No custody
Bridge · Circle · BVNK · Stripe

Background ledger · synthetic data

The problem

Four sources of truth. They drift every day.

Settlement never stops. Banks do.

A USDC transfer confirms any hour, any day. Wires post only on banking days, so Friday's payouts leave a gap in the books until Monday.

No reference on the transfer

A hash, a wallet and an amount. No memo, no invoice number. Someone matches it by hand, from memory.

Double-counted, quietly

Bridge sends and receives booked twice. Fees and spreads left as unexplained lines.

Your provider's dashboard isn't a control. Someone on your team untangles it by hand every month. When volume grows, or that person leaves, the books stop tying out, and the partner bank is the first to ask why.

The cost is on the record. Synapse's trustee estimated a $65–95M shortfall, and the CFPB sued it for “failing to maintain adequate records of the location of consumers' funds.”

How it works

Code matches. AI explains.
Your controller signs off.

Five steps run every day inside your cloud account. Only the last one needs a person.

Hover or tap a step for the detail.

synthetic data

01
Read-only
Ingest
tx 0x7a3f…c91e
Base · 14:02:11Z
Pulls from the chain, your provider's webhooks, your bank feed and your ERP, with read-only keys created in your name.
02
Code
Normalize
one movement table
amount · decimal(38,18)
Every record lands in one table at full token precision, so 18-decimal amounts never round away.
03
Code
Match
hash → transfer ID
→ amount ± tolerance
Fixed rules match in passes: exact keys first, then amounts within tolerance, then one-to-many. Each match records the rule that fired.
04
AI
Explain
bridge legs booked twice
48,500.00 USDC · draft JE
The model sees only what the rules could not match. It writes a plain-English cause and a draft journal entry. It never decides a match.
05
Your controller
Sign off
Signed · 08:14
close pack updated
Your finance team reviews each break and signs off the daily report. Nothing posts until a person approves it.

The AI never decides a match. It only explains what the rules couldn't, with every record cited, so the evidence trail holds up.

Sample break report

Every break explained, with the record that proves it.

Daily break report · Nov 6 · 4,812 movements matched · 9 breaks · 2 awaiting sign-offSynthetic

01 · Found

Payout batch PB-2291 · USDC on Base

Chain

48,500.00 USDC, one movement

Provider

48,500.00 USDC, send and receive

ERP

97,000.00 booked out

Difference$48,500.00

02 · Why

The bridge send and receive were both recorded as outflows. One movement, booked twice.

↳ tx 0x7a3f…c91e↳ Provider transfer tr_8f2c

03 · Fix

Reverse the duplicate $48,500.00 entry and link both legs to one movement. Journal entry drafted for review.

Awaiting controller sign-off

What you get

Daily break reportDaily

Every exception explained and categorized, ready for sign-off.

Weekend WatchMondays

A digest of everything that settled while the bank was closed.

Month-end close packMonthly

Opening-to-closing roll-forward per leg, every open item aged.

Counterparty registryYours

No unknown wallets, no postings to the wrong entity.

Break-reason playbookYours

Your team fixes repeat breaks the same way every time.

Evidence packOn request

A partner-bank or auditor request becomes a download, not a scramble.

GENIUS operations checklistBy Jan 18

Reserve, redemption and reporting data flows mapped. Operational, not legal.

Security

Nothing leaves your cloud

Data, keys and reports stay in your account. We host nothing.

Read-only, no custody

Read-only keys and webhooks. No signing keys, ever.

Revocable access

Our maintenance role is scoped, logged and yours to revoke.

Your model endpoint

The AI step runs on Bedrock, Vertex or Azure in your account.

Getting started

See your breaks first. Live 10 business days after you say go.

01 · Start here

30-Day Break Diagnostic

We run last month's data and show you every break, its cause and the staff hours it costs. In our environment under NDA, or in a sandbox in your own cloud. Credited in full against implementation if you go ahead within 30 days.

02 · Then

Implementation

Deployed in your AWS account from one install template. Connectors built, wallets mapped, rules tuned and 90 days backfilled to a reconciled opening balance. For the first 30 days, we review every report with your team before you take over.

03 · Every month

Maintenance

Connectors kept current as providers and chains change. Monthly releases, installed only with your approval. Job-health monitoring from metadata only.

What we need from you: wallet addresses, read-only keys, a bank export, ERP read access, one approved cloud account and one hour with your engineer. No engineering project.

Built for platforms moving real stablecoin volume across more than one chain or provider. Not for firms with small monthly flows, or teams with their own data engineering.

The 10-Day Guarantee. If the desk isn't producing a fully explained break report within 10 business days of cloud access and read-only keys, your first quarter of maintenance is free, and we keep working until it is.

The 2-Day Fix. If a provider or chain change breaks a connector and we haven't restored it within 2 business days of being told, that month's maintenance is credited.

Book a discovery callTwo new implementations a month

FAQ

Questions finance and security ask first.

Anything not answered here is what the diagnostic call is for.

Bradley Behan

Founder · Novaheim

Bradley runs every implementation and reviews your reports himself for the first 30 days. He brings seven years of measuring model performance. He is not a CPA or a lawyer, and says so.

Does our data leave our cloud?

No. The desk runs inside your own cloud account. Data, keys and reports stay there. Novaheim hosts nothing and holds no copy; we see only job-health metadata, such as whether a run finished and how many breaks it found.

What access do you need?

Read-only API keys for your provider, chain data service, bank feed and ERP, created in your name and stored in your secrets manager. Plus a scoped, logged maintenance role in your cloud that you can revoke at any time. No custody, no signing keys.

Does AI decide what gets booked?

No. Fixed rules do every match. The model only explains the exceptions the rules could not match, and drafts a journal entry for review. Your controller signs off every break.

We already have crypto accounting software. Why this?

Those tools produce journal entries. Someone still matches the chain, provider, bank and books every day and explains the gaps. The desk does that work, neutral across every provider you use.

Why not hire a reconciliation lead?

A senior accountant runs about $97K in salary before benefits (Robert Half), and still needs tools. The desk is live 10 business days after access, and it keeps working when people change roles.

Which providers and chains do you support?

Bridge, Circle, BVNK and Stripe, and chain data through Etherscan, Alchemy or Helius. Bank and ERP connections are confirmed during the break diagnostic.

Do you sign off reports or give opinions?

No. We are not a CPA firm or a law firm, and we don't give opinions or attestations. We run the reconciliation and evidence layer so your accountant, counsel and compliance team can sign off faster.

Every stablecoin dollar, tied out.Every break, explained.