BR-BE-12:Mercurius endpoint format
B2G invoices to Belgian government must use the correct Mercurius endpoint format. The endpoint ID must be a valid Mercurius identifier.
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Mercurius Endpoint ID
What is BR-BE-12?
BR-BE-12 is a fatal validation rule defined in the Mercurius specification (BEL national rules). It checks whether mercurius endpoint format.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Why This Error Matters
BR-BE-12 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-BE-12
- ·Specification: Mercurius
How to Fix It
Technical Reference
Code Example
<cbc:EndpointID schemeID="0208">0123.456.789</cbc:EndpointID>Common Causes
- ·Using wrong scheme ID for Belgian government
- ·Endpoint identifier not from Mercurius system
- ·Outdated government endpoint
Seeing this in production? The API handles BR-BE-12 automatically. See the fix response →
Frequently Asked Questions
B2G invoices to Belgian government must use the correct Mercurius endpoint format. The endpoint ID must be a valid Mercurius identifier.
Use the proper Mercurius identifier from the Belgian government portal. Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.
Yes, BR-BE-12 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.
BR-BE-12 requires specific business data to resolve. Invoice Navigator detects the error and guides you through providing the needed information, then applies the fix with full audit documentation.
Related Content
Last updated: 3 March 2026
Resolve BR-BE-12 with Guided Input
The compliance engine detects this error and prompts for the required business data before applying a safe, auditable fix.