eInvoicing support
| Feature | Public preview | General availability online |
|---|---|---|
| eInvoicing support |  Jun 2026 | Jun 2026 |
Business value
As eInvoicing mandates expand across more countries and localizations, the same purchase can arrive in Business Central twice — once as an expense submitted by an employee, and then again as an eDocument received via Continia Document Capture. Without coordination between the two, bookkeepers can risk posting the purchase twice.
This feature connects Expense Management and Continia Document Capture so an expense and its matching eDocument are handled together. This means companies can enforce expenses to be linked to an eDocument before posting, that expense dimensions are carried through to the eDocument's G/L entries, and that duplicates across the two modules.
Feature details
The support for eInvoicing includes support for the following features:
Linking expenses to eDocuments
The existing Applied Purch. Doc. No. field on the expense identifies the linked Document Capture document. When this field is filled, only the payment or reimbursement side of the expense is posted. The purchase side is handled by the linked eDocument. A new Expense Entry No. field on the Document Capture side links back to the related expense, making the relationship navigable from either module.
Enforcing pairing
New eDocument Expected and Expense Expected flags make it possible to require that an expense and an eDocument are linked before posting. You can configure the flags at three levels:
- On the Payment Type — to apply the requirement to every expense using that payment method.
- On the CDC template — to apply the requirement to every document processed through that template.
- On the individual Document Capture document — for case-by-case enforcement.
This allows administrators to enforce eInvoice pairing globally for a payment method or template, while still permitting exceptions where required.
Duplicate detection
When you configure an eDocument identifier, the system scans Document Capture documents for matches based on document date, amount, and currency. If a likely match is found, configurable messages notify the bookkeeper that a possible match exists or that an expected eDocument has not yet been linked. The bookkeeper retains responsibility for merging the documents. Furthermore, unmatched eDocuments are never automatically blocked, as not all incoming invoices originate from expenses.
Dimension alignment
There is a new Correct eDocument Dimensions setting in Expense Management Setup. Using the Dimension Correction module, you can control whether dimensions from the expense are transferred to the linked Document Capture G/L entries after posting. Correction history is tracked through the Last Dim. Correction Entry No. field on the document, which you can review using the History of Dimension Corrections action on the document card.
Posting behavior
When an expense has an Applied Purch. Doc. No., the purchase side is not posted from the expense, only the payment or reimbursement (bank transaction or user reimbursement) is. The purchase posting remains the responsibility of the linked eDocument, ensuring that a single accounting event is recorded across the two modules.