Straight-Through Processing: Glossary Definition

Straight-through processing automates invoice payment against a purchase order match. Here is what it checks, what it misses, and why that gap matters.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Straight-Through Processing: Glossary Definition

Straight-through processing is the automated movement of an invoice from receipt to payment with no manual intervention, triggered when the invoice clears a set of matching rules. AP teams track it as an efficiency metric: the share of invoices that never stop for human review. It says nothing on its own about whether the amount paid was the amount owed.

1. How does straight-through processing actually work?

Straight-through processing runs an invoice through a rule set the moment it arrives: does the vendor match a known record, does the amount match the purchase order, does the quantity match the receipt. If every rule clears, the invoice posts and pays with no human touch. If any rule fails, the invoice is held in a queue for a person to review before payment.

The rules are usually three-way matching: invoice, purchase order, and receipt, compared within a set tolerance band. An invoice held for review does not get rejected outright. It routes to a queue where a person decides whether to approve, adjust, or return it to the vendor. That decision point is where most contract-level review still happens today, when it happens at all.

2. What does straight-through processing measure?

Straight-through processing measures automation: the percentage of invoices paid with zero manual touches against total invoices processed in a period. It is an efficiency and labor-cost metric for the AP function. It does not measure whether the amount charged matches the vendor contract, because the matching rules driving it test the purchase order and receipt, not the underlying rate card or rebate clause.

A company reporting a high STP rate has reduced manual AP work. That is a real operational gain and a legitimate goal for the finance function, tracked alongside cost per invoice and cycle time. None of those metrics test contract accuracy on their own.

3. Where does straight-through processing break down against contract terms?

The break happens where a contract term lives outside the fields STP checks. A surcharge schedule, a minimum volume commitment, or an index escalation clause sits in a document the matching engine never opens. An invoice can match its purchase order exactly and still bill against the wrong rate tier, and STP has no field built to test that condition.

Purchase orders typically carry a quantity and a unit price, not a full rate card or a rebate structure. A three-way match confirms the invoice agrees with the PO. It does not confirm the PO itself reflects the current contract terms.

This is a structural gap, not a configuration error. Closing it requires reading the contract document and comparing its terms to the invoice line, a step outside what purchase-order-based matching was built to do.

4. How should a finance team use the STP rate alongside contract review?

Treat the STP rate as an efficiency measure and pair it with a separate check of invoices against the underlying contract, not the purchase order. The two serve different purposes: one tells you how much manual work AP is doing, the other tells you whether what was paid matches what was agreed. Neither substitutes for the other.

A team that only tracks STP can raise the rate by loosening tolerance bands, which increases the exceptions passed straight to payment without contract review.

A periodic reconciliation against the contract document, run separately from the daily matching workflow, is the step that tests the terms STP was never built to check.

For the wider pattern this sits inside, start with the margin drift guide. See also margin drift vs. legitimate price increases: how to tell them apart and accessorial charge audit: the surcharges nobody validates.

5. Frequently Asked Questions (People Also Ask)

What is straight-through processing in accounts payable?

Straight-through processing, or STP, is the automated flow of an invoice from receipt to payment with no manual touch, when the invoice matches expected data at every step. It relies on matching logic, usually a purchase order and a receipt, not on reading the underlying vendor contract.

Does straight-through processing check vendor contract terms?

It checks whether the invoice matches the purchase order and receipt. It does not interpret a rate card, a rebate clause, or a not-to-exceed cap sitting in a PDF outside the ERP, so an invoice can pass straight through while still violating the contract behind it.

Why would a company want a lower straight-through processing rate?

A lower rate is not automatically bad. It can mean more invoices are being held for a reason the matching rules were built to catch, including exceptions worth a human look. The rate measures automation, not accuracy against contract terms.

Can straight-through processing catch duplicate payments?

It depends on the rule set. Some duplicate-detection logic runs inside STP workflows and catches exact-match duplicates. It generally does not catch a duplicate paid under a different invoice number or a slightly altered amount, which is why a separate audit still finds them.

Is straight-through processing the same as three-way matching?

No. Three-way matching, comparing invoice, purchase order and receipt, is one rule set that can drive straight-through processing. STP is the broader outcome: an invoice moving from receipt to payment with zero manual intervention, however that outcome is achieved.

What is the relationship between straight-through processing and margin drift?

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. A high straight-through processing rate can mask margin drift, because an invoice can clear every automated check and still bill above the contracted rate.

Does raising the straight-through processing rate reduce vendor overbilling?

Raising the rate means fewer invoices get a human look before payment. Unless the matching rules test the specific contract term at risk, such as a rate card or a volume tier, a higher rate removes a review step without adding a control against that term.

1. How does straight-through processing actually work?

Straight-through processing runs an invoice through a rule set the moment it arrives: does the vendor match a known record, does the amount match the purchase order, does the quantity match the receipt. If every rule clears, the invoice posts and pays with no human touch. If any rule fails, the invoice is held in a queue for a person to review before payment. The rules are usually three-way matching: invoice, purchase order, and receipt, compared within a set tolerance band. An invoice held for review does not get rejected outright. It routes to a queue where a person decides whether to approve, adjust, or return it to the vendor. That decision point is where most contract-level review still happens today, when it happens at all.

2. What does straight-through processing measure?

Straight-through processing measures automation: the percentage of invoices paid with zero manual touches against total invoices processed in a period. It is an efficiency and labor-cost metric for the AP function. It does not measure whether the amount charged matches the vendor contract, because the matching rules driving it test the purchase order and receipt, not the underlying rate card or rebate clause. A company reporting a high STP rate has reduced manual AP work. That is a real operational gain and a legitimate goal for the finance function, tracked alongside cost per invoice and cycle time. None of those metrics test contract accuracy on their own.

3. Where does straight-through processing break down against contract terms?

The break happens where a contract term lives outside the fields STP checks. A surcharge schedule, a minimum volume commitment, or an index escalation clause sits in a document the matching engine never opens. An invoice can match its purchase order exactly and still bill against the wrong rate tier, and STP has no field built to test that condition. Purchase orders typically carry a quantity and a unit price, not a full rate card or a rebate structure. A three-way match confirms the invoice agrees with the PO. It does not confirm the PO itself reflects the current contract terms. This is a structural gap, not a configuration error. Closing it requires reading the contract document and comparing its terms to the invoice line, a step outside what purchase-order-based matching was built to do.

4. How should a finance team use the STP rate alongside contract review?

Treat the STP rate as an efficiency measure and pair it with a separate check of invoices against the underlying contract, not the purchase order. The two serve different purposes: one tells you how much manual work AP is doing, the other tells you whether what was paid matches what was agreed. Neither substitutes for the other. A team that only tracks STP can raise the rate by loosening tolerance bands, which increases the exceptions passed straight to payment without contract review. A periodic reconciliation against the contract document, run separately from the daily matching workflow, is the step that tests the terms STP was never built to check. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. See also [margin drift vs. legitimate price increases: how to tell them apart](/guides/margin-drift-vs-legitimate-price-increases-how-to-tell-them) and [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates).

Questions & Answers

What is straight-through processing in accounts payable?

Straight-through processing, or STP, is the automated flow of an invoice from receipt to payment with no manual touch, when the invoice matches expected data at every step. It relies on matching logic, usually a purchase order and a receipt, not on reading the underlying vendor contract.

Does straight-through processing check vendor contract terms?

It checks whether the invoice matches the purchase order and receipt. It does not interpret a rate card, a rebate clause, or a not-to-exceed cap sitting in a PDF outside the ERP, so an invoice can pass straight through while still violating the contract behind it.

Why would a company want a lower straight-through processing rate?

A lower rate is not automatically bad. It can mean more invoices are being held for a reason the matching rules were built to catch, including exceptions worth a human look. The rate measures automation, not accuracy against contract terms.

Can straight-through processing catch duplicate payments?

It depends on the rule set. Some duplicate-detection logic runs inside STP workflows and catches exact-match duplicates. It generally does not catch a duplicate paid under a different invoice number or a slightly altered amount, which is why a separate audit still finds them.

Is straight-through processing the same as three-way matching?

No. Three-way matching, comparing invoice, purchase order and receipt, is one rule set that can drive straight-through processing. STP is the broader outcome: an invoice moving from receipt to payment with zero manual intervention, however that outcome is achieved.

Margin Drift Resources