Operating in Southeast Asia

Singapore's packaging report is triggered by a turnover figure and made of kilograms by material. One of those we can produce for any period; the other has never been entered into the system by anybody — and the Act gives you exactly one year to start.

The Philippines requires nine disclosures before a consumer credit sale is consummated, and two of them are different interest rates. Our invoice holds a balance and a due date; the word instalment appears nowhere in the codebase.

Singapore's security-of-payment Act defines a day, for every deadline in it, as any day other than a public holiday. Weekends count. That is a third unit of time, and most systems implement two.

Singapore presumes that goods failing within six months of delivery were faulty when they were handed over, and the seller has to establish otherwise. That makes the delivery date and the individual unit the two records that matter.

Singapore prescribes what a payslip contains, item by item. Two are dates of payment, two are the first and last days of a period, and one is a period that need not be the salary period at all — so we held our payroll against all eleven.

A till sale has no approval step to hang a lock on — the money moves and the receipt prints in the same breath. So the signature had to become its own lock: signed once, never replaced, and refused entirely once the sale has been reversed.

There is a report builder here and, by design, no raw SQL — everything protecting your data sits in the layer a raw query would go underneath. For analysts who want more reach, we extend the builder's datasets rather than lower that floor.

A task here can carry story points and a sprint, or estimated hours and a milestone, or all four at once. Only one of those vocabularies reaches the cost figures — so which one you plan in quietly decides whether your plan can be costed.

An employee's hour is recorded twice here — once as attendance that becomes pay, once as effort that becomes project cost. Linking the two, so you can compare what you paid for against what you billed, is an integration we can build into your workspace.

You can record that an asset was verified. You cannot start a verification, assign it, track what is outstanding or close it. The stock module can do all four for a count — which makes this a design inconsistency rather than a missing feature.

A sale from a till app can name the warehouse it came out of. The field is validated and then thrown away in favour of the counter’s own — which is the safe answer, and it leaves the field sitting in the one place a value that does nothing can still do something.

There is no delivery note. An invoice knows which warehouse the goods left from, and there is no separate document that travels with them and gets signed at the other end. For internal transfers there is exactly that.