Accept receipt-based supplier settlement before it creates live payables

In evaluated receipt settlement, the buyer's system generates the supplier invoice record from purchasing and receiving information instead of waiting for an ordinary supplier invoice. That shifts the critical evidence upstream. The company needs confidence in the approved price, receipt quantity and settlement rules before those records create live payables.

SAP describes ERS as an agreed arrangement in which the supplier does not submit an invoice for the covered purchase-order transaction. The system calculates and posts an invoice document using purchase-order and goods-receipt data. This article concerns accepting that buyer-side process, not reconciling self-billed sales from the supplier's perspective.

Have the purchasing, accounting and tax owners confirm that the arrangement and documents are appropriate for the relevant parties and jurisdiction. A software capability does not establish tax-invoice validity or replace the supplier's agreement. Record the covered supplier sites, items and transaction types rather than enabling the approach indiscriminately.

Identify the purchase-order status and price approval required before settlement. Confirm the operative price version, currency, unit, discounts and separately handled charges. A provisional price that was acceptable for an early planning order may be unsuitable for generating a payable without another review.

Define which receiving events enter the run. A delivery recorded at the gate, a warehouse receipt and technical acceptance can be different events. The agreement and approved system design must determine the eligible population. The settlement preparer should not invent a new acceptance rule from whichever quantity is easiest to extract.

Keep disputed, reversed or incomplete receipts visible. If the process excludes them, require an exception report that identifies the missing decision. If a particular receipt state is included under the approved arrangement, preserve the reason so later invoice reviewers do not assume it was overlooked.

Check the tax and payment-term fields with the responsible owners. SAP documents product-specific prerequisites, including relevant purchasing settings and tax data. Treat those as configuration requirements to verify in the actual release, while leaving tax interpretation and policy approval with the qualified reviewers.

Use a test environment or the application's supported nonposting preview. SAP documents an ERS test mode that lists receipts that can and cannot be settled without making the postings. A comparable preview should let the team inspect the proposed documents and the excluded population before approving a live run.

For a hypothetical order, 500 units are authorized at $12 each. Two eligible receipts contain 200 and 150 units, giving 350 units ready for settlement. With no tax or other charges in this simplified example, the proposed supplier invoice amount is $4,200.

The undelivered 150 units are outside that settlement. Using the original order value of $6,000 would create $1,800 unsupported by the example's receipt-based rule. Conversely, settling only the most recent 150-unit receipt would omit $2,400 relating to the earlier 200 units if they had never been settled.

Retain receipt identifiers in the proposed output. A correct total is insufficient if it includes one receipt twice and omits another of the same size. The reviewer should be able to trace each line to its order, eligible receiving event and approved price.

Repeat the preview after the first sample settlement has been recorded in the test. The original 350 units should not become newly payable again. Inspect the system's settlement history or references that identify which receipts have already been processed, rather than rely on a date filter alone.

Now add a hypothetical new eligible receipt of 100 units on the same order. Its incremental settlement is $1,200 under the unchanged $12 price. The cumulative quantity settled is 450 units and the remaining undelivered quantity is fifty. Keep incremental output and cumulative status separate in the review.

Include a failed or interrupted run in the acceptance plan. Determine how the application reports records that posted successfully and those that did not. The authorized operator needs a supported retry process that does not recreate completed documents.

Check whether a revised receipt date, backdated entry or late interface message changes eligibility. These cases should have an explicit treatment. A batch window that works only when all receiving records arrive on time may leave valid transactions unprocessed indefinitely.

Assume twenty units from the original settled receipts are subsequently returned under an approved return process. At the same illustrative $12 price, the related correction is $240 before other applicable items. Preserve the return-to-receipt relationship so it reduces the appropriate settled population.

SAP's ERS guidance describes generation of credit memos for return deliveries following an already posted invoice. Verify the equivalent behavior in the installed system and inspect the resulting document. A physical return alone is not evidence that the financial correction completed successfully.

Distinguish a true return from correction of an erroneous receipt. The source events and required approvals differ, even if both reduce a quantity. Preserve the original record and correction reference rather than deleting the receipt from the review file.

Test a price correction separately from the quantity case. Have the purchasing and accounting owners define how a changed approved price affects already settled receipts and future receipts. Re-running the entire history at today's price without an authorized correction process can create unexplained adjustments.

Agree how suppliers receive settlement documents and report disagreements. The buyer needs delivery evidence and a clear contact route for incorrect quantities, prices or supplier identifiers. A document created successfully inside the ERP may still fail to reach the supplier's receivables team.

Tell accounts payable how to identify an ordinary supplier invoice for a transaction already covered by ERS. It should enter a controlled exception process rather than be posted automatically as a second liability. The supplier may have sent an information copy, misunderstood the agreement or disputed the generated document; those cases require different responses.

Use the source order, receipt and supplier references to compare documents. Two different invoice numbers do not prove that two different supplies occurred. The generated settlement must remain linked to the underlying goods so a later statement reconciliation can identify the same transaction.

Keep noncovered purchases on their appropriate process. A supplier may participate in ERS for specified goods while invoicing freight, services or another site separately. A supplier-wide block on all incoming invoices can hide valid amounts outside the agreed population.

When commissioning setup or outsourced operation, require a documented eligibility rule, approval map, preview output, posted references, supplier-notification evidence and exception ownership. Ask which decisions the provider may make and which must return to purchasing, receiving or the accountant.

Accept the service only after the normal receipt, repeated run, later receipt, return and conflicting supplier invoice behave as approved. Include a rejected record so the internal operator knows how to find unfinished work. A successful first invoice does not demonstrate that the correction and retry paths are reliable.

At close, reconcile eligible receipts to settlements created, returns or adjustments, remaining exceptions and the supplier balance. Keep payment approval separate from document generation under the company's existing controls. The useful result is a supported payable created once from approved upstream facts, with a traceable route for every later change.