“Every month-end close, we spend more time reconciling exports than analysing variances.”
“The commission calculation lives in one spreadsheet, and only one person really understands it.”
“We pay for a licence the team uses at half capacity.”
All three come down to the same thing: repetitive calculations done by hand, on data corrected downstream, with logic written down nowhere.
What nuclai does in finance process automation
At nuclai, finance process automation means handing the finance function’s recurring calculations to purpose-built scripts and models, once those calculations can be traced.
We fix the data at source first, in the ERP or at the point of entry, rather than cleaning it at the end of the chain. Then we write the scripts (Python, LLM environments) that run the calculation: month-end close reconciliations, commission calculation, accounts payable, fixed assets and procurement. Every step leaves a trail your team and your auditors can follow.
What you receive
At the end of the engagement, you hold five things:
- The automation scripts, installed in your environment and connected to your ERP.
- The calculation rules, documented: instructions, calculation models, glossary of terms and accounts.
- The audit trail: for every figure produced, the path back to its source data.
- A tracking dashboard for the automated process, for example month-end close progress.
- The handover pack: technical documentation for whoever maintains the solution, and onboarding for the finance team.
All five are stored on your side. Neither nuclai nor a software vendor holds the keys.
Four steps: diagnostic, pilot, rollout, handover
- Diagnostic. The financial process diagnostic runs in three phases: on site, analysis, debrief. It shows which calculations can be traced, which cannot yet, and what automating them would return. It may conclude that nothing should be automated. It is covered by its own proposal.
- Pilot. We automate one process, chosen with you from those the diagnostic retained. The pilot runs alongside the manual process, and both results are compared before anything is switched over.
- Rollout. Once your team has signed off the pilot, the solution goes live and extends to the other retained processes. Data is fixed at source as the rollout progresses.
- Handover. We hand over the documentation and access, and the finance team takes the solution in hand. From then on, it is yours.
Who it is for
- Companies: SMEs and mid-sized companies.
- Roles: CFO, head of finance, chief accountant, financial controller.
- Prerequisites: an ERP or accounting system in place, with accessible exports; someone in-house who knows the process; a completed diagnostic.
What changes, dimension by dimension
| Dimension | Before | After |
|---|---|---|
| Month-end close duration | Manual reconciliation across exports | Reconciliations run by script, the team works on variances |
| Commission calculation | Recalculated by hand, dependent on one person | Reproducible calculation, documented rules |
| Traceability | Downstream corrections, hard to trace | Every figure linked to its source data |
| Licence costs | Tools paid for, partly used | Unneeded licences identified, cancelled if you decide so |
| Dependency | Logic held by a vendor or in one person’s head | Logic documented and stored on your side |
Pedro Mestre, an accountant by training since 2013, leads the nuclai / finance practice. He applied this method in the analytics department of a Neuchâtel technology company. The Month-End Closing Tracker business case shows one example: close tracking was automated and the BlackLine licence cancelled.
How we work
You set the goal, we check what is feasible
Cutting costs, absorbing growth without hiring, tightening internal control: the goal is yours, and we do not debate it. Nor do we pass judgement on how you choose to use AI. What we check is technical feasibility: a calculation nobody can trace back cannot be automated yet, whatever goal it serves. The diagnostic tells you what is feasible and worth doing. We then build what you decided, in strict confidence.
Your calculation rules stay with you
Instructions, calculation models, glossaries: the mechanics of your processes are documented and stored in your environment. They depend on neither a vendor nor nuclai.
Frequently asked questions about finance process automation
No, nuclai works with the ERP you already have. The scripts connect to its exports or interfaces, and data is fixed at source. The aim often runs the other way: fewer paid tools around the ERP. If a limitation of your ERP blocks a calculation, the diagnostic flags it before any development starts.
On your side, in your own environment. nuclai documents the instructions, calculation models and glossaries, then hands them to your team. No dependency on a vendor is created.
No development starts on that process, and you know before you have invested. Recommending not to automate is a legitimate outcome of the diagnostic. The cause may be incomplete source data or a calculation rule that was never written down. We then tell you what to fix upstream; your goal stays the same.
Your team, or whoever you appoint. The handover includes technical documentation, operational documentation and onboarding for the finance team. Because the logic is stored on your side, another qualified provider can also take it over.
No, every automated calculation leaves a traceable path from source data to final figure. The rules are documented in plain language and reviewed with your team before going live. Your auditors can follow the same path. A calculation that cannot be traced back is not automated.
No. The first conversation takes place remotely, free of charge. It defines the scope and leads to a proposal setting scope, duration and price. The diagnostic starts on signature.
Request a proposal to automate your finance processes
Every automation engagement starts with the financial process diagnostic: it establishes what can be automated, and at what return. The first conversation, remote and free of charge, sets its scope.