Product: Dynamics 365 for Finance and Operations
Article Link: http://help.truecommerce.com/en/articles/11157562-dynamics-365-for-finance-and-operations-truecommerce-extension-overview
The Dynamics 365 for Finance and Operations Integration from TrueCommerce is a file-based Cloud hosted solution. Which transfers files between Transaction Manager and Finance and Operations through a TrueCommerce hosted Cloud FTP
The TrueCommerce Extension for Dynamics 365 for Finance and Operations is a custom-built module that gets added into your Finance and Operations system providing EDI Support with Transaction Manager through processing of those files within the Finance and Operations system.
Import & Export Mailboxes
To help organize all your EDI Transactions the TrueCommerce Extension comes with EDI Mailboxes built in similar to that of Transaction Manager allowing you to view everything within Finance and Operations without needing to log into Transaction Manager to view the data sent from your Trading Partner.
These Mailboxes appear both within the Import and the Export portions of your Accounts Receivable or Accounts Payable categories found within the EDI Module - providing you with the Documents created either for or from an EDI Transaction to be communicated with your Trading Partner
Accounts Receivable
Mailbox | Documents |
Inbound Sales Order Mailbox | Purchase Orders (850) |
Inbound Order Change Mailbox | Purchase Order Changes (860) |
Inbound Remittance Advice Mailbox | Remittance Advices (820) |
Unknown Trading Partners | Unknown EDI Documents Received |
Outbound Invoice Mailbox | Invoices (810) |
Outbound ASN Mailbox | Advance Ship Notices (856) |
Accounts Payable
Mailbox | Documents |
Outbound PO Mailbox | Purchase Orders (850) |
Outbound POC Mailbox | Purchase Order Changes (860) |
Inbound Invoice Mailbox | Invoices/Bills (810) |
Inbound ASN Mailbox | Advance Ship Notices (856) |
Inbound Acknowledgement Mailbox | Purchase Order Acknowledgements (855) |
Inbound Catalog Mailbox | Item Catalogs (832) |
Unknown Trading Partners | Unknown EDI Transactions Received |
Cross References
Built into the TrueCommerce Extension are a series of Cross References that provide you with varying levels of configuration to help you setup your system with various customizations and settings that can be applied at either the System, Company or Trading Partner levels.
The various Cross Reference configurations act upon a hierarchy system in which differing settings the one set at a higher level will take precedence.
Hierarchy | Notes |
System | Utilized as the default - overwritten by Company and Customer/Vendor settings |
Company | If using a multi-company setup you can manage defaults across multiple companies. Override System settings |
Customer/Vendor | Used as a per-Partner level and will override System/Company for specific Trading Partner |
System Cross Reference
The System Level Cross References are the bottom-level references that apply to all Inbound and Outbound documents processed in the system unless otherwise overwritten by either the Company or Trading Partner level.
Not all Cross-References can be found at the System Level - for example Ship To Locations are only applied at the Customer Level
Company Cross Reference
Useful for configuring a multi-company setup within the TrueCommerce EDI Extension allowing each company to have their own unique settings that take precedence over that of the System Settings while still being globally applied to all Trading Partners that fall under that company.
Customer Cross Reference
Customer Cross References are your per-Partner settings for Account Receivable customers within Finance and Operations that would be used with a Sales Order Process (SOP) style configuration.
A Customer Cross Reference would be for a Trading Partner which purchases goods from you by sending you a Purchase Order (850) and receives an Invoice (810) in return
Vendor Cross Reference
Vendor Cross References are your per-Partner setting for Accounts Payable vendors within Finance and Operations that would be used with a Purchase Order Process (POP) style configuration.
A Vendor Cross Reference would be for a Trading Partner that you buy goods from and would be sent a Purchase Order (850) from you returning an Invoice (810) back to you in return
Trading Partner Cross Reference
Trading Partner Cross References are your per-Warehouse or Third Party Logistics (3PL) type of Trading Partners marked as a warehouse Location that handles your Logistics and Shipping needs on your behalf through the use of a Warehouse Process (WHS) style configuration.
A Trading Partner Cross Reference would be for a Warehouse Location that handles shipments for you and would be sent a Warehouse Shipping Order (940) and return a Warehouse Shipping Advice (945) informing you of the shipment details in return
Item Cross Reference
In addition to your settings on processes - the TrueCommerce Extension also includes an Inventory Item Cross Reference allowing you to extend the standard Finance and Operations inventory details with that of information specific to EDI communications such as providing additional Item Codes such as GTIN, UPC, and SCC-14, Custom pricing, and Packaging Information for Pallets/Cartons and Weight details.
EDI Maps
Built into the TrueCommerce Extension are a series of Pre and Post EDI Maps that act as a way of feeding EDI Fields into the appropriate Dynamics 365 for Finance and Operations fields providing both a standardized and a customizable way to configure how your Trading Partner's data is properly pushed and pulled to and from Finance and Operations.
While you will be given a set of default maps pre-configured to work with the standard Finance and Operations fields setup you have the full power to change and update them based off of specific business process requirements or custom fields that you've incorporated into your solution.
EDI Workflows
In addition to the EDI Maps which determine how your data is pushed/pulled the TrueCommerce Extension also comes with EDI Workflows which allow for automated triggering of various processes as apart of the EDI Process such as performing pre-validation checks or sending an email notification of a new order.
Pre-Mapping Workflows
Workflows that trigger prior to the EDI Mapping occurring - allowing for modifications or translations of the data if needed, or performing some sort of validation check to ensure compliance with your systems needs before being accepted into the system.
Post-Mapping Workflows
Workflows that trigger after the EDI Mapping has completed and written to Finance and Operations - allowing processes to run after the data is fully written to the system such as notifying a particular user of new orders arriving.
rev 4/28/2025