Implementation & Rollout

Building a module is the visible half of adding one. The other half is declaring it in a dozen registries that decide whether anybody can find it, search it, report on it, recover from it or be told about it.

Deleting a workspace is a thirty-day request rather than an action, it can be cancelled for as long as it has not started, and exactly three tables survive it — including the record of the deletion itself.

A spreadsheet import here is all or nothing: one unacceptable row and the entire file is undone. That is the opposite of what most systems do, and it is right for a specific reason — a half-loaded file is worse than no file.

We do not do US sales tax at all, and that is the first line rather than a footnote. Then what to ask everyone else, what to ignore, and the five things that should take us off your list.

Five exclusions at the top rather than the bottom: no VAT numbers on the invoice, no VIES check, no reverse-charge treatment, no Belastingdienst connection, no Dutch reference customer. Then the questions worth asking everybody else.

The same organisation signing up in a browser stored one thing and signing up on a phone stored another. One normaliser now serves all three signup routes — and it makes the shape uniform without inventing the country nobody typed.

The application clock is one value for the whole installation, and the deployed value is Nairobi. Report schedules and workflow calendars each carry their own timezone and honour it properly. Every record stamped anywhere else does not, because there is one clock and it is not a column.

Six questions with structural answers — a number, a yes, a name — including the one almost nobody asks: who maintains the municipal rate dataset, and on what schedule?

Ask where rounding happens, and ask to see the tax for one rate on a two-rate invoice. Five tests you can run yourself in fifteen minutes — with our own answers beside each, including the one that cannot be paid.

The question buyers normally lead with — are you compliant here — is the one that tells you least in this market. Four that work better, including two where a confident vendor answer should reduce your confidence rather than increase it.

Ask what your tax is called, not what it costs — then ask who can add a name that is missing. Five questions, four checkable in a trial account, and the first one tells most readers to skip ahead.

Ask what a stored tax figure knows about its destination — then ask whether the vendor would classify goods versus services for you. The right answer to the second is no, and the first question tells many readers to skip ahead.