xmlvalid
Sign in Open validator
XSD+SCH OpenPeppol · PINT MY 1.3.1

PINT MY Invoice

Peppol PINT MY invoice (Malaysia)

A Peppol PINT MY invoice for Malaysia, checked against the UBL 2.1 schema, the PINT Billing rules and the Malaysian rules OpenPeppol publishes.

Validate with this schema Try it with the example

About

PINT MY is the Malaysian specialization of Peppol International (PINT) Billing, for e-invoices exchanged over the Peppol network in Malaysia. Its rules check the Malaysian fields on top of PINT, such as the supplier's Tax Identification Number (TIN), tax categories and amounts in MYR.

Its specification identifier (CustomizationID) is urn:peppol:pint:billing-1@my-1.

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 OpenPeppol's PINT MY 1.3.1 artefacts as published (the compiled XSLT): the general PINT Billing rules, then the Malaysian rules.
  • The example is one of OpenPeppol's PINT MY examples.

Files

14 files · 2.7 MB
  • 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

Invoice-Sample-SA_1-3-0.xml · 18.4 KB · passes the schema and the rules

View Open in validator

In CI and from code

The same schema by its name, pint-my-invoice, through the API.

npx @xmlvalid/cli validate "**/*.xml" --schema pint-my-invoice
- uses: xmlvalid/validate-action@v1
  with:
    files: "**/*.xml"
    schema: pint-my-invoice
    api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
  -H "Authorization: Bearer $XMLVALID_API_KEY" \
  -F document={{ $schema->example ?? 'document.xml' }} -F schema=pint-my-invoice

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