Product: Dynamics 365 for Finance and Operations
A Purchase Order Acknowledgment (855) is an outbound Electronic Data Interchange (EDI) transaction sent to your Trading Partner confirming receipt of their Purchase Order (850) and communicating what will be fulfilled. This process can be automated utilizing the Create Acknowledgment Unattended Task to automatically generate your acknowledgments based on Sales Order confirmations — eliminating the need for manual creation per order.
Outbound - Purchase Order Acknowledgement
Configuring Acknowledgment Unattended Task
Each Trading Partner with a Purchase Order Acknowledgment (855) integration requires its own dedicated Create Acknowledgment Unattended Task. Two query options are available depending on whether you need one acknowledgment per Sales Order or one acknowledgment per confirmation, giving you flexibility to match your Trading Partner's requirements.
Configuring Unattended Tasks
Navigate: EDI module → Accounts Receivable → (Local Company Settings) → Unattended Tasks
Select: New/Edit
Task Definitions
With the Unattended Task open you can configure it to create Purchase Order Acknowledgements automatically you can fill out the Task Definition settings by utilizing the Create ACKS option within the Accounts Receivable module.
Task Name: Name of the Task (Recommended: Create 855 - [Partner Name])
Module: Account Receivable
Document: Create ACKs (Note: Order Acknowledgements is not the same thing)
Query Name: Desired Option (See Options Below)
Email Address: The desired e-mail address who will receive reports on this automated task
EDI Trading Partner ID: Select the desired EDI Partner
Enter: The EDI Trading Partner ID
Check: Enabled
Option | Description |
Task Name | A user-defined name for the unattended task. Recommended format: Create 855 - [Partner Name] to clearly identify which Trading Partner this task is configured for. |
Enabled | Activates the unattended task so it runs on its configured schedule. When unchecked, the task will not execute automatically even if a schedule is configured. |
EDI Trading Partner ID | The EDI Trading Partner this task will generate Purchase Order Acknowledgements (855) for. Each Trading Partner requires its own dedicated task. |
Create As Complete | When enabled, acknowledgements are created with a Complete status, bypassing the need to manually complete them before transmission. Mirrors the Create as Complete setting on the Order Type Cross Reference. |
Last Execution | Read-only. Displays the date and time the task was last executed. |
Next Execution | Read-only. Displays the scheduled date and time for the next automatic run of this task. |
Module | The D3FO module the task operates within. For Purchase Order Acknowledgements (855), this must be set to Accounts Receivable. |
Document | The document type the task will process. Must be set to Create ACKs. Note: Order Acknowledgements is a different option and should not be selected. |
Query Name | Determines how acknowledgements are generated per Sales Order confirmation. Two options are available: TCAutoAckSelectionView (one ACK per Sales Order using the most recent confirmation) or TCAutoACKAllConfirmView (one ACK per each Sales Order confirmation). See Query Name Options below. |
Email Address | The email address that will receive execution reports generated by the unattended task. Used to monitor successful runs and catch errors. |
Error Report Only | When enabled, the task will only send a report email when errors are encountered, rather than sending a report for every execution. |
Max Records | Limits the maximum number of Sales Order records the task will process in a single execution run. Useful for controlling batch load. |
Keep Process | When enabled, retains the batch process record after execution completes rather than automatically cleaning it up. |
Single Instance | Prevents multiple instances of the task from running simultaneously. When enabled, a new execution will not start if a previous run is still in progress. |
Batch Group | The batch server group that will process this task. Determines which batch server(s) are eligible to run the task. |
Active Period | Defines a schedule or date/time window during which the task is permitted to execute. Can be used to restrict execution to specific hours or days. |
Run By (Optional) | Optionally specifies the user account under which the task will run. If left blank, the task runs under the default system user context. |
Query Name Options
The Query Name configuration determines how your Purchase Order Acknowledgement is queried when the task begins to run. Allowing you to have an Acknowledgement per-Sales Order or per-confirmation for a Sales Order.
Query Name | Behavior |
TCAutoAckSelectionView | Creates one Purchase Order Acknowledgment (855) per Sales Order using the most recent confirmation at the time the task runs. If a Sales Order is confirmed multiple times before the task runs, only the latest confirmation is acknowledged. |
TCAutoAckAllConfirmView | Creates one Purchase Order Acknowledgment (855) for each Sales Order confirmation. If a Sales Order has multiple confirmations, each confirmation generates its own separate acknowledgment. |
Once a Purchase Order Acknowledgment (855) is created using TCAutoAckSelectionView, the "ACK Created" flag is set on the extended Sales Order table. This prevents additional acknowledgments from being generated for the same Sales Order — resulting in only one acknowledgment per Sales Order.
Per-Sales Order
With the TCAutoAckSelectionView query, the Unattended Task creates a Purchase Order Acknowledgment (855) for the most recent Sales Order confirmation only. The example below shows two confirmations for Sales Order 005085:
The task produces one Purchase Order Acknowledgment (855), using only the most recent confirmation at the time of execution:
Per-Confirmation
The TCAutoACKAllConfirmView query was introduced to support scenarios where a Sales Order has multiple confirmations and a separate Purchase Order Acknowledgment (855) is required for each one. Previously, the Unattended Task generated only a single acknowledgment regardless of how many confirmations existed for a given Sales Order.
To use this view, select TCAutoACKAllConfirmView from the Query Name dropdown in the Unattended Task for Accounts Receivable:
When TCAutoACKAllConfirmView is active, the Unattended Task generates one Purchase Order Acknowledgment (855) for each Sales Order confirmation. The example below shows two confirmations for Sales Order 005086:
This results in multiple Purchase Order Acknowledgments (855) generated — one for each confirmation:
Additional Resources
rev 08/25/2026