# Build and check Peppol e-invoices against the official rules

> Validate UBL invoice files against the UBL 2.1 schema, EN 16931 and Peppol BIS Billing 3.0, with each failing rule named in its own words, or build a Peppol UBL invoice from fields and get it back checked.

Who it is for: Bookkeepers and finance admins of small businesses in Belgium, where structured e-invoices over Peppol are compulsory for domestic B2B since 2026, and Dutch suppliers invoicing government.

## What you get

- **Validate in bulk**: Up to 20 UBL invoice files per run, each with a verdict: valid, invalid, not verified or not parsed.
- **Failing rules explained**: Every failing rule in the rule's own words, where it fails and which input to change.
- **Fix your template once**: A batch summary shows the most common failing rules across all files.
- **Build valid invoices**: Up to 5 invoices from fields: VAT and totals computed, the Peppol UBL file written and checked against the same rules before it is returned.

## How it works

1. To check files, choose `validate_einvoices` and pass your UBL files in `documents`.
2. To create files, choose `build_einvoices` and pass the invoice fields in `invoices`; your assistant can read them from a PDF or accounting export.
3. Run it in Apify Console, through the API or from your AI assistant.

## Use cases

- Checking your own sales invoices before Peppol becomes the rule for your customers.
- Checking structured invoices you receive before booking them.
- Finding the one template error that makes every invoice fail.

## Pricing

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

You pay per event listed above; there is no monthly fee.

## Limits

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

## Questions

### What does it cost?

$0.036 per document checked and $0.30 per invoice built.

### Are the rules rewritten or simplified?

No. The UBL 2.1 schema, EN 16931 rules and Peppol BIS Billing 3.0 rules run as published, and the rules version is echoed in every result.

### What if a built invoice fails the checks?

It comes back with its failures and the inputs still needed, never as valid.

Check your e-invoices: https://apify.com/eloquent_mountain/einvoice-check?utm_source=actors.taskmastergpt.nl&utm_medium=llms&utm_campaign=einvoice-check