Business Central 29
Release Version 29.0.2.0
Functional Upgrade - 19994
Sending confirmation cannot be rejected when Confirm Sending is enabled
Description: Restored the ability to reject or cancel dispatch sending confirmations when using the Confirm Sending option in Dispatch Profiles. This change ensures users can explicitly decline sending documents from the confirmation cue in the Role Center, preventing unintended dispatches.
Impact: Users can now safely stop or cancel document dispatches at the confirmation stage, ensuring documents are not sent without explicit approval. This resolves the previous issue where dispatch confirmations could not be declined, improving control, compliance, and user confidence in the sending process.
Created: October 22, 2026
Release Version 29.0.1.0
Bug Fix - 20099
Failing entry blocks PREPARE job queue
Description: Updated Document Dispatch PREPARE processing to handle individual entry failures without terminating the entire batch. Failed entries are marked as Error and logged, while processing continues for remaining dispatch entries.
Impact: Prevents one failed dispatch entry from blocking valid entries. Eligible entries are now prepared and assigned the appropriate Created or Print Entry Created status in the same job queue run.
Created: October 22, 2026
Bug Fix - 20041
Document Dispatch – Table name displayed correctly in report overlay settings
Description: Fixed an issue where the Table Name field remained empty on the Document Dispatch – Report Overlay card even though a Table No. was specified. The corresponding table name is now correctly populated when opening or reopening the address overlay settings.
Impact: Administrators can now reliably see the readable table name associated with the technical table number, improving clarity and usability when configuring address overlay settings for dispatch profiles.
Created: October 22, 2026
Bug Fix - 19758
Document Dispatch – Report settings in attachment options are not copied when duplicating a dispatch profile
Description: Fixed an issue where duplicating a dispatch profile with configured attachments and report settings (Berichtseinstellungen) caused an error when using the copied profile for invoice creation or other configured actions. The duplication process now correctly includes the associated report settings without triggering errors.
Impact: Users can now safely copy dispatch profiles with attachment configurations and report settings, and use the copied profiles without encountering errors. This improves reliability and consistency when reusing existing dispatch configurations.
Created: October 15, 2026
Bug Fix - 19736
Missing Dispatch Profile Validation on Schedule Type Change
Description: Fixed an issue where a Dispatch Schedule could be saved without a selected Dispatch Profile when the Schedule Type was changed. The system now enforces validation to ensure a Dispatch Profile is required before saving.
Impact: Document Dispatch Admins are prevented from creating invalid Dispatch Schedules with empty Dispatch Profiles, improving data integrity and reducing configuration errors in dispatch planning.
Created: October 15, 2026
Bug Fix - 19588
Dispatch Schedule Entries Are Created with Immediate Error Status
Description: Resolved an issue in Document Dispatch where schedules created from e.g. the Posted Sales Invoice page resulted in dispatch entries immediately entering an Error status because recipients could not be determined, either dynamically or via extended recipients. The recipient resolution logic has been corrected so that dispatch entries are created as pending according to the configured dispatch profiles.
Impact: Users can now reliably create dispatch schedules for e.g. posted sales invoices, with dispatch entries remaining in a pending state until processed and correctly using configured recipients. This fix eliminates the previous errors and ensures that document dispatch processing functions as intended without manual intervention or troubleshooting.
Created: October 14, 2026
Bug Fix - 19955
Internal function needs to be accessed
Description: Resolved an issue where the functions AddAttachmentForDraft and SynchronizeDialogAttachments were treated as internal and could not be used by other products. These functions have been updated to be accessible and operate as intended.
Impact: Users and integrators can now reliably call AddAttachmentForDraft and SynchronizeDialogAttachments from external products, restoring expected attachment handling and improving interoperability without requiring configuration changes.
Created: October 20, 2026
Bug Fix - 19921
Dispatch Schedules Changes are not saved and Dispatch Profile changes cause an error
Description: Fixed an issue in Document Dispatch Schedules where changes to Schedule Type, Minimum Processing Interval, weekdays, and Processing Time were not saved correctly. The Schedule Description is now retained when changing the Schedule Type, and updating the Dispatch Profile no longer triggers a technical error or closes the schedule unexpectedly.
Impact: Users can reliably edit and save all schedule configuration fields without data loss or errors. Schedule updates behave as expected, confirmation messages display correctly when changing the Dispatch Profile, and the schedule remains open and assigned to the selected profile, improving stability and usability of dispatch scheduling.
Created: October 1, 2026
Bug Fix - 19549
Extended Recipient with CC Address Does Not Create Dynamic Dispatch Entry
Description: Resolved an issue in Document Dispatch where selecting an Extended Recipient other than the first entry could prevent the additional dispatch entry from the dynamic email setup from being created.
Impact: The additional dispatch entry from the dynamic setup is now created consistently, regardless of which Extended Recipient is selected.
Created: September 18, 2026
Bug Fix - 19538
“Unsent” cue cannot be opened when an unsent entry references a field that no longer exists on the source table
Description: Fixed an issue where opening the “Unsent” cue in the Document Dispatch Role Center caused the “Unsent Dispatch Entries” page to close when a business partner mapping referenced a field that no longer exists. Mappings with missing source or target fields are now skipped.
Impact: Users can access existing unsent dispatch entries despite these invalid mappings. Valid mappings continue to be evaluated. Affected mappings must be corrected before they can be used to determine recipients.
Created: September 18, 2026
Bug Fix - 19748
Document Dispatch – “Transfer to History” requires direct Modify permission on SIM_EDS Setup
Description: Resolved an issue in Business Central Document Dispatch where the “Transfer to History / Übertrag in die Historie” action required direct Modify permission on the SIM_EDS Setup table (TableData 5487157). The permission handling has been adjusted so that the action can execute using indirect Modify permissions through the appropriate application object, removing the need for direct write access to the setup table.
Impact: Regular Document Dispatch users can now perform the “Transfer to History” operation without being granted direct modification rights on the SIM_EDS Setup table. This improves security and compliance by limiting unnecessary setup table access while maintaining full functional capability for operational users.
Created: September 18, 2026
Bug Fix - 19590
Invoice attachments are duplicated on reminders when a non-due invoice is included
Description: Resolved an issue in automatic Document Dispatch via the job queue where invoice attachments for reminders containing at least one non-due invoice were added multiple times. The data mapping logic determining invoices from reminder lines was corrected so each referenced invoice is attached exactly once.
Impact: Users sending reminders through automatic dispatch now receive correct document outputs, with each invoice attachment appearing only once. This improves accuracy of reminder communications and prevents confusion caused by duplicate invoice documents.
Created: September 18, 2026
Bug Fix - 19558
Posting Preview for Warehouse Shipment fails with COMMIT error
Description: Added the PreviewMode parameter to the event subscriber used during Warehouse Shipment posting preview with Document Dispatch installed, ensuring that no invalid COMMIT operations are executed in preview mode and preventing the previous error.
Impact: Users can now run posting previews for Warehouse Shipments without encountering COMMIT-related errors, resulting in a stable and uninterrupted preview posting process.
Created: September 17, 2026
Bug Fix - 19747
B2Brouter sending fails because of CORE Data mapping
Description: Resolved a transaction handling issue that occurred when using Core Data Mapping with JSON B2Brouter eDocuments schemas. The process no longer triggers a transaction error before the CORE Data Mapping codeunit is executed.
Impact: Users can now configure and run JSON B2Brouter eDocuments with Core Data Mapping without encountering transaction errors, improving process reliability and ensuring successful document processing.
Created: September 17, 2026
Bug Fix - 19491
Copilot said: B2Brouter Dispatch Fails When Using Dynamic Setup Only
Description: Resolved an issue where documents could not be sent via B2Brouter when a dispatch profile was configured with only Dynamic Setup. The system now correctly identifies the business partner using B2Brouter configuration without requiring an email-based setup, allowing successful dispatch in this scenario.
Impact: Users can now reliably send documents through B2Brouter using dispatch profiles that rely solely on Dynamic Setup. This fix eliminates the previous error preventing dispatch, improves flexibility in configuration, and aligns B2Brouter behavior with its intended reliance on B2B network recipient information rather than email addresses.
Created: September 17, 2026
Bug Fix - 19547
B2Brouter transaction in TryFunction
Description: Resolved an issue in OnPrem Business Central where sending documents via B2Brouter in Document Dispatch failed with an error related to the use of the MODIFY function within a TryFunction in OnRun. The logic has been corrected to comply with platform constraints and allow successful document sending.
Impact: Users can now send documents through B2Brouter in OnPrem Business Central without encountering the previous error. This fix restores expected dispatch functionality and improves reliability of document processing in affected environments.
Created: September 7, 2026
Bug Fix - 19331
Document Dispatch – Add to Print List only processes one record when multiple posted documents are selected
Description: Fixed an issue in Document Dispatch where the Add to Print List action from the FactBox only added the current record to the Print List, ignoring other selected documents in supported lists such as Posted Sales Invoices. The implementation was updated to correctly process the full multi-selection set so that one Print List entry is created for each selected document.
Impact: Users can now reliably add multiple documents to the Print List in a single operation, with the action behavior matching the Business Central multi-selection and the existing tooltip description. This resolves inconsistent processing of selected records and improves efficiency and predictability when working with Print Lists across supported document lists.
Created: August 26, 2026
Bug Fix - 19348
ePOST Information Page receives no status-update on opening page or simular
Description: Resolved an issue in Document Dispatch where E-POST status information was not being retrieved via the API, even though dispatch IDs were correctly stored and entries were marked as sent. The status-checking job queue and E-POST Information page now trigger the API status retrieval as intended.
Impact: Users can now reliably track E-POST dispatch statuses. This fix restores accurate status synchronization with the E-POST API, improving transparency and monitoring of sent documents without requiring manual intervention.
Created: August 26, 2026
Bug Fix - 19398
Dispatching while posting in seperate session
Description: Resolved an issue where Document Dispatch was executed inside the active posting transaction for posted sales, purchase, or service documents, causing explicit commits to be suppressed and Codeunit.Run() evaluations to trigger transaction errors. The dispatch process has been adjusted so that, when "Create Session while Posting" is enabled, queue creation and processing run in a separate Business Central session while the posting process waits for completion; when the option is disabled, the original synchronous behavior is preserved.
Impact: Document posting now completes reliably without failures caused by Document Dispatch interfering with the posting transaction, and queue entries are created and processed as expected. Users benefit from more robust posting and dispatch behavior, reduced transaction errors, and predictable execution semantics aligned with the configured session handling option.
Created: August 26, 2026
Bug Fix - 19365
based Data Mapping fails when used as an e-mail placeholder
Description: Resolved an issue where Data Mappings of type CODEUNIT failed during Document Dispatch e-mail generation when used as e-mail placeholders, even though they executed correctly in the Test Data Mapping action. The Codeunit execution and transaction handling around Data Mapping evaluation have been adjusted so that the configured Codeunit reliably receives the required record context and returns the expected value.
Impact: Users can now safely use CODEUNIT-based Data Mappings as dynamic e-mail placeholders for subjects and body texts in Document Dispatch without e-mail creation failing. This restores the intended functionality for dynamic content generation and ensures consistent behavior between Test Data Mapping and actual e-mail dispatch, with no adverse impact on other Codeunit-based scenarios such as attachment handling.
Created: August 25, 2026
Bug Fix - 19137
Document Dispatch – Incorrect field caption "Description" in eDocuments attachment options
Description: Updated the caption of the eDocuments attachment option field in the Document Dispatch – Attachment Options page to clearly indicate that it is used to select the XML/eDocument format (schema) for generated attachments, improving clarity in dispatch profile setup.
Impact: Users can now more easily understand and correctly configure which XML/eDocument schema is applied during attachment generation, reducing confusion and the risk of misconfiguration in eDocuments setup.
Created: August 11, 2026
Bug Fix - 19266
e-Invoice is sent without attachment (XRechnung/UBL)
Description: Fixed inconsistent validation of mandatory PDF attachments in Document Dispatch when using XSD/eDocument profiles. The system now reliably checks that the required PDF is generated and embedded in the XML before sending, and correctly sets Queue Lines and Queue Entries to Error with meaningful log entries if the PDF is missing or not embedded, across all output types and processing methods.
Impact: Users now receive consistent error handling and logging when mandatory PDF attachments fail to generate or embed, preventing documents from being sent in an incomplete state. This resolves cases where Queue Entries were incorrectly processed or reset to Created during Job Queue processing despite attachment-generation errors, improving reliability and traceability of document dispatch.
Created: August 10, 2026
Bug Fix - 18836
mulit-digit placeholders based on data mappings get displayed incorrectly (not reproduceable)
Description: Fixed an issue in Document Dispatch where email placeholders in the range %11 to %21 were incorrectly parsed as combinations of lower-numbered placeholders (such as %1 or %2) plus trailing digits, instead of being resolved using their configured Data Mappings.
Impact: Placeholders %11 to %21 now resolve correctly according to their Data Mappings in all environments, ensuring accurate email content generation and consistent behavior across installations.
Created: August 10, 2026
Bug Fix - 19133
Document Dispatch – Creating a business partner fails with missing email address mapping key in version 27.1.4.0
Description: Resolved an issue in Document Dispatch 27.1.4.0 that prevented manual creation of business partners from the “Document Dispatch – Business Partners / Geschäftspartner” page due to a missing email address mapping key during initialization.
Impact: Users can now create new business partners manually without encountering the error. Email address mappings are correctly initialized, restoring consistent behavior with previous versions and ensuring stable business partner setup across all creation flows.
Created: August 10, 2026
Bug Fix - 19205
Sending Multiple Dispatch Profiles Fails During Document Layout Processing
Description: Resolved an issue where Document Dispatch reused temporary Custom Report Selection entries across multiple applicable Dispatch Profiles using PDF attachments or Document Layouts. This caused duplicate entries during ProcessDocumentLayout and interrupted the dispatch process. Each Dispatch Profile is now processed with its own isolated temporary entries to ensure correct handling of Document Layouts and PDF attachments.
Impact: Users can now send documents using multiple applicable Dispatch Profiles without dispatch failures. All selected profiles are processed and sent successfully, eliminating duplicate-record errors in SIM_EDS Queue Mgt.ProcessDocumentLayout and ensuring reliable automated and manual dispatch scenarios.
Created: August 5, 2026
Bug Fix - 19129
The Event OnAfterInsertQueueEntry throws an error if the Queue Entry is modified
Description: Resolved an issue in Document Central for Dispatch where uploading attachments failed with an error indicating the record was not up to date. The upload process was corrected to properly handle record state and allow successful attachment saving.
Impact: Users can now reliably upload and save attachments in Document Central for Dispatch without encountering the record state error, improving workflow continuity and reducing upload failures.
Created: July 30, 2026
Bug Fix - 18831
Embedded PDF in Peppol Invoice Is Not Included Reliably
Description: Resolved an issue in Document Dispatch where PDF invoices were not consistently embedded into Peppol UBL/XML files despite the embedding option being enabled. The logic handling PDF attachment during Peppol transmission has been corrected to ensure deterministic and reliable embedding across all sending methods and repeated executions.
Impact: Users can now rely on Peppol invoices to consistently include the embedded PDF when configured, improving compliance and traceability for recipients. This fix eliminates intermittent missing PDFs observed at multiple customers and ensures stable behavior without requiring configuration changes or workarounds.
Created: July 30, 2026
Bug Fix - 18940
Codeunit Dispatch Profile still sends if a attachment could not be created
Description: Fixed an issue where dispatch profiles using the codeunit output type with XSD attachments could show queue entries as Sent even when a mandatory attachment failed to be created or contained errors. The sending logic has been corrected to prevent completion when non-optional attachments are not successfully generated.
Impact: Queue entry statuses now accurately reflect attachment creation results, preventing false-positive Sent states and ensuring that failed mandatory attachments block dispatch as intended. This improves reliability of error handling and visibility into failed sends.
Created: July 21, 2026
Bug Fix - 18865
Synalis'es Problem with EPOST and Reminder using sending through posting
Description: Fixed an issue where Dispatch Profiles using output type EPOST and based on Issued Reminders were incorrectly validated against the Issued Reminder table instead of the Business Mapping table. The validation logic has been updated to use the Business Mapping table field mappings so that EPOST profiles are correctly recognized as valid.
Impact: Users can now configure and use EPOST Dispatch Profiles for Issued Reminders without validation errors. Profiles are correctly marked as valid, allowing automatic sending and job queue processing to function as intended and ensuring reliable creation and processing of dispatch entries.
Created: July 30, 2026
Bug Fix - 18761
Document Dispatch – SFTP connection fails with imported PPK private key although converted PEM key works in external SSH/SFTP test
Description: Resolved an issue in Document Dispatch where SFTP connection tests failed when using customer-provided .ppk SSH private keys. The private key import and parsing logic has been corrected so that .ppk keys are properly handled and passed to the internal SFTP authentication, ensuring consistent behavior with external SSH/SFTP tools.
Impact: Users can now successfully establish and test SFTP connections in Business Central / Document Dispatch using valid .ppk private keys, restoring critical document dispatch and invoicing workflows. This fix improves reliability of SFTP authentication and eliminates misleading host key fingerprint errors that previously appeared when the underlying issue was key parsing or authentication.
Created: July 14, 2026
Bug Fix - 18767
Document Dispatch – Dialog Send overwrites the main document's Source and Type with the values from the last attachment
Description: Fixed an issue in the Dialog Send process where the main document (e.g. Sales Invoice) incorrectly inherited the Source and Type metadata from the last generated or remaining attachment after attachments were added, removed, or replaced. The main document now consistently retains its original metadata regardless of attachment modifications.
Impact: Users can now rely on accurate metadata for main documents sent via Dialog Send, ensuring correct document classification and traceability. This aligns Dialog Send behavior with Manual Send and Automatic Send, eliminating inconsistencies and reducing the risk of reporting or integration errors caused by incorrect Source and Type values.
Created: July 14, 2026
Bug Fix - 18748
Parallel Multimail dispatch causes Cross-User Email and Attachment mismatch
Description: Resolved an issue where concurrent EDS Multimail dispatches could mix email metadata between parallel processes, causing recipient addresses and attachments from different users’ selections to be combined. The dispatch logic has been corrected to ensure strict isolation of email data per user session during simultaneous multimail operations.
Impact: Users can now perform parallel EDS Multimail dispatches without risk of documents being sent to unintended recipients. All emails are reliably generated with the correct recipients, attachments, and sender information, improving data integrity and compliance in high-volume, multi-user dispatch scenarios.
Created: July 14, 2026
Bug Fix - 18755
Enhance Multimail Preview functionality and Download/Codeunit Output Type optimization
Description: Resolved an issue where Multimail sessions were not properly isolated, causing recipients and attachments from different users to be mixed when multiple users sent emails concurrently. Additionally, adjusted the handling of codeunit dispatch profiles so they no longer require a mandatory email address.
Impact: Users can now safely use the Multimail function in parallel without cross-contamination of recipients or attachments between sessions, improving reliability and data integrity. Codeunit dispatch profiles are more flexible, as they can be configured and used without specifying a mandatory email address.
Created: July 8, 2026
Bug Fix - 18542
E-POST entries send even when user is not licensed
Description: Resolved an issue where E-POST dispatch entries were incorrectly created with status "Created" and processed for sending, even when the associated user license had been revoked or deactivated. The dispatch logic has been updated to correctly mark such entries as "Not licensed" and prevent them from being sent.
Impact: This fix ensures that E-POST dispatches are no longer sent from unlicensed users, improving compliance and preventing unauthorized or unintended email dispatches. Users can now rely on accurate status handling for dispatch profiles when licenses are revoked or deactivated.
Created: July 8, 2026
Bug Fix - 18544
Document Dispatch – Extended Recipient Setup value becomes greyed out when Recipient Type is cleared
Description: Fixed an issue in the Extended Recipient Setup on the Customer Card where clearing the Recipient Type caused the associated email Value field to appear disabled without any clear validation or explanation. The UI now consistently enforces required fields and provides clearer feedback when the Recipient Type is missing.
Impact: Users can now clearly understand and manage recipient configurations without confusion from greyed-out email values. This improves usability, ensures consistent behavior across Extended Recipient Setup lines, and reduces the risk of misinterpreting whether an email address is active, valid, or editable.
Created: July 8, 2026
Bug Fix - 18645
Make PDF/A1b available for every dispatch, not only specifically for epost
Description: Resolved an issue where PDF/A-1b conversion could only be configured and applied for E-POST dispatch types. The PDF/A-1b option is now available and correctly processed for all dispatch types in the Output Type Settings, ensuring consistent document conversion behavior.
Impact: Users can now configure and use PDF/A-1b conversion for any dispatch channel, improving compliance and consistency in document archiving and delivery. This fix removes the previous limitation tied to E-POST and ensures that documents are converted to PDF/A-1b before submission or delivery across all supported dispatch types.
Created: July 8, 2026
Bug Fix - 18713
Merge receipients creates error entries
Description: Resolved an issue where sending a document with only an extended recipient configured in the “Merge recipient” feature incorrectly generated an error entry in the system log.
Impact: Users can now send documents using extended recipients without triggering unnecessary error log entries, improving log accuracy and reducing confusion during troubleshooting.
Created: July 6, 2026
Bug Fix - 18701
General Bugfix
Description: General bug fix to resolve issues in the system.
Impact: Improved stability and reliability of the application.
Created: July 3, 2026
New Feature - 19315
Archive B2Brouter Invoices created from json
This enhancement extends the Document Central for Dispatch connector to fully support archiving B2Brouter invoices generated from JSON data. When Document Dispatch sends invoice data as JSON and B2Brouter generates the final e-invoice, that invoice is now automatically retrieved and stored in Document Central. This ensures a complete, auditable archive of all invoices—regardless of where the document itself is created—improving compliance, traceability, and operational reliability.
How it works
- 📤 JSON-based invoice creation via B2Brouter
Document Dispatch sends the invoice payload as JSON to B2Brouter, which generates and delivers the final e-invoice document to the recipient. - 🔄 Automated retrieval of the final invoice
After B2Brouter confirms successful invoice creation, the Document Central for Dispatch connector automatically calls B2Brouter to retrieve the generated invoice document (e.g., PDF or supported e-invoice format). - 🗄️ Seamless archiving in Document Central
The retrieved invoice is transferred to Document Central, where it is archived together with the relevant document metadata (such as invoice identifiers, timestamps, and dispatch information), ensuring consistent indexing and searchability. - 🧩 Connector-driven process control
The entire flow—from retrieval to archiving—is managed by the Document Central for Dispatch connector, enabling centralized configuration, reliable execution, and traceable error handling for B2Brouter invoice archiving. - 🔍 Improved visibility and compliance
Users and administrators gain a single source of truth in Document Central for invoices sent via B2Brouter, including those created externally from JSON data, supporting audit requirements and downstream processing. - ⚙️ Technical alignment with existing dispatch flows
The feature integrates with existing Document Dispatch processes without requiring changes to how invoices are generated or sent. Document Dispatch does not need to generate or store the invoice document itself; instead, it relies on B2Brouter as the source and Document Central as the archive.
With this enhancement, all invoices generated and sent through B2Brouter—whether created from JSON or not—are automatically available in Document Central, ensuring consistent archiving and streamlined document lifecycle management.
Created: September 10, 2026
New Feature - 19134
Document Dispatch – Enable dispatch profile specific job queue processing
Profile-specific scheduling for Document Dispatch
Document Dispatch now supports individual processing schedules per dispatch profile within the existing delayed-send job queue. Administrators can control when documents from each profile are eligible for automatic processing—for example, invoices every day and reminders only on Fridays—without creating additional job queue entries.
Scheduling options
Each dispatch profile can have one schedule using either of two scheduling types:
- Recurring Interval: Define a minimum interval between processing windows using date formulas such as
1D,2W, or1M. Hourly and minute-based intervals are not supported. - Weekday and Time: Select processing weekdays and a shared Earliest Processing Time. A profile can normally be processed in one eligible job queue run per selected calendar day. Entries arriving after that run wait until the next eligible day.
The job queue evaluates each profile’s schedule during automatic processing. Actual processing takes place during an eligible job queue run; the schedule does not trigger a separate run. The existing Dispatch Time setting continues to apply.
Profiles without a schedule, or with Apply Schedule turned off, remain subject to the existing processing rules without additional schedule restrictions.
Visibility and administration
The Document Dispatch Schedules list and Document Dispatch Schedule card show whether processing is currently allowed or the earliest time it may be allowed again. The card also displays the Last Processing Window, which records schedule authorization rather than successful delivery.
Administrators can use Reset Processing Window to clear the previous processing window and allow processing again when the configured timing conditions are met. Assigned schedules can also be opened directly from dispatch entries and dispatch history using Show Dispatch Schedule.
This enhancement gives organizations more control over the timing of automated document dispatch while retaining their existing job queue setup.
Created: September 9, 2026
New Feature - 11812
Outbound Peppol Dispatch Integration via b2brouter (BIS Billing 3.0)
This release introduces end-to-end support for Peppol-compliant outbound e-invoicing from Document Dispatch using b2brouter as an external Peppol Access Point (AP) and SMP provider. By leveraging b2brouter’s certified infrastructure, you can generate, validate, and transmit BIS Billing 3.0 (UBL 2.1) invoices directly from Business Central, while reducing operational overhead, ensuring regulatory compliance, and gaining full visibility into dispatch and delivery statuses.
How it works
- 📄 Peppol BIS Billing 3.0 invoice generation
- Outbound invoices are automatically generated in UBL 2.1 format, fully Peppol BIS Billing 3.0-compliant.
- Existing invoice data from Business Central is mapped to the required Peppol structures and business rules, enabling seamless electronic exchange with Peppol participants.
- ✅ Pre-dispatch validation and quality assurance
- Invoices are validated using Peppol Schematron rules and XSD schema checks before transmission.
- Invalid documents are blocked from being sent, with clear validation feedback so users can correct data issues proactively and avoid downstream rejections.
- 🔗 Secure API-based integration with b2brouter
- Document Dispatch connects to b2brouter’s API to submit validated invoices to the Peppol Delivery Network.
- All communication is handled via secure, authenticated API calls, removing the need to operate or maintain your own AP/SMP infrastructure.
- 📬 Automated outbound dispatch and delivery
- Once validated, invoices are dispatched automatically to the customer’s Peppol endpoint via b2brouter as Access Point.
- The process is fully automated from invoice creation to network delivery, supporting scalable, multi-tenant deployments.
- 📊 Status tracking, error handling, and retries
- Dispatch statuses such as sent, delivered, failed, and rejected are synchronized back into Document Dispatch for centralized monitoring.
- Detailed error information is available for failed or rejected transmissions, enabling quick troubleshooting and corrective actions.
- Built-in retry logic helps recover from transient issues, improving reliability and reducing manual intervention.
- 🚀 Operational and compliance benefits
- Eliminates the need to build and maintain proprietary Peppol AP/SMP components.
- Accelerates time-to-market by using a certified Peppol provider (b2brouter).
- Reduces regulatory and operational risk while providing a fully automated Peppol outbound invoicing flow directly from Business Central.
Created: June 30, 2026
Functional Upgrade - 19086
Export Json Output Action
Description: Added a new action in the B2Brouter eDocument Schema creation process that allows users to view the JSON files generated during schema configuration, providing direct visibility into the data being set.
Impact: Users can now easily verify and validate the JSON content created during schema setup, improving transparency, reducing configuration errors, and simplifying troubleshooting.
Created: July 30, 2026