SAP S/4HANA procurement integration: what connects

Payhawk’s SAP S/4HANA integration now supports SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private Edition and selected on-prem setups. Payhawk pulls master data from SAP S/4HANA and posts each approved expense and supplier invoice back as its own correctly typed SAP document in real time. Payhawk already supports two-way PO sync for Oracle NetSuite through its NetSuite purchase order workflow, and bilateral PO sync with SAP S/4HANA is planned.

That gives you a clear route from intake to pay. Raise and approve purchase orders (POs), capture supplier invoices, and apply matching and proactive controls before spend happens at all. SAP S/4HANA remains your source of truth.

Many procurement tools say they integrate with SAP. For some, "integration" means a scheduled CSV upload or a middleware connector sitting between the two systems. Even fewer explain which edition they support, which direction data moves or what still doesn't sync.

This guide gives you the full picture of SAP S/4HANA procurement integration, including the current PO-sync limitation. You’ll also learn what to look for when evaluating procurement software that integrates with SAP.

What “SAP integration” really means for a procurement tool

When a vendor says “SAP integration”, it can mean multiple things. A file export, a middleware connector, a certified add-on and a native application programming interface (API) integration can move data. But they don’t offer equal control, speed, or ownership models.

A file export creates a gap between approval and posting. A middleware connector adds another workflow to monitor. A certified add-on can extend SAP S/4HANA, but can hide how data moves or who owns it.

Payhawk’s SAP S/4HANA integration is native, built in-house. It connects directly to SAP S/4HANA without third-party middleware or scheduled CSV exports. SAP S/4HANA owns financial records and master data. Payhawk controls indirect spend workflows before approved data reaches SAP S/4HANA.

Payhawk’s solution can:

• Code spend at source using general and specific master data from SAP S/4HANA, whether an employee files a request, a supplier bill arrives or a card is used
• Post each approved expense and supplier invoice to SAP S/4HANA as its own document, as a journal entry (JE) or vendor invoice (VI) in line with your posting rules
• Support a faster close by giving Finance all spend data in SAP S/4HANA as it happens, with no month-end upload
• Hide blocked SAP S/4HANA accounts, so approved purchases don't fail at posting

What master data procurement pulls from S/4HANA

When spend is coded after the purchase, errors reach SAP S/4HANA before Finance can catch them. Pulling master data from SAP S/4HANA at the start of the workflow puts the right GL account, tax code and cost centre on a request before anyone approves it.

Each procurement software with SAP integration works differently. For example, Payhawk pulls the coding data your team needs from SAP S/4HANA before employees submit spend. This S/4HANA master data sync supports accurate spend coding and cost centre mapping SAP workflows at the point of purchase.

Most master data flows one way, from SAP S/4HANA into Payhawk. Payhawk pulls GL accounts, tax codes, cost centres and suppliers from SAP S/4HANA, which remains the source of truth and system of record. Suppliers are the exception: [what Payhawk sends back]. This S/4HANA master data sync lets teams code indirect spend with the right values before it is captured.

See the full overview of data shared with SAP S/4HANA.

How the procurement flow connects to S/4HANA

So, how does Payhawk move spend from a request to an SAP S/4HANA record? Payhawk keeps the indirect spend workflow in one place. SAP S/4HANA keeps the accounting record. This setup gives Finance an audit trail from request to posting.

Payhawk manages the workflow before SAP S/4HANA receives the approved document. Here’s where each stage lives:

• Intake: Employees raise a request in Payhawk
• Purchase order (PO): Teams create and approve POs in Payhawk
• Request approval: Payhawk routes each request to the right approvers before a PO exists
• Finance approval: Finance approves the matched invoice for payment after the goods received note (GRN) and invoice arrive
• Match: Payhawk matches supplier invoices against the approved request or PO
• Post: Payhawk exports reviewed expenses and payment data to SAP S/4HANA in real time, as individual documents

Approved spend posts to SAP S/4HANA in real time, so Finance can review current records instead of working through a month-end backlog.

Payhawk runs the full PO workflow for POs raised in Payhawk. POs created in SAP S/4HANA or another tool don't sync into Payhawk yet. Bilateral PO sync with SAP S/4HANA is planned, and Payhawk already runs two-way PO sync with Oracle NetSuite through its NetSuite purchase order workflow. Payhawk works alongside SAP Materials Management (SAP MM) rather than replacing it.

If your team raises POs in SAP S/4HANA, Payhawk currently works as an accounts payable and expense layer with a request and approval workflows for indirect spend.

Two-way and three-way matching, and what actually posts

Invoices in inboxes. Purchase orders (POs) in email chains. Goods receipt note (GRN) data in shared drives. When data sits across systems, matching takes longer and errors slip through. AI-driven invoice extraction and PO matching can cut procure-to-pay cycle times by up to 80%. Automated matching controls help teams realise that potential, enabling faster, more accurate reconciliations and financial closes.

For instance, Payhawk’s SAP S/4HANA integration gives Finance and Procurement teams a defined point of control. Two-way matching vs three-way matching depends on whether a purchase requires goods receipt note matching. Payhawk checks supplier invoices before payment using the matching method that fits the purchase. Here’s how each method works:

Payhawk’s AI-driven optical character recognition (OCR) reads the PO ID on the supplier invoice and links the invoice to the PO. When OCR can’t find the PO ID, your team can link the invoice manually. Payhawk can also apply discrepancy rules, so small price or quantity differences don’t block payment.

After Payhawk matches and approves the invoice, Payhawk posts the invoice to SAP S/4HANA as its own document. Payhawk includes the GL account, cost centre, tax code, and document date. Payhawk also prevents duplicate orders automatically and itexports payment data for an expense only after the bank settles the transaction.

These two-way and three-way matching workflows strengthen goods received note matching. They help teams catch price and quantity differences before payment, reduce maverick and duplicate-payment risk, and keep SAP S/4HANA and AP records aligned.

Where SAP procurement integrations usually break

Your workflow can look solid at first. A manager approves a request. Procurement raises a PO. The supplier sends an invoice. Then the data reaches SAP S/4HANA, and the workflow stops.

A GL account is missing for the subsidiary. A supplier record uses a different name. A CSV upload leaves SAP S/4HANA behind on the latest spend insights. Whatever the cause, Finance must investigate the problem instead of focusing on strategic work.

For many, this scenario is the norm. Finance teams spend up to 40% of their time on manual reconciliations. That work increases errors and slows decision-making.

A procurement software that integrates with SAP only works when the data stays current. Here are four places where it can break, how to resolve it, and the risks to watch:

• Stale data from CSV and batch uploads: CSV uploads and scheduled batches leave SAP S/4HANA behind current spend
  Fix: Use real-time ERP posting for spending reviews
  Residual risk: Teams must still maintain current SAP S/4HANA master data
• POs raised outside Payhawk: Matching breaks when POs sit in a different system from the invoices they need to match
  Fix: Raise POs in Payhawk from approved requests, so every supplier invoice has a PO to match against
  Residual risk: Until bilateral PO sync with SAP S/4HANA is live, POs created in SAP S/4HANA stay outside Payhawk's matching
• Catalogue and item mismatches: Different item names, supplier records, or catalogue data can break matching
  Fix: Keep SAP S/4HANA as the single source of truth for supplier and catalogue data
  Residual risk: Teams must make supplier and catalogue changes in SAP S/4HANA first, not in Payhawk
• Missing or blocked subsidiary codes: This is the most common export failure in multi-entity SAP S/4HANA businesses. A GL account, tax code, or cost centre may not exist for the right subsidiary
  Fix: Use S/4HANA master data sync and keep SAP S/4HANA as the master-data owner
  Residual risk: SAP S/4HANA changes can still stop a posting until teams correct the code

For the complete seven-point list, see the what actually syncs in procurement-to-ERP integration (and where it breaks) guide.

Two capabilities worth asking every vendor about

From AI-driven invoice capture to approval workflows, you’re likely weighing features to improve your AP technology around SAP S/4HANA. Prioritise these questions to find the best stack.

Does each transaction post in real time?

Batch exports can leave Finance with a month-end backlog. A transaction may sit outside SAP S/4HANA until the next upload. Finance then has to reconcile data after the event.

Check how each vendor posts spend to SAP S/4HANA: does the vendor create individual documents in real time, or wait for a batch export? Look for real-time ERP posting that keeps SAP S/4HANA current throughout the month.

For example, Payhawk’s SAP S/4HANA integration posts each approved transaction as its own correctly typed SAP S/4HANA document.

Payhawk’s solution helps you avoid monthly CSV uploads, reduce manual reconciliations, and keep spend visible in SAP S/4HANA throughout the month.

Who is the issuer of record?

A bank feed can delay transaction data until a statement arrives. A third-party card issuer can add another dependency between the purchase and the finance record.

Ask who receives transaction data first. The answer determines whether Finance sees card spend at authorisation or waits for a bank statement or third-party feed.

For instance, Payhawk acts as the issuer of record for its corporate cards. Payhawk receives transaction data at authorisation, not from a later bank statement or third-party feed. That gives Finance visibility of card spend and more time to spot and block unauthorised transactions.

Payhawk-issued debit cards support UK, US, European Union (EU), European Economic Area (EEA), and European Free Trade Association (EFTA) entities. Payhawk-issued credit cards support UK and US entities.

What this means for your role

The same SAP spend management integration can solve different problems across Finance, Procurement, and IT. The best SAP S/4HANA procurement integration gives each team control before spend reaches SAP S/4HANA.

For example, a UK entity can approve a software subscription before buying. Payhawk can also apply the right cost centre and tax code before posting. That reduces the correction work finance teams do later.

Here’s how the best SAP S/4HANA integration can benefit each role:

• Financial Controller: Finance teams spend less time correcting coding errors and more time reviewing exceptions and strategic work. As posting accuracy improves, financial close reviews replace rescue missions
• CFO or Finance Director: Finance leaders see approved spend before month-end and can act before budget gaps grow. As a result, approval cycle time improves, and maverick spend control strengthens
• Head of Procurement: Procurement teams apply policy at request time, reducing off-policy buying and making supplier commitments easier to track. Intake and POs stay in one place
• SAP owner: SAP S/4HANA remains the master-data and financial-record owner. That setup enables SAP owners to protect data governance, support clean data, and reduce integration risk

Take Essentia Analytics, for example. Before Payhawk, the finance team relied on point solutions, spreadsheets and separate credit cards. The team chased invoices and corrected rekeying errors across payments, which slowed month-end close and limited visibility. Since onboarding Payhawk, the team has:

• Cut month-end close time in half, from more than 10 days to five
• Gained 100% visibility and control over payments, cards, invoices and reimbursements
• Eliminated rekeying and re-entry errors, improving reporting accuracy
• Reallocated 50% of a finance employee’s time to revenue-generating work

Questions to ask any vendor claiming SAP S/4HANA integration

Integration claims can sound convincing in a demo. The right questions will reveal how the workflow will behave in your SAP S/4HANA environment. Use this checklist when you compare procurement software vendors:

1. Which SAP S/4HANA edition does the vendor support, and is the integration available now?
   Ask whether the vendor supports SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private Edition, or both.
2. Which direction does master data flow, and can the vendor change it?
   Confirm that SAP S/4HANA stays the source of truth and system of record. Check which master data the vendor pulls from SAP S/4HANA, and which records, if any, it writes back.
3. Does each approved transaction post as its own document or in a batch?
   Enquire when the vendor posts data and which SAP S/4HANA document type each transaction creates
4. Do POs raised in SAP S/4HANA sync into the vendor platform?
   Confirm whether the vendor can see and match against SAP S/4HANA-created POs. Don’t assume two-way integration includes POs.
5. When does payment data reach SAP S/4HANA?
   Check whether payment data arrives at authorisation, after approval, or only after bank settlement.

Final takeaways

A procurement software that integrates with SAP should make life easier for Finance, Procurement, and IT by reducing manual re-entry, improving data quality, strengthening control over indirect spend, and cutting month-end reconciliation work.

Your chosen solution should also clarify the operating model. SAP S/4HANA should remain the source of record, while the solution manages indirect spend workflows before approved data reaches SAP S/4HANA.

The solution should also pull master data from SAP S/4HANA, so teams use the right GL accounts, tax codes, cost centres and supplier data from the start. In Payhawk, most master data flows one way from SAP S/4HANA into Payhawk, with suppliers as the exception.

Payhawk’s native SAP S/4HANA integration supports both Cloud Public and Private Editions. Approved spend posts in real time as individual SAP documents, not batch files. Invoice matching happens before payment. This setup helps Finance maintain cleaner records and tighter control without slowing the business down.

But one boundary remains: POs created in SAP S/4HANA don’t currently sync into Payhawk. If SAP MM manages PO creation, Payhawk supports the accounts payable and expense workflows around it.

To see how the workflow fits your SAP S/4HANA setup, explore Payhawk’s SAP S/4HANA integration and book a demo.

FAQ

Which SAP S/4HANA Cloud editions does Payhawk support?

Payhawk’s native SAP S/4HANA integration supports SAP S/4HANA Cloud Public Edition and SAP S/4HANA Cloud Private Edition. Each edition has its own connection and setup process.

Which way does master data flow between SAP S/4HANA and Payhawk?

Most master data flows one way, from SAP S/4HANA into Payhawk. Payhawk pulls GL accounts, tax codes, cost centres and suppliers from SAP S/4HANA, which remains the source of truth and system of record. Suppliers are the exception: [what Payhawk sends back]. This S/4HANA master data sync lets teams code indirect spend with the right values before it is captured.

Does Payhawk post transactions to SAP S/4HANA in real time?

Yes. Approved expenses and supplier invoices post to SAP S/4HANA as individual documents rather than as a batch export. This real-time ERP posting gives Finance cleaner records and reduces manual reconciliation work.

Do purchase orders created in SAP S/4HANA sync into Payhawk?

Not currently. Payhawk supports purchase order automation SAP workflows when purchase orders are raised and approved in Payhawk, but POs created in SAP S/4HANA don’t sync into Payhawk yet.

Does Payhawk use two-way or three-way matching?

Payhawk uses both. Whether Payhawk uses two-way or three-way matching depends on whether a purchase requires a GRN. Two-way matching checks the PO amount against the supplier invoice. Three-way matching also checks the quantity recorded on the GRN before payment.