SAP consulting and implementation services

FyerX helps finance, procurement and people teams implement and improve SAP business applications. We scope S/4HANA processes, SuccessFactors handoffs, Fiori experiences and ABAP or BTP extensions around the transactions that must still reconcile at close.

Discuss your technology project

When to bring in FyerX

One reason to review SAP purchase-to-pay is an amended invoice line still referencing its original goods receipt. It raises questions about company code, material, quantity, tax code and currency, the groups affected and the action each can take when something goes wrong. Our starting point is the purchase requisition and invoice hold. We trace it from goods receipt to accounting document with the people who own those decisions. The result gives your SAP process owner a specific first release, a testable operating outcome and a record of dependencies. For this example, the practical standard is simple: finance posts to the intended ledger and can trace the document chain.

First-release scope

Choose one purchasing organisation, a representative supplier and a limited set of document types. Agree how the team handles open orders at cutover. An order already received in the legacy application needs a different migration decision from one that has only been approved.

SAP S/4HANA process design

Map the movement from requisition to purchase order, goods receipt and accounting document. Review how company codes, purchasing organisations and approval roles affect exception routing. Bring the purchase requisition and invoice hold and its history to the design discussion. Check company code, material, quantity, tax code and currency against the policy in effect at the time. For a case involving an amended invoice line still referencing its original goods receipt, ask how the team currently recognises that the decision is complete. Agree whether the invoice reference is unique within its applicable company and supplier scope.

Fiori and role design

Choose the apps and business roles each user needs to carry out a task. Validate that a requester can see progress while posting and release authority remain with the right teams. Include buyer, goods-receipt clerk and accounts payable analyst in the walkthrough. Each sees a different part of the purchase requisition and invoice hold. Ask them to trace goods receipt to accounting document and establish where authorisation to release a blocked payment actually sits. Differences between the documented responsibility and the person carrying out the action belong in the scope.

ABAP and BTP extensions

Evaluate configuration, in-app extension and side-by-side development against the business rule, upgrade effort and ownership. Give each approved extension an interface contract and test evidence. Work through a purchase order converted in the legacy system and paid in SAP. Inspect the purchase order line and its linked receipt quantities before and after the event and ask the receiving team to explain the difference. A useful test includes partial returns, reversals and split deliveries, especially when the business consequence is an invoice matched to the wrong partial delivery. Agree which information to keep and who will use it during a period close and payment run.

Illustrative engagement

A goods receipt arrives after month end

  1. Starting point

    Purchasing has the purchase order and the warehouse has recorded delivery, but accounts payable cannot match the invoice.

  2. Decision

    Walk the receipt, invoice and posting dates through a test company code with a finance owner. Check tolerance rules and who can release an exception.

  3. Deliverable

    An agreed three-way match test pack and a named owner for blocked invoices.

SuccessFactors and employee data

Map where employee identifiers, organisational assignments and effective dates cross into downstream systems. Test a backdated transfer before enabling an automated update. For operational handover, give the SAP process owner a worked example from the quarter-close matching report. Reconcile the result against posted invoice values versus approved receipts. Agree how to hold the disputed posting for finance review before resuming payment when the evidence falls outside the accepted range.

A closer look at open purchase orders

Suppose a purchase order contains ten units and six have already arrived. Loading the original ten as a new open commitment can leave finance and the warehouse disagreeing on the quantity still due. The team needs the original order reference, the received quantity, any invoice already posted and the destination for the remaining commitment. Ask the buyer, warehouse operator and accountant to agree an example before rehearsing the conversion. Then test a return against that same order after cutover. This reveals whether references and posting rules survive the move well enough for normal support. The signed example becomes a useful regression test when purchasing rules change later.

Prove the finance posting before moving the plant

Ask two plants to process the same purchase order and the differences can be surprising. One books receipt on delivery, another waits for inspection, and the invoice may arrive before either event. We bring a purchasing lead, a warehouse supervisor and a finance user to the same session. Together we follow one real order through receipt, invoice matching and posting, including who releases a blocked invoice. That gives the SAP team actual decisions to configure for the first plant and a clear record of which differences the second plant must retain.

Before the first cutover rehearsal, we agree how finance will recognise a successful conversion. An order count alone tells us little about open quantities, amounts in local currency or tax postings. We prepare a small reconciliation pack with the source amounts, converted balances, tolerances and named signatories. Where a discrepancy falls outside tolerance, the pack identifies the team that can investigate and the point by which the migration lead needs a decision. Repeating that reconciliation during rehearsal lets the business assess its readiness with evidence it already understands.

What to bring to discovery

Bring an anonymised purchase requisition and invoice hold, a recent quarter-close matching report and an example of an amended invoice line still referencing its original goods receipt. Where the inputs contain sensitive information, supply synthetic equivalents that preserve the decision sequence. Ask the SAP process owner to identify who may approve authorisation to release a blocked payment. Record company code, material, quantity, tax code and currency with their meanings, including whether an empty value is permissible. Invite the people who use the purchase order line and its linked receipt quantities to describe the hardest discrepancy from the last cycle. The discovery log should capture the source evidence, responsible team and decision required.

Agreeing the first work package

Anchor the first work package in SAP S/4HANA process design and choose a deliverable such as a fit-to-standard decision log and reconciliation workbook. Define the boundary from goods receipt to accounting document so both teams know what a completed item looks like. For planning purposes, list partial returns, reversals and split deliveries separately from ordinary cases and record whether each is included in release one. Material scope changes include a company-code extension, a different owner for purchase requisition and invoice hold or a dependency that changes a period close and payment run. Agree the cost and acceptance consequence of each before committing delivery capacity.

An acceptance exercise for your team

Give the operators a supplier invoice matched to a purchase order with a partial goods receipt. Ask the SAP process owner to describe the expected business result before showing them the implementation. Introduce an amended invoice line still referencing its original goods receipt and follow the chain from goods receipt to accounting document. At each point, record the values of company code, material, quantity, tax code and currency that matter to the decision. The test succeeds when finance posts to the intended ledger and can trace the document chain. If evidence from the purchase order line and its linked receipt quantities disagrees, stop at the first observable difference and establish who can resolve it. Keep the starting data and explanation with the quarter-close matching report. This example can be adapted to the rules and responsibilities of your organisation.

How expenses reach management reporting

A transaction can post successfully yet reach an unexpected cost centre or profit centre. Select representative purchases, corrections and intercompany postings and trace them into the management report. Document which values are derived, which the user enters and who owns the master data that controls the derivation.

Planning around the operating calendar

Build the release around a period close and payment run. For SAP purchase-to-pay, that means agreeing when the purchase order line and its linked receipt quantities are available, when the SAP process owner can decide and what work would be interrupted by a late change. Select test material covering partial returns, reversals and split deliveries before reserving a business sign-off slot. Treat authorisation to release a blocked payment as a release dependency. If a company-code extension is introduced at the same time, check whether the original baseline for unresolved invoice blocks and posting differences still supports a meaningful comparison.

Exception ownership and recovery

One credible failure is an invoice matched to the wrong partial delivery. The first diagnostic step is to inspect the purchase order line and its linked receipt quantities and identify the authoritative version of the purchase requisition and invoice hold. Next, determine whether the invoice reference is unique within its applicable company and supplier scope. For an incident involving backdated employee transfers, an operator may need to hold the disputed posting for finance review before resuming payment. Agree that authority with the SAP process owner ahead of a period close and payment run. Capture the resolution in a fit-to-standard decision log and reconciliation workbook, including how buyer, goods-receipt clerk and accounts payable analyst can confirm recovery from their different perspectives. For repeat occurrences, compare the underlying fields rather than assuming every item in the exception queue has the same cause.

Handover and ongoing ownership

Put a fit-to-standard decision log and reconciliation workbook in the hands of the staff who will own SAP purchase-to-pay. Include a completed example from goods receipt to accounting document and a walkthrough for an amended invoice line still referencing its original goods receipt. Someone outside the delivery team should be able to locate the purchase order line and its linked receipt quantities, identify authorisation to release a blocked payment and act when the quarter-close matching report shows a discrepancy. After the rehearsal, update ownership for purchase requisition and invoice hold and document where to propose changes to company code, material, quantity, tax code and currency.

Planning your engagement

How to measure the outcome

Agree the measurement definition for unresolved invoice blocks and posting differences before changing SAP purchase-to-pay. Start with posted invoice values versus approved receipts, then review partial returns, reversals and split deliveries as a separate population if their expected treatment differs. A reliable baseline needs the reporting date, an owner for purchase requisition and invoice hold and a consistent definition of completion from goods receipt to accounting document. Test the quarter-close matching report with a case involving an amended invoice line still referencing its original goods receipt. If a company-code extension alters the population later, preserve the original baseline alongside the revised one. This gives the SAP process owner an explanation for a change in the number and a decision about which improvement to fund next.

Delivery and support responsibilities

For an advisory phase, ask FyerX to focus on the decision behind SAP S/4HANA process design. For an implementation, agree the behaviour of purchase requisition and invoice hold through goods receipt to accounting document and the evidence required from the purchase order line and its linked receipt quantities. For a team that already owns delivery, a bounded specialist assignment can focus on ABAP and BTP extensions. Keep authorisation to release a blocked payment with its named business or technology owner unless explicitly delegated.

What drives an SAP implementation estimate?

A template rollout across similar plants is a different undertaking from harmonising several charts of accounts. Show us the company codes, plants, interfaces and open transactions in scope. A sample month-end close is especially useful. It exposes local tax, valuation and reconciliation requirements that a module list tends to miss.

Frequently asked questions

SAP

What should stay standard in SAP?

A plant wants an extra step before releasing a purchase order. Ask whether the policy applies across the purchasing organisation or only to one material group. That distinction can change the configuration choice, who maintains the rule and the number of regression cases required at the next upgrade.

Which business users belong in testing?

Invite the buyer who raises the order, the warehouse user who posts the receipt and the accountant who clears the invoice. Have them work from the same document chain. If one tester creates all three records, a missing authorisation or handoff can remain invisible until the first real posting.

What would you need to assess SAP purchase-to-pay?

Bring one purchase requisition and invoice hold, an example from the quarter-close matching report and the people responsible for the purchase order line and its linked receipt quantities. A useful discovery exercise follows goods receipt to accounting document under both ordinary conditions and an amended invoice line still referencing its original goods receipt. The resulting scope should identify the business decision, environment access and operating owner required for the first work package.

Can we begin with SAP S/4HANA process design?

Yes. Define the first deliverable in terms of finance posts to the intended ledger and can trace the document chain. Agree with the SAP process owner how to test it using the purchase order line and its linked receipt quantities. The first phase can stop after the decision and evidence are delivered, or continue into Fiori and role design with scope and responsibilities already documented.

How does Fiori and role design fit into delivery?

It addresses the point in SAP purchase-to-pay where the team must understand company code, material, quantity, tax code and currency. Use an amended invoice line still referencing its original goods receipt to establish how information, permissions and ownership cross that boundary. The resulting acceptance case should demonstrate the invoice reference is unique within its applicable company and supplier scope and identify who takes over if the outcome is uncertain.

What happens to cases involving partially received orders?

Use purchase requisition and invoice hold as the starting reference and examine the purchase order line and its linked receipt quantities. The key question is whether the invoice reference is unique within its applicable company and supplier scope. Agree a treatment with the SAP process owner, preserve evidence for the quarter-close matching report and make the authorised next action visible to the team. Include the case in later release checks, especially after a company-code extension.

How do you test a backdated employee transfer?

Use two dates in the example: when HR entered the change and when the transfer took effect. Ask HR and finance which cost centre owns transactions in the intervening period. Test downstream records against that decision and record whether any adjustment is required.

What should we expect at handover?

Expect the agreed delivery evidence and a fit-to-standard decision log and reconciliation workbook. A useful sign-off is for the receiving team to trace goods receipt to accounting document, read the relevant entry in the quarter-close matching report and respond to an amended invoice line still referencing its original goods receipt using the material supplied. Document ongoing responsibility for updates to purchase requisition and invoice hold before closing the engagement.

How will our team decide whether to go ahead?

Ask whether finance posts to the intended ledger and can trace the document chain. Check the purchase order line and its linked receipt quantities with the SAP process owner and verify that authorisation to release a blocked payment is available during a period close and payment run. If a critical dependency remains open, identify its effect on posted invoice values versus approved receipts and the owner who can accept, resolve or defer it.

Which measures are useful after release?

Use unresolved invoice blocks and posting differences alongside the quarter-close matching report. For SAP purchase-to-pay, reconcile a sample against posted invoice values versus approved receipts and review the influence of partial returns, reversals and split deliveries. Confirm that a company-code extension or a new reporting definition has not changed the population before crediting an improvement to the work.

Who can operate the outcome internally?

Agree responsibilities among the buyer, goods-receipt clerk and accounts payable analyst. Give the receiving operator an unfamiliar example involving backdated employee transfers and ask them to investigate it through the purchase order line and its linked receipt quantities. Their ability to explain goods receipt to accounting document and identify authorisation to release a blocked payment is a practical test of the handover.

Can the rollout cross a financial close?

Work backwards from finance's close calendar. The controller needs time to compare balances, approve adjustments and rehearse any manual postings before the cutover window is fixed.

Talk to FyerX about SAP

Contact Technology