Guide
JSON to UBL
Most billing systems already have an invoice as JSON: number, dates, seller, buyer, lines, tax and totals. UBL is a different file. Mapping it by hand means keeping schematron, code lists and national identifiers in your own codebase.
codecafe24 accepts that JSON once and returns UBL. Validation runs before the file is returned, so a missing VAT identifier or a wrong profile fails in the API response instead of at the buyer.
Choose the CIUS (Peppol BIS, EN 16931, XRechnung UBL) so the CustomizationID matches the buyer.
Invoice bytes are processed for that request and are not stored as an archive. Account data and usage metadata are separate from the invoice XML.
Related
Questions
What JSON fields are required for UBL?
invoice number, issue date, currency, seller, buyer and at least one line. National identifiers (Leitweg-ID, NIP, IPA code, Peppol endpoint) are required only for the formats that use them.