The Finance Module Is Judged on One Thing: Can You Close the Month
Every ERP has a general ledger and every vendor will show you a dashboard. What decides whether finance works is duller than that. A chart of accounts that was designed rather than inherited. Subledgers that reconcile to their control accounts every month. Periods that lock. Currency handled in three layers instead of one. Get those right and the close lands in days. Get them wrong and no amount of software will save the numbers.
50+ ERP and software projects. Zero failed projects since 2021.
Two decisions decide whether finance works
Most finance modules can do far more than the client ever uses. The value comes from the chart of accounts and the process design around the close, not from the software brand. Both are cheap to get right in month one and painful to change in year three.
A chart built badly in month one constrains every report for a decade
Almost every chart we inherit is too deep. Somebody coded cost centre, department, project and location into the account number, so travel became fourteen accounts and the list ran past a thousand lines. That chart cannot be changed later without restating history, and it still fails the first question anyone asks, which is what a department spent across all of its categories. A shallow chart with good dimensions beats a thousand-line chart every time. Keep the account for the nature of the transaction, and push everything about who, where and why into dimensions that can be reported in any combination.
- The account answers what was bought, never who bought it.
- Cost centre, department, project and location are dimensions.
- 150 to 300 accounts is usually enough for a mid-market group.

Every subledger must reconcile to its control account, every month
AR, AP, bank, fixed assets and stock each keep their own detail, and each rolls into one control account in the general ledger. The discipline is that those two figures agree at the end of every period, not at year end when an auditor asks. The single most common ERP finance problem we are called in to fix is a stock ledger that does not agree with the GL, and it is almost always caused by postings made outside the process: a manual journal into the stock account, a receipt reversed the wrong way, a valuation method changed mid-period. Lock the control accounts against manual journals and most of it stops.
- Five subledgers, five control accounts, reconciled monthly.
- Manual journals blocked on stock, AR, AP and bank control.
- Every movement carries a document and a reason behind it.

Six areas make up the finance module
They are not separate systems. Every one of them posts into the same ledger, and each has a control account that has to tie at the end of the period.
The record to report cycle, five stages
Nothing here is optional. Skip a stage and it reappears in the close, usually on the last day.
What we set up when we configure finance
Chart and dimension design
An account list built for your reporting, with cost centre, department, project and location moved out of the code and into dimensions.
Approval and tolerance rules
Three-way match tolerances in value and percentage, approval limits by role and amount, and a documented path for the exceptions.
Bank import and matching
Statement formats mapped, auto-match rules tuned on reference, amount and date window, and a working queue for what does not match.
Multi-currency configuration
Transaction, functional and reporting currency set per entity, rate sources loaded, and revaluation posting realised and unrealised gain separately.
Tax and statutory setup
Determination logic on the document, return formats for each jurisdiction you file in, and e-invoicing where a mandate applies.
Close checklist and lock policy
A named checklist with owners and day offsets, period locking rules per role, and the reconciliation pack the close is signed off against.
What a properly designed finance module buys you
What this connects to
The ledger is downstream of almost everything. These three are where the postings come from and where the reporting goes.
Why finance teams hand us this module
Finance and accounting module questions
How deep should our chart of accounts be?
Does the ERP handle multi-currency and multi-entity properly?
How long should a month-end close take?
What happens when the stock ledger and the general ledger disagree?
Will the ERP handle our local tax rules and e-invoicing?
Can we run the ERP alongside our existing accounting software during transition?
Get Your Finance Module Designed Properly
Book a free consultation. We will look at your current chart of accounts, how your subledgers reconcile today, where your close actually loses its days, and what your entity and currency structure demands before anyone talks about a platform.
Book a Free Consultation โNo commitment. A straight read on your chart, your reconciliations and your close, whichever ERP you end up on.
What the Finance and Accounting Module Actually Does
Ledger, subledgers, currency, entities, tax and the close. This is the detail an accountant asks about in the second meeting, once the dashboard demo is over and the real question is whether the thing will tie at month end.
From a posted document to a locked period
One ledger, five subledgers, and control accounts that tie
The general ledger carries the account, the dimensions and the posting date. AR, AP, bank, fixed assets and stock each hold their own detail and roll into a single control account. Journal types are defined so a sales invoice cannot be posted as a cash receipt, and the control accounts are closed to manual journals so nothing enters the ledger without a document behind it. Reconciliation of each subledger to its control account is a monthly task with an owner, not a year-end exercise.
- Accounts for nature, dimensions for cost centre, department, project and location.
- Control accounts locked against manual journal entry.
- Subledger to GL reconciliation packs produced every period.

Match on the way in, enforce the credit limit on the way out
On payables, the supplier invoice is matched three ways against the purchase order and the goods receipt, with tolerance rules in both value and percentage so a rounding difference does not need a human. Approval limits route by amount and role, and payment runs group by due date, currency and bank. On receivables, credit limits are enforced at order entry rather than discovered at collection, which prevents far more bad debt than chasing ever does. Dunning runs on a sequence, aged debt is visible by customer, and cash allocation handles part payments, on-account receipts and deductions without a suspense account.
- Three-way match with tolerances and a documented exception path.
- Credit limit checked when the order is entered, not at collection.
- Allocation that copes with partial and on-account payments.

Three currencies, several entities, one locked period
Every transaction carries its transaction currency, the entity functional currency and the group reporting currency. At period end, open AR, AP and bank items are revalued at the closing rate, with realised gain on settlement and unrealised gain on open items posted to separate accounts so the auditor can see which is which. Intercompany documents create both sides and are matched between entities before elimination. Consolidation runs on a shared chart where you can have one, or on a maintained mapping where local statutory charts differ. Then the checklist is signed and the period is locked, so nobody posts back into a month you have already reported.
- Transaction, functional and reporting currency held on every posting.
- Realised and unrealised exchange gain kept in separate accounts.
- Intercompany matched and eliminated, then the period locked per role.

Everything the finance setup delivers
Chart and dimension model
A documented account list with the dimension set behind it, mapped to every statutory and management report you have to produce.
AP rules and payment runs
Match tolerances, approval limits by value and role, supplier payment terms, and scheduled runs grouped by due date and bank.
Credit and collections setup
Credit limits blocking at order entry, dunning sequences by days overdue, aged debt views and allocation rules for part payments.
Bank import and match rules
Statement formats mapped per bank, auto-matching on reference, amount and date window, and a working queue for exceptions.
Currency and consolidation
Rate sources, revaluation runs, intercompany matching, elimination entries and a consolidated position in the group currency.
Close checklist and handover
A dated checklist with owners, period locking rules, the reconciliation pack, and written procedures so your team runs the next close alone.

