Map an inbound EDI X12 810 Invoice to a Dynamics 365 Finance and Operations vendor invoice using the DMF VendorInvoiceHeaderEntity and VendorInvoiceLineEntity
Parse the 810 transaction set: BIG segment contains invoice number and date; N1/N3/N4 loops contain vendor and remit-to address; IT1 loops contain line item details (quantity, unit price, item number); TDS carries total invoice amount.
Build a DMF import package with two CSV files — one for VendorInvoiceHeaderEntity and one for VendorInvoiceLineEntity — linked by the InvoiceNumber key; set DataAreaId to the correct legal entity.
Upload and import via the DMF package API (ImportToPackage) or via the recurring integrations enqueue endpoint targeting a pre-configured inbound recurring job.
After import, verify the vendor invoice in D365 F&O under Accounts Payable > Invoices > Pending vendor invoices; check the DMF job history for row-level errors.
For three-way match (PO/Receipt/Invoice), populate the PurchaseOrderNumber and PurchaseOrderLineNumber fields in VendorInvoiceLineEntity to enable automatic matching.
Known gotchas
VendorInvoiceHeaderEntity requires the vendor account to be resolved from the N1*SE vendor identifier in the 810 — this typically requires an external mapping table between trading partner IDs and D365 F&O vendor account numbers since the 810 carries the EDI partner's internal ID.
The 810 IT1 loop item number (using qualifier VC for vendor catalog) may not match D365 F&O item numbers directly; a cross-reference table (item vendor external codes) must be maintained and applied during the mapping step before DMF import.
DMF import of pending vendor invoices does not automatically post or match them; a separate workflow or batch job in D365 F&O must be triggered to route the invoices through the approval and matching process.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp