XSD+SCH DFØ (Norwegian Agency for Public and Financial Management) · EHF Forward Billing 3.0, EHF Post-Award G3 release 2026-09-29

Norway EHF Forward Billing 3.0

Norwegian forward billing invoice (EHF Forward Billing 3.0)

A Norwegian forward billing invoice (viderefakturering), such as grid rent billed by an electricity supplier, checked against the UBL 2.1 schema and DFØ's EN 16931 and Peppol rules for it.

About

EHF Forward Billing 3.0 is DFØ's format for invoices one company issues on behalf of another, for example an electricity supplier billing the grid company's rent (nettleie). It is a UBL Invoice with the identifier urn:fdc:anskaffelser.no:2019:ehf:forward-billing:3.0 after the Peppol BIS one.

E-invoicing in Norway: the rules in short and how to check an invoice →

Good to know

  • Rules run only when the document matches the schema. Documents over 50 MB are checked against the schema only.
  • The rules are the EN 16931 and Peppol BIS rules as DFØ adapts them for forward billing, from the EHF Post-Award G3 package of 29 September 2026.
  • The example is DFØ's grid rent example for a business customer from the same release.

Files

14 files · 2.7 MB · Download all (.zip)
  • maindoc/UBL-Invoice-2.1.xsd main
    58.8 KB View Download
  • common/UBL-CommonAggregateComponents-2.1.xsd
    2.3 MB View Download
  • common/UBL-CommonBasicComponents-2.1.xsd
    214.7 KB View Download
  • common/UBL-CommonExtensionComponents-2.1.xsd
    9.3 KB View Download
  • common/UBL-QualifiedDataTypes-2.1.xsd
    3.5 KB View Download
  • common/UBL-UnqualifiedDataTypes-2.1.xsd
    26.7 KB View Download
  • common/UBL-ExtensionContentDataType-2.1.xsd
    4.2 KB View Download
  • common/CCTS_CCT_SchemaModule-2.1.xsd
    44.2 KB View Download
  • common/UBL-CommonSignatureComponents-2.1.xsd
    5.4 KB View Download
  • common/UBL-SignatureAggregateComponents-2.1.xsd
    7.6 KB View Download
  • common/UBL-SignatureBasicComponents-2.1.xsd
    4.1 KB View Download
  • common/UBL-xmldsig-core-schema-2.1.xsd
    10.5 KB View Download
  • common/UBL-XAdESv132-2.1.xsd
    21.2 KB View Download
  • common/UBL-XAdESv141-2.1.xsd
    1.3 KB View Download

The validator loads all of these with their folder structure, so includes and imports resolve as published.

Business rules

Schematron · run in this order

The rules run after the schema check, only when the document matches the schema, and in your browser like the schema check (with SaxonJS by Saxonica). Each finding names its rule, such as BR-CO-15, and the line it points at; each rule has a page with what it checks.

Example document

no-ehf-forward-billing.xml · 6.2 KB · passes the schema and the rules

In CI and from code

The same schema by its name, no-ehf-forward-billing, through the API.

npx @xmlvalid/cli validate "**/*.xml" --schema no-ehf-forward-billing
- uses: xmlvalid/validate-action@v1
  with:
    files: "**/*.xml"
    schema: no-ehf-forward-billing
    api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
  -H "Authorization: Bearer $XMLVALID_API_KEY" \
  -F document=@no-ehf-forward-billing.xml \
  -F schema=no-ehf-forward-billing

Free accounts get 100 API validations a month. On Pro, a URL monitor can check a published document against this schema every hour and email you when it breaks. More CI setups