E-Invoice Check avatar

E-Invoice Check

Pricing

Pay per event

Go to Apify Store
E-Invoice Check

E-Invoice Check

Peppol UBL invoices built and checked against the official EN 16931 and Peppol rules, with the failing rules named.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Paco

Paco

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

10 days ago

Last modified

Categories

Share

Peppol UBL invoices built and checked against the official EN 16931 and Peppol rules, with the failing rules named.

Who it's for

Bookkeepers and finance admins of small businesses in Belgium (structured e-invoices over Peppol are compulsory for domestic B2B since 2026) and Dutch suppliers invoicing government. Use it for your own sales invoices, which you issue yourself, and to check structured invoices you receive.

What you get

Two tools. Validate takes up to 20 UBL invoice files and runs each through the UBL 2.1 schema, the EN 16931 rules and the Peppol BIS Billing 3.0 rules, all as published and not re-written. Each file gets a verdict (valid, invalid, not verified, not parsed), the failing rules in the rule's own words, where they fail, and which input to change. A batch summary shows the most common failing rules, so you fix your template once.

Build takes up to 5 invoices as fields (your assistant reads them from your PDF or accounting export), computes the VAT and totals, writes the Peppol UBL file and checks its own output against the same rules before returning it. A file that fails comes back with its failures and the inputs still needed, never as valid.

Limits

Produces and checks files; it does not send them through a Peppol access point and does not state legal compliance. Rules version is echoed in every result. Invoices (not credit notes) are built, with VAT categories S, Z, E, AE, K, G, O; no document-level discounts. Files above 200 KB are not parsed. Nothing is stored.

How to use

  • Run it in Apify Console or through the API: choose what to do, fill in the fields for that tool and start. The result is one item in the run's dataset.
  • From an AI assistant through Apify's MCP server (mcp.apify.com), which finds and runs this Actor with the same fields. What each choice does:
    • validate_einvoices: Check 1-20 UBL 2.1 invoices or credit notes (XML text) against the UBL schema, the EN 16931 rules and the Peppol BIS Billing 3.0 rules.
    • build_einvoices: Build 1-5 Peppol BIS Billing 3.0 UBL invoices from fields read off the issuer's own sales invoices (number, dates, seller, buyer, payment, lines with VAT), compute the totals, then run each result through the official rules before returning it.

Pricing

  • E-invoice validated (EN 16931 + Peppol): $0.036
  • Peppol UBL invoice built and verified: $0.3

Failed calls are never charged.