Card-blind spend
Updated August 22, 2026
Software your company pays for that a corporate card tool structurally cannot see, because the money never moves across its card. It is paid by ACH transfer, paper check, bill pay, an annual invoice, or a reimbursed personal card instead.
Why can't a card tool see this spend?
A card tool can only see transactions on its own card. Software paid by ACH transfer, paper check, bill pay, an annual invoice, or a reimbursed personal card never touches it. Those rails are usually where the largest annual contracts sit. A general ledger records all of them.
This is an architecture limit rather than a missing feature. A card platform's data is its own authorization stream. A charge that never touches that card produces no record for it to read, so no amount of product work inside the card tool surfaces it. The full argument is in why corporate card tools miss subscriptions.
Which rails carry card-blind spend?
- ACH transfers, which is where most annual and negotiated contracts settle.
- Paper checks, still common for insurance, telecom, and professional services.
- Bill pay and AP automation, where an invoice is approved and paid outside any card.
- Annual invoices billed to accounts payable rather than to a card on file.
- Personal cards reimbursed through expense reports, which land as reimbursements rather than as vendor charges.
Every term in this glossary is defined from the general ledger, because that is the one place a company's whole software estate is already written down. See how a software spend audit reads a ledger for what that involves.