Process
What actually happens, written down — including the workarounds nobody documented.
ERP · EPM · CRM · HCM · Integrations · Advisory
Choosing a finance system is one of the few decisions a CFO cannot quietly reverse. We start with your process, argue the recommendation against the alternatives, and keep the same people on the work through go-live.
Talk to a personThe current homepage’s systems story becomes a technical section in its own right—one drawing, one transformation, no floating widgets.
Start where it hurts
Pick the one that sounds like your last quarter. The wrong first move is how a project loses six months before anyone notices.
Have the system examined before anyone proposes replacing it.
See what a Health Check looks atFix planning and close first — the reporting problem is usually downstream.
Plan and close without rebuilding itLocalization and consolidation belong in the ledger, where the posting happens.
Run the business on one set of booksMap the processes first. The shortlist then falls out of the map.
See how the selection runsThe deck uses your numbers and processes and argues the alternatives.
Talk to the person who would run yoursOne template, localized where the law demands it and nowhere else.
Connect the islandsHow this works
In that order, and we do not skip one. A system selected before the process is understood is a guess with an invoice attached.
What actually happens, written down — including the workarounds nobody documented.
The system chosen from the mapped process and argued against alternatives.
Repeated, rule-shaped work handed to the system once the rule is stable.
Used today in design and analysis, not inside the live finance system.
Before you sign anything
Most of this industry runs the list backwards: demo first, process later, usually during the build and usually at your cost.
What the business sells, where it is heading, and what is breaking right now. Nobody opens a demo and nobody mentions a licence.
Your version of the work, next to the way it is normally run. That comparison shows which differences are real and which are habits.
Options A, B and C, with the reasoning next to each — written for a board that will ask why the other two were dropped.
You see the system once we understand how you actually work. A demo run on somebody else’s data proves nothing about your close.
And once the contract is signed
Discovery ends with your legal entity structure, chart of accounts, integration landscape and period-close workflow written down. Configuration starts after that.
Financial architecture review, entity mapping, integration audit, and KPI alignment.
Chart of accounts, consolidation structure, workflows and recognition rules documented first.
Sprint-based configuration, data migration, integrations, and testing against real scenarios.
Hypercare, managed parallel run, and a financial close signed off.
A named support consultant, module expansions, and an annual Health Check.
Work already delivered
Five are the ones Cloudmaven has written permission to describe. The rest are not named here.
From international expenses and multi-country rules handled by hand to standardised approvals and master data synchronised into SAP.
From disparate consolidation and intercompany systems to one reliable source with automated consolidation and elimination.
From manual international expenses across twenty entities to end-to-end expense management integrated with Exact ERP.
From manual expenses across six entities to automatic posting into Microsoft Dynamics 365 Business Central.
From disparate data and manual consolidation to one integrated financial platform with automated elimination.
Who stays
After the project closes, somebody still owns your account, and it is a person rather than a queue.
Managing Director
Managing Director
ERP & NetSuite Specialist
Head of Products
Install base
One bounded way to start
We examine how the system is set up, what that setup costs you, and what to fix first. You keep the report and its prioritised first-fix list.
Talk to someone first