e-invoice.be logoe-invoice.be
E-invoicingAdvisoryAPI
Peppol Radar

Scan your customer and supplier list for Peppol readiness

Invoice Viewer

View and inspect UBL invoices and credit notes

Peppol Check

Check any company's Peppol registration status

Peppol Validator

Validate your Peppol BIS 3.0 invoices against EN 16931

EN 16931 Mapper

Map invoice fields to the EN 16931 semantic model

VAT Validator

Validate EU VAT numbers against the VIES database

GLN Lookup

Look up GLN numbers and their Peppol registrations

Invoice Generator

Generate valid Peppol BIS 3.0 invoices from a form

Blog

Latest news, updates and insights about e-invoicing

Guides

Step-by-step tutorials and documentation

API Documentation

Complete API reference and integration guides

Contact

Get in touch with our support team

Peppol CheckStart now
E-invoice.bee-invoice.be
E-invoicingAdvisoryAPI

Tools

Peppol RadarInvoice ViewerPeppol CheckPeppol ValidatorEN 16931 MapperVAT ValidatorGLN LookupInvoice Generator

Help

BlogGuidesAPI DocumentationContact
Peppol CheckStart now

Stay updated

Get the latest updates about e-invoicing and e-invoice.be


E-invoice.bee-invoice.be

Simple, secure, and convenient e-invoicing solution and Peppol API. Send and receive e-invoices directly via email. No expensive software integration, no hassle

Certifications and status

Peppol Access Provider All systems normal

Product

  • Peppol API
  • Peppol CLI
  • Managed Access Point
  • Advisory
  • MCP Server
  • API Documentation

Tools

  • Peppol Validator
  • Invoice Viewer
  • Invoice Generator
  • Peppol Radar
  • Format Detector
See all tools →

Company

  • About Us
  • Contact
  • Customers
  • Blog
  • Guides
  • Webinars
  • CareersWe're hiring!

Resources

  • Pricing
  • Alternatives
  • Developers
  • Peppol Check
  • Sitemap

© 2026 E-invoice.be · All rights reserved · Terms · Privacy · Cookie policy · Brusselsesteenweg 119A, 1980 Zemst, Belgium · BE1018.265.814 · Made with 🥤

FacebookXGitHubLinkedIn

Customer story · PIXL CREATIONS

One credit pot. Every company they invoice for.

PIXL CREATIONS is a Brussels editorial and digital solutions agency. They run the work and the platforms that carry it. When the Belgian Peppol mandate landed, they needed one provider that could handle invoicing for every company in their portfolio, without splitting the bill across subscriptions.

Talk multi-entity setupRead the Peppol API
The PIXL CREATIONS homepage at pixl.brussels: editorial and digital solutions, Brussels.
pixl.brussels

The studio

Contenus. Contenants. Print and web. Sur-mesure.

PIXL handles editorial strategy, content production, and the digital platforms that carry the content. Half editorial agency, half software studio. The same team that writes the words also ships the code.

Editorial strategy
Audience-first content planning across print and web.
Creation des contenants
Multichannel supports. Sites, microsites, print, social.
Production and animation
Text, image and video shipped on a real publishing rhythm.
Gestion administrative
Behind every project, several companies that need clean invoicing.
“As a software and digital solutions company, we needed a Peppol provider that was both technically solid and easy to integrate into our workflow. e-invoice.be delivered exactly that. The platform is efficient, the support team is knowledgeable, and the credit-based model gives us the flexibility we need to manage multiple companies from a single partner.”
HPHugo PeraltaManaging Director, PIXL CREATIONS

Three reasons it fit.

PIXL evaluated a handful of Belgian access points. e-invoice.be won on three points that mattered for a studio running invoicing across several companies at once.

One credit pot, every company

PIXL invoices for several entities. A single prepaid balance covers Peppol traffic across all of them. No per-company subscription, no monthly minimum to defend. Credits draw down as documents ship.

An API a digital studio can actually wire in

Flat JSON, a Bearer token, clear docs. PIXL is half editorial, half software. The integration sat in the half that ships code, not the half that argues with XML schemas.

Support that knows Peppol, not a script

When the question is about a BIS rule, an SMP lookup, or a tax-category quirk, the answer comes back from someone who runs the access point. No level-one queue, no stalling.

The shape that fits a multi-entity studio.

The same Peppol traffic, two billing shapes. PIXL ran the numbers on a separate subscription per company versus one prepaid pot that covers all of them.

  1. 01

    Billing model

    Per-entity subscriptions

    One subscription per company. Each entity carries its own monthly base fee whether you ship one document or a thousand.

    One credit pot

    One prepaid balance. Credits draw down per document, no monthly base. Top up when the pot runs low.

  2. 02

    Adding a new company to the portfolio

    Per-entity subscriptions

    New contract, new payment instrument, new admin user, separate login.

    One credit pot

    Add the entity inside the existing account. Same login, same balance.

  3. 03

    Volume that sits across entities

    Per-entity subscriptions

    Each subscription has its own document allowance. Underused companies subsidise nothing.

    One credit pot

    Credits are fungible. A quiet month at one company funds a loud month at another.

  4. 04

    Stopping use of one company

    Per-entity subscriptions

    Cancel that subscription. Mind the notice period.

    One credit pot

    Stop sending under that sender identity. Credits stay on the balance.

  5. 05

    Peppol ID registration per company

    Per-entity subscriptions

    Same regardless of model. Every legal entity registers its own Peppol ID, tied to its VAT number.

    One credit pot

    Same. The platform runs the registration flow for every company you add.

How it runs in production

One balance. Many companies. Clean invoices.

  1. 01

    Top up the credit balance once

    PIXL keeps a prepaid balance on a single e-invoice.be account. The balance funds Peppol traffic for every company in the portfolio. No reconciliation across separate subscriptions.

  2. 02

    Each company invoices under its own VAT number

    Inside the account, every entity has its own sender identity. Invoices ship under the right company name, the right VAT number, the right Peppol ID. Credits get debited from the shared pot.

  3. 03

    Send. Get a Peppol receipt back.

    Documents leave the platform structured, signed, and routed to the buyer's access point. The dashboard shows real delivery status. No PDFs to chase, no silent failures.

Multi-entity FAQ

Questions every multi-company studio asks first.

Can we invoice for several companies from a single e-invoice.be account?

Yes. Each company sits inside the account as its own sender identity, with its own VAT number and Peppol ID. Invoices ship under the right company name. The credit balance is shared across every entity.

How does the credit-based model work in practice?

You top up a prepaid balance on the account. Every document sent or received debits the balance at the published per-invoice rate. No monthly subscription, no minimum spend, no per-entity fees. When the balance runs low, you top up again.

What does receiving cost? Is it included?

Receiving Peppol invoices is billed per document, the same way sending is. There is no free receive tier. Credits cover both directions on the same balance.

Do we need a separate Peppol ID for each of our companies?

Yes. Peppol identifies senders and receivers by their VAT or company number. Every legal entity registers its own Peppol ID. Inside e-invoice.be the registration flow handles it for each company you add.

Is KYC done once for the account or per company?

Per company. Account creation is instant, but each entity that issues invoices goes through company KYC. The check takes 24 to 48 hours and runs on the company itself. That is on purpose: everyone registered is a legitimate business.

Is the API the same whether we send from one company or several?

Same API. The sender identity is a field on the request. Pointing at a different company is a parameter change, not a separate integration.

Are credits ring-fenced per company, or shared?

Shared. One balance funds Peppol traffic across every company on the account. That is the point of the model.

What if we later spin out a company and want it on its own account?

Move it. Create a fresh account for the entity, transfer the Peppol ID registration over, and the company invoices from there. The old account keeps the remaining balance.

PIXL CREATIONS
Editorial and digital solutions agency
Brussels, Belgium
French-speaking studio, sur-mesure work
Customer since 2026
Live on the e-invoice.be Peppol API
Multi-entity invoicing

Invoicing for several companies at once?

If your studio, holding, or agency runs invoicing across more than one entity, the credit-based model is built for that shape. One balance, every company, no per-entity subscription.

Talk to us about your portfolio

Account creation is instant. Company KYC takes 24 to 48 hours. That is on purpose.