Deterministic lookup over a version-pinned mandate table: given supplier/buyer country, transaction type, and transaction date, routes to the applicable e-invoicing regime, format, phase status, and transmission channel. France's B2B receive obligation is live from 2026-09-01 via the PDP channel; Germany's XRechnung B2G/B2B receive obligation is already live; Belgium's Peppol BIS 3.0 mandate has been live since 2026-01-01; Poland's KSeF FA(3) mandatory-use phase-in starts 2026-02-01; UAE PINT-AE and Malaysia MyInvois dates are DRAFT-PIN pending re-confirmation. Zero network.
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Scope
Third node of the einvoice-validation-pipeline chain (art-293→294→295→296). A deterministic lookup, not a live regulatory feed; refresh the mandate table at each rebuild. See einvoice-validation-pipeline chain.
Presets
Transaction Facts
Result
Execution Hash & §4 Artifact
SHA-256 execution hash (JCS canonical, RFC 8785):
Ask your agent
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.
Run the AINumbers MCP tool `route_einvoice_jurisdiction_mandate`. Task: Route a transaction to its applicable e-invoicing mandate regime, format, phase status, and transmission channel via a version-pinned mandate table keyed on supplier/buyer country, transaction type, and transaction date.
Call it with arguments: {"policy_parameters":{"supplier_country":"DE","buyer_country":"FR","transaction_type":"B2B","transaction_date":"2026-09-15"}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string, or re-run the in-page WebMCP tool `route_einvoice_jurisdiction_mandate`.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-295-einvoice-jurisdiction-mandate-router.html#p=v1.H4sIAAAAAAAA_wFnAJj_eyJzdXBwbGllcl9jb3VudHJ5IjoiREUiLCJidXllcl9jb3VudHJ5IjoiRlIiLCJ0cmFuc2FjdGlvbl90eXBlIjoiQjJCIiwidHJhbnNhY3Rpb25fZGF0ZSI6IjIwMjYtMDktMTUifbvB50BnAAAA