PLATFORM · RULES & FLAGS
Your firm’s controls, in plain language: compiled, tried on the period first, then run deterministically.
01 · FROM SENTENCE TO CONTROL
How one rule is made.
Someone at the firm writes the control the way they’d say it. LZR compiles it, shows what it would have raised on the period, and only then puts it to work.
IN PLAIN LANGUAGE
Payments over ₹50,000 need a purchase order.
STEP 1 · WRITE
Someone at the firm writes the control in one sentence. No formulas, no scripting.
APPROVAL LIMIT
ILLUSTRATIVE
when payment.amount > 50000
require purchase_order on file
raise APPROVAL_LIMITSTEP 2 · COMPILE
The sentence becomes a structured rule: what it checks, what must be on file and the reason code it raises.
TRIED ON JUNE
EXAMPLE
Would have raised 4 flags in June
STEP 3 · TRY
Before it goes live, the rule runs over the open period, so you see what it would have raised.
SAME DATA, SAME FLAGS
The same 4 flags, both times.
STEP 4 · RUN
The same data always raises the same flags, on every upload and every time the open period is run again.
02 · THE RULEBOOK
The Rules screen, in the app.
Rules come from the firm’s template or are written for one client. Each shows what it applies to, what it raised this period, and whether it’s active, muted or a draft.
03 · ANATOMY OF A FLAG
Five parts, always the same.
Every flag has the same five parts. It states what was observed, shows the records behind it and names where it came from, so it can be checked months later.
A fixed reason code, not free text.
One or two lines stating what was observed, never what to do about it.
The two records side by side, and the fields they differ on.
Dismissing a flag is a recorded
decision and asks for a reason.
It is not a close button.
Which rule, agent or person raised it, and when. A flag with no attributable source is not shown.
Two or three mutually exclusive outcomes, one of which is acceptance.
Bank transfer: Kavro Holdings
–₹4,500
No payee record · reference KAVH/2506/22
POSSIBLE DUPLICATE
Same payee and amount as an entry 5 days earlier. Neither has an invoice attached.
TREATMENT
Agent suggests Professional Fees · 61%
EVIDENCE
No document attached
Required for payments over ₹2,000
TRAIL
Flagged by rule · 2 events
A fixed reason code, not free text.
One or two lines stating what was observed, never what to do about it.
The two records side by side, and the fields they differ on.
Which rule, agent or person raised it, and when. A flag with no attributable source is not shown.
Two or three mutually exclusive outcomes, one of which is acceptance.
Dismissing a flag is a recorded
decision and asks for a reason.
It is not a close button.
04 · BY DESIGN
What holds for every flag.
Open any closed flag and the whole story is there: the rule that raised it, the records it saw, and who closed it, with their reason.
01
Rules are compiled before they run, so the same data always raises the same flags.
02
Every flag names the rule, agent or person behind it, and when. A flag with no attributable source is not shown.
03 · WHERE A PERSON DECIDES
Closing a flag takes a reason. The decision stays on the trail, with the reviewer’s name on it.
05 · EXAMPLES
Examples from a practice rulebook.
Five rules from a practice rulebook, as the firm wrote them. Each says what it applies to and where it came from.
Two payments to the same payee for the same amount within 7 days, where neither carries an invoice.
Every expense above ₹2,000 needs a tax invoice on file before it can be reconciled.
Payments above ₹50,000 need a purchase order on file and a partner’s sign-off.
Do not claim input credit where the payee has no GSTIN on record for the period.
Kavro Holdings and SR Enterprises are related parties. Every payment to them needs a written purpose.
| RULE | APPLIES TO | WHERE IT CAME FROM |
|---|---|---|
Duplicate payments Two payments to the same payee for the same amount within 7 days, where neither carries an invoice. | LEDGER | Firm template |
Tax invoice required Every expense above ₹2,000 needs a tax invoice on file before it can be reconciled. | LEDGER · FORMS | Firm template |
Approval limit Tuned for this clientPayments above ₹50,000 need a purchase order on file and a partner’s sign-off. | LEDGER | Firm template |
Input credit without GSTIN Do not claim input credit where the payee has no GSTIN on record for the period. | LEDGER · FORMS | Firm template |
Related-party payees Kavro Holdings and SR Enterprises are related parties. Every payment to them needs a written purpose. | LEDGER · STATEMENTS | Written for the client |
Rules run on every upload and re-run across the open period.