E-Invoice Mandate Lint - EU 2026
Runs the same checker as the npm package
@readystack/einvoice-mandate-linton a Node.js runtime that pip installs for you (nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Lints UBL and CII invoice XML against EN 16931 and the national e-invoicing mandates that are live in 2026
Install
einvoice-mandate-lint file
Node 18+. The same 35 rules as the VS Code extension, from a terminal or CI.
Free
- Lint the invoice XML you have open - every EN 16931 core field plus the country mandate rules its CustomizationID and seller country select, reported with line numbers.
--ruleslists every rule
With a licence ($29 once)
- Scan every invoice XML in the workspace in one pass and export the findings as JSON, CSV or SARIF you keep and run in CI.
@readystack/einvoice-mandate-lint --dir ./templates --report html --out report.html
An EN 16931 / Peppol integration consultant reviews an invoice mapping at about $170 an hour.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "einvoice-mandate-lint": { "command": "npx", "args": ["-y", "@readystack/einvoice-mandate-lint", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: E-Invoice Mandate Lint - EU 2026
run: npx -y @readystack/einvoice-mandate-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/einvoice-mandate-lint --dir /work --ci)
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install readystack-einvoice-mandate-lint
einvoice-mandate-lint --help
Metadata
Release files for readystack-einvoice-mandate-lint 1.0.10.post1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| readystack_einvoice_mandate_lint-1.0.10.post1.tar.gz | 20.4 kB | Without provenance | Details for readystack_einvoice_mandate_lint-1.0.10.post1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_einvoice_mandate_lint-1.0.10.post1-py3-none-any.whl | Python 3 | none | any | Details for readystack_einvoice_mandate_lint-1.0.10.post1-py3-none-any.whl |
Total release size: 43.1 kB
Release files / readystack_einvoice_mandate_lint-1.0.10.post1.tar.gz
| Download URL | readystack_einvoice_mandate_lint-1.0.10.post1.tar.gz |
|---|---|
| Size | 20.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fd026e89884cc483f264a00d5a45e708d9a66ea200fb18af287eb4673ddf379
|
|
BLAKE2b-256 checksum How to use checksums |
841c1b10f3b6ab6abad4729839e139df74f2b6f5930381be655595f853fe4077
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_einvoice_mandate_lint-1.0.10.post1-py3-none-any.whl
| Download URL | readystack_einvoice_mandate_lint-1.0.10.post1-py3-none-any.whl |
|---|---|
| Size | 22.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b14b03191d3b23a981df37731405ed79f955aae5a1ab589bb0b521586fc64680
|
|
BLAKE2b-256 checksum How to use checksums |
9d3b03cc250b1bbb3014fc01c7daf60b8efd0329d6ecd1ca046342b887ff87a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-einvoice-mandate-lint 1.0.10.post1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.