Reports & BI

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.

Every market that sets a retention period is really asking whether you can put back what the report said at the time. Three things differ by market and only one is the number of years — and our own audit log turned out to expire on a two-year default while a legal hold on the record it describes did nothing to stop it. We published that, fixed it the same day, and both dates are on the page.

Four ways a search box lies, all of them silent: it searches the page instead of the list, a typed percent sign matches everything, an ungrouped condition drops your filters, and the escaping meant to prevent the second one does nothing on the database the tests run against.

Victoria wants a written incident record within 48 hours, on a form the Authority defines, kept five years and shown on request to people who do not work for you. Every report we make well is one you designed yourself.

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.

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.

Large UK companies publish how fast they pay suppliers twice a year, and every figure is a difference between two dates the Regulations define precisely. One of them is not the invoice date, not the date you entered it, and not the due date.

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.

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.

A journal entry here carries an account, an amount, a reference and a description — clean, fast and easy to audit. Branch, department and project dimensions, so you can read profit by any of them, are an extension we can make for you.

A saved filter here belongs to one person. A report schedule can be driven by one. So the weekly figures a team runs on can rest on a private view that nobody else is able to open, inspect or inherit.

A report schedule in this product carries its own timezone and computes its next run in it. The deadline engine three modules away has no timezone at all. The capability exists, once, in the place where getting it wrong matters least.