Microsoft Dynamics 365 Business Central for Construction: Our Review

We implement Business Central at AltaVistaTech, contractors included, so we sat down with Kevin Alexander, our Microsoft Dynamics 365 Solution Architect, to pressure-test it for construction. His test is one sentence: judge it on one real job. Can the proposed setup carry a messy project of yours all the way to a margin report, on your data, without finance fixing it in Excel afterward? If it can, keep it on the list. If the demo quietly swaps in clean sample data, that tells you something too.

If you run finance at a construction company, you’ve probably had this conversation already. Maybe your current system is creaking, maybe you’re a Microsoft shop and someone asked the obvious question, maybe a peer switched and won’t stop talking about it. And the demo looked great, the way demos do. Before you call a sales rep, here’s the short version: what Business Central does well, where it needs help, and who should probably look elsewhere, including the parts that get glossed over, like WIP, retainage, and what breaks after go-live.

What it’s genuinely good at

As a financial system, Business Central is excellent. General ledger, AP, AR, purchasing, jobs, and approvals in one place.

Dimensions do the reporting. You tag each transaction by job, phase, cost type, or PM, then report across the business without a bloated chart of accounts. Set up well, it kills a lot of spreadsheet work.

The Microsoft connection is underrated, and the payoff shows up late. In the demo it sounds like a sales slide. Six months in, approvals run in Teams, vendor emails sit in Outlook, and Power BI reads straight from the ledger instead of four exports. As Kevin says, “Nobody’s changing an ERP platform because Outlook works.” True. But once you are live, that connected stack is the quiet win.

One caution on Power BI: it makes good data clear. It does not fix bad data. If your cost codes are messy or change orders live outside the system, it just shows the mess faster. Fix the source first.

Where it stops being construction software

This is the part to understand before you sign. “The mistake companies make,” Kevin says, “is assuming Microsoft ERP automatically means construction ERP. And it doesn’t.”

The construction depth comes from add-on apps and a partner who has built it before. AIA billing, certified payroll, equipment costing, subcontractor compliance, lien waivers, heavy field capture, deep project management. Those usually live in construction-specific apps or connected systems, not in Business Central itself.

That is normal. You are buying a stack, not one product. The risk is not the apps. It is the seam nobody owns. When the field import fails the night before close, you do not want the ERP partner, the app vendor, and IT pointing at each other while your numbers sit wrong.

So the partner matters as much as the software. “The implementation partner often determines whether the company ends up with a scalable operational platform, or a heavily customized system nobody wants to maintain three years from now,” Kevin says. Make any partner draw the line for you: what is standard Business Central, what is configuration, what is an app, and what stays outside it.

WIP and billing: where a weak setup shows

WIP is where a job that looks fine in the field gets corrected in finance. When the setup is bad, the symptom is always the same. The controller rebuilds the WIP schedule in Excel because the system’s number cannot explain itself.

So in the demo, do not ask if it “does WIP.” Ask to see your method. Who enters cost-to-complete. How percent complete is calculated. How pending change orders stay out of revenue until they are approved.

Same for progress billing and retainage. Look at the invoice format, retainage held and released, and whether it all ties back to the job without a side spreadsheet. If retainage is tracked off to the side, ask why. Sometimes it is fine. Often the demo is dodging your hardest billing.

What to test in the demo

Bring a real job. A fixed-price one with retainage and a change order that went sideways is ideal. Clean sample data hides the things you need to see.

For each row below: bring the example, watch what happens, and make the partner say whether the answer is standard Business Central, configuration, an app, an integration, or a system you keep outside it.

Red flags in the demo

None of these kills a project on its own. But each one needs a straight answer before you sign.

• Committed cost is not visible until the invoice arrives.
• Retainage is tracked or released in a separate spreadsheet with no clear reconciliation.
• WIP is rebuilt in Excel every month because the ERP report is not trusted.
• Project managers cannot approve or fix job cost coding before invoices post.
• Pending change orders look the same as approved contract value.
• Field time arrives late, and nobody can say who fixes a failed import.
• The partner cannot say which system owns billing, payroll, equipment, documents, or compliance.
• The demo uses clean sample data and never runs your real billing and WIP example.

What breaks first after go-live

It is rarely the software. “Construction implementations succeed or fail less on software feature checklists and more on operational alignment,” Kevin says. Three things break first:

• Cost structure. If the chart of accounts, dimensions, and cost codes do not match how your team actually works, the reports exist but nobody trusts them.
• Handoffs. AP enters the invoice, the PM approves coding, the foreman logs time, finance reviews WIP. If one person is not bought in, the close slips.
• Migration. Open jobs, commitments, retainage balances, and historical cost come over dirty, and a correct system looks broken on day one.

Who should buy it, and who shouldn’t

Buy it if you want a modern financial core, your team already lives in Microsoft 365, and you will design your construction workflows instead of expecting them prebuilt. For that company it is one of the best options out there, and it gets better the longer you use the Microsoft tools.

Look elsewhere if you want construction depth out of the box. If field operations, certified payroll, equipment, compliance, and project management all need to work natively on day one, a construction-native ERP (Sage Intacct Construction, Viewpoint, Foundation) will fight you less. Force all of that into Business Central and you get the customized system nobody wants to maintain.

One last thing, especially if you are a Microsoft shop that has already decided. Liking the ecosystem is a fair reason to lean toward Business Central. It is not a reason to skip the test. As Kevin puts it, “Good ERP evaluations should reduce operational risk, not validate preconceived vendor preferences.” Run the messy job first. Then decide.