Fractional CFO · and the engineering to fix what we find
What did we earn, where is the money, who do we owe — three questions your systems answer differently. Most finance help stops at telling you that. We go one step further and rebuild the part that produces the numbers, so the answers come out the same way every month.
Most of it belongs there. Some of it is money you can still get back. The difference is what a pipeline is for.
The volume threshold
A record you can quietly edit is not evidence.
A good accountant closes the month. Nobody closes the system that feeds it. That is the part we take on: every cent of revenue, tax and fee lands on the right account by rule — and lands there once, no matter how many times the data is replayed.
And a closed month stays closed. A refund arriving in May against a March sale is posted in May, pointing back at what it reverses — not written quietly into March. Both months stay true, and the link between them is visible instead of implied.
What we take on
We intercept the payout batch and break it back apart: gross sales, processing fees, refunds, taxes and holds. This is the job of a revenue subledger — the clearing account nets to zero on its own, because every component has somewhere to go.
Journal entry automation that follows your rules, not whichever API trigger happened to fire: gift cards, partial refunds, platform holds and COGS.
The rate is captured at the moment of the order and held. When the money actually lands, the difference is posted as realized FX gain or loss — not smeared across revenue.
Moving from QuickBooks to Odoo or NetSuite without losing transaction history — and without a year that exists in two systems and reconciles in neither. Month-end close keeps running while the move happens.
A separate subledger, not a line in the revenue split: what you owe partners is a liability, and it is accrued at the moment the sale qualifies — with the rate and the base recorded as they were then.
Otherwise a chargeback three months later silently moves the base a payout was already calculated on, and the partner asking why cannot be answered. Multi-level structures make this worse, not different.
We don’t ask you to move. We work inside what you already run, and where a gateway or a bank is missing from this list, adding it is work we quote, not a reason to say no.
High-Volume & US
Custom ERP & Global
The same gap from the top of this page, taken apart line by line.
Four of the five belong there. One is money you can still get back. The report tells you which.
One month, one payout account, taken apart into the lines above.
Get a Payout Gap Report →$149 · three days · exports only
What comes after
This is how the work runs, not how the software is licensed. You take the next step when the last one paid off; stop after any of them and you keep what it produced. Prices are here because you should not have to ask.
Step one · $149
One month, one payout account. Every difference between your sales and your bank, with the reason it exists.
Access · exports only
Step two · $750
Chart of accounts, what splits into what, how fees and currency are treated, what a closed period means for you. Yours to keep either way.
Access · exports only
Step three · $2,000
The model becomes rules, and one real month runs all the way through to the three statements.
Access · exports in, journal files out — or a sandbox copy if you prefer
Step four · $3,500
Idempotent ingestion, duplicates caught, exceptions queued for a person, periods that close and stay closed.
Access · read-only keys, asked for here and not before
After that, $500 a month keeps a person on the exception queue and on the gateways when they change their APIs. That is what the retainer is — not support.
How we work
No discovery call, no scoping workshop, no meeting to decide whether there should be a meeting. You send what you already have; we send back something you can read, keep and check.
You send
Exports you already produce — payout reports, statements, the spreadsheet you actually reconcile in. Nothing you have to build for us.
We return
A document, not an opinion. Every difference named, every rule written down, so the next person to look at it does not have to ask us what we meant.
Why in writing
Because a call convinces and a document proves. If we are wrong, you can point at the line. That is harder for us and better for you.
Every report is checked by a person before it goes back. There is no model deciding what your numbers mean.
Access
We start from the exports you already produce — no access to your store, your bank or your accounting system. Only a running pipeline needs read-only keys, and we say so long before you buy one.
Retention
Your files are deleted seven days after delivery.
Review
Every report is checked by a person before it goes back.
Coverage
Shopify, Amazon, Stripe, PayPal and Klarna on the money side; Odoo, NetSuite, QuickBooks and Xero on the accounting side. A gateway or a bank that is not on that list is work we quote, not a reason to say no.