Skip to content

Procure-to-Pay Automation and System Evaluation

Requisition to payment, automated, and an independent view of which procure-to-pay software fits. An approval trail that stands up in an audit.

What procure-to-pay actually is

Procure-to-pay is everything between someone deciding they need something and the supplier being paid for it: requisition, approval, purchase order, receipt, invoice matching, payment.

The reason to treat it as one process rather than as procurement plus accounts payable is that the money is committed at the requisition. Everything after that is administration of a decision already made.

Of EU enterprises send an invoice a machine can process
38.7%Of EU enterprises send an invoice a machine can processEurostat, ICT usage in enterprises (isoc_eb_ics), EU27, ten or more employees, reference year 2023.
Still send paper invoices
70.2%Still send paper invoicesSame Eurostat dataset. The question allows more than one answer, so the shares overlap.
German issuing obligation, above EUR 800,000 turnover
1 Jan 2027German issuing obligation, above EUR 800,000 turnoverBundesministerium der Finanzen, FAQ on the mandatory e-invoice. Everyone else follows on 1 January 2028.
AustriaSwitzerlandGermany

One of these three countries has a deadline set by parliament. The other two have one set by their customers.

Select a country for its runway. Every one of them is also written out below.

Germany

Fixed statutory dates. Two of them are inside the next two budget cycles.

  1. 1 January 2025: You must be able to receive In force

    Every domestic business has had to accept a structured e-invoice since this date. An email inbox satisfies it, which is why it passed quietly. Being able to receive one is not the same as being able to process one.

  2. 1 January 2027: Issuing, above EUR 800,000 Ahead

    Issuers with more than EUR 800,000 of prior-year turnover must send structured invoices. This is the date most German mid-caps are actually working to, and it is one year earlier than the one usually quoted.

  3. 1 January 2028: Issuing, everyone Ahead

    The transition ends. Domestic B2B invoicing is structured, without exception, and the EDI arrangements tolerated until the end of 2027 are not.

Austria

No B2B mandate, and no legislated date for one. The dates you will be quoted are advisory commentary.

  1. Since 2014: Public sector only In force

    Suppliers to federal bodies must invoice electronically, through the Unternehmensserviceportal in ebInterface or via Peppol. It is a procurement condition rather than a tax obligation, and it has been settled for over a decade.

  2. No date: B2B is voluntary No obligation

    There is no adopted Austrian law requiring structured B2B invoices, and no draft with a date in it. The finance ministry has signalled a Peppol-based approach aligned to the EU timetable. Anyone quoting you 2027 or 2028 for Austria is quoting an expectation, not a statute.

  3. By 2030: The EU dates apply anyway Ahead

    Austria is a Member State, so the EU obligations below land regardless of what Vienna legislates domestically. An Austrian company invoicing across a border is on the 2030 date whether or not a domestic mandate ever arrives.

Switzerland

Outside the EU, so none of it applies. Your German customers apply it for you.

  1. Since 1 January 2016: Federal contracts above CHF 5,000 In force

    Suppliers to the federal administration invoice electronically. The detail most summaries leave out is that it has to go through one of the certified service providers or an approved interconnect: direct Peppol and plain email are not accepted routes.

  2. No date: B2B is voluntary, and likely to stay that way No obligation

    There is no Swiss B2B mandate and none proposed. eBill and the QR-bill are what actually runs, and adoption is high in manufacturing, pharma and logistics because it pays for itself rather than because anyone requires it.

  3. From 1 January 2027: Your German customers become the mandate Ahead

    This is the one that matters. A German buyer above EUR 800,000 of turnover has to issue structured invoices from 2027, and will expect to receive them the same way. A Swiss supplier to that buyer is on the German timetable, enforced commercially rather than legally, which in practice is the stricter of the two.

The EU, above all three

Two dates, both from adopted law. Several published summaries get the first one wrong by two years.

  1. 1 July 2030: Cross-border digital reporting Ahead

    Under ViDA, intra-EU B2B transactions are reported digitally and invoiced in the European standard. If you invoice across a border, this is the date your invoice data becomes a filing rather than a document. You will see 2028 quoted for this. It is 1 July 2030.

  2. 1 January 2035: Domestic systems converge Ahead

    Member States running their own real-time reporting must align it with the EU model. Anything built to a purely national specification between now and then carries a conversion cost, and that cost is worth pricing into the decision today.

Which of the three you are in changes the deadline, not the work

The build is the same in all three: structured invoice data, checked against the contract before it is sent, in the format the receiving market expects. What changes is who sets the date. In Germany it is the legislature, and it is close. In Austria and Switzerland it is whichever of your customers is subject to a mandate first, which is harder to plan around precisely because nobody publishes it.

Germany: Wachstumschancengesetz and the Federal Ministry of Finance guidance. EU: Directive (EU) 2025/516, adopted 11 March 2025, and the European Commission ViDA pages. Austria and Switzerland: the absence of a B2B instrument, confirmed against both finance ministries rather than inferred from a vendor roadmap. All listed in full under Sources.

The money is committed at the requisition. Most finance functions find out at the invoice.

Six stages, one line. The distance between the two marks is the part of your spend that nobody is deciding any more.

  1. RequisitionCommitted here
  2. Approval
  3. Purchase order
  4. Receipt
  5. InvoiceDiscovered here
  6. Payment

Committed here

An approved requisition is a liability. Nothing after this point decides whether you spend, only how long it takes to record that you did.

Discovered here

By the time the invoice arrives the goods are delivered, the supplier has performed, and the only open question is whether you pay. That is recording spend, not controlling it.

Which is why starting at the invoice does not work

A programme that begins with invoice processing moves the second mark left by nothing at all. The invoices post more quickly and the spend is still a surprise. Underneath it sits the other cost: every invoice that needs a person is a few minutes of someone’s day, and the total is a headcount nobody has ever added up.

What moves the first mark

Approval happens before the commitment, not after it

Requisition and approval move ahead of the order, with the rules applied by the system rather than by whoever reads the email first. The control point lands in the one place in the cycle where the answer can still be no.

Orders and receipts carry structured data

Not because structure is virtuous, but because it is what makes automatic matching possible at all. An order a machine cannot read is an order a person has to read, and that person is the bottleneck you were trying to remove.

Only the exceptions reach a person

Three-way matching posts an invoice that agrees with its order and its receipt without a human. The ones that need judgement are the ones that get it. And the receiving side is on a legal timetable rather than a preference, so the format is not a choice you get to defer.

The German timetable is set by the Wachstumschancengesetz and the Federal Ministry of Finance guidance; the format is EN 16931 in its 2026 edition. Access to the approval trail is scoped and evidenced under the same controls as everything else the group runs. All listed in full under Sources.

What you get

Four consequences of moving the control point, and each one is the same move rather than a separate feature. Open any of them for what it means in practice.

  • Spend becomes visible while it can still changeFrom the control point moving to the requisition.

    A budget conversation held at the invoice is not a conversation, it is a reconciliation. The goods are delivered, the supplier has performed, and the only decision left is whether you are the sort of company that pays its bills. Held at the requisition, the same conversation can still end in no, or in a different supplier, or in a smaller quantity.

    That is the whole of the difference between controlling spend and recording it, and it is why the sequence matters more than the tooling. A finance function that sees commitments as they are made can forecast them; one that sees invoices can only explain them afterwards.

    It does not make anyone spend less by itself. It puts the decision in front of a person who has the authority and the budget in view at the moment it is still a decision.

  • Most invoices post without a personFrom orders and receipts carrying structured data.

    Three-way matching is not new and most finance functions already have it. What they do not have is orders and receipts a machine can read, which is the precondition rather than the feature. An invoice can only be matched automatically against documents that exist in a form something can compare.

    Once they do, the ordinary invoice stops involving anyone. It agrees with its order and its receipt, it posts, and nobody sees it. The exceptions are the ones that reach a person, which is what an accounts payable team is for and what it has mostly not been doing.

    The saving is not in minutes per invoice. It is that the volume needing a person collapses to the volume that genuinely needs judgement, and those are two very different numbers.

  • The approval trail is evidence, not archaeologyFrom the approvals happening in a system rather than in email.

    An approval that happened in an inbox has to be found before it can be shown. An approval that happened in the process is recorded by the system that performed it, at the moment it happened, with who, when and against which budget already attached.

    That changes what an audit costs. A sample request is answered by retrieval rather than by investigation, and the answer is the same every time it is asked. Access to that trail is scoped and evidenced under the same controls as everything else the group runs, so the audit trail does not become its own exposure.

    It also survives people leaving. A trail held in one person’s mail file leaves when they do, and nobody notices until the year it is needed.

  • Maverick spend stops being invisibleFrom every commitment passing the same gate.

    Spend outside the agreed process is not usually defiance. It is someone with a deadline finding the shortest path, and the shortest path is short precisely because it skips the requisition. You cannot manage what you only meet at the invoice.

    Once every commitment passes the same gate, the ones that went around it are visible as a category rather than as individual surprises. That is the point at which you can decide whether the process is being avoided because it is wrong or because it is slow, which are different problems with different fixes.

    The usual finding is that it is slow. Which is an argument for making the gate fast rather than for making it stricter.

The number to ask for

What proportion of your invoices could post today without anyone touching them, split between those with a purchase order behind them and those without. That single figure is the whole business case, it depends far more on your data than on any product, and it is usually what nobody has measured before a supplier is asked to quote.

The mirror image, money coming in rather than going out, is order-to-cash. The tail end of this process, taken on its own, is invoice-to-pay.

Where this sits

Choosing a suite is its own piece of work, and we have written the criteria down: how to evaluate a procure-to-pay suite.

Procure-to-pay is a control problem on the surface and an information problem underneath it. That underneath is Information Value Management: what the information behind it is worth, what it costs to hold, and what a change to either returns.

We start with the invoices that need a human today and work out why, which is usually a smaller list than anyone expects and a bigger saving.

Review your spend flow

Procure-to-pay, asked plainly

  • What is procure-to-pay?

    Procure-to-pay, often shortened to P2P, is the full cycle from someone deciding they need something to the supplier being paid for it. It covers requisition, approval, purchase order, receipt, invoice matching and payment. The point of treating it as one process is that spend is committed at the requisition, not at the invoice, and control applied only at the end is control applied too late.

  • What are the key benefits of procure-to-pay automation?

    Three that survive scrutiny. Spend is visible when it is committed rather than when it is invoiced, so the budget conversation happens while it can still change something. Invoices that match a purchase order and a receipt post without anyone touching them, which is most of them once the data is structured. And the approval trail is a by-product of the process rather than something reconstructed for an auditor afterwards.

  • What is the difference between procure-to-pay and order-to-cash?

    Procure-to-pay is money going out and order-to-cash is money coming in. P2P runs from requisition through approval and receipt to paying a supplier; O2C runs from a customer order through invoicing to the cash arriving. They share the same automation problem in mirror image, which is why the second one is usually far cheaper to do than the first.

  • What should you look for in procure-to-pay software?

    Ask what proportion of invoices it can post without a human, and under what conditions. That number is the whole business case, and it depends far more on whether your purchase orders and receipts carry structured data than on the product. Also ask how it handles the invoices that have no purchase order behind them, because that is where the manual effort actually sits.

  • How does e-invoicing affect procure-to-pay?

    It removes the argument about sequencing. Receiving structured electronic invoices is already mandatory for domestic B2B transactions in Germany, with issuing following on a fixed timetable, and invoices have to conform to EN 16931. That turns the receiving side of P2P from a discretionary improvement into a dated obligation, so it is usually the right place to start.