Inbound Freight Management for Dynamics 365: What Purchase Orders Don't Capture

Inbound freight management covers carrier selection, shipment execution, in-transit visibility, and freight invoice reconciliation for goods moving from suppliers into a warehouse or production facility. Dynamics 365 handles the procurement document flow on either side of that process well. What it does not manage is the freight execution layer in between.

For manufacturers and distributors shipping LTL, FTL, and ocean freight, that gap shows up in receiving delays, inaccurate landed cost, and AP teams reconciling carrier invoices manually after goods are already on the floor.

This post covers what Dynamics 365 includes natively, where inbound freight operations require additional capability, and how a freight management integration extends the workflow across Business Central and Finance and Operations.

Key Takeaways

Dynamics 365 Finance & Operations (F&O) includes a Transportation Management module for inbound load planning, but it does not connect to live carrier rate feeds or execute real-time bookings. Business Central has no native inbound freight execution layer.

The most common gaps across D365 operations are carrier selection from the PO, in-transit visibility, pre-receipt freight cost capture, and automated carrier invoice reconciliation.

A freight management integration connects D365 to the carrier network via Business Central APIs (Business Central) or the Data Management Framework (F&O), enabling multi-carrier rate shopping, booking, tracking, and invoice auditing from inside the ERP workflow.

Landed cost accuracy improves when freight cost is written back to the PO before receipt rather than captured after the carrier invoice arrives.

Inbound carrier invoices carry the same discrepancy risk as outbound. Automated audit on both directions reduces manual reconciliation and prevents overbilling from reaching AP.

What Does Dynamics 365 Include for Inbound Freight?

Purchase orders in Dynamics 365 move through a well-defined document lifecycle: created, confirmed, received, and invoiced. In F&O, the Transportation Management module extends that with inbound load planning: teams can assign routes, consolidate shipments into loads, and plan dock appointments against confirmed POs.

Business Central includes purchase order management and receipt processing but does not have a native transportation planning layer equivalent to the F&O module.

Across all three products, the ERP manages the document flow reliably. Where Dynamics 365 reaches its natural boundary is at live carrier connectivity. For a detailed breakdown of where the native module ends and a third-party integration begins, see Dynamics 365 TMS: Built-In Module vs. Third-Party Integration. The Transportation Management module in F&O supports load and route configuration, but it does not connect to carrier rate feeds in real time or execute carrier bookings directly. Business Central has no native inbound freight execution capability at all. Both products track what the ERP knows; neither tracks what is happening with the physical shipment between carrier booking and warehouse receipt.

Where Does Inbound Freight Management Require Additional Capability?

As inbound freight volume grows and vendor networks become more complex, four gaps appear consistently across Dynamics 365 operations.

Carrier selection from the purchase order. 

When a vendor ships on a collect basis, D365 has no mechanism to rate shop carriers or book a shipment directly from the PO. Teams manually access carrier portals outside the ERP, which means freight decisions happen in disconnected tools with no record in the system of record.

In-transit visibility between confirmation and receipt. 

PO status in Dynamics 365 reflects the ERP's understanding: open, confirmed, received. It does not reflect where the physical shipment is while it is in transit. For ocean imports, that gap can span several weeks with no vessel-level tracking visible inside the ERP. Receiving teams plan against expected dates rather than actual shipment positions.

Freight cost capture before receipt. 

Dynamics 365 F&O includes a native Landed Cost module that allocates freight, duties, and other charges to purchase orders—but it depends on having actual freight cost data available at the time of receipt. The actual freight cost on an inbound shipment is typically unknown until the carrier invoice arrives, which is often after the goods have already been received and the PO closed. That makes landed cost calculations approximate until after the fact, and it makes it harder to catch cost discrepancies before they become accounting entries.

Carrier invoice reconciliation on inbound shipments. 

Inbound freight invoices carry the same discrepancy risk as outbound: accessorial charges, dimensional weight adjustments, and billing errors that differ from the original quote. Dynamics 365 AP processes vendor invoices but does not automatically compare each line against the booked shipment rate. That comparison happens manually, or it doesn't happen at all. See how automated freight auditing addresses this for D365 operations.

How Does a Freight Management Integration Extend Dynamics 365 Inbound Freight?

A Dynamics 365 freight management integration connects Dynamics 365 to the carrier network and creates a two-way data flow between the ERP and the logistics platform. The connection method depends on which D365 product is in use: Business Central connects via Business Central APIs; F&O connects via the Data Management Framework or API.

Once connected, the workflow runs like this:

The integration pulls open purchase orders from Dynamics 365. From the logistics platform, teams rate shop inbound carriers in real time, select a carrier, and book the shipment without leaving the ERP workflow. The booked freight cost writes back to the PO record before receipt, giving procurement and finance an accurate landed cost figure ahead of the goods arriving.

During transit, the platform pulls carrier tracking updates automatically and writes shipment status back into D365. For ocean imports, that includes vessel-level tracking so receiving teams can see where a container is rather than working off an estimated arrival date.

After delivery, the platform compares the carrier invoice against the booked rate. Invoices that match are approved and posted to Dynamics 365 AP automatically as vendor invoices. Invoices with discrepancies, whether an unexpected accessorial charge or a rate that doesn't match the quote, are flagged for review before payment.

The result is that Dynamics 365 stays the system of record for procurement and finance, while the logistics platform handles the carrier-level execution that the ERP wasn't built to manage.

FreightPOP is available on Microsoft AppSource and connects to all three Dynamics 365 products, supporting inbound freight across parcel, LTL, FTL, ocean, and international air modes. Operations using FreightPOP for inbound freight management report up to 30% savings on freight spend through multi-carrier rate shopping and 8 to 15% savings through invoice auditing. See how Flair Packaging achieved this running Dynamics 365.

What Should Dynamics 365 Teams Look for in an Inbound Freight Integration?

For teams evaluating options, a few capabilities distinguish a purpose-built freight integration from a more limited shipping app.

Compatibility with the specific D365 product in use. 

Business Central via Business Central APIs and F&O via the Data Management Framework are different integration architectures. A solution that connects well to one doesn't automatically extend to the other. Confirm which D365 variants are supported before evaluating further.

Coverage across all inbound freight modes. 

Parcel-only apps handle label generation and basic tracking well, but they don't address LTL, FTL, or ocean freight. For manufacturing and distribution operations where inbound freight includes full and partial truckloads and ocean imports, mode coverage matters.

Landed cost write-back before receipt. 

Dynamics 365 F&O includes a native Landed Cost module for allocating freight, duties, and other charges to purchase orders—but its accuracy depends on having the actual freight cost available at the time of receipt. Some integrations capture that cost only after the carrier invoice arrives. A tighter integration writes the booked freight cost back to the PO before goods are received, so the Landed Cost module has accurate data from the moment of receipt rather than after the fact.

Automated audit on inbound invoices. 

Freight audit is more commonly discussed in the context of outbound shipments, but the same discrepancy risk applies to inbound carrier invoices. An integration that audits both reduces the manual reconciliation burden on AP teams and ensures accurate freight cost posting regardless of direction.

Pre-built carrier network. 

Configuring individual carrier API connections from scratch adds significant implementation time and ongoing maintenance overhead. A pre-built carrier network covering the carriers the operation already uses reduces that burden considerably.

Frequently Asked Questions

Does Dynamics 365 support inbound freight management natively? 

Dynamics 365 F&O includes a Transportation Management module that handles inbound load planning and route assignment. Business Central manages purchase order receipt but does not include inbound freight execution. Neither product connects to live carrier rate feeds or executes real-time carrier bookings without a freight management integration.

What is the difference between the D365 F&O Transportation Management module and a freight management integration? 

The Transportation Management module in D365 F&O handles load planning, route configuration, and dock scheduling. It does not connect to live carrier rate feeds, execute bookings in real time, or audit carrier invoices against booked rates. A freight management integration adds those capabilities on top of the ERP's native load planning functionality.

Can a freight integration pull purchase order data from both Business Central and F&O? 

Yes, though the integration architecture differs. Business Central connects via Business Central APIs. F&O connects via the Data Management Framework or direct API. A freight integration that supports all three products handles those connection methods separately.

How does real-time inbound freight visibility work with Dynamics 365? 

A freight management integration sources tracking data directly from carriers and writes shipment status updates back into Dynamics 365. For ocean imports, that includes vessel-level tracking. Without a connected logistics platform, status updates require manual lookups across individual carrier portals.

What is landed cost and how does a freight integration improve it in Dynamics 365?

Dynamics 365 F&O includes a native Landed Cost module that tracks and allocates freight, duties, and other non-product charges against purchase orders. That module works best when actual freight cost data is available at the time of receipt. Without a freight integration, that figure typically isn't captured until the carrier invoice arrives after the PO has already closed. A freight integration writes the booked freight cost back to the PO before receipt, so the Landed Cost module—and finance—has accurate data from the moment goods arrive rather than after the fact.

Can carrier invoices for inbound shipments be audited inside Dynamics 365? 

Not natively. Dynamics 365 AP processes vendor invoices but does not automatically compare carrier invoice line items against the original shipment quote. A freight management integration automates that comparison, flags discrepancies before payment, and posts only audited freight costs back to D365 AP.

Does FreightPOP support inbound freight management for Dynamics 365? 

Yes. FreightPOP connects to Business Central via Business Central APIs and to F&O via the Data Management Framework. The integration supports inbound freight from purchase orders across parcel, LTL, FTL, ocean, and international air modes, including freight cost write-back to the PO and automated carrier invoice auditing..

How long does it take to implement an inbound freight integration with Dynamics 365? 

Implementation timelines typically range from 3 to 6 months depending on the D365 product, the freight modes in use, and the number of carrier connections required. Straightforward Business Central implementations via Business Central APIs tend to move faster than more complex multi-mode F&O environments.

Purchase orders give Dynamics 365 operations a clear record of what was ordered. A freight management integration gives them a clear record of what it cost to receive it, where it was at every point in transit, and whether the carrier charged correctly. Those two records, connected and reconciled inside the same ERP workflow, close the gap between procurement data and freight reality.