Business Central Consultant in Canada

GST, HST, PST and QST through tax areas and jurisdictions

The Canadian localization of Business Central handles sales tax with a structure that feels unfamiliar to people coming from VAT systems. Tax jurisdictions represent each taxing authority, tax areas combine the jurisdictions that apply at a destination, and tax groups on items and resources describe what kind of thing is being sold. Tax details then hold the rate for each jurisdiction and group. For example, goods sent from a warehouse in one province to a buyer in another should pick up a different tax area from the same item sold locally.

Design work starts with your accountant's view of where you are registered and what is taxable where. I record it as a matrix of province, customer type and product type, including exempt customers and the registration numbers you must keep on file. On the purchase side, I check how recoverable and non-recoverable tax will be separated, because provincial sales tax you cannot recover usually belongs in the cost of the item or expense, not in a receivable from the government. The partner should show where that is configured in the current version.

UAT then covers shipments between provinces, a return of a taxed sale, a sale to a tax-exempt customer and a purchase with non-recoverable tax. Tax obligations are for your accountant to confirm; my job is making sure the configuration reflects their advice.

Posting groups and dimensions after GP, Sage or Acomba

Canadian mid-market companies leaving Dynamics GP often bring account strings with segments for division, department and location. Users of Sage mid-market products have similar structures, and Sage desktop or Acomba users sometimes encode analysis in account names. Business Central works best with a lean chart and dimensions doing the analytical work, so I go through the old structure with your controller and decide what becomes an account, what becomes a dimension and what is no longer needed.

Posting groups determine where every document lands. I prepare a workbook covering general business and product posting setup, customer and vendor posting groups for domestic, US and other foreign parties, and inventory posting setup by location. A manufacturer or distributor with several warehouses will also need decisions on costing method, landed cost through item charges and how freight and duty from US suppliers are allocated.

Dimension defaults set on master records reduce manual coding, and mandatory dimension rules on selected accounts stop incomplete postings. The workbook becomes the reference the partner configures from and the document your team uses later when a new product line or location is added. My gap analysis service applies the same discipline to the rest of the business.

EFT payments, checks and reconciliation in two currencies

Most Canadian companies pay suppliers by EFT, still print some checks and hold at least one US dollar account. The product offers payment journals, a function to propose which vendor invoices to pay, check printing and electronic payment exports, and the Canadian localization has included EFT export capability. The exact file layout, originator details and test process differ by bank, so I obtain each bank's file documentation up front and have the partner name the export method and who keeps it current.

Reconciliation needs design too. I agree how statements are imported for each account, how the payment reconciliation journal should match customer receipts that cover several invoices, how card settlements and bank fees are treated, and how US dollar receipts against Canadian dollar invoices, or the reverse, are handled. Exchange rate sources and revaluation timing are agreed with finance in advance.

Payroll in Canada usually runs in a specialist service that manages federal and provincial deductions and posts summarized journals into Business Central. I define that journal interface, including allocation to departments or jobs. Construction and other sectors with contractor reporting obligations should ask the partner what the current localization supports and test it on real vendors. UAT includes a bank-accepted test file, a full month reconciled from statements and a printed check run.

US subsidiaries, intercompany and consolidation

Canadian groups often own a US sales or distribution company. In Business Central online, the localization is chosen per environment, so a US subsidiary using the US localization typically lives in a separate environment from the Canadian companies. That affects how intercompany transactions travel between them and how consolidation is run, so I ask the partner to explain their approach for your version rather than assume everything sits in one place.

I design the intercompany partner setup, the accounts and items that map across entities, how transfer pricing entries and management fees are recorded according to your advisor's guidance, and how consolidation translates the US company's results into Canadian dollars with eliminations. Where all entities are Canadian, for example an operating company and a holding company, they can usually share one environment, which simplifies the design.

Quebec adds language requirements. I list which customer documents, item descriptions and emails need French, whether users need the interface in Canadian French and whether the partner can train in French. Data location also deserves a question: ask where your environment and its backups will be hosted and check Microsoft's documentation on microsoft.com. The multi-currency ERP guide and multi-company ERP page give more background. Workshops run remotely around your head office hours.

Testing a Canadian partner's estimate, and when Business Central is too much

Canadian proposals vary most in four places: how much GP or Sage history is migrated, whether provincial tax scenarios are explicitly in scope, whether French documents and training are included, and how support hours line up with your time zones. Each SOW and estimate is compared with your requirements; I list the assumptions that move risk to you and return specific questions for each partner. The vendor proposal review page describes what I check. For data, the data migration service explains how unpaid items, starting balances and finance approval are handled.

I will also tell you if Business Central is more than you need right now:

• A single company selling in one province, without inventory, may do well on cloud accounting with a few connected apps.
• A Quebec business that needs French-first support from every consultant should confirm the partner can provide it before going further.
• A team with no internal owner for tax setup and posting groups will find the design eroding within a few months.

See Dynamics 365 in Canada for the platform view, ERP consulting in Canada for neutral advice, or the Canada hub. The ERP evaluation service scores alternatives in writing.