How to send Factur-X (hybrid PDF) over Peppol with phase4? (SBDH BinaryContent/TICC, correct DocType/Process IDs, sample usage) #336
tamndse62381
started this conversation in
General
Replies: 1 comment
-
Hi @tamndse62381 - very good questions. I had a Webinar on exactly that topic, and you get the recording and the slides from https://shop.peppolhub.com/ - this should help to answer your questions :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Philip/phase4 team 👋
Goal
I need to send a Factur-X invoice (PDF/A-3 with embedded CII XML) over the Peppol network using phase4 (C2 → C3). We already send UBL BIS Billing 3.0 successfully; now we must support Factur-X for France.
What I’ve read / understood so far
Peppol SBDH v2.0.1 allows non-XML payloads via the BinaryContent wrapper in the ticc/envelope/1.0 namespace (i.e., “TICC wrapper”), with the binary payload base64-encoded inside the SBD.
The Peppol Document Type Code List includes “France Factur-X” with DocType ID:
urn:peppol:doctype:pdf+xml##urn:cen.eu:en16931:2017#conformant#urn:peppol:france:billing:Factur-X:1.0::D22B
and Process IDs cenbii-procid-ubl::urn:peppol:france:billing:regulated / …:non-regulated.
Helger’s public tools/news indicate ongoing support for ZUGFeRD/Factur-X rule sets and show the Factur-X DocType in participant listings, so it seems supported in the ecosystem.
Questions
For DocumentIdentification in SBDH, which exact values should we use for:
I’ve seen an example detecting incoming Factur-X using Standard="urn:peppol:doctype:pdf+xml", Type="factur-x", TypeVersion="0". Is that still the recommended triplet for sending, or should it align more closely with the current DocType ID entry? (Happy to adjust to whatever phase4 expects.)
When wrapping the PDF, should BinaryContent@mimeType be application/pdf (raw Factur-X PDF bytes), or should we package ASiC-E and use application/vnd.etsi.asic-e+zip? The SBDH doc shows the ASiC-E example, but I want to confirm the correct mimeType for Factur-X in practice.
For France, is the correct combination to use exactly the “France Factur-X” DocType ID (above) + Process ID …:regulated or …:non-regulated depending on the receiver? Any caveats for cross-border scenarios when the receiver is outside France?
Is there a first-class helper to send a BinaryContent-wrapped SBD directly (e.g., via PeppolUserMessageBuilder), or should we build the SBDH XML (with BinaryContent) ourselves (via peppol-sbdh) and pass it as the single AS4 payload? Pointers to a current sample would be great.
Really appreciate your time.
Beta Was this translation helpful? Give feedback.
All reactions