Skip to content
papii

Document template · be.accounting.invoice

Invoice — Facture (BE)

  • Render-verified
  • Commercial
  • Version 1.1.0

Belgian VAT invoice per Art. 53 §1 2° Code TVA and Art. 5 AR n°1 du 29.12.1992. E-invoicing mandatory for B2B from 1.1.2026 (Law 6.2.2024).

JSON Schema

Fields in this template

Data sent to the API is validated against the template’s JSON Schema before anything is rendered. This template defines 38 fields:

Field Required Type Description
company Required object Invoice issuer — Art. 5 §1 3° AR n°1.
company.name Required string
company.legal_form Optional string
company.bce_number Required string
company.vat Required string
company.address Required string
company.postal_code Optional string
company.commune Optional string
company.phone Optional string
company.email Optional string
company.iban Optional string
company.bic Optional string
company.logo_base64 Optional string
client Required object Invoice recipient — Art. 5 §1 4° AR n°1.
client.name Required string
client.vat Optional string Client VAT number (required for B2B).
client.bce_number Optional string
client.address Optional string
client.postal_code Optional string
client.commune Optional string
client.contact_person Optional string
invoice Required object Invoice body.
invoice.number Required string Sequential invoice number (Art. 5 §1 9° AR n°1). E.g. F-2026-0042.
invoice.date Required date
invoice.due_date Optional date
invoice.purchase_order_ref Optional string Optional purchase order reference.
invoice.peppol_routing_id Optional string Peppol routing ID for e-invoicing (mandatory B2B from 1.1.2026).
invoice.lines Required array of object Invoice lines (Art. 5 §1 5°–8° AR n°1).
invoice.vat_lines Optional array of object VAT breakdown by rate (Art. 5 §1 10°–11° AR n°1).
invoice.total_excl_vat Required stringnumber Total excl. VAT (€).

+8 more fields — the full JSON Schema is available in the dashboard and via the API.

POST /render

Generate it

One POST /render call: send your JSON, get the finished PDF back. Or skip the JSON entirely and describe the document in plain language on chut.app.

curl 
curl -X POST https://api.papii.eu/render \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "template": "be.accounting.invoice",
    "data": { ... },
    "options": {"language": "en"}
  }' -o invoice.pdf
Generate with AI on chut.app Try in the dashboard

Frequently asked questions

What is “Invoice — Facture (BE)”?

Belgian VAT invoice per Art. 53 §1 2° Code TVA and Art. 5 AR n°1 du 29.12.1992. E-invoicing mandatory for B2B from 1.1.2026 (Law 6.2.2024). On papii this document is available as template be.accounting.invoice: a JSON Schema plus a deterministic PDF renderer, so the same data always produces the same document.

Can I generate a Invoice — Facture (BE) with AI?

Yes. chut.app — the AI back office papii powers — fills this template from a plain-language description: you describe the document in one sentence, the AI structures the data, papii validates it against the schema and renders the PDF. Developers can also call the papii API directly with structured JSON.

Is the Invoice — Facture (BE) template legally compliant?

This template is render-verified: its schema, sample data and PDF output are automatically tested on every release. It is published with status “ready”, meaning it has not yet been through papii’s final legal review. Where it references specific legislation, that is stated in the template description — always have a professional check documents with legal effect before relying on them.