Combine invoicing and VAT validation in a larger n8n workflow

The scenario

A business selling B2B across several EU countries wants an n8n workflow that, for every order: validates the customer’s VAT number, generates the correct fiscal document (SdI or PEPPOL depending on the recipient), and keeps processing the remaining orders even if one fails — all inside the same automation that already handles CRM, shipping, or other systems, not in a separate script.

How it fits together

The official n8n node exposes two operation groups on the same credential: VAT Validation (via VIES, with automatic retries up to 5 times on temporary service failures) and Invoice (Create SdI Invoice, Create Peppol Invoice, Get Invoice Status, Verify SdI Document). In a structured workflow, the Validate VAT node’s output becomes the input deciding which invoicing operation to run, before continuing with the rest of the automation (notification, CRM, shipping).

To process a batch of orders without one failure blocking the whole workflow, the POP node exposes a “Continue On Fail” option: the error is attached to the output item instead of stopping execution, so the remaining orders still get processed.

Why it works

Teams already orchestrating multi-country orders in n8n get invoicing and fiscal validation as another node in the workflow they already run, with the same retry/failure-tolerance behavior already built into the node — no need to build retry or error-handling logic from scratch around a direct API call.