xmlvalid
Sign in Open validator
XSD+SCH OpenPeppol · PINT JP 1.1.3

PINT JP Invoice

Peppol PINT JP invoice (Japan)

A Peppol PINT JP invoice for Japan, checked against the UBL 2.1 schema, the PINT Billing rules and the Japanese rules OpenPeppol publishes.

Validate with this schema Try it with the example

About

PINT JP (JP PINT) is the Japanese specialization of Peppol International (PINT) Billing, made for the qualified invoice system (インボイス制度): its rules check the Japanese fields on top of PINT, such as the seller's Registration Number for Qualified Invoice and tax amounts in JPY without decimals.

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

E-invoicing in Japan: 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 OpenPeppol's PINT JP 1.1.3 artefacts as published (the compiled XSLT): the general PINT Billing rules, then the Japanese rules.
  • The example is one of OpenPeppol's PINT JP 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

Japan-PINT-Invoice-UBL-Example.xml · 28.7 KB · passes the schema and the rules

View Open in validator

In CI and from code

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

npx @xmlvalid/cli validate "**/*.xml" --schema pint-jp-invoice
- uses: xmlvalid/validate-action@v1
  with:
    files: "**/*.xml"
    schema: pint-jp-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-jp-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