Peppol Network over B2Brouter and more
This release introduces the ability to import XML documents from the Peppol network directly into the Document Inbound module using B2Brouter. We have streamlined the connection process to make your e-invoicing workflow faster and more automated.
Key features
Peppol Network over B2Brouter
This release introduces the ability to import XML documents from the Peppol network directly into the Document Inbound module using B2Brouter. We have streamlined the connection process to make your e-invoicing workflow faster and more automated.
Key Enhancements
- New Import Configuration Type: A dedicated "B2Brouter" import type is now available. Simply create your account via B2Brouter and enter your credentials in the Document Inbound Module Setup to get started.
- Peppol Network Access: Seamlessly import documents from the global Peppol network using the new B2Brouter (Peppol) import type.
- Flexible Format Selection: While UBL is the standard import format for invoices, you can now manually select which format should be used for your imports.
- Advanced XML Validation: We’ve added validation support for XMLs arriving outside of the Peppol network. These can now be validated both manually and automatically.
- Invoice State Management: Gain better control over your workflow. You can now edit and manage invoice states directly within the Document Inbound list.
For a full setup guide and technical specifications, please visit our Documentation.
Smaller improvements
Description: Updated Smart Processing integration by changing six procedures from internal to public in the SIM_DI Templ. Field and SIM_DI Temp. Document Line tables, providing a stable API surface for accessing template and temporary document line data during custom processing.
- Table 5673215 – SIM_DI Templ. Field:
GetFilteredFields(...),GetViaFieldName(...) - Table 5673242 – SIM_DI Temp. Document Line:
GetNextLineNo(),GetCellValueViaFieldNo(...),GetCellIndex(...),HasInvalidLookUpValue(...)
Impact: Partner extensions can now use these public procedures for lookup logic, data access, and validation without relying on internal methods, improving integration stability and maintainability.
Description: The review functionality has been made publicly accessible to improve extensibility for customer-specific implementations. Additionally, a new function has been added to the process templates that enables verification whether a payment amount lies within a defined range.
Impact: Users and integrators can now more easily extend and reuse the review features in custom scenarios, enhancing flexibility and reducing development effort. The new range-check function in process templates improves validation accuracy for payment comparisons and supports more robust and configurable business rules.
Description: Improved the B2Brouter connector refresh behavior in the Document Inbound Module Setup by adding clear visual feedback on the connection status.
Impact: Users now receive immediate and clear confirmation when refreshing the B2Brouter connection, helping them validate configuration data more efficiently.
Description: Added a dedicated B2Brouter Invoice Search that enables users to retrieve invoices using configurable API filters and pagination. Selected invoices can be imported into an Inbound List or processed through the Document Distributor. The page includes duplicate detection, Document Central content matching, invoice state filtering, and actions for opening matching Document Central entries.
Impact: Users can find, review, and import B2Brouter invoices more efficiently without relying solely on automatic import processes. Duplicate and Document Central checks reduce unintended reimports, while the execution mode allows the same workflow to be used for both Inbound Lists and the Document Distributor.
Description:
Removed the New and Delete actions from the Validation Card in the Document Inbound Admin workflow.
Impact:
Users are guided through the intended validation process, reducing unnecessary actions and keeping validation management consistent within the Document Inbound workflow.
Description: The matching process in Smart Processing has been completely redesigned to support simultaneous execution of multiple matching setups. Users can now perform multi-header and multi-line matching, allowing each incoming line to be matched to a different document header and line. This enables flexible scenarios such as assigning line 1 of an incoming document to one order line and line 2 to another, improving control over how each line is processed and archived.
Impact: Users gain finer, line-level control over document matching, enabling multiple matching configurations to run in parallel for the same document. This enhances accuracy, supports complex business scenarios where lines must be distributed across different target documents, and ensures that all processes can be fully archived without limiting matching to a single header per document.
Description: Enhanced the Product Backlog Item to support configurable updates of matched document line fields. A new configuration table and list page allow administrators to define, per Template Code and Matching Setup, which line fields are automatically updated and whether they use a fixed value or a value from the incoming document line. These updates are applied automatically during document creation, but only when the matching status is FullyMatched.
Impact: Administrators can now centrally configure and review all automatic line field updates for each Matching Setup, improving control and transparency. Users benefit from more consistent and automated population of line fields on fully matched documents, reducing manual corrections and ensuring that predefined business values or captured document data are reliably transferred to the final document lines.
Description: Introduced a new standard lookup codeunit that searches exclusively in the No. field, unlike codeunit 5673300 which also searches in the Description field. This change was implemented to provide a more precise and controlled lookup behavior where description-based search is not desired.
Impact: Users and partners can now perform lookups that are not influenced by description text, resulting in more accurate and predictable search results. This enhancement reduces unintended matches, improves data entry reliability, and supports scenarios where strict No.-based identification is required.
Description: Enabled model selection when configuring analyzers, allowing users to choose from multiple AI models instead of being restricted to a single default. This change provides flexibility to use newer, more powerful models or smaller, more cost-efficient ones based on specific requirements.
Impact: Users can better balance performance, quality, and cost by selecting the most suitable model for each analyzer. However, changing models may alter analysis results and can require adjustments to existing schemas and prompts to ensure consistent and accurate outcomes.
Fixed and improved
Description: Fixed an issue where emails containing MSG attachments could repeatedly import attachments without completing processing. Emails now complete processing and are marked as read. New duplicate protection ensures that each email document is imported only once, even if the email remains unread or is manually marked as unread again.
Impact: Prevents duplicate entries and repeated imports. Previously imported emails can no longer be reimported by marking them as unread.
Description: Fixed an issue where the Document Inbound Guided Experience always displayed in English and did not respect the user’s language settings in Business Central. The Guided Experience now correctly follows the configured application language.
Impact: Users now see the Document Inbound Guided Experience in their selected Business Central language, improving usability and making the setup process clearer and more efficient for non-English speakers.
Description: Fixed an issue where template rules executing a custom codeunit within the process template did not persist updated values, causing all changes made by the codeunit to be discarded.
Impact: Custom codeunits invoked by template rules now correctly apply and retain their updates, ensuring that configured automation behaves as expected and that no changes are silently lost.
Description:
An issue has been fixed where Document Inbound could incorrectly process QR codes when Data Matrix was configured as the barcode type and Business Central was running in German.
Impact:
Barcode based document assignment now works consistently across supported Business Central languages and prevents unrelated QR codes from interfering with documents configured to use Data Matrix codes.
Description:
Updated the validation workflow for inbound B2B documents so that attempting to view validation results before running am validation is not possible anmyore.
Impact:
Users receive accurate guidance when viewing validation results, reducing confusion and support needs. The misleading JSON error no longer appears in this scenario, improving usability and transparency of the validation process.
Description:
Resolved an issue where the "Validate Document" action remained available in the Inbound List even when B2B Router XML validation was disabled. The action is now correctly hidden or disabled when XML validation is turned off to align with the configuration settings.
Impact:
Users can no longer perform B2B Router XML validation when it is disabled in the configuration, preventing unintended validations and ensuring system behavior matches administrative settings. This improves consistency, reduces configuration-related errors, and enhances control over validation processes.
Description:
Resolved an issue where XML validation was not automatically triggered for XML files received via B2Brouter, even when B2Brouter XML Validation and Automatic B2Brouter XML Validation were enabled. XML validation now runs automatically for both manually uploaded XML files and those received through B2Brouter.
Impact:
Users can rely on consistent XML validation behavior for all inbound XML documents, improving data integrity and reducing the risk of unvalidated files entering the system. No configuration changes are required; existing validation settings now apply as intended.
Description: Resolved an issue where the smart line GL Account suggestion feature failed when creating a draft, resulting in an error instead of functioning as expected. The underlying error condition was identified and corrected to restore normal operation.
Impact: Users can now reliably use the smart line GL Account suggestion feature when creating drafts without encountering errors, improving workflow continuity and reducing disruption during GL account selection.
Description: Resolved an issue where completing a Document Inbound review workflow with a final reviewer not authenticated against SharePoint caused the approval process to fail. The SharePoint authentication flow is now handled without initiating UI interactions during write transactions, allowing document approval, unposted purchase invoice creation, and archiving to complete as intended.
Impact: Users can now complete document approvals even when the final reviewer is not pre-authenticated to SharePoint, preventing transaction failures and business process interruptions. This fix removes the dependency on certificate-based archive uploads for standard approval scenarios and ensures more reliable integration between Document Inbound and Document Central.
Description: Resolved an issue where inbound lists created with the "|" separator and using email as the assignment method could not be opened from the list setup. The system incorrectly reported that the inbound list did not exist, preventing access.
Impact: Users can now reliably open inbound lists configured with the "|" separator and email assignment. This fix restores expected behavior, eliminates related error messages, and ensures consistent access to all valid inbound lists.
Description: Resolved an issue where email attachments were not accessible via the Inbound List or the contact’s data grid when using the “Package (EML + Attachments)” import option with the Document Distributor disabled. The handling of this configuration has been corrected so that attachments are now properly imported and exposed in the UI.
Impact: Users can now reliably access email attachments directly from the Inbound List and contact data grid without needing to download the original email. This fix restores expected behavior for the “Package (EML + Attachments)” import mode and aligns it functionally with configurations where the Document Distributor is enabled.
Description: Resolved an issue in smart processing where email-imported documents with errors caused the process to stop without correctly updating their status. The logic has been updated so that such emails are processed, marked as read, and their inbound document status is set to failed as intended.
Impact: Prevents repeated imports of the same erroneous documents and ensures more reliable processing of email-based inputs. Users will see improved consistency in document status handling and reduced risk of duplicate imports.
Description: Fixed an issue where documents uploaded via Silent Upload were incorrectly assigned the default document library content type instead of the content type specified in the Silent Upload configuration.
Impact: Documents uploaded through Silent Upload now consistently receive the correct configured content type, improving data consistency, reducing manual corrections, and ensuring that downstream processes relying on specific content types function as intended.
Description: Resolved an issue in the Document Inbound job queue process where some PDF attachments were incorrectly marked as “Failed” despite being successfully assigned and archived to the corresponding contact. The assignment logic and status handling within the job queue processing have been corrected to ensure consistent and accurate results.
Impact: Users will now see accurate assignment statuses for all PDF attachments processed via the job queue in the Inbound List, eliminating misleading “Failed” indicators for successfully processed documents. This improves transparency, reduces confusion during automated document processing, and ensures more reliable monitoring of inbound documents handled by the job queue.