Table of Contents

Version Compatibility

This overview lists only features whose availability depends on the target system. Features that work consistently across all supported product versions are intentionally omitted.

Status

Status Meaning
The feature is available.
The feature is not available.
⚠️ The feature is available but requires a technical prerequisite or workaround.
not applicable The feature does not apply to this version.

AL Versions

Feature BC28 BC27–20 BC19 BC18–15 BC14 AL Notes
E-Rechnung Report Parameters
Enter E-Rechnung Note The note is stored in a BLOB and can hold up to 2 GB.
Maintain BT-49 Endpoint ID and endpoint scheme
Setup by Configuration Package
Validate imported XML file against XRechnung Business Rules
Enable Azure-based ZUGFeRD Automatic Service
E-mail editor with enhanced e-mail handling The editor is not shown for batch postings.
Send E-Rechnung e-mail during Service batch posting Available for Service Orders only, not Service Invoices or Service Credit Memos.
Control sender e-mail via Business Central Email Scenarios Before BC20, the sender is instead maintained directly in the E-Rechnung Setup.
Search resources during automatic import-line matching
Transfer imported attachments to purchase documents
Automatic e-mail import Requires a configured e-mail account with inbox retrieval.

C/AL Versions

Feature BC14 C/AL–NAV2017 NAV2016 NAV2015 NAV2013 R2–2013 NAV2009 R2 Notes
E-Rechnung Report Parameters
Enter E-Rechnung Note Input is limited to 1,024 characters.
Maintain BT-49 Endpoint ID and endpoint scheme
Setup by Configuration Package
Validate imported XML file against XRechnung Business Rules
Enable Azure-based ZUGFeRD Automatic Service
Export and import ZUGFeRD documents ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ Requires an external ZUGFeRD DLL. NAV2009: install it on the client; from NAV2013 onward: install it on the server.
ZUGFeRD with the Send xml file with embedded pdf file option
Classic and RDLC PDF output for NAV2009 not applicable not applicable not applicable not applicable ⚠️ Classic layouts require PDF24. RTC and RDLC layouts require a configured web service.