Our team
DEED
- Project management and planning
- Discovery phase and configuration
- Build, migration and testing
- Instruction, manual and aftercare
NEXERA CoreImplementation
Live in phases. With a safety net at every step.
We take NEXERA Core live in phases. Each phase is configured and tested in its own environment, runs alongside your current system and only goes live when the results are right.
- 4
- phases, each with a clear end point
- 3
- separate environments
- 2
- languages in the manual
- 1
- team from analysis to aftercare
The phases
Four phases. Each with a clear end point.
For each phase you can see what we do, what you receive, what we ask of you and when the phase is complete.
01
Discovery phase
We map your process chain with the people who do the work: from quotation to general ledger, including the exceptions that have never been written down.
- Working sessions per department: sales, operations and finance
- Overview of current systems, integrations and data
- A decision list with an owner for each decision
- A phasing plan with a go/no-go for each phase
Complete when the decision list and the phasing have been approved.
You receive
Process map from quotation to general ledgerDecision list with ownersPhase plan with a go/no-go per phaseMigration plan per dataset
From you
Project sponsorKey user per departmentReal orders as examples
02
Configuration and build
The core is configured for your organisation. Whatever you do differently, we build on in small steps, which key users see straight away in the test environment.
- Legal entities, number sequences, chart of accounts and VAT codes
- Payment terms, document templates and standard texts per language
- Roles, permissions and approval rules
- Customisation in small, tested steps
Complete when key users have approved their processes in the test environment.
You receive
A configured test environmentDocuments in your house styleOverview of roles and permissionsManual in Dutch and English
From you
Decisions on the decision listTesting by key usersHouse style and standard texts
03
Migration and parallel run
Master data and outstanding items are transferred under control. Old and new then run side by side until the results match.
- Contacts, items and price agreements, with a check list for discrepancies
- Open orders, outstanding items and the opening balance per legal entity
- Chart of accounts, Dutch RGS codes and a test XAF audit file, agreed with your accountant
- A parallel run: the same documents through both systems
Complete when the figures reconcile and the accountant has confirmed the chart of accounts.
You receive
Migration report per datasetReconciliation of the opening balanceReport on the parallel run
From you
Exports from the current systemCoordination with the accountantReview of discrepancies
04
Go-live and continued development
You choose the moment. The team that built the system stands beside you at go-live and stays involved afterwards.
- Users invited, with mandatory two-step verification
- A short briefing per role, together with the manual
- Aftercare up to and including the first month-end close
- Continued development in small releases, with a changelog
Complete when the first period in NEXERA Core has been closed.
You receive
The production environmentAccounts per roleThe feedback button in the applicationA changelog of every change
From you
The timing of go-liveWho gets which roleFeedback from daily use
How we work
Build step by step,
deliver with certainty.
Four commitments that every phase rests on.
This is how we work on the core of NEXERA Core, and this is how we work on your configuration and customisation.
Decision list
We do not guess business rules
Anything still to be decided gets an owner on the decision list. Until then the system runs with a safe default, and the answer becomes a setting rather than code.
Review and tests
Small steps, always tested
Every change passes four checks: code scan, AI review, human review and the full test run. It only goes to production after a deliberate, manual approval.
Priority
Money and compliance first
Findings about money, data loss, security or compliance are resolved in the same change. We never put them off.
Changelog
Everything traceable
Every change that goes through is added to a changelog automatically, with what changed and why.
Data migration
What we transfer, and how we know it is right.
Every dataset has its own check. Discrepancies go on a list first, so that nothing incorrect slips in unnoticed.
| Dataset | How | Check |
|---|---|---|
| Contacts | Import from the current system or from Excel | Discrepancies, such as delivery addresses, first go on a check list |
| Items | Import with the new item codes | Old codes stay recognisable and keep their own price |
| Price agreements | Per customer, valid from a start date | Compared against the current price lists |
| Open orders | At the moment of switching over | Quantities and amounts match the old system |
| Outstanding items | Receivables and payables per legal entity | Reconcile with the trial balance |
| Opening balance | Per legal entity and financial year | Agreed with your accountant |
| Fixed assets | Register with depreciation schedules | Book value matches the accounts |
Who does what
Three parties, one schedule.
An implementation succeeds when everyone knows what is expected of them. This is how the work is divided.
Your organisation
Sponsor and key users
- A project sponsor from senior management
- A key user per department
- Decisions on financial and operational rules
- Real orders and documents as test material
- Acceptance at the end of each phase
Your accountant
Reconciliation with the books
- Confirmation of the chart of accounts
- RGS codes per general ledger account
- Check of an XAF test file
- Reconciliation of the opening balance
Go-live check
Ready for go-live? This must be green first.
We tick off these points together before a phase goes live. Tick them to see where a project stands.
10 points still openNot yet cleared for go-live
Finance
Data and technology
Organisation
Example: a project shortly before go-live. Your ticks are kept in this browser only.
After go-live
Modules for a next phase The team stays. The system grows with you.
Go-live is where use begins, and with it continued development. Support on working days, with a fixed response time set out in the agreement.
Feedback from the screen
The feedback button sends your report to the team, together with the screen you were on and what the application was doing at that moment.
Direct contact with the build team
You speak to the people who built the system and know your configuration.
Small, frequent releases
Improvements arrive in small, tested steps, and every change is recorded in the changelog.
A manual that grows with you
In Dutch and English, updated as soon as a part is stable.
A first phase with contacts, items, orders and shipments is usually live within 12 weeks. In the discovery phase we draw up the schedule for each phase.
Yes. The current system remains the system of record until a phase goes live. During the parallel run, the same documents pass through both systems.
Confirmation of the chart of accounts, the RGS codes for each general ledger account, a check of an XAF test file and the reconciliation of the opening balance.
It is mainly the key users who are involved: contributing in the discovery phase, testing in the test environment and accepting each phase. We schedule this in advance, so that it fits alongside their normal work.
It remains the system of record until go-live. After that, you decide how long it stays on as an archive; by then the outstanding items and the opening balance are in NEXERA Core.
NEXERA Core
Book a discovery phase.
After three weeks, you know the phasing and the price per phase.