Skip to content
Quillix docs
Home Support Open app → (opens in a new tab)

Data Integrity

Where Sidebar Data Integrity

A second opinion on your numbers. Every booked sale, purchase and expense is re-checked on the server — the GST split recomputed from taxable value times rate — and anything that does not add up is listed here. Auditors only.

First
These are advisory. Nothing was blocked and nothing was changed. The record saved exactly as entered — this is Quillix telling you afterwards that the arithmetic does not hold.
SCREENSHOT · the integrity queue with the record-type filter chips and their counts above a table of flagged rows

One row per record whose GST does not reconcile, naming the client, the document, what specifically disagrees, the taxable value, and when it was flagged. Rows are newest first.

  1. Read the Issue column first — it says what did not add up, not merely that something did.
  2. The Document column names the invoice or bill, so you can find it in that client's books.
  1. Click All open, Sales, Purchases or Expenses above the table.
  2. The counts on the chips are the open issues of each type, so you can see where the problem is concentrated without filtering.

There is no Resolve button here, and that is deliberate. The flag clears itself the moment the underlying record is corrected or deleted.

  1. Note the client and the document from the row.
  2. Open that client's books and go to the matching history page — Sales History for a sale, Purchases & Expenses for a purchase or expense.
  3. Correct the record so its GST follows from its taxable value and rate, and save.
  4. The row disappears from this queue on its own. You do not need to come back and dismiss it.
Why there is no dismiss
A dismiss button would let a genuine mismatch be waved through without the number being fixed — exactly the wrong affordance for a page like this. So there is not one.

An empty queue means every booked record's GST reconciles. Nothing needs to be run or scheduled.

  1. New issues appear here by themselves as records are booked — the check runs on the server every time something is written.
  2. Treat a non-empty queue as work waiting, and an empty one as genuinely all clear.

Last updated