HarakahTec Help centre العربية

Step 29 · Part 7 — Selling, reporting, going live

Keeping the system honest

A daily, weekly, monthly, VAT-period and yearly routine — and the system log, for when you need to know who changed what.

Applies to: Everyone, forever. This is the section that decides whether the rest of it was worth doing.

A system is only as good as what goes into it. This is the routine that keeps HarakahTec's answers true, written as five lists by how often each thing needs doing.

None of it takes long. All of it takes longer if you skip it for a month.

#Every day

At the till

  1. Open the shift, counting the float — §26
  2. Record cash in and out as it happens — a cash-out with its reason, a cash-in with a note — §26
  3. Log waste when it happens, not at the end of the week — §26
  4. Close the shift, counting the drawer — §26

In the office

  1. Work the cash review queue to empty — §23

    This is the one that matters. Every cash-out from yesterday gets its document: the supplier's invoice, the wage, the owner's money to the bank. Every cash-in gets its source: the bank, the safe, the owner, or other income. When the queue is empty, the cash-in-transit account reads zero and your profit and loss is telling the truth.

  2. Glance at the dashboard. You will notice a bad day faster than a report will tell you about it.

#Every week

#Every month

#Every VAT period

Careful: Do not leave the VAT return to the last day of the deadline. If the self-check disagrees, you want time to find out why. The usual causes are purchase invoices entered but never received, and sales made before the books opened.

#Every year

#The system log

Settings → System logs is the record of who changed what.

The system log with its filters and one entry expanded to show what was sent
Every change, who made it, and what was refused as well as what went through.

Every entry carries:

Column Meaning
When
Who The user, marked (left) if they have since gone
Area Which part of the system
What The action
Record What it was done to
Result Done, or Refused with the reason
Branch Which branch it happened at, where it belongs to one

And a Detail view showing what was sent.

Two things that make it useful

It records refusals as well as successes. Tick Include what was refused. Somebody repeatedly trying to do something they are not allowed to do is worth knowing about — and so is a permission that is stopping somebody from doing their job.

It survives the person. A user who has left still appears, marked as such, against the changes they made. Account removed appears where the account is gone entirely.

When to open it

Filter by area, by person, or search a record's id or part of an action.

Worth knowing: The log is a record, not a recycle bin. It tells you what happened; it does not put it back. That is what the reversal and deactivation patterns throughout the system are for.

#If something looks wrong

A rough order of investigation, which holds for most problems:

  1. Is it the business unit picker? An empty screen is usually the wrong unit selected — §2
  2. Is it a permission? Missing screens are almost always a role — §5
  3. Is it the date range? Reports default to a period that may not be yours
  4. Is it in the stock movement history? Every quantity change is there, with what caused it — §19
  5. Is it in the journal? Every posting is there, with what caused it — §22
  6. Is it in the system log? Every change is there, with who made it

Six screens, in that order, will explain almost anything.

#And that is the whole system

You have gone from an email address to a business running on HarakahTec: a company with its papers in, staff with the right access, a catalog with real costs, tills that sell and print and balance, books that post themselves, and reports that agree with each other.

The rest is trading.