Evaluated Receipt Settlement (ERS): A Complete Guide

Evaluated receipt settlement (ERS) is an invoiceless payment method where the buyer automatically generates a payment to the supplier based on the purchase order and goods receipt, without waiting for a supplier invoice. When goods arrive and match the PO terms, the system creates a payment obligation directly, eliminating invoice processing entirely. This is distinct from self-billing, where the buyer issues an invoice on the supplier's behalf. ERS skips the invoice altogether.

The concept traces back to General Motors in the 1990s. At that scale, GM was processing roughly 1.5 million supplier transactions per month. The traditional cycle of waiting for supplier invoices, matching them against purchase orders and receiving documents, and resolving the inevitable discrepancies was a massive operational bottleneck. GM's solution was to flip the model: if the goods showed up and matched what was ordered, pay the supplier. No invoice required. ERS allowed GM to pay suppliers automatically upon confirmed receipt of goods that matched PO terms, stripping an entire document layer out of the procure-to-pay process.

The underlying insight is straightforward. Traditional three-way matching compares three documents: the purchase order, the goods receipt, and the supplier invoice. But if your PO-to-receipt matching is reliable, the invoice is redundant — it merely confirms what the buyer can already calculate from the PO and goods receipt. ERS acts on that logic by treating the confirmed receipt as the trigger for payment, rather than waiting for a document that restates information both parties already have.

This guide covers how ERS works mechanically, how it differs from self-billing (the most common point of confusion), when invoiceless processing makes sense for an organization, and the risks that derail ERS programs in practice.

How the Evaluated Receipt Settlement Process Works

ERS replaces the traditional invoice-driven payment cycle with a streamlined flow where the goods receipt becomes the payment trigger. No invoice is issued, received, or matched. The buyer's system handles everything from receipt confirmation to payment generation.

Here is how the evaluated receipt settlement process works, step by step:

1. Buyer and supplier agree on ERS terms and PO pricing. Before any goods move, both parties formally agree that the supplier will not send invoices. They lock in pricing, payment terms, and quality expectations. This agreement is the foundation: without pre-agreed unit prices, the entire model falls apart.

2. The buyer issues a purchase order flagged for ERS. The PO carries a specific indicator (often an ERS flag in the ERP system) that tells downstream processes to skip invoice matching. The PO price is the authoritative price for payment calculation.

3. The supplier ships goods and optionally sends an Advance Shipping Notice. Many ERS arrangements rely on EDI (electronic data interchange) for PO transmission and ASN for shipment notification. The ASN gives the buyer visibility into what is arriving, in what quantities, and when. This early signal enables warehouse teams to prepare for receipt and allows the buyer's system to begin pre-matching shipment data against the PO before goods even arrive.

4. The buyer receives the goods and records a goods receipt against the PO. Warehouse staff confirm what was delivered, noting quantities, condition, and any discrepancies. The goods receipt document captures exactly what the buyer accepted.

5. The system compares the goods receipt to the PO. This is where invoiceless processing diverges sharply from convention. The ERP system checks whether the received quantity and the PO price align. If they match, the system automatically generates a payment obligation with no invoice involved. The buyer's system effectively creates the payable record internally, calculated as received quantity multiplied by the agreed PO unit price.

6. Payment is scheduled according to agreed terms. The payment flows on the contractually agreed timeline, just as it would after a traditional invoice approval, but without the weeks of delay that invoice processing typically introduces.

How This Differs from Traditional Three-Way Matching

In a conventional accounts payable cycle, three documents must align before payment: the purchase order, the goods receipt, and the supplier's invoice. The supplier ships goods, then sends an invoice. The buyer's AP team matches that invoice line by line against both the PO and the goods receipt. Price discrepancies, quantity mismatches, or missing documentation trigger exception holds. Manual resolution follows. Payment only moves forward once all three documents agree.

This process works, but it is slow and labor-intensive. Organizations that spend significant resources matching delivery notes against invoices will recognize the core insight behind ERS: most of those discrepancies originate from the invoice itself. Remove the invoice, and the matching problem shrinks to a two-document comparison.

ERS eliminates the invoice from this equation entirely. Instead of three-way matching, you have a two-way match: PO against goods receipt. The supplier's role ends at delivery. The buyer's system does the rest. No invoice means no invoice exceptions, no invoice data entry, no invoice disputes.

ERS vs Self-Billing: The Key Distinction

ERS and self-billing are both forms of buyer-initiated payment, but they operate through fundamentally different mechanisms. The confusion between them is the single most common question practitioners raise, and most available explanations either conflate the two or gloss over the distinction. Here is the definitive answer.

In evaluated receipt settlement, no invoice document exists at all. The buyer's system calculates what is owed by matching the purchase order against the goods receipt and generates a payment obligation directly from that data. The supplier never sends an invoice, and the buyer never creates one.

In self-billing, the buyer creates and issues an invoice on the supplier's behalf. An invoice document still exists in this arrangement. The difference is that the buyer authors it rather than the supplier.

That single structural difference, the presence or absence of an invoice document, drives every practical distinction between the two approaches.

Why the Distinction Matters

Whether or not an invoice exists has direct consequences for tax compliance, audit trails, and accounting treatment.

VAT and tax implications represent the most significant area of divergence. In many jurisdictions, self-billing is a formally recognized tax arrangement. The buyer issues a tax invoice, including VAT, on the supplier's behalf. This comes with specific regulatory requirements:

The supplier must agree in writing to the self-billing arrangement
The buyer must issue invoices that meet tax authority standards for format, content, and numbering
Clear rules govern who reports and remits the tax

ERS, by contrast, generates no invoice at all. The tax treatment then depends on how the jurisdiction views payment obligations that lack supporting invoice documents. Some tax authorities accept the PO-and-receipt combination as sufficient documentation; others require supplementary records. This distinction makes ERS more straightforward operationally but potentially more complex from a tax compliance standpoint, depending on where you operate.

From an audit perspective, self-billing produces a conventional document trail (buyer-issued invoices that auditors recognize), while ERS relies on system-generated matching records. Both are auditable, but they require different documentation strategies.

When Each Approach Fits

ERS is most common in high-volume manufacturing procurement with stable pricing and repetitive orders. The automotive industry pioneered this model: when General Motors receives thousands of identical parts shipments against standing purchase orders with pre-agreed pricing, generating invoices for each delivery adds cost without adding information. The PO and goods receipt already contain everything needed to calculate payment.

Self-billing is more common in industries where the buyer controls or measures the deliverable, and the final quantity or value is not known until after delivery. A dairy processor self-bills a farmer based on measured milk volume and tested fat content. A publisher self-bills an advertiser based on tracked impressions. In these cases, only the buyer has the data needed to produce an accurate invoice, so it makes sense for the buyer to author one.

Addressing the Terminology Confusion

Some organizations and ERP systems use "ERS" and "self-billing" interchangeably, which has muddied the terminology across the industry. Notably, certain SAP configurations label what is functionally an ERS process as "self-billing," and some vendor documentation follows suit. Other platforms treat them as synonyms in their menus and help text.

The underlying mechanisms remain distinct regardless of how any particular system labels them. If your process eliminates the invoice entirely and pays from PO-to-receipt matching, that is ERS. If your process has the buyer generating an invoice document on the supplier's behalf, that is self-billing. When evaluating either approach, pin down which mechanism is actually in play rather than relying on the label your ERP applies to it.

What ERS Means for Buyers and Suppliers

Evaluated receipt settlement changes the daily work of both the buyer's accounts payable team and the supplier's accounts receivable team. Understanding what shifts for each side is essential before any organization commits to an ERS program.

The Buyer's AP Perspective

For the buying organization, ERS removes several labor-intensive steps from the payables workflow. Invoice receipt, data entry, and three-way matching disappear entirely for covered purchase orders. There is no invoice to receive, no line items to key in, and no document to reconcile against the PO and goods receipt.

This elimination has a direct effect on exception handling. In traditional invoicing, a significant share of AP labor goes toward resolving mismatches between what the invoice states and what the PO or receiving report shows. Under ERS, these invoice-driven exceptions cease to exist. The only data points that matter are the purchase order terms and the confirmed receipt of goods.

Payment timing also becomes more predictable. Instead of waiting for a supplier's invoice to arrive, which can happen days or weeks after delivery, the payment obligation is created the moment goods are received and accepted. AP teams can forecast cash outflows with greater accuracy because the trigger event is internal, not dependent on a supplier's billing cycle.

One often-overlooked benefit involves accrual accounting. The goods received, not invoiced (GRNI) accrual, a persistent reconciliation challenge in manufacturing environments, simplifies considerably under ERS. Because the liability is recognized at receipt rather than held open until an invoice arrives, the gap between receiving goods and recording the obligation shrinks. Organizations that struggle with reconciling goods received but not yet invoiced often find that ERS reduces the volume and aging of their GRNI balances.

The Supplier's AR Perspective

Suppliers participating in an ERS program no longer need to generate, transmit, or track invoices for covered orders. This reduces invoicing costs and eliminates a common source of friction: invoice rejections. When there is no invoice to reject, suppliers avoid the cycle of resubmission and follow-up that consumes AR staff time.

However, ERS requires suppliers to accept a meaningful trade-off. They lose the ability to adjust pricing through the invoice. In traditional invoicing, a supplier might reflect a price change, a surcharge, or a quantity adjustment on the invoice itself. Under ERS, the payment amount is determined by the PO price and the buyer's receipt quantity. Any pricing discrepancy must be resolved before shipment, through PO amendments, or handled after the fact through separate credit or debit memo processes.

Suppliers must also trust the buyer's receiving process. The goods receipt record directly determines how much the supplier gets paid, and the supplier has no invoice document to contest that amount. If a buyer's warehouse records a short receipt, the supplier's payment reflects that shortage. Accurate receiving on the buyer's side is not just an internal concern; it is a contractual obligation to the supplier.

The Relationship Dynamic

ERS demands a higher baseline of trust and data transparency than traditional invoicing. The buyer commits to maintaining accurate purchase order data and disciplined goods receipt procedures. The supplier commits to shipping exactly what was ordered at the agreed price. Both parties must keep their item master data, pricing records, and unit-of-measure definitions aligned.

When this discipline holds, both sides benefit. Buyers see faster close cycles and lower processing costs. Suppliers receive payment sooner and spend less on collections. The overall cost of the trading relationship drops because neither party is investing labor in producing, transmitting, matching, and disputing invoice documents.

When discipline breaks down, the consequences are harder to manage than in traditional invoicing. Without an invoice to anchor a payment dispute, disagreements over quantities or pricing lack a clear documentary reference point. Resolution often requires digging into PO revision histories, shipping records, and receiving logs, a process that can be more time-consuming than resolving a straightforward invoice mismatch.

The costs of ERS are front-loaded (master data governance, receiving process investment, supplier onboarding), while the savings recur with every transaction. For high-volume, repetitive procurement relationships, the payback period is typically short. For low-volume or highly variable purchasing, the upfront discipline may not justify the operational savings.

When to Adopt ERS: Decision Criteria and Prerequisites

Evaluated receipt settlement is not a universal solution. It works exceptionally well under specific conditions and creates problems under others. Before committing to an ERS program, you need an honest assessment of where your organization stands on two fronts: whether your purchasing patterns actually favor invoiceless payment processing, and whether your internal processes are mature enough to support it.

Where ERS Delivers the Most Value

ERS produces the strongest returns in environments with high-volume, repetitive purchasing from the same suppliers. If you issue hundreds or thousands of purchase orders per month to a core set of vendors for the same materials, eliminating invoice matching on those transactions frees significant AP capacity.

The model works best when pricing is stable and contract-based. ERS depends on the PO price being the payment price. When you have negotiated fixed-price agreements that hold between PO issuance and delivery, the system can generate accurate payment documents without human review. Similarly, goods-based procurement where quantity is objectively verifiable at receipt is ideal. A warehouse team can count pallets, weigh bulk materials, or scan barcodes with high confidence, giving you the reliable receipt data ERS requires.

Organizations that have already invested in purchase order discipline and accurate goods receipt processes are natural candidates. If your teams consistently create complete POs before shipment and your receiving dock captures quantities precisely, you have the operational foundation ERS demands.

When ERS Is the Wrong Fit

Certain purchasing scenarios make ERS inappropriate or introduce more risk than it eliminates:

Variable or commodity-driven pricing. If the price at delivery regularly differs from the price at order, as with raw materials tied to market indices, the PO price will not match what the supplier expects. ERS cannot reconcile that gap automatically.
Complex service contracts. When deliverables are subjective or milestone-based, there is no "goods receipt" event that objectively confirms what was provided. Services require human judgment that ERS bypasses.
Low-volume or one-off purchasing. The setup cost of onboarding a supplier, configuring ERP rules, and establishing formal agreements exceeds the processing savings when you only transact with that supplier a few times per year.
Jurisdictions with strict e-invoicing mandates. Some tax regimes legally require a supplier-issued invoice document. In those environments, ERS may conflict with compliance obligations, regardless of its operational benefits.
Suppliers unwilling or unable to participate. ERS is a bilateral arrangement. Suppliers who lack the systems, trust, or contractual willingness to forgo invoicing cannot be forced into the model.

Implementation Prerequisites

Moving from traditional three-way matching to ERS requires specific capabilities to be in place before you flip the switch. Gaps in any of these areas will generate payment errors at scale.

1. Master data accuracy. Item numbers, pricing, and units of measure must match exactly between your system and your supplier's system. A discrepancy as minor as "each" versus "case" in the unit of measure field will produce incorrect payment amounts on every transaction.

2. Purchase order discipline. Every ERS-eligible purchase must have a complete, accurate PO issued before shipment. Understanding how the purchase order process works and enforcing it consistently is non-negotiable. Without a valid PO, the system has no reference document to generate payment from.

3. Goods receipt accuracy. Receiving staff must record exact quantities, because in an ERS environment, what they enter is what the supplier gets paid. There is no invoice to catch a discrepancy. Errors at the dock translate directly into overpayments or underpayments.

4. Supplier agreement and onboarding. Each ERS supplier needs a formal agreement that specifies payment terms, dispute resolution procedures, and which items or categories fall under the ERS arrangement. This is not a handshake deal; it requires documented terms both parties have signed.

5. ERP configuration. Major platforms including SAP and Oracle offer native ERS functionality, but enabling it requires careful alignment of vendor master records, purchasing document types, and automatic payment parameters. Misconfigured settings can trigger duplicate payments or block legitimate ones.

The Change Management Factor

ERS reshapes responsibilities across your organization in ways that are easy to underestimate. AP staff lose their core invoice processing workload, which often means role changes, redeployment to exception handling, or reductions in headcount. This requires transparent communication and planning.

At the same time, receiving teams gain operational importance they may not have had before. Their data entry accuracy now directly determines payment amounts. Investing in training, scanning technology, and quality checks at the dock is not optional; it is a prerequisite for ERS to function without generating a steady stream of payment disputes.

Risks, Failure Modes, and Legal Considerations

ERS delivers measurable efficiency gains, but it also shifts risk in ways that deserve careful analysis before implementation.

Operational Failure Modes

Four categories of operational failure account for the majority of ERS problems in practice.

PO price vs. actual price mismatches. Supplier pricing rarely stays static. Contract renegotiations, raw material surcharges, volume tier adjustments, and currency fluctuations all create situations where the price on the original purchase order no longer reflects the agreed-upon cost at the time of delivery. When ERS generates payment based on the PO price, the result is either an underpayment that strains the supplier relationship or an overpayment that goes unnoticed until reconciliation. Both require manual adjustment, debit memos, or credit notes, precisely the kind of intervention ERS was designed to eliminate.

Quantity discrepancies at goods receipt. The accuracy of your receiving process becomes the accuracy of your payments. If a warehouse clerk records 100 units received but only 95 actually arrived, your supplier gets paid for 100. The reverse is equally problematic: partial deliveries generate partial payments that may not align with the supplier's billing expectations or cash flow planning. Unlike traditional invoicing, where the supplier's invoice quantity serves as a second data point, ERS relies entirely on your internal receiving records.

Quality issues discovered after receipt. Goods that pass an initial receiving inspection but are later found defective present a distinct challenge under ERS. Payment has already been triggered at the point of goods receipt, so rejecting or returning defective items requires a separate debit memo or return-goods process to recover funds. The longer the gap between receipt and quality discovery, the more complex the recovery becomes.

Master data drift. ERS matching depends on precise alignment between buyer and supplier master data: item numbers, units of measure, pricing terms, delivery tolerances. Over time, these records drift. A supplier updates a part number in their system but the buyer's PO still references the old one. Units of measure shift from "each" to "case" without both parties updating simultaneously. When this data falls out of sync, automated matching breaks down and exceptions pile up, eroding the efficiency gains that justified ERS in the first place.

Audit and Internal Control Concerns

ERS fundamentally changes the control environment around payables. In a traditional three-way match, the supplier's invoice functions as an independent verification that someone outside your organization is asserting the amount owed. ERS removes that external check. The same system that records goods receipt, creating the payment obligation, also authorizes the disbursement. Auditors, both internal and external, will flag this as a separation-of-duties concern.

The solution is not to abandon ERS but to implement compensating controls:

Regular reconciliation of ERS-generated payments against purchase orders, catching pricing and quantity variances before they compound.
Periodic supplier statement reconciliation, where you compare your payment records against the supplier's accounts receivable records to identify discrepancies from either side.
Clear audit trails that link every payment unambiguously to its corresponding purchase order line and goods receipt document, with timestamps and user identifiers at each step.
Tolerance thresholds that route payments exceeding defined variance limits to manual review rather than automatic processing.

These controls should be documented in your ERS policy and tested regularly as part of your internal audit cycle.

Legal and Tax Considerations

The legal dimension of invoiceless processing is where many ERS implementations encounter their most consequential risks. In numerous jurisdictions, tax authorities require an invoice document as the formal basis for VAT or GST input tax deduction. Where ERS eliminates the traditional invoice entirely, the buyer must establish that the payment record, or a generated settlement document, meets local tax documentation requirements. Failure to do so can result in denied input tax credits, penalties, or both.

The regulatory picture varies significantly across jurisdictions. Some countries explicitly accommodate ERS or self-billing arrangements through specific provisions that define what documentation the buyer must produce and retain. Others are entirely silent on the topic, creating ambiguity that organizations typically resolve through conservative interpretation or advance rulings from tax authorities. At a broad level, the US places relatively few invoice-specific requirements on domestic B2B transactions but requires adequate records for tax substantiation, while EU member states generally have formal self-billing provisions that can accommodate ERS-like arrangements when structured to meet local invoicing rules.

Mandatory e-invoicing adds a further layer of complexity. Jurisdictions including EU member states, India, and parts of Latin America are progressively requiring structured electronic invoice documents for every B2B transaction, often transmitted through government-operated clearinghouse platforms. Some of these regimes may require an electronic invoice to exist for each transaction regardless of the commercial arrangement between buyer and supplier, which can directly conflict with pure ERS arrangements where no invoice is generated at all.

Be cautious with older published guidance listing specific countries as "ERS-friendly" or "ERS-compatible." Regulations change, and the interaction between ERS rules, self-billing provisions, and emerging e-invoicing mandates is evolving rapidly across nearly every major trading jurisdiction. A country that accommodated invoiceless processing five years ago may have since introduced e-invoicing requirements that alter the compliance calculus entirely.

The practical recommendation is straightforward: consult local tax counsel in every jurisdiction where you plan to operate ERS before implementation. This applies to both the buyer's jurisdiction and each supplier's jurisdiction, since VAT and GST obligations often involve both parties. The cost of jurisdictional tax review is modest compared to the exposure from non-compliant invoiceless processing across your supply chain.

ERS and the Modern Procurement Landscape

Evaluated receipt settlement has been available as a procurement strategy since the early 1990s, yet its adoption has remained concentrated among large manufacturers and their tier-one supply chains. The reason is not that ERS lacks value. Rather, the broader procurement technology environment remains remarkably underdigitized. According to Bain & Company's analysis of digital procurement adoption, fewer than 10% of companies have deployed procurement solutions based on key digital technologies, and for critical workflows like supplier relationship management, more than 60% have no tools or rely primarily on improvised Microsoft Office systems. Against that backdrop, the prerequisites ERS demands — clean master data, reliable goods receipt processes, tight PO discipline — have been out of reach for most organizations.

That picture is shifting. Modern AP automation platforms now achieve much of what ERS invoiceless processing promised, but through a different mechanism. Instead of eliminating the invoice entirely, AI-powered matching engines automatically reconcile incoming invoices against purchase orders and goods receipts with high accuracy, flagging only genuine exceptions for human review. For organizations that still receive invoices from their suppliers, this approach delivers many of the same labor-saving benefits as ERS: automated three-way matching, reduced manual intervention, and faster payment cycles. The key difference is that the invoice document is preserved, which satisfies compliance requirements and provides a clear audit trail without requiring suppliers to restructure their billing processes.

This distinction matters more now than it did a decade ago, because the global regulatory environment is moving decisively toward mandatory electronic invoicing. The EU's VAT in the Digital Age (ViDA) directive, India's expanding e-invoicing mandate, and established Latin American regulations all share a common expectation: a structured invoice document for every B2B transaction, transmitted through government-approved channels. In jurisdictions adopting these frameworks, pure ERS arrangements face new friction. If the tax authority expects to receive or validate an invoice for each transaction, a buyer-generated settlement without a corresponding invoice document may not comply. Organizations operating across multiple regulatory environments are increasingly turning to hybrid approaches — combining automated invoice generation on the supplier side with ERS-level matching efficiency on the buyer side.

ERS remains a valid and effective approach for high-volume, stable-pricing procurement relationships, particularly in manufacturing contexts where contract pricing is fixed, deliveries are frequent, and both parties have the systems maturity to support invoiceless processing. But it is one tool within a broader spectrum of AP automation strategies. Organizations evaluating whether to adopt ERS should weigh it against modern matching automation on three factors:

Supplier mix: How many of your vendors can realistically support ERS agreements? For the remainder, automated invoice matching may deliver comparable efficiency without requiring bilateral process changes.
Transaction volume: Does the volume of repetitive, stable-price purchasing justify the implementation and onboarding investment?
Regulatory environment: Do the jurisdictions where you operate accommodate invoiceless processing, or do e-invoicing mandates require an invoice document for every transaction?