Skip to content

Use case

Accounting for agent commerce

Give ERP and accounting systems a UBL 2.1 artifact bound to a signed fiscal receipt.

Problem

Agent purchases still have to enter books. A blockchain transfer is not an invoice. Accounting systems expect structured fiscal documents.

Input

A processed Fiscal402 event: UBL 2.1 XML hashed as exact UTF-8 bytes, plus the fiscal402.receipt that binds that hash.

Fiscal402 processing

Fiscal402 generates UBL 2.1 (EN 16931 flavour) in EUR using USDC→EUR historical FX at settlement time, then stores SHA-256 of the exact generated bytes on the receipt.

Output

Fetchable UBL at GET /settlements/:id/ubl and a receipt whose artifacts.ubl_sha256 must match those exact bytes. No XML C14N.

Limitations

Integration path

Retrieve UBL and receipt over HTTP after ingest. Bind the two with SHA-256 of the exact UTF-8 invoice bytes. See /docs/ubl and /protocol/artifact-binding.

Last updated 11 September 2026