-
Notifications
You must be signed in to change notification settings - Fork 688
Description
Why do you need this change?
Description
In Codeunit 13919 "Import ZUGFeRD Document", the current implementation (around line 56) only accounts for standard Invoices and Credit Memos.
Our customers in the construction industry regularly receive electronic invoices that use a much broader range of document types (e.g., partial invoices, final settlements, or prepayment requests). According to the ZUGFeRD 2.4 / Factur-X 1.0.8 specification, there are over 50 valid document type codes.
Since the current implementation is hardcoded, these documents cannot be processed at all. This creates a significant gap in the standard European electronic invoicing functionality for specialized industries.
Business Value
Allowing the processing of all ZUGFeRD-compliant document types ensures that Business Central remains compliant with modern electronic invoicing standards across all industries, especially construction and public procurement, where specialized codes are mandatory.
Additional Context
Object: Codeunit 13919 "Import ZUGFeRD Document"
Version Reference: ZUGFeRD 2.4 / Factur-X 1.0.8
Current Limitation: Documents with codes other than '380', '384', '751', '877' or '381', '261' result in a failure to import, making the feature unusable for certain business sectors.
Describe the request
Proposed Change
We request that the hardcoded document type mapping be opened up for extensibility. Specifically:
Refactor the mapping logic: Instead of a fixed assignment, provide a way to map the ~50 available ZUGFeRD codes to the supported Business Central document types.
Add an Integration Event: This would allow partners to handle specific industry codes (e.g., mapping a "Partial Invoice" to a standard "Invoice") without having to rewrite the entire import routine.
Internal work item: AB#620280