Category: E-Invoice Mappings

In the export mappings we have changed the output of BT-81 to use the attribute instead of the attribute format of the attribute. We also now use the information from the structure, if available,...

We have changed the behaviour of the Buyer ID (BT-46) in exports. You can now select none or multiple values, including a custom field from the Bill-to Customer. If you have custom mappings or...

There are a few changes to the export mappings that shouldn’t change the default export. Any breaking changes are only relevant if you’re using custom mappings. New Features Breaking Changes

Fix for multiple line comments, which where not correctly concated into one cbc:Note element.

When using receipts the quantity of Resources and GL/Account lines is now automatically set to direct and the full quantity.

We’ve updated the mapping to allow the import of full comments from XML structures into purchase invoices. The system will automatically insert line breaks based on the length of the purchase line description field....

We have updated the default behavior of the XRechnung export to improve consistency and flexibility. Previously, the system used the internal Dynamics unit of measure code. Now, it first attempts to use a field...

Mapping updates are available that modify how discounts are processed in outgoing XRechnung files. Please test these changes in a sandbox environment before deploying to production. The mapping updates require module version 5.4.14.0 or...

We’ve updated the sales invoice creation mapping: For manual lines (without receipts), comment lines are allowed, even if they don’t fully conform to standards. Previously, the check ensured no price was transferred. Now, it...

We’ve introduced an option to search by Registration No., which can be activated in the Features settings. This allows you to enable multiple search methods simultaneously, providing greater flexibility in vendor identification. Updated Behavior...