See how the ERP is being used

01Read the period first

Everything on the page is for one window: the last 7, 30 or 90 days, or the last 12 months. Change it before you read anything else, because the same company looks very different over a week and over a year.

Thirty days is the useful default. A week tells you about this week — a slow one, a holiday, a big order — rather than about how you work.

02Which modules are being used

The bars count the records each module owns: invoices, quotations, deliveries and credit notes for Sales; rounds for Distribution; movements, products and reorder minimums for Inventory; payments, cheques and bank imports for Finance; employees, leave and payroll for People.

Counter sale counts till sessions, not sales. Opening a till, closing it and counting the drawer are the till's own records. The sales it takes are sales invoices, and they are counted under Sales — a counter sale is a sales invoice. So a busy shop shows a modest number here and a large one under Sales, and that is correct rather than a fault.

The line under the bars matters more than the bars:

Switched on, untouched this period. A module enabled that nobody has opened in thirty days is one of two things, and both are worth an answer. Either somebody was never shown how to use it — that is a training problem — or the business does not need it, and it should be switched off so it stops crowding everybody's navigation.

If a module ever appears as not separable from another module, its work cannot be told apart from a neighbour's in the record, and the page says so instead of showing a zero you would act on. Nothing sits there today.

03Who is working in it

Actions recorded per person, most active first.

Read it as a picture of where the work sits, not as a ranking of who is worth more. The person who fixes everybody else's documents will be near the top, and so will whoever does the daily posting. Someone who spends the day reading reports and deciding things will be near the bottom, or absent entirely.

That absence is not a bug. This measures work that was saved, not attention. Reading a screen writes nothing to the trail, and the ERP does not watch people read. Anyone using this page to judge who is working hardest is using the wrong page, and will get the wrong answer.

04Activity by day

One bar per day, so the shape of the week shows: the day your invoicing gets done, the day nobody posts anything, the run-up to month end.

A long flat run followed by a spike usually means the work is being kept somewhere else and entered in a batch — on paper, or in a spreadsheet. That is worth finding, because everything between the work and the entry is a figure your ERP did not have when somebody needed it.

05What is deliberately not counted

The bookkeeping the system posts by itself. Confirming an invoice writes journal entries automatically; so does a payment, a delivery, and a month of depreciation. Those are the engine running, not a person working, and counting them would make your accounting look like your busiest module while nobody had it open.

Anything anyone read. Covered above, and worth repeating because it is the question people ask first.

Work done before the trail existed. Records that predate the activity trail were brought in with their original dates and are marked as historic. They are excluded, so installing the trail does not look like a day everybody worked very hard.

06Ask the assistant instead

If Horizon213 AI is switched on for your company, you can ask it directly — "which modules are we actually using?", "is anyone using the till?", "should we turn off projects?" — and it reads this same page's figures, with the same limits attached, and refuses the same way if you do not have the rights.