3 minute read

What is a Purchase-to-Pay Process?

The Purchase-to-Pay process

A Purchase-to-Pay process is defined as the process from the dispatch of an order up to settlement of the supplier accounts payable. The Purchase-to-Pay process should thus be assigned to the procurement side of a company. The Purchase-to-Pay process may in some cases also be called Procure-to-Pay process. The Order-to-Cash process is the sales side equivalent of the Purchase-to-Pay process.

The diagram below shows an example of a Purchase-to-Pay process between a company (the customer) and a supplier.


Example of a Purchase-to-Pay process
Example of a Purchase-to-Pay process

Today, Purchase-to-Pay processes are executed with the support of EDI messages. Instead of paper documents, electronic business documents are exchanged directly between the IT systems of involved partners, with minimal human intervention.

The diagram above shows a customer transmitting an electronic purchase order (ORDERS) to a supplier. A supplier will be able to directly read the order data into his ERP system to also check the order there.

Can Web EDI Transform My Supply Chain - White Paper

A positive or negative purchase order response (ORDRSP) will be returned, depending on acceptance of the order or not. A supplier may indicate in his order response whether he accepts the order as is, accepts with changes or declines. A customer may in some instances also change his original purchase order. To do this, a customer will transmit a purchase order change (ORDCHG) to his supplier. For the sake of clarity, order changes are not shown in the diagram above. Order changes are also acknowledged with an order confirmation (ORDRSP).

Suppliers will send a despatch advice (DESADV) to their customer before shipping the goods. The despatch advice will inform the customer of an imminent delivery, allowing him to prepare his inbound logistics – e.g. free up storage space.

Upon receiving the goods, the customer will transmit a goods receipt advice (RECADV) to the supplier. With the goods receipt advice, the supplier is informed about any deviations, possibly due to loss in transit or rejection of goods.

A supplier will invoice his customer after delivery. A customer will provide the supplier with a remittance advice (REMADV) after settlement of the invoice.

Different types of documents may be used depending on the application and degree of complexity of the process.

Purchase-to-Pay process in an SAP ERP system

ERP system support is required for the effective implementation of a Purchase-to-Pay process. ERP systems such as SAP ERP offer excellent support for various types of Purchase-to-Pay processes and the necessary EDI document types.

In an SAP ERP system the Purchase-to-Pay process is supported by the MM module (Materials Management). Invoices may also have dependencies to the FI module (Finance) – especially invoices without an order reference.

Any questions?

Any questions about Purchase-to-Pay processes and support by EDI – also in connection with SAP systems? Please contact us – we look forward to assisting you!

 

SAP ERP and SAP S/4HANA are the trademarks or registered trademarks of SAP SE or its affiliates in Germany and in several other countries. 

most read

Keep on reading

7 minute read

Choosing an EDI Platform - A Breakdown

Looking for advice and information on EDI platforms and what what to look for when deciding between the various options? Look no further!

7 minute read

A Guide to Efficient EDI Systems

In this article we break down what an EDI system is, what different types of system offer, and things to remember when selecting a solution.

9 minute read

EDI Integration: What is It and How Can It Help Your Business?

Efficient EDI integration can have a transformative effect on your business. Read our article to find out how it can benefit you.

4 minute read

The Most Common ANSI ASC X12 Party Identifiers and How to Use Them

ANSI X12 party identifiers are a common source of errors. In this article we explore how to avoid issues and what the most common X12 party identifiers are.

9 minute read

Using EDIFACT Parties Correctly - A Breakdown

Errors involving EDIFACT party codes (or EDIFACT parties) are a key cause of master data issues. Find out why.

8 minute read

What is Master Data Synchronisation and Why is it Needed?

Find out how conducting a master data synchronisation can make everyday EDI exchanges and partner onboarding easier and more efficient.

4 minute read

A Brief Introduction to Modern EDI Systems

Are you aware of what modern EDI systems can offer? In this article we explore the recent trend towards fully managed solutions.

5 minute read

The Three Most Common EDI Pitfalls

While EDI can offer substantial benefits, achieving the perfect solution isn't always easy. Read our article to find out where many go wrong.

4 minute read

The Five Top EDI Trends: Expert Forecast

In this article we explore five current EDI trends and the extent to which they reflect the future of EDI more widely.

10 minute read

Full Service EDI Explained

What is full service EDI (AKA fully managed EDI), what benefits can it offer your business and is it really the future of B2B integration?

5 minute read

How Easy is Handling EDI In-house?

Handling EDI in-house may seem like a simple solution, but do you know what setting up and running an EDI system really entails?

5 minute read

What is EDI (Electronic Data Interchange)?

What is electronic data interchange? How does it work, and what benefits can it deliver for your business?

We use cookies to provide an optimal website experience. You decide which one you want to allow. Depending on the setting, however, not all functionalities may be available to you. Data protection & Imprint.