Skip to content
Change language: English

Error

FX-SCH-A-000555: Use a permitted invoice type code

In short

Error: fails the selected checks.

FX-SCH-A-000555 means your invoice type code (BT-3) is non-empty but not permitted by the EN 16931 profile. Put the appropriate permitted code in rsm:ExchangedDocument/ram:TypeCode, such as 380 for an invoice or 381 for a credit note.

On this page

What it means

This rule compares a non-empty ram:TypeCode under rsm:ExchangedDocument with the EN 16931 profile's permitted document type codes for Factur-X and ZUGFeRD. Examples include 380 for an invoice, 381 for a credit note, 384 for a corrected invoice and 389 for a self-billed invoice. An empty value passes this particular test; BR-04 addresses the type code's presence separately.

Why it matters

The type code identifies the kind of document. Using the appropriate standard code distinguishes an invoice from a credit note or another document type.

How to fix it

Confirm which document type you are issuing. Correct it in your source invoice or export configuration, ensuring ram:TypeCode contains the corresponding permitted code without a text label. Do not change the code to 380 unless the document is an invoice. Export the corrected document and check it again.

Once the file is corrected, check it again for free: Validate a ZUGFeRD invoice

Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice Beta

The rule as published

Value of 'ram:TypeCode' is not allowed.

Where this rule applies

Rule set Version
Factur-X 1.09 EN 16931 1.0.9-2
ZUGFeRD 2.5 EN 16931 2.5.2
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether FX-SCH-A-000555 still fails, and which other rules do.

Updated 6 November 2026