Finance 6 min read

How to automate receiving e-invoices via Peppol and n8n

I won't go over the law or PDF invoices sent by email; other articles cover those. I'm showing the practical receiving process: what arrives via Peppol, and how the XML is parsed, checked and passed on.

How to automate receiving e-invoices via Peppol and n8n
Author: Maksym Kamenchuk, Nexflow — Banská Bystrica Published Updated

Electronic invoices are received through certified delivery providers, known as Access Points. Automation can only start after the Access Point: n8n can parse the invoice, check it and hand it over to your accounting system. How a particular provider makes the invoice available to you needs to be verified with them.

According to Peppol.org, the obligation to issue and receive electronic invoices starts on 1 January 2027 and applies to domestic transactions between VAT payers and to transactions with the public sector. Whether you need automation depends mainly on how many invoices you receive and on what your accounting software already handles on its own.

What actually arrives when you receive an e-invoice

According to the Slovakia profile on Peppol.org, invoices are sent and received through certified delivery providers (Access Points). They are usually made available through accounting software, a website or a mobile app.

The Financial Administration's e-invoice page describes a standardized format based on UBL 2.1, which defines the structure, rules and constraints of invoices in the Peppol network. According to the Financial Administration's document on the Slovak solution, the standard Peppol BIS Billing 3.0 "Invoice" is adopted. It is a structured electronic document, not an image or a PDF meant for reading.

According to Peppol.org, the structured e-invoice applies to domestic transactions between VAT payers and to transactions with the public sector. It does not apply to supplies to individuals for private use.

What an automated receiving process can look like

This is an example architecture, not a description of how any particular provider works.

  1. Delivery: the invoice arrives through your Access Point. If the provider offered a webhook call or file transfer via API, this could trigger the workflow.
  2. Receiving in n8n: the Webhook node serves as the workflow trigger and can receive data from other services. The maximum request size is 16 MB.
  3. Parsing the XML: the XML node converts XML to JSON, which is convenient to work with in n8n.
  4. Checking: the workflow verifies that the required fields are filled in and that the amounts add up.
  5. Handover: the HTTP Request node calls the REST API of your accounting system and creates the document.
  6. Exceptions: an invoice that fails the checks goes to a person for review, not into the books.

Whether your Access Point offers a webhook or API, and whether your accounting system does too, needs to be verified with the specific provider. The handover will look different depending on that.

Example of automated invoice receivingExample of automated invoice receiving1 · Delivery• Invoice arrives via Access Point2 · Receiving in n8n• Webhook node• Max request size 16 MB3 · Parsing the XML• XML node converts XML to JSON4 · Checking• Required fields filled• Amounts add up5 · Handover• HTTP Request calls REST API• Fails the checks: person reviewsExample architecture, not a description of a particular provider.
Diagram. Process illustration: from invoice delivery to handover to the accounting system.

Which n8n nodes are used

NodeWhat it does in this process
Webhookstarts the workflow when an event arrives from another service
XMLconverts XML to JSON and back
HTTP Requestcalls the API of any service with a REST API, for example an accounting system

Webhook supports authentication via Basic auth, Header auth or JWT. I recommend enabling it so that not just anyone who knows the address can trigger the workflow. You can find more about n8n on the n8n automation page.

n8n nodes in the receiving processn8n nodes in the receiving processNodeRole in the processWebhookstarts the workflow on an event from another serviceXMLconverts XML to JSON and backHTTP Requestcalls the API of a REST service, e.g. accounting system
Diagram. Three n8n nodes and their role in the process.

What the automatic check should verify

This is my practical suggestion, not a rule. A reasonable check before creating a document includes:

My recommendation: automatically create only invoices that pass all the checks. Let a person see everything else until you have verified the rules on real documents.

What to keep in mind regarding the rules

According to the Slovakia profile on Peppol.org, oversight of the Slovak environment is the responsibility of the Financial Directorate of the Slovak Republic (Finančné riaditeľstvo Slovenskej republiky) as the Peppol Authority. It accredits Access Points and manages the national rules. Questions go to efaktura@financnasprava.sk.

Verify the exact obligations and deadlines directly in the sources. The context is described in the article eInvoice 2027 in Slovakia (in Slovak). Nexflow does not provide tax or legal advice.

When it is not worth it

How to start without a big project

  1. Find out which Access Point you will receive invoices through and what it offers.
  2. Check whether your accounting system has an API.
  3. Build the workflow for one type of invoice and send exceptions to a person.
  4. Expand only after verifying on real documents.

The price of the work starts at €390; details are in the article How much AI automation costs for a small business.

Frequently asked questions

Can n8n receive invoices directly from Peppol?

You connect to the Peppol network through a certified provider (Access Point). n8n would receive the invoice from it and process it further. What exactly your provider allows needs to be verified with them.

What format does an e-invoice arrive in?

The Financial Administration describes a standardized format based on UBL 2.1 for invoices in the Peppol network. If you have the invoice as XML, the XML node in n8n converts it to JSON, which can be worked with further.

Do I need to write code to receive e-invoices?

An n8n workflow can use the Webhook, XML and HTTP Request nodes. Integration with a specific accounting system depends on its API and may also require custom development.

When does the obligation to receive e-invoices start?

According to Peppol.org, on 1 January 2027. It applies to domestic transactions between VAT payers and to transactions with the public sector. Verify the exact wording in the sources. Nexflow does not provide tax or legal advice.

What if an invoice fails the check?

I recommend not creating it automatically but sending it to a person for review. That way the error doesn't get into the books, and you can gradually adjust the check rules.

Sources

Related services

Servicen8n automation ServiceBusiness process automation

Related articles

FinanceInvoice automation: from the inbox to the ledger PricingHow much does AI automation cost for a small business?

Not sure whether automating invoice receiving pays off for you?

Tell me how many invoices you receive and which accounting system you use. I'll tell you whether it makes sense to build anything or whether what you already have is enough.

I want a free consultation →