Skip to main content

ERP for CFOs — Financial Steering and Compliance

Finance carries the ERP project twice: once as the department with the most configuration to get right, and again as the function that has to justify the spend. Both jobs go better when the CFO is involved in the selection rather than handed the result.

Where the finance requirements actually bite

General ledger, AR, AP and fixed assets are table stakes; every system in the directory has them. The differences show up at the edges, and the edges are where the work is.

The close. Ask any vendor how long a close takes for a company your size on their system, then ask to see the reconciliation screens. A system that requires exports to Excel for a bank reconciliation or an intercompany match has told you something about the next five years of your team's month-ends.

Revenue recognition under ASC 606. If you sell subscriptions, multi-element contracts, or anything delivered over time, revenue recognition is a system capability, not a policy document. Systems differ enormously here: some handle performance obligations natively, others expect a bolt-on, and a few expect a spreadsheet and a hopeful attitude. This single question eliminates more shortlist candidates than any other in project-based businesses.

Sales tax and nexus. Post-Wayfair economic nexus means a growing company acquires filing obligations in states it has never visited. Most ERP systems delegate this to a tax engine; what varies is how cleanly, and whether nexus thresholds are monitored or merely calculated once you already know you owe.

Multi-entity and consolidation. Two entities is a configuration question. Twelve entities with intercompany transactions, shared services allocations and a foreign subsidiary is an architecture question, and it should be on the table during selection rather than after.

Controls and audit trail. Public companies need SOX-grade internal controls over financial reporting; private companies with institutional investors increasingly get asked the same questions. What you want to verify is segregation of duties in the permission model and whether the audit trail is genuinely immutable or merely a log somebody with admin rights can edit.

Reading a vendor proposal

Three lines in every ERP proposal deserve more attention than they get.

Implementation services are usually quoted against an assumed scope. Ask what happens when the scope changes — the rate, the approval process, and whether the estimate is capped. Fixed-fee proposals that exclude data migration are not fixed-fee proposals.

Annual increases. Subscription contracts frequently allow uplifts at renewal. A cap in year one is worth more than a discount in year one.

User counts. Named versus concurrent, full versus limited, and what counts as a user at all — a warehouse scanner, an approver who logs in twice a month — changes the five-year figure more than the headline per-user rate does.

Our cost guide works through the full line-item structure, and the TCO calculator lets you model your own five-year view. Worth knowing before you start: of the 302 products in our directory, ten publish enough pricing detail to budget from without a vendor conversation.

CapEx, OpEx and the honest version

Cloud deployment shifts spend from capital to operating expense, which is often presented as a straightforward win. It is a genuine change in cash-flow profile and balance-sheet treatment, and it is also permanent: subscription costs continue at full rate indefinitely, whereas a perpetual license eventually depreciates to a maintenance line. Over five years cloud usually costs more in nominal terms and less in risk and internal effort. Which of those matters more is a question about your company, not about the software — the deployment comparison sets out the trade-offs.

Related topics

Frequently asked questions

Do we need a separate consolidation tool?

Depends on how much your entities differ. Two US subsidiaries on the same chart of accounts consolidate fine inside most mid-market ERPs. Once you add foreign currency, minority interests, intercompany eliminations at volume, or a second reporting standard, dedicated consolidation software usually pays for itself. Ask the vendor to demonstrate a close with your actual entity structure, not their demo company.

How should ERP subscription costs be treated on the balance sheet?

Cloud subscriptions are generally an operating expense, while perpetual licenses and certain implementation costs may be capitalized under ASC 350-40 depending on the nature of the work. The split between capitalizable configuration and expensed process work is a judgment call your auditor will have views on. Have that conversation before the project starts, not during the audit.

What does sales-tax automation actually require?

An ERP that can hold jurisdiction-level tax determination, or a connector to a dedicated engine such as Avalara or Vertex. What matters operationally is where the nexus tracking lives: economic-nexus thresholds vary by state and change, and a system that cannot flag when you cross one turns a compliance question into a discovery-during-audit question.

Is a faster close actually worth the project?

On its own, rarely. A close that drops from fifteen days to five is worth something in decision speed and in the finance team's retention, but it is not a number you can defend to a board by itself. The defensible case usually bundles it with something measurable: working-capital release from better inventory data, fewer credit memos from order errors, or the cost of the headcount you would otherwise add.

How much of the implementation budget should finance own?

More than most CFOs expect. Financial configuration — chart of accounts, dimensions, revenue recognition rules, tax determination, approval hierarchies — is where rework is most expensive, because errors surface only at close and then have to be corrected retroactively. Underfunding this phase to save on consulting days is a well-worn path to a bad first quarter after go-live.