Why corporate card tools miss subscriptions
Updated August 22, 2026
Because a card platform's data is its own authorization stream, and a charge that never crosses its card produces no record for it to read. Software paid by ACH transfer, paper check, bill pay, or annual invoice is invisible to it by construction rather than by oversight.
Corporate card platforms are good at what they observe. The limit is what reaches them at all.
What does a card tool actually see?
Transactions authorized on its own cards, and nothing else. That is the complete list. It is a strong dataset for the spend that runs through it: real-time, categorized, tied to a cardholder. It is also a closed one, because the platform's visibility ends where its authorization stream ends.
Does a card tool read my accounting ledger?
Not for finding spend. The accounting integrations these platforms ship run in the outbound direction: they push their own transactions into QuickBooks or Xero as journal entries so the books reconcile. They do read back reference data, the chart of accounts, vendor list, and classes, but that is so they can map their own charges correctly. They do not ingest the transactions already in your ledger to find spend that never touched their card.
Checked against Ramp's and Brex's own integration documentation in August 2026, both describe a one-directional sync of this shape. This is worth stating precisely, because the loose version of the claim, that these tools cannot read your books at all, is wrong and easy to disprove.
Which subscriptions go missing?
Disproportionately the expensive ones. Small monthly tools get put on a card because that is the fastest way to buy them. Large annual contracts get invoiced, negotiated, approved, and paid by ACH or check, because that is how a company buys something significant. So the spend that escapes a card tool is skewed toward the contracts most worth reviewing.
In the sample ledger on the demo page, $1,652 of monthly software spend across 9 subscriptions is paid on rails a card tool never sees, which is $19,824 a year. Those figures are the detection engine's own output over that file, not an estimate.
What sees all of it?
The general ledger, because every payment a company makes has to be recorded somewhere in the books regardless of how it was paid. That is the one dataset with no rail-shaped hole in it. It is also the reason a spend audit can run without issuing a card, installing an agent, or asking anyone to change how they buy things.
What a ledger cannot tell you is who is using a tool. It records what was paid, not who logged in. Seat-level usage is a different data source and a different question. See the glossary entry on card-blind spend for the payment rails involved.