Dynamics 365 Business Central Freight Invoice Validation — What the System Misses
D365 Business Central matches freight invoices against POs but not carrier rate schedules. Here is what Power Automate can and cannot fix.
The Problem
Microsoft Dynamics 365 Business Central (D365 BC) provides a robust AP workflow with purchase invoice matching, approval workflows via Power Automate, and vendor ledger management. For physical goods with POs and item receipts, D365 BC’s matching works well.
For freight invoices, D365 BC has the same structural gap as other mid-market ERPs: the matching engine validates against POs and receipts, not against carrier contract rate schedules. And freight invoices — with their base charges, fuel surcharges, accessorial line items, and variable rates by lane and service level — require contract-term validation to catch overbilling.
What D365 BC Misses on Freight
No service receipt for freight. D365 BC’s warehouse management module tracks goods receipts. Freight delivery is a service, not a goods receipt — the system does not have a native mechanism to record “carrier delivered shipment X on date Y at location Z and the service was performed correctly.”
No rate-by-lane validation. D365 BC’s purchase invoice matching checks against PO amounts. Carrier contracts define rates by origin-destination lane, service level, weight break, and equipment type. This multi-dimensional rate lookup does not exist in standard D365 BC.
No fuel surcharge verification. Same limitation as other ERPs. Fuel surcharges require a table lookup (DOE index → percentage tier → applied to base rate) that D365 BC does not perform natively.
No accessorial schedule validation. Accessorial charges on freight invoices are entered as purchase invoice lines. D365 BC processes them as amounts to be coded to the GL — it does not validate them against a contracted accessorial schedule.
The D365 BC Advantage (and Its Limits)
D365 BC has one advantage over QBE and some NetSuite configurations: Power Automate can be used to build custom validation flows. A sufficiently skilled D365 BC partner can build a Power Automate flow that looks up carrier rates from a custom table, compares invoice line items, and flags discrepancies.
The limitation is that building and maintaining this is a custom development project. The carrier rate tables need to be structured and kept current. Every contract change requires a table update. And the Power Automate flow needs to handle the complexity of fuel surcharge tiers, accessorial conditions, and lane-specific exceptions.
Most D365 BC customers who attempt this build the basic rate-lookup for their largest carrier and stop there — leaving the remaining carriers and all accessorial validation unaddressed.
How to Fix It
Quick fix (this week): Export purchase invoices for freight vendors from D365 BC (last 6 months). Compare the top 20 invoices against your carrier contracts. Focus on accessorial charges — they are the most common source of overbilling and the easiest to spot manually.
Systematic fix (4 weeks): Run a ValueXPA diagnostic. The diagnostic team structures your carrier contracts and analyzes 12–24 months of freight AP data from D365 BC. Output: vendor-by-vendor findings with dollar estimates.
Ongoing fix (continuous): Deploy FynFlo. Data-export model, no Power Automate development required.
What This Costs
For a D365 BC company spending $2M–$8M annually on freight, the validation gaps typically produce $20,000–$80,000 in annual overpayments. D365 BC companies tend to have slightly better control than QBE companies (because Power Automate enables some custom validation) but worse than companies that have invested in SuiteScript development on NetSuite.
Signs You Have This Problem
You likely have freight validation gaps in D365 BC if:
-
Purchase invoices for freight are matched against PO amounts but not carrier rate schedules
-
Your Power Automate flows do not include carrier-rate lookup logic
-
Accessorial charges on freight invoices are coded to a single GL account without line-item verification
-
Your carrier contracts are stored in SharePoint but not structured for automated comparison
-
You have not built a service receipt equivalent for freight deliveries in D365 BC
If three or more apply, a diagnostic will quantify the exposure.
FynFlo is a proprietary AI-native invoice validation product of ValueXPA.
Related Reading
Questions & Answers
Can our D365 BC partner build this validation?
Yes, but expect 60–120 hours of partner development time plus ongoing maintenance. For a single carrier with a simple rate structure, this may be cost-effective. For multiple carriers with complex accessorial schedules, an external validation tool is typically more practical.
Does FynFlo integrate with D365 BC via API?
FynFlo currently works from data exports (CSV/Excel). A D365 BC API integration is on the product roadmap. For most mid-market customers, the data-export model provides the same validation coverage without the integration complexity.