Sign in Open validatorValidator
XSD+SCH Erhvervsstyrelsen (Danish Business Authority), NemHandel · OIOUBL 2.1, Schematron 1.17.2

Denmark OIOUBL 2.1 Reminder

Danish payment reminder (OIOUBL 2.1 Reminder)

A Danish payment reminder (rykker) in OIOUBL 2.1, checked against the UBL 2.1 Reminder schema and the OIOUBL Schematron.

Validate with this schema Try it with the example

About

A reminder (rykker) tells the buyer that an invoice is overdue, with any fee or interest. OIOUBL sends it as the UBL Reminder document, through NemHandel like invoices.

E-invoicing in Denmark: 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 NemHandel's OIOUBL Schematron 1.17.2; the rule ids and levels (F- errors, W- warnings) are the ones their messages name.
  • The example is from the test files of the OIOUBL Schematron package, as phive-rules keeps them.

Files

14 files · 2.7 MB · Download all (.zip)
  • maindoc/UBL-Reminder-2.1.xsd main
    44.6 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

dk-oioubl-reminder.xml · 7.7 KB · passes the schema and the rules

View Open in validator

In CI and from code

The same schema by its name, dk-oioubl-reminder, through the API.

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

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