Service acceptance in Accounts Payable: what to check before approving an invoice

A supplier invoices the entire project, although the team has accepted only the first milestone. Accounts Payable sees the correct supplier details and the agreed order price. That does not establish that the invoiced scope has been performed and accepted. For services, the evidence is usually a reviewed outcome or confirmation of agreed work, rather than a box received into a warehouse.

Outsourced AP needs a clear rule for who can confirm service completion and how that evidence reaches the invoice team. The model below is an operational proposal, not a universal accounting or legal rule. Advance payments, subscriptions, payment deadlines and disputes must be considered under the contract and the client’s policies.

1. Define what will be accepted before work starts

Specify the billing unit in the order or contract: an hour, completed milestone, accepted document, batch or period of availability. Describe the expected outcome and acceptance criterion. A budget limit alone does not identify work already completed.

For hourly work, agree how timesheets are approved. For a project, identify the deliverable and version submitted for acceptance. For a subscription, check the period and availability conditions instead of inventing unit quantities. Do not demand evidence inconsistent with the contractual model.

2. Link completion evidence to the invoice line

The confirmation should identify the supplier, purchase order or contract, line, period or milestone, accepted quantity or value, review outcome and approver. Link the report, acceptance record or agreed deliverable. A general “everything is fine” cannot reliably match several milestones.

SAP Ariba documentation describes reviewing and approving a Service Entry Sheet before invoicing in that workflow. Oracle describes matching as linking an invoice to an order, receipt or consumption document. These are examples of system mechanisms, not a requirement for every business to use the same form.

3. Reconcile partial acceptance cumulatively

For each line, separately track ordered value, accepted value, previously invoiced value and the amount currently submitted for billing. Distinguish the current increment from the cumulative total. A report showing 60% completion does not mean another 60% if 30% was previously billed.

Example: a project comprises three milestones at PLN 4,000 net each. The first was accepted and billed. The second has just been accepted; the third remains in progress. An invoice for PLN 8,000 net covering milestones two and three requires clarification of the PLN 4,000 relating to unaccepted work. This is not automatic authority to make a partial payment or alter the invoice; an authorised person decides under the contract.

Example: three milestones at PLN 4,000 net each

4. Separate invoice registration from cost approval

Record the invoice arrival and due date even when acceptance evidence is missing. Then identify the exact gap: milestone confirmation, timesheet, price agreement or quality decision. Do not keep the document outside the register while waiting for the full evidence package.

Missing operational acceptance does not by itself determine accounting treatment, tax obligations or the right to withhold payment. These decisions belong to authorised client personnel. AP should expose the gap and deadline, not independently change settlement terms.

5. Do not replace missing acceptance with invented evidence

Do not create a confirmation merely because the system expects a receipt document. An approved purchase order confirms an intention to buy, not completed work. A submitted report may also require review by the service owner.

If the ERP technically labels service acceptance as a “goods receipt”, retain the correct category and real evidence. Do not imply delivery of materials that never existed. An acceptance correction should preserve the previous value, reason and approval; do not silently overwrite history.

6. Set the boundary between the AP provider and service owner

An external team may collect records, match identifiers, compare quantities and amounts, and route discrepancies for resolution when these activities are in scope. Confirming work quality requires someone who knows what was performed and has appropriate authority.

Appoint a substitute for the service approver and an escalation route before the invoice due date. No response should not automatically become “accepted”. Agreed exceptions, such as an advance payment, must remain identifiable as a separate case.

7. Test one service category before expanding

Choose one category and test full acceptance, partial acceptance, earlier invoicing, scope changes and corrections to an approved milestone. Measure invoices with complete evidence and the time needed to obtain confirmation. The aim is faster resolution of a specific gap, not an extra signature without review.

BackOffice Outsourcing provides Accounts Payable support within its finance and accounting processes. To organise records and the transfer of confirmations, review the finance and accounting service scope and describe your process to the team. Activities, system requirements and service acceptance responsibilities must be agreed for the particular engagement.

Sources and scope

• SAP Ariba: Examining service entry sheet approvals and spend accumulation
• Oracle: Matching Invoice Lines

Primary sources checked on 14 October 2026. SAP and Oracle descriptions concern their system mechanisms. The example, allocation of work and proposed controls are editorial guidance; we do not claim that BackOffice Outsourcing has implemented these systems.