Tail spend is the part of a company's purchasing made of many low-value transactions with many suppliers: a minor share of spend, but a large share of suppliers, invoices and approvals. Rank suppliers by annual spend, and the tail is everything after the few that carry most of the money.
There is no standard cut-off: each company sets its own, by share of spend, supplier threshold or category, and the cut-off decides which controls apply. The tail typically includes:
- one-off suppliers created in the vendor master for a single invoice
- software subscriptions paid by card, which renew without a new approval
- small services and supplies bought outside framework contracts
- purchases reimbursed through expense reports
The usual remedies: consolidate the tail onto preferred suppliers and catalogues, or pay it by purchasing card. French public bodies use cards under decree 2023-209: the entity sets authorisation and ceiling parameters for each card, checked with the issuer at every use.
That control has a precise limit. A ceiling checks how much a holder can spend, not what is bought. It does not see three teams paying for three video tools, a free trial turning into an annual plan, or a supplier already under contract at a better price.
Tail spend is defined by size, maverick spend by compliance. A small order from a referenced supplier is tail but not maverick; a large order placed outside the contract is maverick but not tail. Many non-PO invoices sit in the tail, which spend analysis measures.
Phacet's agent that monitors card spend and detects duplicate SaaS tools categorises every card expense, detects recurring charges and functional duplicates, and flags unusual new expenses. On invoices, the agent that validates invoices before payment applies the same rules to every row, small amounts included.