Evaluated Receipt Settlement (ERS): How It Works
Jul 19, 2026
Jul 19, 2026
Convert a purchase order to Excel, CSV, or JSON
Submit your purchase orders
Drop documents here, or click to file
Up to 50 files per batch
Uploading...
Evaluated receipt settlement (ERS) is an accounts payable method where the buyer pays a supplier without a supplier invoice. Instead of waiting for an invoice, the buyer generates payment automatically from two documents it already has: the purchase order, which sets the agreed price and terms, and the goods receipt, which confirms what actually arrived. Payment equals received quantity times PO unit price, plus tax calculated by the buyer. Remove the invoice, and you remove the document that causes most matching exceptions.
ERS is common in high-volume, repetitive buying relationships, especially in manufacturing and automotive supply chains, and it is a native feature in ERP systems like SAP. Here is how it works and what it takes to run it well.
Evaluated receipt settlement is an invoice-free payment process. The buyer and supplier agree that the supplier will not send an invoice at all. When goods are received and recorded, the buyer's system values the receipt using the price on the purchase order, adds tax, and creates the payment on its own. The supplier gets paid on the buyer's schedule without ever cutting an invoice, and the buyer never has to match one.
The flow is short. First, the buyer issues a purchase order with agreed prices, tax codes, and payment terms. Second, the goods arrive and the receiving team records a goods receipt confirming quantities. Third, the system multiplies received quantity by the PO unit price, applies tax, and posts a payment to the supplier. There is no fourth step for an invoice, because there is no invoice. The purchase order and the receipt carry all the information the payment needs.
Traditional accounts payable runs a three-way match, comparing the purchase order, the goods receipt, and the supplier invoice before paying. ERS drops the invoice and effectively becomes a two-way process: PO against receipt. That is why ERS is sometimes described as an automated two-way match that pays on its own. The trade-off is control versus speed. Three-way matching catches invoice discrepancies but creates exception queues; ERS eliminates invoice discrepancies entirely because there is no invoice to disagree with, but it depends completely on the PO price and the receipt being right.
| Aspect | Three-way matching | Evaluated receipt settlement |
|---|---|---|
| Documents compared | PO, receipt, invoice | PO and receipt |
| Supplier invoice | Required | Not sent |
| Payment basis | Approved invoice | Receipt priced from the PO |
| Main exception source | Invoice mismatches | Wrong PO price or receipt |
| Best for | Variable or one-off spend | High-volume, stable, repeat buys |
ERS removes invoice processing, which is where much of AP labor and most matching exceptions live. Suppliers get paid faster and more predictably because payment no longer waits on an invoice arriving and clearing a match. Both sides cut paperwork, and disputes over invoice line items disappear because the price comes straight from the mutually agreed purchase order. For a buyer processing thousands of receipts against stable pricing, the savings compound quickly.
ERS only works when the purchase order price is accurate and current, because that price, not an invoice, is what gets paid. If a PO carries a stale or wrong unit price, ERS pays the wrong amount automatically and no invoice review stands in the way. It also depends on disciplined receiving, since the received quantity drives payment. That means ERS needs clean, structured PO data as its foundation, correct prices, tax codes, and line items on every order. Automated invoice and receipt matching and accurate purchase order line item extraction are what keep an ERS program from quietly overpaying. Broader accounts payable automation often sits alongside ERS to handle the spend that is not a fit for it.
SAP supports ERS natively in its materials management module. When a vendor is flagged for ERS and a purchase order is marked accordingly, SAP can generate the settlement automatically after goods receipt, pricing the receipt from the PO conditions and posting the liability without an invoice document. The setup requires the vendor master, the PO, and the tax handling to be configured correctly, which reinforces the same point: ERS is only as reliable as the purchase order data behind it. Teams moving PO data into SAP can see purchase order to SAP.
Rolling out evaluated receipt settlement works best as a phased move rather than a flip of a switch. Start by identifying suppliers that fit the profile: high volume, stable and agreed pricing, and a reliable receiving process on your side. Confirm the commercial agreement in writing, including that the supplier will stop sending invoices for the covered items and that your PO price plus your tax treatment will govern payment. Clean up the purchase order data for those suppliers first, since every wrong price becomes an automatic overpayment or underpayment once the invoice is gone. Configure your ERP so the ERS flag is set at the vendor and PO level, run a pilot on a small group of items, and reconcile the first cycles closely to catch pricing or tax gaps before you scale. Once the pilot proves out, expand supplier by supplier, keeping traditional three-way matching in place for everything that does not clearly qualify. Treat ERS as a program you extend where the conditions hold, not a policy you impose everywhere.
ERS pays off when you buy the same items from the same suppliers at stable, agreed prices in high volume. It is a poor fit for variable spend, frequent price changes, or one-off purchases where an invoice still serves a purpose. If most of your spend is repetitive and your PO pricing is trustworthy, ERS can take a large slice of manual invoice work off the table. If it is not, keep three-way matching where it earns its keep and reserve ERS for the suppliers where the conditions clearly hold.
From the same family of tools