Document Dispatch
Multimail stops the BC Sessions when selecting many entries
Description: When using the Multimail functionality in the Document Dispatch system in a production environment, selecting more than 10 entries causes the BC Sessions to crash during the sending process. This issue does not occur when 10 or fewer entries are selected. Testing in a sandbox environment did not replicate the issue.
Impact: This issue prevents the successful dispatch of emails when more than 10 entries are selected, potentially causing delays and disruptions in communication processes within production environments.
Created: January 13, 2026
Priority: High
Multimail of Documents result in BC-Sided-Error
Description: When attempting to send multiple records through Document Dispatch with the output type "E-Mail," the entries are set to error, and a message is displayed indicating that the application has exceeded its IncomingBytes limit. This issue is triggered when more than 150 MB of data is uploaded within a 5-minute period per mailbox, causing throttling on the specific App ID and Mailbox combination.
Impact: Users are unable to send multiple records via email through Document Dispatch when the data exceeds the specified limit within the given time frame, resulting in incomplete dispatch entries and operational delays.
Created: January 28, 2026
Priority: High
Not all recipients are displayed in Sent Dispatch Entry when Email is sent via Job Queue
Description: When using the Document Dispatch Admin to enable Merge Recipients and create a Dispatch profile for Posted Sales Invoices with Automatic Sending and processing via Job Queue, the system fails to display CC and BCC email addresses in the Sent Dispatch Entry. This issue affects Extended Recipients, Dynamic Recipients, and Business Partner sources. Only the "To" email address is displayed, although all email addresses are correctly included when the email is sent manually via the Factbox.
Impact: Users are unable to verify that CC and BCC recipients have received the dispatched emails when processed automatically, potentially leading to communication gaps and tracking issues.
Created: March 5, 2026
Priority: Medium
Error occurs when using “Additional Email Address” in Extended Recipient Setup
Description: When sending an email from the Posted Sales Invoice, the system incorrectly validates entries with the type Additional Email Address in the Extended Recipient Setup as invalid. This results in the email dispatch failing and generating an error.
Impact: Users are unable to send emails successfully when including additional email addresses as recipients, disrupting communication processes and requiring manual intervention to resolve the error.
Created: March 5, 2026
Priority: Medium
Behavior of Email addresses in Merge Recipients
Description: When creating a Dispatch Profile as a Document Dispatch Admin and entering multiple email addresses in the Extended Recipient Setup for a customer, the system converts all email addresses to lowercase when they are merged using merge recipients.
Impact: This issue affects the formatting of email addresses, potentially causing problems with case-sensitive email systems and leading to inconsistencies in email address records.
Created: March 5, 2026
Priority: Medium
Archiving of documents via Connector is not possible
Description: When DD, DC, DI, and DD for DC are installed and invoices are configured so that attachments are uploaded to DC, the attachment upload intermittently fails or results in an error instead of completing successfully.
Impact: Users may be unable to reliably upload invoice attachments to DC, leading to incomplete invoice records and potential delays in processing or reviewing invoices.
Created: May 8, 2026
Priority: High
Send Delayed not working for B2B
Description: When using Document Dispatch with eDocuments and the FactBox “Send Delayed” option enabled in Document Dispatch Module Setup, dispatch profiles of type B2B with output type JSON using Extended Recipient Setup are sent immediately from the Posted Sales Invoice FactBox instead of being queued for delayed sending.
Impact: Users expecting delayed transmission of B2B JSON documents from Posted Sales Invoices experience immediate sending, which can disrupt intended processing workflows and timing-dependent integrations.
Created: May 13, 2026
Priority: Medium
Email address inconsistent between direct and delayed sending
Description: When using Document Dispatch with a Dispatch Profile for Extended or Dynamic Setup on Posted Sales Invoices, the email address in Sent Entries is not displayed consistently. For direct sending, the email address is converted to lowercase, while for delayed sending it is shown exactly as stored in the Customer Card.
Impact: Users may experience confusion or uncertainty when verifying sent email addresses in the Factbox, as the displayed casing differs between direct and delayed sends. This can complicate validation processes and may lead to questions about whether the correct email address was used, especially in environments where the exact formatting of email addresses is important.
Created: May 18, 2026
Priority: Medium
Codeunit Output type creates either an error or entries with draft
Description: When using Document Dispatch with a dispatch profile output type set to Codeunit, processing fails if the custom Codeunit is implemented with an incorrect TableNo. In affected environments, dispatch entries remain in status “Draft” or eventually fail with the error: Record(5487168) ist nicht kompatibel mit 'Codeunit.Run(Record(5487159))'. This occurs when the Codeunit is defined for the “SIM_EDS Record Attachment” table instead of the required “SIM_EDS Queue Entry” table.
Impact: Custom Codeunit-based dispatch processing for documents such as Posted Sales Invoices does not complete successfully, preventing automated sending via the configured dispatch profile and requiring manual intervention or correction of the Codeunit configuration.
Created: June 8, 2026
Priority: High
B2b Send Delayed not working
Description: When using Document Dispatch with B2B and the “Send Delayed” FactBox setting enabled, posted sales invoices are sent to B2B immediately on “Send” and then attempted again by the job queue. The second attempt fails with the error “Number has already been taken,” indicating a duplicate submission to B2B.
Impact: Users experience failed transmissions and error statuses for posted sales invoices in the Document Dispatch FactBox, leading to confusion about the actual transmission state and requiring manual follow-up or correction to ensure documents are sent and processed only once.
Created: June 10, 2026
Priority: Medium
Job Queue Update B2Brouter Status not updating Status
Description: When using the B2BRouter output type in Document Dispatch, the “Update B2BRouter Status” job queue does not update the status of sent entries as expected. After successfully sending invoices to B2BRouter, running the job queue does not retrieve or reflect the latest status from B2BRouter.
Impact: Users relying on the “Update B2BRouter Status” job queue cannot see the current delivery status of dispatched documents in the system, which may lead to uncertainty about invoice delivery and hinder monitoring and follow-up processes.
Created: June 10, 2026
Priority: Medium
Automatic deletion in B2BRouter not executed on Error
Description: When using a Dispatch Profile with Output Type B2B Router and the “Automatic Deletion if Error Occurs” option enabled, documents that end in error are not automatically deleted from B2BRouter. Instead, the invoices remain available in the B2B Portal despite the error status shown in the Document Dispatch Factbox.
Impact: Organizations relying on automatic cleanup of failed B2BRouter documents may see incorrect assumptions about document removal, leading to outdated or erroneous invoices remaining visible in the B2B Portal and requiring manual intervention to ensure data consistency.
Created: June 10, 2026
Priority: Medium
B2BRouter information not shown for Error Entries
Description: When using Document Dispatch with the B2B Feature activated and a Dispatch Profile configured with Output Type B2Brouter, B2BRouter Information is not displayed for error entries after updating the B2BRouter status. Initially, B2BRouter Information can be opened from an error entry, but following the use of “Update B2BRouter Status,” reopening B2BRouter Information shows no data.
Impact: Users cannot view B2BRouter Information for affected error entries after updating the B2BRouter status, which hinders troubleshooting and analysis of B2B-related dispatch errors.
Created: June 10, 2026
Priority: Medium
Incorrect handling of different Dispatch Profiles for CC/BCC Recipients
Description: When using Extended Recipient Setup with Merge Recipients enabled, CC and BCC addresses configured with different dispatch profiles are still included in the email for the Posted Sales Invoice dispatch profile. The system does not distinguish that these CC/BCC recipients belong to separate dispatch profiles and incorrectly merges them into the same email.
Impact: Emails for Posted Sales Invoices may be sent to unintended recipients configured as CC or BCC under other dispatch profiles, leading to incorrect distribution of documents and potential information exposure to recipients who should not receive that specific dispatch profile’s output.
Created: June 15, 2026
Priority: Medium
Deleted dispatch profiles remain assigned in Extended Recipient Setup
Description: When a Dispatch Profile assigned in the Extended Recipient Setup is deleted from Dispatch Profiles, the profile reference is not removed and remains assigned in the Extended Recipient Setup.
Impact: Users may see and rely on outdated or invalid Dispatch Profile assignments in Extended Recipient Setup, potentially causing confusion, misconfiguration, or unexpected behavior in document dispatch processes.
Created: June 15, 2026
Priority: Medium
E-POST entries send even when user is not licensed
Description: When an E-POST Dispatch Profile is assigned to a customer and the responsible user’s license is revoked or deactivated, invoices generated for that customer still create dispatch entries with status “Created” instead of “Not licensed.” These entries are then processed by the job queue and sent out using the unlicensed user.
Impact: E-POST dispatches may be sent from users who are no longer licensed, potentially causing compliance issues, incorrect audit trails, and unintended outbound communication.
Created: June 15, 2026
Priority: Medium
Standard CC and BCC email addresses are not applied during Email Sending
Description: When a dispatch profile is configured with standard CC and BCC email addresses in the Output Type Settings for documents such as Posted Sales Invoices, these addresses are not applied when sending the document via the dialog. The email is sent without the configured standard CC and BCC recipients.
Impact: Users relying on predefined CC and BCC recipients for dispatched documents may unintentionally omit key stakeholders from email communications, potentially affecting notification workflows and audit or compliance requirements.
Created: June 15, 2026
Priority: Medium