27 clear, jargon-free definitions for CFOs, controllers and procurement leaders. No buzzwords. No fluff.
Classifying spend or inventory into A, B and C tiers by value and importance.
ABC analysis is the classic Pareto-based segmentation: A items get the most attention (strategic), B items get standard governance, C items run through catalogs and one approval. It is the foundation of any sane tail-spend program.
The approval step a request passes before it becomes a purchase order.
An approval workflow defines how a purchase request is reviewed before a purchase order is issued. In Tail Sourcing Essentials, an Admin or Procurement Manager provides one human approval before the PO; invoices are compared to the PO and goods receipt before approval. Multi-level approvals are coming soon.
Buying from pre-approved items with pre-negotiated prices and suppliers.
Catalog buying converts repetitive purchases into a self-service experience: the requester picks from approved items, the price and supplier are locked in and approval is required. It is the single most effective lever against maverick spend.
A department or team whose spend is tracked and budgeted separately.
Cost centers are the unit of financial accountability for spend. Every requisition, PO and invoice is attributed to a cost center so finance can roll up actuals vs budget by team, region or function.
The elapsed time from a requisition to PO issuance (or to payment).
Cycle time is the operational health metric for procurement. Top-quartile mid-market teams hit median requisition-to-PO and requisition-to-payment.
Goods and services that go directly into the final product sold to customers.
Direct spend covers raw materials, components and inputs that become part of the product or service delivered to customers. It is usually more visible and contract-driven than indirect spend.
Native data flow between the procurement platform and the system of record (ERP).
ERP integration syncs cost centers, GL codes, vendors, POs and invoice status between the procurement platform and the ERP (for example QuickBooks Online). It eliminates double entry and keeps finance and procurement on the same numbers.
Goods and services that don't go into the final product (office, IT, marketing, services).
Indirect spend covers all purchases that support the business but aren't part of the product or service sold to customers — facilities, office supplies, software, marketing, travel and professional services. It is the category where tail spend most commonly hides.
Purchases made outside of negotiated contracts or approved channels.
Maverick spend is buying outside negotiated contracts or approved channels — related to tail spend, but not the same thing. Tail spend describes where the volume sits (many small purchases across many vendors); maverick spend describes how it happens (without the contract, preferred supplier or approval). Example: a manager buys $900 of laptops with a corporate card from a retail site instead of the contracted IT reseller — different price, terms and approval trail, same category.
A purchase that doesn't reference a pre-negotiated contract or framework agreement.
Off-contract purchases bypass negotiated pricing, payment terms or compliance requirements. They are the structural cause of most maverick spend.
The full workflow from a requisition to a paid invoice.
P2P is the operational backbone of procurement: requisition → approval → PO → receiving → invoice match → payment. Modern P2P platforms unify this flow across systems so finance and procurement work from the same data.
A live connection to a supplier's online catalog from inside the procurement platform.
Punchout lets users browse the supplier's full catalog with negotiated pricing without leaving the procurement workflow. The cart returns to the procurement platform for approval, PO and invoice match. In Tail Sourcing, punch-out (cXML) is coming soon.
A formal authorization to buy specific goods or services at agreed terms.
A PO turns an approved requisition into a binding commitment to a supplier. It locks in price, quantity, delivery and payment terms and becomes the document the invoice is matched against.
A requisition is the internal request to buy; a PO is the external order that commits you.
The core difference is internal versus external: a purchase requisition is the internal document where an employee describes what they need and why, while a purchase order is the external commitment sent to the supplier once the request is approved. You use the requisition to secure budget-owner sign-off; you use the PO to buy. Matching the invoice back to the PO is what keeps payment honest.
Umbrella term for RFI, RFQ and RFP — structured supplier-evaluation events.
RFx covers Request for Information (early discovery), Request for Quotation (pricing) and Request for Proposal (full evaluation). Well-run RFx events use weighted scoring on outcomes — not capabilities — to pick the supplier that actually performs.
P2P plus the upstream sourcing activities (RFx, supplier selection, contracts).
Source-to-Pay extends P2P upstream to include category strategy, RFx events, supplier qualification and contract management. It's the end-to-end procurement lifecycle.
The share of negotiated savings that actually shows up in the P&L.
Savings realization is the practice of reconciling negotiated rates against actual invoices monthly so scope creep, reverted pricing and off-contract buying are caught early.
An independent audit confirming security, availability and confidentiality controls.
SOC 2 is the standard security audit most US enterprise buyers require from SaaS vendors. Type II covers operating effectiveness over a 6–12 month window, not just design. Tail Sourcing: SOC 2 planned.
The share of total spend actively governed by procurement processes and controls.
SUM measures how much of the company's spend is flowing through structured workflows: contracts, catalogs, approvals and reporting. Top-quartile mid-market teams keep SUM high.
Single sign-on protocols that let employees log in with their corporate identity.
SSO via SAML or OIDC is the baseline identity integration for any enterprise procurement platform. It centralizes access control, accelerates onboarding/offboarding and is usually required by security teams. Tail Sourcing: coming soon.
Tracking and growing spend with certified diverse suppliers (MWBE, veteran-owned, etc.).
Supplier diversity programs measure and grow spend with diverse-owned businesses. Many enterprise customers report diversity spend to their own customers as a contractual requirement.
Quantitative assessment of financial, operational and compliance risk for each supplier.
Supplier risk scoring combines financial health, delivery performance, compliance status and concentration risk into a single score. It helps procurement spot trouble before it disrupts the business.
Small, fragmented purchases across suppliers that often fall outside structured procurement processes.
Tail spend is the large share of a company's purchase volume made in small, individual transactions — usually scattered across hundreds of vendors with no shared contract or category strategy. It matters for controls because these small purchases slip past the approval, contract and invoice-matching checks that apply to larger spend: that is where off-contract buying, duplicate invoices and unmanaged suppliers concentrate. Bringing tail spend under a request-to-order-to-invoice workflow restores those controls without enterprise-suite overhead.
The typical indirect categories where tail spend concentrates.
Tail spend rarely sits in one category — it spreads across low-value indirect purchases. The usual suspects: office supplies, facilities and maintenance, IT hardware and software, MRO (maintenance, repair and operations), professional services, marketing, travel and shipping. Each category holds a handful of large transactions and many small ones, which is why category-level visibility — not a single enterprise contract — is what makes tail spend controllable.
Reconciling the PO, the goods receipt and the invoice before paying.
Three-way match compares the purchase order, the goods/services receipt and the supplier invoice. If the three documents agree within tolerance, the invoice can be approved for payment. It is the strongest control against overpayment and duplicate invoices. In Tail Sourcing, the invoice is compared to the PO and goods receipt before an approver signs off.
The full lifetime cost of a purchase, not just the sticker price.
TCO includes implementation, integration, training, support, maintenance and exit costs. For procurement software, TCO over 3 years often diverges from headline license price, depending on integration scope.
Reducing the number of active suppliers to gain volume leverage and simplify operations.
Vendor consolidation groups overlapping suppliers within a category into a smaller set of strategic partners. Most mid-market companies can cut vendor sprawl while improving service and price.
Looking for deeper guides? Browse the resource library.
