JP PINT e-invoice validation / JP PINT デジタルインボイスの検証

    1

    Validate Japanese Peppol JP PINT e-invoices against UBL 2.1 XSD, Schematron rules, and NTA registry.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    JP PINT e-invoice validation / JP PINT デジタルインボイスの検証

    Example session with this skill installed

    Validate the attached JP PINT 1.1.3 XML invoice and check if the seller's T-number is registered with the NTA. Use the registry_enhance option.

    • Read your context and instructions
    • Compiled the jp pint e-invoice

    I have validated the JP PINT 1.1.3 UBL Invoice XML against the OASIS UBL 2.1 XSD and OpenPeppol Schematron rules. The seller's T-number registration status was also checked via the National Tax Agency registry.

    Validation Results

    AttributeValue
    Document Validtrue
    Decisionaccepted
    Trustedtrue
    Registry Statusregistered
    VersionJP PINT 1.1.3
    T-NumberT1234567890123
    Issuer NameExample Japan K.K.
    Credits Charged$0.02

    The document successfully passed all 142 Schematron rules and matches the UBL 2.1 schema. The seller is a verified Qualified Invoice Issuer in the NTA database as of the current date.

    Next steps

    • Proceed with the payment workflow as the invoice is compliant.
    • Archive the validation evidence log for tax audit purposes.
    • Check X-JPVerify-Credits-Remaining if processing a batch.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Validate Japanese Peppol e-invoices (JP PINT 1.1.3 UBL Invoice XML) with JPVerify against the official OASIS UBL 2.1 XSD and OpenPeppol JP PINT Schematron, optionally checking the seller's qualified-invoice T-number in the National Tax Agency registry. Use when a task involves checking a JP PINT / Peppol (デジタルインボイス) XML invoice before sending it, accepting it into accounting, or paying it. Paid per call (API key credits or x402).

    Only processes JP PINT 1.1.3 UBL XML. No support for PDFs or images. Requires JPVerify API key or x402 credits. Registry check requires T-number in XML.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed today

    • Free with an Agensi account

    Requires

    Jpverify

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Environment Variables

    Allowed Hosts

    api.jpverify.com
    Listed7 days ago
    Updatedtoday

    What's inside

    Frequently Asked Questions

    The skill specifically validates Japanese Peppol JP PINT 1.1.3 UBL XML documents. It does not support older formats, international Peppol variants outside of Japan, or unstructured files like PDFs and JPEGs.

    Unlike LLMs which may guess at structure, this skill uses a dedicated validation engine to run official OASIS UBL 2.1 XSD and Schematron rules. This provides the exact rule IDs and error locations required for compliance, which general AI models cannot reliably generate on their own.

    Yes, by enabling the `registry_enhance` feature, the skill will cross-reference the seller's T-number (Qualified Invoice Issuer number) against the Japanese National Tax Agency database to ensure the sender is a registered tax entity.

    This skill is designed for seamless integration via standard REST HTTP calls or MCP (Model Context Protocol) servers, making it compatible with any AI agent or platform that supports external tool calls and API keys.

    The skill provides a clear `document_valid` status and a `decision` signal (`accepted`, `rejected`, or `manual_review`). If an invoice fails, you receive a detailed list of error messages and specific rule violations to help your team fix the document quickly.

    The validation engine is maintained to stay current with the latest Japanese Digital Agency and OpenPeppol standards. When JP PINT rules are updated, the skill is updated server-side so your workflows remain compliant without requiring manual code changes on your end.

    New in APIs & Backend