When the money stops making sense, we start digging.
Payments produces an incredible amount of financial data. Unfortunately, very little of it arrives with a friendly note explaining what actually happened.
There are settlement files, processor reports, residual statements, interchange tables, card-brand fees, ACH activity, reserves, adjustments, chargebacks, prefunding, FBO accounts, and enough cryptic transaction codes to make perfectly intelligent people question their career choices.
Most of the time, everything more or less works. Until it doesn't.
Maybe an ISO or Third-Party Sender collapses and suddenly an acquiring bank or ODFI needs to know exactly how much exposure it has. Maybe a receiver gets appointed. Maybe a bankruptcy court is looking at an account balance and asking who actually owns the money. Maybe the FBO account keeps going negative and everyone has a different theory about why.
Or maybe nothing is on fire at all. Maybe you have just been looking at your residuals thinking, "We used to make more money than this."
That is forensic accounting in payments. We follow the money until the story makes sense.
Traditional accounting starts with a fairly comforting assumption: the financial records were designed to help somebody understand the finances.
Payments frequently skipped that meeting.
A single merchant transaction can generate interchange, network assessments, processor fees, gateway fees, sponsor-bank economics, ISO residuals, reserves, chargebacks, ACH movements, adjustments, and several other entries whose descriptions appear to have been written by someone with a personal grudge against vowels.
Multiply that by millions of transactions, multiple processing platforms, settlement accounts, FBO structures, and years of activity, and apparently simple questions become surprisingly difficult.
How much money should be in this account? Whose money is it? Why is the account short? What did the processor actually charge? Did the residual calculation change? Are interchange costs being passed through correctly? Is that a real card-brand fee, or did somebody invent a fee and give it a sufficiently official-sounding name?
We have spent years working inside these systems. We know the files. We know the economics. We know the weird reports. And, perhaps most importantly, we know which numbers should reconcile even when the systems producing them seem determined to prevent that from happening.
This is not ordinary accounting. It is closer to financial archaeology with significantly more CSV files.
When the program blows up, somebody has to explain where the money went.
You sponsored the ISO, PayFac, Third-Party Sender, or payments program.
Everything was moving along reasonably well — until suddenly it wasn't.
Maybe the program files bankruptcy. Maybe a receiver gets appointed. Maybe a court freezes an account and your team is explaining that the balance is not simply the program's money — some or all of it belongs to merchants. Maybe the FBO account keeps slipping into the red and nobody can tell you whether you are short $500,000 or $5 million.
Then comes the question nobody wants to hear without an answer ready: "Show me the accounting."
That is what this service is built for.
When a payments program fails, the records rarely arrive in one clean ledger. The answer may be spread across processor settlement reports, ACH files, bank statements, merchant-level activity, reserve accounts, chargeback records, card-brand data, internal accounting systems, processor adjustments, and years of operational history.
We pull those pieces together. We reconstruct the movement of funds across the program, trace settlement activity, identify discrepancies, quantify shortfalls, analyze account behavior, and build a defensible picture of who received what, who is still owed what, and where the accounting stopped reconciling.
Sometimes that means going back months. Sometimes it means going back years. And sometimes it means discovering that the answer everyone assumed was true on Monday looks considerably less convincing by Thursday.
Program failures have a habit of becoming legal matters.
We have worked alongside law firms, financial institutions, receivers, and other stakeholders in situations where the accounting needed to be understood well enough to explain it to people who were not part of the payments program when things were still operating normally.
That matters when accounts are being frozen, merchant funds are being disputed, obligations are being evaluated, or a court wants to understand what the numbers actually represent.
We are not replacing counsel, and we are not making legal conclusions about ownership. We are doing the part that has to happen before anyone can make those conclusions intelligently: figuring out where the money went.
This work is typically for acquiring banks, ODFIs, sponsor banks, receivers, law firms, and other parties dealing with a payment program that has failed, become financially unstable, or produced an accounting problem nobody wants to inherit.
If the program is collapsing, the FBO account is chronically short, merchants may not have been fully funded, or everyone involved has a slightly different answer to the question "How much are we exposed for?", this is where we come in.
Forensic accounting in payments is not about making a spreadsheet prettier. It is about taking complicated, fragmented financial information and turning it into something you can actually use.
Different circumstances. Same basic job: follow the money, figure out what happened, and make the numbers explain themselves.
If the trail is messy, that is fine. We brought a flashlight.
