Implementation
An implementation is judged on the first month-end, not the go-live
Any competent consultancy can get SAP Business One switched on. The question that matters is what happens four weeks later, when your finance team has to close the month in it for the first time. That is the date we plan backwards from.
- Finance involved from the first workshop
- Written solution design you approve
- First close supported, not handed over
Why implementations disappoint
The failure modes are remarkably consistent
Very few ERP implementations fail outright. Most go live and then quietly underdeliver, in one of these ways.
The chart of accounts was never designed
It was copied from a template or lifted from the old system. Every management report afterwards needs a spreadsheet to translate it into something the board recognises.
Finance saw it too late
The design was agreed with operations, and the finance team met the system at training. By then the decisions that shape the close were already made.
Data was migrated, not reconciled
Balances came across and nobody could prove they matched. The opening position was signed off on trust, and the doubt never fully went away.
Testing was a demonstration
The consultant showed the system working with clean data. Nobody tested a credit note against a part-delivered order, or a month with a stock adjustment in it.
Training was a day on the system
Users were shown which buttons to press but never why the process changed, so they went back to the old workarounds within a fortnight.
Go-live was the last day of the project
The team left the week the system went live, which is exactly the point at which the business needs them most.
How we run it
Design agreed on paper before anything is configured
The expensive mistakes in an ERP implementation are made in the first three weeks and discovered in the ninth month. Getting the design written down and agreed is what prevents that.
We start with how the business actually runs — order to cash, purchase to pay, stock, and the close — observed with the people doing the work rather than gathered from a requirements questionnaire. That produces a written solution design: the chart of accounts and its control accounts, cost centres and distribution rules, document flows, stock valuation method, approval thresholds, what will be configured, what will be built, and which processes need to change. You approve that document before configuration starts.
Because our consultants also do finance work, the design is tested against the month-end from the beginning. We ask what the management pack has to show, what has to reconcile to what, and which numbers a director will question — and then configure so those answers come out of the system rather than out of a spreadsheet built on top of it.
Delivery runs in stages you can see. You get working demonstrations against your own data rather than a long silence ending in a go-live weekend. Migration is run as at least two rehearsals before the real thing, each reconciled and signed off, so the opening balances are proven rather than trusted.
Non-negotiables on our projects
- Finance in the room from workshop one
- A signed solution design before configuration
- At least two rehearsed, reconciled data loads
- We are there for the first month-end close
What is included
What an implementation covers
Discovery and solution design
Process walkthroughs across finance, sales, purchasing and stock, ending in a written design document you approve and keep.
Financial configuration
Chart of accounts, control accounts, cost centres and distribution rules, tax codes and VAT handling, banking, and the posting behaviour behind every document type.
Operational configuration
Document flows, item and business partner master data, pricing, warehouses, approval procedures and user authorisations.
Data migration
Master data, open items and the history you actually need, loaded through rehearsed runs with a reconciliation your finance team signs off.
Testing and UAT
Scripted testing on a copy of your own data, including the awkward cases — part deliveries, credit notes, returns, adjustments and period end.
Training and go-live
Role-based training on your configuration and your data, a planned cutover, and support through the first close rather than a handover at go-live.
How it works
From first workshop to a closed month
Discover
Process walkthroughs with the people doing the work, a review of your current data, and a clear statement of what the system has to produce.
- Process observation
- Data quality review
- Reporting requirements
Design
The written solution design: chart of accounts, document flows, valuation, approvals, integrations and any development. Approved before configuration.
- Solution design document
- Gap analysis
- Fixed scope and quotation
Configure
The system built in stages against the design, with working demonstrations at each stage rather than one reveal at the end.
- Staged build
- Demonstrations on your data
- Change log maintained
Migrate
Rehearsed data loads — at least two before the live run — each reconciled to your existing system and signed off.
- Extract and cleanse
- Rehearsal loads
- Reconciliation sign-off
Test
User acceptance testing to scripts you agreed, run by your people on a copy of your own data, including the edge cases that break systems.
- UAT scripts
- Edge and failure cases
- Written sign-off
Go live and close
A planned cutover with a rollback position, then support through the first month-end close in the new system.
- Cutover plan
- Hypercare period
- First close supported
Detail
The decisions an implementation actually turns on
These are the choices that determine whether the system helps or hinders three years from now. They are cheap to get right at design and expensive to unpick later.
Financial structure
- Chart of accounts and segmentation
- Control accounts and reconciliation design
- Cost centres and distribution rules
- Tax codes, VAT and Making Tax Digital
- Multi-currency and revaluation
- Posting periods and period-end locking
Stock and costing
- Valuation method by item group
- Warehouse and bin structure
- Batch and serial requirements
- Landed cost treatment
- Goods received not invoiced handling
- Stock take and adjustment process
Document and process flow
- Order to cash and purchase to pay flows
- Approval procedures and thresholds
- Credit limits and blocking rules
- Document numbering series
- Printing layouts and templates
- User authorisations and segregation of duties
Data migration
- Master data cleansing before load
- Open item and balance strategy
- How much history to bring across
- Reconciliation approach and evidence
- Cutover sequencing and freeze periods
- Fallback position if the load fails
Platform
- SQL Server or SAP HANA selection
- Environment strategy: live, test, training
- Backup, recovery and refresh process
- Authorisation and licensing model
- Integration points identified at design
- Upgrade approach agreed up front
Adoption
- Role-based training on your configuration
- Process documentation for each role
- Super-user identification and support
- Post-go-live hypercare
- First close run alongside your team
- Benefits review after three months
What changes
What a well-run implementation leaves behind
A close that works from month one
Reconciliations designed into the configuration, so the first close is a process rather than an investigation.
Reporting from the ledger
A chart of accounts built for the reporting the board wants, so the management pack comes out of the system.
An opening position you can prove
Migrated balances reconciled and signed off, so nobody spends the next two years doubting the numbers.
Users who understand why
Training on your processes rather than generic screens, which is what makes new ways of working survive past the first fortnight.
Documentation you own
The solution design, the configuration decisions and the reasons behind them, written down and handed over.
What to expect
How long an implementation takes
These are the ranges we see. The variables that move them most are the number of legal entities, whether you manufacture, and how much integration is in scope.
Single company, distribution
Typically three to four months from first workshop to go-live, with the first close a month after that.
Manufacturing
Four to six months. Bills of material, routings, costing and MRP add design time and a great deal more testing.
Multi-company or multi-currency
Add four to eight weeks. Consolidation, intercompany handling and revaluation are design decisions, not switches.
Heavy integration
Each interface adds two to eight weeks and is usually the critical path, because it depends on a system that is not ours.
Your team’s time
Expect meaningful involvement: workshops, data cleansing, UAT and training. An implementation nobody in the business has time for is one that will underdeliver.
After go-live
A hypercare period, the first month-end run alongside your team, and a benefits review at three months.
We quote against a signed solution design, not against a wish list, so the number you are given is one we can stand behind.
Fit
Whether this is the right conversation
A good fit if
- You have outgrown your accounting software and are hitting its limits
- You are running several disconnected systems and re-keying between them
- You have selected SAP Business One and need it implemented properly
- You are still choosing, and want an assessment rather than a demonstration
- A previous implementation underdelivered and you are considering a restart
Probably not us if
- You need a system live in under a month
- Nobody in the business has time to be involved
- You want the new system to replicate the old one exactly, including its problems
Common questions
Questions we are asked before a project starts
How long does an SAP Business One implementation take?
For a single-company distribution business, typically three to four months from first workshop to go-live, with the first month-end close about four weeks later. Manufacturing, multiple companies, multiple currencies or significant integration extend that. Anyone quoting a fixed duration before understanding your processes is guessing.
How much of our team’s time will it take?
More than most vendors imply. Expect your finance lead and one person from each operational area to be substantially involved in workshops, data cleansing, testing and training. This is the single strongest predictor of whether an implementation delivers: projects nobody has time for go live and then underperform.
Can you take over an implementation that has stalled?
Yes. We start with a review of what has been configured and what has been agreed, then give you a written assessment of the options — finish it, correct it, or restart. We will say plainly if we think restarting is cheaper than rescuing, even though that is the less comfortable answer.
What happens to our historical data?
Master data and open items always come across. Full transactional history usually should not: it is expensive to migrate, it slows the new system, and it is rarely used. The common approach is to bring balances and open items, keep a defined period of history, and retain read-only access to the old system for the rest. We agree that at design and reconcile whatever moves.
Do you stay involved after go-live?
Yes, and we regard that as part of the implementation rather than an upsell. There is a hypercare period immediately after cutover, and we run the first month-end close alongside your finance team. The first close is where the design is genuinely tested.
Related
Where to go next
Data Migration
Moving master data, open items and history across with a reconciliation you can sign off.
Read more
Support
What happens after go-live: named consultants who already know your configuration.
Read more
ERP + Accounting
Why the finance function and the system are better designed by the same team.
Read more
Planning an implementation?
Whether you have chosen SAP Business One or are still deciding, a first conversation will tell you what the work realistically involves — including whether we think it is the right system for you.
Or call +44 7493 619245 — Monday to Friday, 09:00–17:30.