Implementation
The system runs on your machine. The way there is written down and walked one step at a time.
One script puts everything on a clean machine. There are installers for Ubuntu, Windows and macOS.
The system asks about your accounting policy before it opens anything else. Each answer keeps who gave it and when.
Partners and items come in from a file, with a preview before anything is saved.
Balances, stock and open invoices each have their own screen. They stay correctable until you go live.
You say where your series carry on from, so there is no break against the old system.
A separate database cloned from yours, with a banner over every page. People learn there and break nothing.
A screen lists what is not ready yet. You go live when the list is empty.
You compare the balances against the old system before the first real document.
And afterwards
On a schedule, kept for a period you set. The attached files are included, not only the database.
The new version is prepared alongside and goes live only if everything is sound. The previous one stays as the way back.
You can hold an update for up to 31 days. The reason reaches us.
If you would rather not run a server, you request the move from the program itself.
Taking the system home again is the same button on the same screen.
What is specific to you is switched on by licence rather than by a separate build. So everybody gets the same fixes.
Before you request any move at all, the screen lists what it will mean for you.
Next step
No slide deck. Bring one of your invoices and one of your deliveries and we will run them through the system in front of you.
We reply within the working day.