First 90 Days on Business Central: A Finance Team's Checklist

The go-live date is not the finish line. It is the starting pistol. Most Business Central implementations that struggle do not fail during the technical setup — they fail in the weeks that follow, when the finance team is left to figure out how the system works in practice without a clear plan for what to do first.

This is a practical checklist for the first 90 days: what to lock down in month one, what to make routine in month two, and what to review by day ninety so you know whether you are getting the full value from the platform.

Month one: get the foundations right

The first thing that will cost you later if you get it wrong is the chart of accounts. Resist the pressure to go live with the default CRONUS chart and then sort it out. Spend time in the first two weeks confirming that your account categories, posting groups, and dimensions match how your business actually reports. A dimension wrong now becomes a reporting correction later — and those corrections eat real time.

Bank import is the second priority. If your team is still manually reformatting statement files to get them into BC, fix that now rather than building a habit around a workaround. Clean statement import is the gateway to automatic reconciliation; without it, you are adding steps to every month-end.

User access should be locked to role by the end of week two. The default BC permission sets are a starting point, not a finished answer. At minimum, split posting access from approval authority, and ensure no one user can create, approve, and post a purchase invoice unaided.

Month two: make the core processes routine

Month one is about configuration. Month two is about behaviour. The aim is to get every core finance process on a documented cadence that the team follows without exception.

Bank reconciliation should happen at least weekly, not monthly. BC's matching engine is fast — a weekly rec on a clean import typically takes ten to fifteen minutes. A monthly rec on accumulated transactions is where errors compound and exceptions multiply.

The purchase invoice workflow deserves particular attention. If approvals are still happening outside BC — by email, by word, by a signed paper copy on someone's desk — then BC is not your purchase ledger; it is a secondary record-keeping system. The approval must happen inside the system for the audit trail to mean anything.

Run your first full period close in month two even if it is messy. A messy close with lessons learned is more valuable than a clean month-end where the finance manager quietly fixed it without the team knowing what went wrong. Capture the exceptions, note the manual steps, and schedule those as items to automate or eliminate before month three.

Month three: review and level up

By day ninety you should have real data in the system and a clear picture of where the team is still working around it rather than through it. A structured review at this point typically surfaces three or four specific process gaps that were invisible at go-live.

Common ones we see at this stage: approval workflows that exist in BC but are not enforced, dimensions that are applied inconsistently (or not at all), and reports that are exported to Excel and rebuilt manually because the built-in output does not match what management actually wants to see.

None of those are system limitations. They are configuration choices that can be changed. The question at day ninety is which ones are costing the most time, and which can be addressed in a single focused session.

The mistakes most teams make in the first 90 days

The most common error is treating the implementation as complete at go-live and moving the project resource away before the team has built real confidence. The system knows how to do the right thing; the team needs enough repetitions with support present to trust it.

The second is deferring user training on the assumption that people will pick it up as they go. They will — but they will also pick up shortcuts and workarounds that become habits. A two-hour walkthrough of the posting logic in week one is cheaper than untangling six months of inconsistent postings in month seven.

The third — and the one that causes the most damage — is skipping the 90-day review itself. The review is not a sign that the implementation went wrong. It is the normal checkpoint for any system that has been live for a quarter, and the easiest moment to course-correct before bad habits are embedded.

What a 90-day review looks like in practice

If your team has been live on Business Central for two or three months and you are not certain the configuration is working for you, a free BC review is the fastest way to find out. We look at the live system — postings, approval chains, period-close records, reporting setup — and give you a specific list of what to fix and in what order.

It is not a sales conversation. It is a working session. Most teams leave with two or three changes they can make immediately and a clear view of what the next quarter should focus on.