Process
What actually happens, written down — including the workarounds nobody documented.
ERP · EPM · CRM · HCM · Integrations · Advisory
The decision has your name on it. So does ours.
Choosing a finance system is one of the few decisions a CFO cannot quietly reverse. So the work starts with your process rather than a product demo, and the recommendation arrives argued against the alternatives. Then the people who drew that map stay on the project.
Talk to a personEvidence, after the argument
A certified Oracle NetSuite Solution Provider and implementation partner, specialising in complex, multi-entity deployments for international companies. Customers include Sherpany, DOCO and Bitpanda.
90+NetSuite projects behind the advice
~100people across ERP and EPM
2006supporting finance teams since
<100days to go-live on a single-entity build
Start where it hurts
Six situations. A different first move in each.
Pick the one that sounds like your last quarter. The wrong first move is how a project loses six months before anyone notices.
01The workarounds have workarounds.
Have the system examined before anyone proposes replacing it.
See what a Health Check looks at02Investors want answers the system cannot produce.
Fix planning and close first — the reporting problem is usually downstream of them.
Plan and close without rebuilding it03Every new country adds another workaround.
Localization and consolidation belong in the ledger, where the posting happens.
Run the business on one set of books04Spreadsheets and local systems no longer keep up.
Map the processes first. The shortlist then falls out of the map on its own.
See how the selection runs05The CFO needs a case the board can interrogate.
The deck is built in your numbers and your processes, and it argues the alternatives rather than asserting one.
Talk to the person who would run yours06I don’t have a company. I have isolated islands.
One template, localized where the law demands it and nowhere else.
Connect the islandsHow this works
Process, tool, automation, AI.
In that order, and we do not skip one. The damage happens when a stage gets skipped — automating a process nobody has mapped, or putting AI on top of numbers still corrected by hand.
Tool
The system chosen from the mapped process, argued against the rejected alternatives.
Automation
The repeated, rule-shaped work handed to the system once the rule is stable.
AI
Used today in design and analysis. It is not running inside your live finance system.
Before you sign anything
Four things. Software comes last.
A first call about the business, your process walked end to end, a proposal that argues the options against each other, and only then the software on screen. Most of this industry runs that list backwards.
The first call
What the business sells, where it is heading, and what is breaking right now. Nobody opens a demo.
Your process, end to end
Your version of the work, next to the way it is normally run. The differences become visible.
A price and an argument
Options A, B and C, with the reasoning next to each — written for the board.
The software
You see the system once we understand how you actually work, not before.
And once the contract is signed
Five phases. Finance signs off before handover.
Discovery ends with the legal entity structure, chart of accounts, integration landscape and period-close workflow written down. Configuration starts after that, not alongside it.
Discovery
Financial architecture review, entity mapping, integration audit, and KPI alignment with finance leadership.
Design
Chart of accounts, consolidation structure, approval workflows and revenue recognition rules documented first.
Build
Sprint-based configuration, data migration, integrations, and testing against real scenarios.
Go-live
Hypercare through cutover, a managed parallel run, and a financial close signed off.
Scale
A named support consultant, module expansions when needed, and an annual system Health Check.
Work already delivered
Five published projects.
Expenses, consolidation or revenue recognition being done by hand, in a spreadsheet, by somebody who could not go on holiday in the first week of the month.
AMANN
BeforeInternational expenses, multi-country rules and reimbursement standards handled by hand.
AfterCountry rules and approvals standardised, with master data synchronised into SAP.
Scenic
BeforeConsolidation and intercompany work spread across disparate systems.
AfterOne reliable source across subsidiaries, with automated consolidation and elimination.
Hasenkamp
BeforeInternational expenses differed across twenty legal entities.
AfterEnd-to-end expense management integrated with Exact ERP.
NZYM
BeforeManual expenses across six entities, with no real-time view.
AfterApproved expenses post automatically into Microsoft Dynamics 365 Business Central.
Perk
BeforeDisparate data, manual consolidation and different ledgers reporting differently.
AfterOne integrated financial platform with automated consolidation and elimination.
Who stays
The same names, through the year after go-live.
In the order you meet them. After the project closes, somebody still owns your account, and it is a person rather than a queue.
Lars Kirschstein
Managing Director
Christoph Schweins
Managing Director
Fares Khattab
ERP & NetSuite Specialist
Jarrid Gilfillan
Head of Products
Eric Roger Jean
Install base
One bounded way to start
The Health Check: ten working days, and a written answer you keep.
We look at how your system is set up, what that setup costs you, and what to fix first. You keep the findings report and its prioritised first-fix list.
Talk to someone first