Operating in the United States and Canada

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.

Our table holds Canada at the federal rate, which is correct. It then writes that rate into an organization's own settings and never revisits the question — so a business in a harmonised province is configured at the federal figure and nothing says otherwise.

Five exclusions at the top, one of which rules us out of an entire province. Then the questions worth asking every vendor selling into a country where a sale can carry two taxes owed to two governments.

Both are a percentage added at the till, which is where the resemblance ends. One is collected in stages and reclaimed; the other is collected once and avoided with a document. Software built for the first models the second incorrectly rather than incompletely.

Our engine computes each Canadian levy against its own base and hands back the breakdown. The document then stores a single blended rate and discards it — so the total is right and the split, which is the only thing either return needs, is gone.

US sales tax follows the customer. Our customer record holds a latitude to seven decimal places and no state field — and the question turns out to be asked in four places in our own code and answered from the organization every time.

A custom report here belongs to whoever built it. The machinery deciding who may open a shared report is complete, careful and will never be consulted, because nothing in the product can create the record it reads — and the only test asserts the columns exist.

The moment a report becomes a file it stops being a view of your data and becomes a copy. Live shared report links, and a stored metric series to reconcile against later, are both additions we can enable so the number stays current.

Canada gives you two days to report a product incident, counted from the day you became aware. That is a date about your organization rather than about a record — and it is the one date no operations system holds.

A consumer privacy request does not come through a privacy console. It arrives as a support ticket from somebody who has never logged in. Our help desk can identify that person and time the reply; our export and erasure tooling is built around user accounts, which is the one thing they do not have.

Canada's legal-tender limits are written in denominations, and a till records a payment as one number. The gap is not a compliance problem — it is a modelling one, and two of the missing pieces are worth having anyway.

The card-data question worth asking a point-of-sale vendor is not how the number is encrypted — it is whether there is anywhere to put one. Our payments table has six columns and no card among them, which is the strongest position available and has a price we would rather state than let you find.

A US forklift certification has no expiry date. Five things oblige you to retrain the operator and four of them are events, not dates — which is a problem for every mechanism built to watch a calendar.

There is a working document-expiry reminder in this product. It reads a date, respects your notification settings and warns you thirty days out. It is filtered to employees — so a work permit gets a warning and an equipment insurance certificate gets silence.

A certified payroll has a period of one week, a scope of one contract, and a signature attesting to three specific things. None is a cost figure — and its most unusual requirement is something this product already does, in the wrong module.

A project carries one money budget. Its actual cost arrives from four independent streams — logged time, purchases, expenses and stock issued to the job. So the system can say a job is eighty per cent through its money and cannot say which of the four is why.

The US food traceability rule is summarised as lot codes and a 24-hour clock. The sentence nobody quotes asks for your coding systems, abbreviations and a written map from your records to the elements it names — a document about your software.

In most of the world the inventory costing method is an accounting preference and any defensible one will do. In the United States it can be a commitment with consequences reaching past the ledger — which makes it the one market where "our system supports exactly one method" is a fact a buyer needs before signing rather than after. We support exactly one.

A tax rate here cannot be created above one hundred per cent by any route. It can be updated above it through one. The rule was written on two doors out of three, which is the ordinary way a validation gap happens and the ordinary reason nobody notices.

There is no recurring invoice here. No schedule, no template, no next-run date. Forty monthly retainers are forty invoices somebody creates by hand — and the failure mode is not that one is wrong, it is that one is missing.

Two people agree to trade Saturday and somebody changes a name on the roster. The roster is now correct and the trade has left no trace — not who asked, not who agreed, not who approved, and not what the shift said an hour ago.

American overtime is owed above forty hours in a workweek — a fixed seven-day period the employer designates, which need not start on Monday and need not match the pay period. Our records have no workweek in them at all, and the boundary they do enforce, by locking it, is the calendar month.

A purchase order in our system records what you ordered, when it is due, who acknowledged it and where the truck is. It does not record the one term that decides whether the freight on it was ever yours to pay — and we will attach that freight to your stock cost without asking, because nothing in the system knows.