Documentation Index

Fetch the complete documentation index at: https://payhawk.document360.io/llms.txt

Use this file to discover all available pages before exploring further.

Still waiting weeks after close for invoices? Agent Fetch finds them automatically. | Learn more

E-invoicing networks to which Payhawk connects and their scope

Prev Next

This article explains which e-invoicing networks Payhawk connects to, and what Payhawk does and does not do with e-invoices, so you can tell whether a given country or use case is covered.

The networks Payhawk connects to

Payhawk receives e-invoices through exactly three network integrations:

  • Peppol - The open, country-agnostic network. It works in any Peppol-native market once you register, whether or not a mandate applies.

  • PPF - France's national network, through Payhawk's partner Invopop as the accredited platform (PDP).

  • KSeF - Poland's national network.

Any other national clearance network, for example SdI in Italy, myDATA in Greece, or ANAF/SPV in Romania, is not connected today. Whether a country is supported follows from this list and the country's network model:

  • If a country exchanges invoices over Peppol, you can receive through Peppol

  • If it relies only on its own national network and that network is not one of the three above, it is not connected.

How does Payhawk treat e-invoices

Payhawk receives e-invoices only. Issuing invoices, self-billing, and e-reporting are out of scope. E-reporting is a function of your ERP, and Payhawk is not an ERP.

Registration runs through Invopop as a white-label partner. This means Payhawk itself does not appear on official registers such as the French DGFiP list of accredited platforms. This is expected and is not a defect.