Operating in East Asia

Japan makes the main contractor keep a register of everyone working below it, on site — and makes each tier tell the tier above who it engaged. The party who keeps the register is not the party who fills it in, and our supplier portal is already the right channel.

A sprint belongs to a project, and a task can only join a sprint in its own project. For a squad built around one engagement that is invisible; for a standing team carrying a client portfolio it is one cadence turned into four records, four burndowns and four velocities.

Japan gives a mail-order buyer eight days from delivery to send the goods back — and takes the right away if you published your own terms in the advertisement. The window is a property of a document, and our return row records neither the route nor the postage.

The most common way a support team hits its first-response target without responding is to write a note to itself. One condition in this codebase makes that impossible, and it is worth knowing which one before somebody helpfully removes it.

Japan's misleading-representation penalty is three per cent of the sales you made of those goods during the period the claim was displayed. We can produce the sales for any window; nothing here records when a price or a claim was in force.

A comment on the till code promised that failed fiscal filings were reconciled with a manual button. The comment had been copied from the invoice flow, which had one. The till did not, and the job gave up after three attempts.

Japan makes an employer of over a hundred people measure four things before writing a plan about women at work. Three are arithmetic over records this product already keeps. The fourth needs a column we do not ship, and we think we are right not to.

A report here is built on one dataset — a sound design that keeps a whole class of double-counting out of your numbers. The joins worth adding on top, where you need a supplier and a customer, or a purchase and a complaint, in the same row.

Japan caps overtime with four tests running at once — a monthly limit, an annual one, a rolling average across two to six months, and a count of how many months went over. Only the first can be answered by looking at a month.

Our public holidays repeat on the same date every year. Six of Japan's sixteen are not on a date at all — four are the nth Monday of a month and two are announced annually. The first year is correct, which is the problem.

Document numbers are sequential per organisation, per type, per prefix and per year, zero-padded, and safe when two people press save together. What the key does not contain is a branch — so ten sites share one run.

Every quotation, invoice and till sale carries eight fields recording the conditions it was raised under — country, currency, tax type, rate, enabled, inclusive, exchange rate and a timestamp. Change any of those settings tomorrow and the document does not move.

Our asset register knows a forklift on your floor might be owned, leased or borrowed, and enforces it in five places. Our stock system has no equivalent idea at all — every unit is yours by assumption. For anyone holding supplier-owned components, that assumption is the difference between what is in the building and what belongs on the balance sheet.

Serial-number tracking for stock has a table, a model, three screens, two routes and a count on the dashboard. It has no code path that can create a row. The screens work perfectly and will always be empty — and the test that would have found it takes ninety seconds.

When stock runs low our system can raise a purchase requisition on its own. It raises it against a department. It does not name a supplier, look at who supplied the item last time, or consider who is cheapest — because nothing in the automation has any concept of who you buy from.

We record how much tax was paid on a purchase and not what it means. That gap has a general shape — a stored value whose interpretation lives outside the data — and once you see it you find it in landed costs, quantities and dates.

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.

Ask whether tax mechanism is a property of the country or of your business — then ask whether the vendor would guess it from your industry. The right answer to the second is no.

Taiwan runs two tax mechanisms inside one statute. Most businesses deduct what they paid a supplier; financial businesses cannot. The same payment is a receivable for one and a cost for the other — and nothing about that is a percentage.

Japan does not only say what your invoice must show. It says how the consumption tax may be rounded — once per rate band — and the yen has no minor unit. Our own system produces a tax figure of ¥423.4.

An asset label has two readers. One is a person who will complain when it looks wrong, and one is a camera that will simply fail. We shipped a barcode that was invisible in dark mode and perfect in every screenshot — which is exactly the failure a machine reader produces.