Rubrol Factur-X Compliance Pipeline Setup (Delivery)

Rubrol Factur-X Compliance Pipeline Setup (Delivery)

1. 01

   Deploy the Rubrol Enterprise sidecar container in the client's staging environment

   Use Docker, Kubernetes, or an AWS Fargate sidecar. Confirm the container exposes the local compilation endpoint and that the Rubrol Enterprise license key is mounted as a secret. This tier is required for Factur-X and PDF/A-3b output; Rubrol Pro only compiles PDF/A-2b.

2. 02

   Validate the base compilation path with a sample Typst template and JSON payload

   Send a test invoice payload through the sidecar and confirm the response returns a PDF in under 6ms. Check the output header for ISO 19005-3 conformance before adding compliance layers.

3. 03

   Map the client's invoice schema to a Rubrol Typst template

   Translate the client's billing fields (line items, VAT breakdown, seller and buyer identifiers) into the template's data contract. Keep the template in the Rubrol interactive studio during editing so layout changes render against live sample data.

4. 04

   Enable Factur-X / ZUGFeRD 2.2 packaging on the Enterprise compilation profile

   Switch the output profile from PDF/A-2b to the certified PDF/A-3b + Factur-X mode. This embeds the XML invoice payload inside the PDF container as required by EU e-invoicing mandates.

5. 05

   Run the built-in Schematron semantic validator against XRechnung 3.0 rules

   Execute the validator on the generated Factur-X file and resolve every flagged rule violation before the document leaves staging. A passing Schematron run is the gate for production cutover.

6. 06

   Apply the German DIN 5008 or French Chorus Pro template variant if the client bills in those markets

   Rubrol Enterprise ships both template sets. Select the variant matching the client's buyer jurisdictions and re-run the Schematron validator, since layout changes can alter field placement that the validator checks.

7. 07

   Wire the production billing system to the Rubrol endpoint and log the first live batch

   Connect the client's billing platform via webhook or REST call, then compile a real batch of invoices. Compare compute and memory figures against the client's previous Puppeteer or Headless Chrome pipeline to document the 96% compute and 57x memory reduction.

8. 08

   Hand off the runbook and archive the validated template set in the client's repository

   Deliver the deployment runbook covering sidecar restart, license renewal, and validator invocation. Store the final Typst templates and Schematron pass reports where the client's delivery team can retrieve them for future invoice cycles.