The Business Central finance module

Financial management is the heart of Business Central. Every other module — sales, purchasing, inventory, jobs, manufacturing — eventually posts to the same general ledger, using the same dimensions and the same posting groups, which is what makes Business Central feel like one system rather than a collection of bolt-ons. It also means finance configuration decisions made in week one echo through every subledger for the life of the system, so this is the module to design carefully rather than quickly.

General ledger

The GL is structured around a customer-defined chart of accounts and an unlimited number of dimensions — flexible analytical tags such as Department, Cost Centre, Project, Region, or Salesperson that are attached to every posting. Dimensions replace the proliferation of GL sub-accounts you see in other ERPs and make slice-and-dice reporting in Power BI or the built-in account schedules straightforward.

The design advice that survives every project: keep the chart of accounts short and push the analysis into dimensions. A 300-account chart with six well-chosen dimensions out-reports a 3,000-account chart every time, and it is far easier to maintain. Two dimensions can be marked as global (stored directly on every ledger entry and filterable everywhere) — choose those two deliberately, because changing them later is disruptive. The full reasoning is in the dimensions design guide.

Posting groups are the other structural decision: customer, vendor, inventory, and general posting groups map subledger activity to GL accounts automatically. Users never pick a GL account on a sales invoice — the posting group setup does. This is why data entry stays clean, and why a wrong posting group mapping quietly mis-posts hundreds of documents until someone reconciles.

Accounts payable and receivable

Vendor and customer ledger entries are posted automatically from purchase and sales documents, and can also be entered through general journals. Standard features include payment terms, payment discounts, due-date reminders, customer statements, finance charge memos, and a built-in payment journal that produces bank files (SEPA in Europe, ACH/positive-pay variants in North America). Application — matching payments to invoices — can be automatic on import or handled manually, and unapplication is possible when someone matches wrongly. Prepayments handle deposits collected or paid before the goods or service is delivered, and revenue or expense that needs spreading across future periods instead goes through deferrals.

Banking

Bank account cards, bank reconciliation (with AI-assisted matching via Copilot), and bank file import/export are first-class objects. Many regions have bank feeds available through partner extensions, which turn reconciliation from a monthly chore into a near-daily non-event. Reconcile frequently: a bank reconciliation done weekly takes minutes; one done quarterly takes days.

Fixed assets

Asset register, depreciation books, partial disposals, insurance, and maintenance — covered out of the box, with multiple depreciation methods in parallel for tax vs accounting. Depreciation runs as a batch job and posts through a dedicated FA journal, so the GL trail is as auditable as everything else. The fixed assets deep dive covers the setup order that saves rework.

Cash flow and budgeting

Cash flow forecasts pull from sales orders, purchase orders, jobs, fixed asset disposals, and manual entries — the mechanics are in cash flow forecasting. Budgets are dimension-aware and can be imported from Excel — which in practice is how nearly everyone builds them: model in Excel, import, report actual-vs-budget through account schedules or Power BI, and budgets in Business Central covers the setup in detail.

Reporting: account schedules

Financial reports (long known as account schedules) are the built-in report writer: row definitions over accounts and dimension filters, column definitions over periods, budgets, and comparisons. They cover the standard P&L, balance sheet, and cash-flow statements without any external tool, and they export to Excel. Learn them before reaching for an ISV reporting product — for most SMBs they are enough. See account schedules and financial reports.

Intercompany and consolidations

Business Central supports posting between legal entities — intercompany general journals and purchase/sales documents that mirror into the partner company — and consolidating multiple companies into a reporting company with currency translation and eliminations. It is genuinely usable for a handful of related companies; groups with dozens of entities and complex ownership usually add a consolidation tool on top. Multi-company setup walks the options, consolidation in Business Central covers the eliminations mechanics, and the Company Hub is the day-to-day single pane finance teams use across those companies. Multi-currency groups should also read currencies and foreign exchange.

Statutory reporting

VAT statements, EC sales lists, e-invoicing formats, and country-specific localizations are delivered either by Microsoft (for the major countries) or by ISV localization partners on AppSource. This is the single biggest reason to verify country coverage before signing a contract: the finance module is global, but tax compliance is local, and the quality of the localization decides how much manual work month-end involves.

The month-end rhythm

A well-configured finance module makes month-end close boring: run Adjust Cost, reconcile bank and interim accounts, post recurring journals, run the VAT statement, review account schedules against budget. If close takes more than a few days, the cause is almost always upstream — posting groups, missing item charges, or unapplied payments — not the GL itself. The month-end close guide has the checklist.

Decision matrix — BC finance vs Dynamics 365 Finance

Signal	Stay on Business Central	Move to Dynamics 365 Finance
Legal entities	Up to ~50 similar-shape entities	Dozens with mixed statutory shapes, complex ownership
Country footprint	A handful of Microsoft-supported countries	Global rollouts, exotic jurisdictions, per-country customisations
Consolidation	A few companies, straightforward eliminations	Multi-level ownership, intercompany matrix, IFRS/US-GAAP dual books
Reporting complexity	Account schedules + Power BI cover it	Rebate management, allocations, complex intercompany allocations at scale
Team	Controller + a couple of finance users per entity	Corporate finance, treasury, tax, audit all with dedicated toolsets
Budget	SMB pricing sensitive	Enterprise licensing accepted for the scale

Two boxes in the right column typically decide it. One box on its own is rarely enough — it is usually cheaper to keep BC and add a targeted ISV than to move a whole finance team to F&O.

A worked example: setup order for a new entity

An SMB adds a UK sales subsidiary to a BC tenant that already runs three group companies. The order that avoids rework:

1. Load the UK localisation, VAT posting setup, and Making Tax Digital submission configuration before any master data.
2. Import the group chart of accounts as the entity's chart, unchanged, so consolidation stays clean.
3. Confirm the two global dimensions (Cost Centre, Region) are identical to sibling entities — do not diverge just for the new entity.
4. Populate customer, vendor, general, VAT business, and VAT product posting groups from a RapidStart package exported from the closest-shaped sibling.
5. Configure the UK bank account, its bank feed, and payment file format (Bacs), then reconcile a test month before opening AR/AP to users.
6. Open period one, post opening balances by journal, and run a full mini month-end (sale → payment → close) with the finance lead watching every GL entry.

Skipping any step here is what makes month one of a new entity feel like month one of a whole implementation.

Wrong-fit signals

• The group's real accounting engine is Excel, and BC is expected to be a pretty face over it — the posting-group discipline the module needs will fight that setup.
• Statutory reporting for a country BC does not localise, with no viable ISV — that is a hard blocker, not a workaround.
• More than one team wants to own the chart of accounts and dimensions independently — BC assumes one owner per tenant, and diverging opinions post as diverging entries.

None of these mean BC is a poor product; they mean the shape of the finance function is not what the module is designed for. Address the shape, or pick a bigger tool.