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
- Current FX pair is USDC/EUR only. Generic FX is not implemented.
- Fiscal402 does not file VAT returns or replace an accountant.
- National clearance networks (SDI, KSeF, PDP, Peppol AP) are not provided.
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.