Business Central Consultant in the USA

Posting groups and dimensions: the decisions US controllers inherit

In Business Central, almost every ledger entry is driven by posting setup rather than by the person entering the document. A sales invoice line finds its revenue account through the combination of the customer's general business posting group and the item's general product posting group. Receivables land through the customer posting group. Inventory and cost of goods sold follow the inventory posting setup by location. Get that matrix right and the general ledger looks after itself. Get it wrong and the controller spends every close reclassifying.

US companies arriving from Dynamics GP often expect to rebuild their account segments. I usually recommend the opposite: a shorter natural account list with dimensions carrying department, location, division or project. QuickBooks users face a similar choice with classes and locations, which map fairly naturally to dimensions once the duplicates are cleaned up.

I document the matrix and dimension rules in a single workbook the partner configures from, including default dimensions on customers, vendors and items and any mandatory dimension rules on specific accounts. That workbook becomes part of the scope, so a later disagreement about how something should post has a written reference rather than two memories of a workshop.

Sales tax areas, exemptions and vendor information returns

The US localization handles sales tax through tax jurisdictions, tax areas that combine them, and tax groups assigned to items and resources. Customers carry a tax area and a tax liable flag. For a business selling in one or two states with simple taxability, that structure can be maintained in house. For a distributor shipping across many states, or selling through marketplaces, maintaining rates and taxability by hand becomes a risk, and many companies connect a tax calculation app from AppSource instead. I help you decide which path fits, based on your CPA's view of where you have obligations, not on what was easiest to demo.

Exemption certificates deserve a named owner and a place to live. Whether that is a field on the customer card, a document attachment or the tax app's own certificate store, UAT should include a tax-exempt wholesale customer, a partially taxable order and a credit memo against a taxed invoice.

On the payables side, vendors who receive information returns need the right flags and box mapping before the first payment is posted, not in December. I ask the partner to show how year-end output is produced in the current version and confirm it in writing. Filing decisions stay with your tax advisor.

ACH payments, checks, positive pay and bank reconciliation

Treasury setup is where demo systems and real banks part company. Business Central can export electronic payment files and print checks, but the exact file layout your bank accepts, the company ID and batch header details, and whether a positive pay file is required for check runs all vary by bank. I collect those specifications from your bank early and ask the partner to confirm whether the standard export works or a data exchange definition or app is needed.

Reconciliation design matters just as much. Decide how statements reach the system, whether through a bank feed service, a file import or an app, and how the payment reconciliation journal should match deposits to open invoices. Lockbox receipts, card settlements net of fees and payroll clearing accounts each need a matching rule or a documented manual step.

During testing I want a real statement from each operating account, a live ACH test file accepted by the bank in its test environment where one exists, and a check run printed on actual stock. That evidence is far more useful than a sign-off checkbox. The UAT service explains how I script these cases with your AP and treasury staff.

Intercompany, consolidation and the move off GP or QuickBooks

Many US mid-market groups run an operating company, a real estate entity that owns the building and sometimes a separate entity per state or brand. In Business Central each is normally its own company. Intercompany partners, intercompany posting and the inbox and outbox flow let one company's transaction create the mirror document in another, and a consolidation company brings the trial balances together for group reporting. I design which accounts are intercompany, how management fees and shared costs are charged and how eliminations are posted. The multi-company ERP page covers the wider pattern.

Migration choices interact with this. Microsoft provides migration tooling for some Dynamics GP data, but what it brings across, and whether you want years of detailed history in the new system at all, should be decided deliberately. From QuickBooks, the work is usually cleaning items, classes and customer duplicates before anything moves. The QuickBooks migration guide and my data migration service describe how I plan open items, opening balances and reconciliation sign-off.

All of this happens remotely, in workshops scheduled for your main team's time zone, with recordings for other locations.

Reading a partner's statement of work, and when Business Central is too much

US Business Central proposals tend to follow a recognizable shape: a fixed or estimated block of hours by phase, a list of assumptions, a set of AppSource apps and a support plan. The risk usually sits in the assumptions. I look for migration limited to master data only, integrations described as out of scope, the client owning all testing, training delivered as a single session, and change request rates that apply from the first week. I return a written list of questions for each bidder, as described on the vendor proposal review page.

Sometimes the honest finding is that Business Central is more system than the business needs right now:

• A single-entity service firm with no inventory and simple billing may be better served by strong accounting software plus a CRM.
• A company that will not appoint an internal owner for posting setup and master data will see the design erode quickly.
• A business whose real problem is one broken process, such as order entry, may fix it faster without changing the ledger.

For the broader platform picture see Dynamics 365 in the US, my US ERP consultant page, or the US overview. If you are still choosing, the ERP evaluation service compares options in writing.