A compliant UBL invoice is more than valid XML. To clear a Peppol Access Point it has to satisfy the UBL 2.1 schema, the European standard EN 16931, and the Peppol BIS Billing 3.0 Core Invoice Usage Specification at the same time. This wizard builds all three into every document, so you can create a sendable invoice without reading a single page of the spec.
What the wizard handles for you
Electronic addresses - Peppol routing depends on the seller and buyer Endpoint IDs (BT-34 and BT-49), each with an Electronic Address Scheme such as 0088 (GLN), 0192 (Norwegian org number) or 9930 (EU VAT). These are first-class fields here, not an afterthought, because a UBL invoice without them cannot be delivered.
Tax breakdown - enter each line with its VAT category and rate and the wizard computes the per-category breakdown and document totals, keeping BR-CO-14 (VAT total equals the sum of category amounts) satisfied automatically.
References - Peppol expects a buyer reference (BT-10) or a purchase order (BT-13). The wizard surfaces both so your invoice is routable to the recipient's accounts-payable system.
UBL, CII, and where this fits
UBL and CII are two XML syntaxes for the same EN 16931 data model. UBL is the syntax most Peppol networks expect; CII is the one embedded inside Factur-X and ZUGFeRD hybrid PDFs. If you already have data in CII, use the CII to UBL converter instead of re-keying it. Once you have generated a UBL file here, you can validate it against Peppol BIS 3.0 or preview it as a readable PDF.
Your invoice data is sent to our API only to generate the XML and is discarded immediately afterwards. We never store invoice content and never share it with third parties.