Evaluated receipt settlement is a procurement-to-payment method in which the buyer pays the supplier based on the purchase order and the goods receipt alone, with no supplier invoice in the cycle. The buyer’s system compares what was ordered against what arrived, and if the data matches within pre-set tolerances, it releases payment automatically. The trade-off is straightforward: lower processing cost and faster, more predictable payment to suppliers, in exchange for a heavier compliance and controls burden on the buyer, whose own records now stand in for the invoice.
How the Automated Payment Works
Traditional accounts payable performs a three-way match across the purchase order, the invoice, and the receipt. ERS drops the invoice and runs a two-way match: what the buyer ordered, at what price, against what the buyer actually received. If the quantities and prices align within the tolerance set in the contract, the transaction validates for payment with no human review.
Once validated, the system multiplies the purchase order unit price by the quantity on the goods receipt, applies tax accruals and any agreed pricing terms, and schedules an ACH or electronic funds transfer to the supplier’s account on the timeline in the master agreement. Because the payment clock starts at receipt rather than at invoice approval, suppliers generally see funds arrive more predictably than under traditional invoicing.
After payment is triggered, the system generates an electronic remittance advice for the supplier, itemizing which items and quantities are being paid for. That document is the supplier’s tool for reconciling their books and confirming that the buyer’s system calculated the payment correctly.
What the Contract Has to Cover
ERS cannot begin until both parties sign a master purchase agreement that formally waives the standard invoicing requirement and replaces the invoice, as the payment trigger, with a data-driven settlement tied to confirmed delivery. Both sides must explicitly consent, because the arrangement changes who bears the burden of payment accuracy.
The agreement locks in the commercial terms the automated system will use to calculate every payment: finalized unit prices per item, payment timelines such as 30 or 60 days from receipt, and delivery protocols spelling out how shortages and overages are resolved without a paper bill to reference. With no invoice arriving to confirm the price, the contract data is the single source of truth for every dollar that moves.
Price and Quantity Tolerances
Most ERS contracts include a tolerance clause defining how much a price or quantity can deviate from the purchase order before the system flags the transaction for manual review. A common approach sets both a percentage threshold and an absolute dollar cap, with the lower of the two controlling. Set the tolerances too tight and routine rounding differences stall payments; set them too loose and genuine pricing errors slip through unnoticed.
Discounts and Price Changes
Volume rebates, tiered discounts, and scheduled price adjustments have to be mirrored exactly in the buyer’s system. A mismatch between the contract and the system means the buyer either overpays or underpays on every affected transaction until someone catches it. Contracts typically require that price changes take effect only after both parties confirm the update in their respective systems, and they designate who is responsible for initiating that change.
The Documents That Drive the Process
ERS depends on clean, synchronized data across a small set of electronic documents. Each feeds the next, and a data error in any of them can stall the automated payment cycle.
Purchase Order
The purchase order is the origin point. It carries the fixed unit prices, item numbers, and quantities the buyer intends to procure, and it is generated in the buyer’s ERP system before being transmitted electronically to the supplier. The unit price on this document is the price the system will pay, so accuracy here is non-negotiable.
Advance Ship Notice
When the supplier prepares the shipment, they send an advance ship notice (ASN) telling the buyer what is in transit, including tracking numbers and item-level detail. In organizations using Electronic Data Interchange, the notice follows the standardized 856 transaction set format. The ASN gives the receiving dock advance warning, but it is not part of the payment match itself.
Goods Receipt
When the shipment arrives, receiving personnel create a goods receipt by scanning barcodes or entering quantities into the warehouse management system. Every field, including part number, quantity, and receipt date, must align precisely with the purchase order. The goods receipt is the document that, together with the purchase order, triggers the payment calculation, and sloppy data entry at the dock is the single most common reason ERS payments stall.
Handling Discrepancies and Returns
No supply chain runs perfectly, and ERS needs clear protocols for the inevitable mismatches between what was ordered, what shipped, and what actually arrived.
Quantity Discrepancies
When the quantity received differs from what the supplier shipped, the resolution depends on the direction of the mismatch. If the buyer receives less than the ASN indicated, the system pays based on what was actually received, and the remaining quantity may generate an additional payment if and when it arrives. If the buyer receives more than expected, a correction is processed, generating a corrected payment record that typically carries a suffix or flag linking back to the original transaction so both parties can reconcile the net amount.
Returns and Debit Memos
When goods are returned, the buyer’s system automatically generates a debit memo rather than waiting for the supplier to issue a credit. This is a meaningful shift from traditional AP, where the supplier initiates credits. In ERS, the buyer controls the financial record on both sides of the transaction, and suppliers should not send credit memos in an ERS arrangement, because the buyer’s system has already created the offsetting entry.
Price Corrections
If a price discrepancy surfaces after payment, the procurement representative initiates a correction that flows through the same automated system. The corrected record replaces the original, and the supplier reconciles the two records to determine whether a net payment or refund is owed. In a high-volume ERS environment, a single wrong unit price can compound across hundreds of receipts before anyone notices, so catching errors quickly matters.
Internal Controls the Missing Invoice Used to Provide
ERS removes a natural fraud checkpoint. In traditional AP, the invoice is an independent third-party document that must match internal records before payment flows. Without it, the buyer’s own data becomes the sole basis for disbursement, so internal controls need to be tighter, not looser.
Segregation of Duties
The most important control is ensuring that no single person can both create a purchase order and confirm receipt of the goods. If one employee can do both, they can fabricate an order, “receive” goods that never arrived, and trigger payment to a vendor they control. The same logic applies to other dangerous permission combinations:
- Purchase order creation combined with goods receipt lets someone order items for personal use and confirm receipt to hide the misuse.
- Vendor master maintenance combined with accounts payable processing lets someone create a fictitious vendor and route payments to it.
- Goods receipt combined with payment approval lets someone confirm receipt of goods that never arrived and approve the resulting payment.
Where a small team forces one person to hold conflicting permissions, compensating controls such as independent transaction reviews or automated exception reports become essential.
System-Level Safeguards
Beyond role segregation, the ERP system itself should enforce controls that humans might skip under time pressure. Automated tolerance checks prevent payments that deviate too far from expected amounts. Workflow rules should require multiple approvers for transactions above a dollar threshold. Vendor master changes, particularly bank account updates, should trigger a secondary verification step, because redirecting a vendor’s payment details is one of the most common procurement fraud schemes in any AP environment, and ERS makes it easier to execute if controls are weak.
Tax and Record-Keeping Obligations
Dropping the invoice does not drop the tax obligations. If anything, ERS increases the buyer’s compliance burden, because the buyer’s system generates the financial record of the transaction rather than receiving one from the supplier.
Electronic Records and Retention
IRS Revenue Procedure 98-25 provides the framework for businesses maintaining books and records electronically. It specifically acknowledges that a taxpayer who does not create the electronic equivalent of a traditional paper invoice in the ordinary course of business is not required to construct one, provided other record-keeping requirements are met.1Internal Revenue Service. Rev. Proc. 98-25 – Requirements for Keeping and Maintaining Books, Records, and Other Documents in an Electronic Storage System That provision is what gives ERS its legal footing for federal tax purposes: the goods receipt and payment record, maintained electronically, substitute for the invoice.
The IRS requires that these electronic records be retained in machine-readable form for as long as their contents may be material to tax administration, meaning at minimum until the statute of limitations for assessment expires.1Internal Revenue Service. Rev. Proc. 98-25 – Requirements for Keeping and Maintaining Books, Records, and Other Documents in an Electronic Storage System The general limitations period is three years from the date a return was filed, extending to six years if unreported income exceeds 25 percent of gross income shown on the return, with no limit at all for fraudulent or unfiled returns.2Office of the Law Revision Counsel. 26 USC 6501 – Limitations on Assessment and Collection Most tax professionals recommend retaining records for at least six or seven years to cover extended assessment scenarios, but the statutory minimum is three.
The system must also create a permanent, traceable link between the goods receipt and the subsequent payment record. Federal auditors expect to follow a clear path from the receipt of items to the exact price paid, without gaps. Failure to maintain this audit trail can result in the disallowance of business expense deductions during an examination.3Internal Revenue Service. Use of Electronic Accounting Software Records – Frequently Asked Questions and Answers
Sales and Use Tax
Under traditional invoicing, the supplier calculates and charges sales tax, and the buyer pays it. ERS flips that. Because the buyer’s system calculates the payment amount, the buyer also calculates and accrues the applicable sales or use tax, multiplying the unit price by the quantity received and applying the rate based on delivery location and the taxability of the item.
That creates a real compliance risk. Outdated tax tables or the wrong jurisdiction produce under- or overpayments on every transaction the system processes. States that audit use tax compliance will look at the buyer’s self-assessed calculations, and defending those calculations requires the same clean audit trail between the purchase order, goods receipt, and payment record. Tax engine configurations should be reviewed regularly, and exemption certificates for tax-exempt purchases should be documented and linked to the relevant vendor records.
Form 1099-NEC Reporting
When ERS payments go to service providers rather than goods suppliers, the buyer must track cumulative payments for information-return purposes. For tax years beginning after 2025, any person paid $2,000 or more for services in the course of a trade or business must receive a Form 1099-NEC, up from the previous $600 threshold.4Office of the Law Revision Counsel. 26 USC 6041 – Information at Source The form is due to both the IRS and the recipient by January 31 of the following year.5Internal Revenue Service. General Instructions for Certain Information Returns (2026)
ERS complicates this tracking, because the system is built around goods receipts rather than service milestones. Organizations using ERS for service payments need to make sure the system flags vendors approaching the $2,000 threshold and captures each vendor’s taxpayer identification number before the first payment. If a vendor fails to provide a TIN, the buyer must withhold 24 percent of each payment as backup withholding.6Internal Revenue Service. Backup Withholding Businesses filing 10 or more information returns during the year must e-file.5Internal Revenue Service. General Instructions for Certain Information Returns (2026)
Periodic Compliance Reviews
Because ERS automates so much of the payment process, problems tend to compound silently. A misconfigured tax rate or an incorrect unit price can run for months across thousands of transactions before surfacing. Internal audits should test a sample of ERS transactions at least quarterly, verifying that the purchase order price, the goods receipt quantity, the calculated payment, and the tax accrual all tie together correctly. Those reviews also confirm that tolerance settings, segregation of duties, and vendor master controls remain properly configured as staff turnover and system updates occur.