M365Con 2027 – 無料オンラインカンファレンス · 11–22 Jan 2027 · 120 sessions m365con.net

Freight reconciliation

Concept

The process of comparing a carrier's freight invoice with the expected transport charge, rate and shipment details recorded during planning before the invoice is paid.

✦ CONCEPTFreight reconciliationM365.FM
Title graphic: Freight reconciliation (Concept)

あわせて取り上げられたテーマ

Freight reconciliationに関するエピソードでは、Dynamics 365 Transportation Management、Dynamics 365 Supply Chain Management、Purchase order、Dynamics 365 Business Centralも取り上げられています。

Description

Freight reconciliation is the process of comparing a carrier's freight invoice with the expected transport charge, rate and shipment details recorded during planning before the invoice is paid. In Dynamics 365 Supply Chain Management it is part of Transportation Management and is also called matching. The goal is to confirm that what a carrier bills agrees with what was planned and shipped, and to handle any differences in a controlled way before the amount is posted.

According to Microsoft Learn, the comparison is made between system-generated freight bills and the actual invoices received from carriers. Freight bills carry estimated freight costs. The carrier rate engine calculates the rates, and a freight bill is created when a load is confirmed. Once the carrier invoice arrives, either electronically or on paper, it is matched to the freight bill. Matching can be done line by line or automatically.

Differences between the estimated and the invoiced amounts are called variances. They are resolved with reconciliation reason codes, and these codes determine how the amounts are posted in the general ledger. After variances are handled, the invoice is submitted for approval, and only then is the journal posted. This sequence places a review step between the carrier's bill and the accounting entry, so that charges are checked against planning data before payment.

Several setup elements support the process. Freight reconciliation is enabled in the transportation parameters. Reconciliation reasons, billing groups and freight bill types are then defined, with the freight bill types specifying the matching criteria. An audit master holds minimum and maximum tolerances; when a difference falls outside those tolerances, automatic reconciliation is blocked, so large discrepancies are not matched without review.

Automatic matching follows a defined order. Invoices are sorted by amount, largest first, and applied until the freight bill is fully matched. The documentation advises matching invoices with negative amounts manually and first. It also recommends a match interval of at least 120 seconds when automatic matching is turned on. Typical decisions around the topic therefore include how wide the tolerances should be, which reason codes to offer for variances, and which invoices should be matched by hand instead of automatically.

The M365.FM episode "Dynamics 365 Transportation Management - Simply Explained" places freight reconciliation within the wider transportation flow. The episode, presented by Mirko Peters, describes how Transportation Management works from the moment goods need to move through load planning, carrier selection, warehouse execution, delivery and freight reconciliation. It describes Dynamics 365 Transportation Management as the transportation planning capability inside Dynamics 365 Supply Chain Management, connecting warehouses, vendors, customers, carriers, orders, shipments and freight costs. In that picture, freight reconciliation is the final step, where the cost side of a shipment is checked after planning, execution and delivery.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Maintained by Mirko Peters (Microsoft MVP) · Last updated: