LZR
Ask your CA about LZR

Some of what it costs you never reaches your books.

LZR checks your bank, invoices, GST and payroll against each other and catches it before your return locks.

Ask your CA about LZRTell us who keeps your books
NEEDS ATTENTION
₹40,000 missed invoice
Bank shows a transaction with no invoice, costing ₹7,200 in tax credits
EVERYTHING INSIDE THE BAND AGREES
FIG. 01THE FIELD
1,284 LINES · JUN 2025
4
NEED ATTENTION
11
WORTH A SECOND LOOK
1,269
AGREE
WHAT YOUR ACCOUNTANT SEES
Item 1 of 11
FLAGGED
25 JUN 2025 · HDFC ••4471
Wire transfer to ACME Holdings
–₹4,500
No payee record · reference ACMEH/2506/22
POSSIBLE DUPLICATE
Same payee and amount as an entry 5 days earlier. Neither has an invoice attached.
THIS
Jun 25
Wire transfer
–₹4,500
MATCH
Jun 20
Unknown wire
–₹4,500
Differs by: date, reference
Compare in full
TREATMENT
Category
Not set — choose one
Agent suggestsProfessional Fees· 61%
EVIDENCE
No document attached
Required for payments over ₹2,000
Ask client
TRAIL
Flagged by rule · 2 events
Merge into Jun 20
Keep both
01 · THE PROBLEM

You find out what June looked like in August. By then the duplicate is a write-off and the 2B mismatch is a lapsed credit.

Days between period end and books you can act on.

MEASURED AGAINST YOUR OWN LAST FOUR PERIODS

Anomalies caught before close rather than after.

COUNTED PER CLIENT FROM THE FIRST PERIOD
JUNE · IT HAPPENS
AUGUST · YOU SEE IT
02 · HOW IT WORKS

Three steps, and a person stands in the middle of the second one.

STEP ONE
The agent proposes

Bank statements, invoices, GST returns, TDS records and payroll arrive. Each entry gets a proposed category, a confidence figure, and the reasoning that produced it.

STEP TWO
A person decides

Approve, change, or flag. Nothing posts to the books on the agent's word alone, and the reviewer can disagree with it.

STEP THREE
The trail records who

Every entry carries the person, the rule, or the agent that set it, and the time it happened. The trail is readable later without reconstruction.

THE FLAG ITSELF

A flag states what was observed, names the rule that raised it, and offers exclusive outcomes.

Dismissing a flag is a recorded decision and asks for a reason. It is not a close button. Violet appears here and nowhere else in the product: it means a person needs to look at this. Red is kept for the system failing, never for your money.

REASON
A fixed reason code, not free text.
CLAIM
One or two lines stating what was observed, never what to do about it.
EVIDENCE
The two records side by side (invoice against bank line, books against GSTR-2B) and the fields they differ on.
SOURCE
Which rule, agent, or person raised it, and when. A flag with no attributable source is not shown.
RESOLVE
Two or three mutually exclusive outcomes, one of which is acceptance.
03 · WHAT A FLAG IS
Six shapes. Every flag is one of them.

A flag is not a tidiness note. It is two documents disagreeing about money that already moved or money that never arrived.

WHAT IT READS
BANK & LEDGERS
Bank statements · Purchase and sales invoices · Creditors · Debtors
GST
GSTR-1 · GSTR-3B · GSTR-2B
TDS & PAYROLL
Form 16A · Form 26AS · Salary slips · PF
01
ABSENCE
Books × GSTR-2B

A ₹40,000 purchase sits in your books. Your supplier never filed it, so it isn't in your GSTR-2B. That's ₹7,200 of input credit you cannot claim.

Nothing in your own records looks wrong. The gap exists only between two documents and it repeats every month.

02
HISTORY
Bank × Creditors

First payment ever to this account. ₹85,000, and the creditors ledger has no prior history with this vendor. It gets a second look before it clears, not after.

Changed bank details on a familiar invoice is how most of this money leaves. The stakes are theft, not tidiness.

03
COMPARISON
Invoice × Bank

The same vendor invoice is booked twice in creditors and paid twice from the bank, in the same week. Flagged before the second one clears, not found three months later.

Recoverable at the bank this week. A credit note you chase for a quarter after that.

04
THRESHOLD
Invoice × GSTR-1

An invoice crosses the e-invoice limit, and your filed GSTR-1 has no e-invoice against it. That's a compliance gap, not a line item.

Missed, it becomes a notice. Nobody runs a query to find this one and it looks correct until someone asks.

05
DISTRIBUTION
Invoice × History

This vendor's bill is usually ₹12,000 a month. This month it's ₹38,000, no explanation. Flagged, not paid on autopilot.

A question asked before the payment goes out, while the vendor still has to answer it.

06
CONFLICT
26AS × Debtors

Form 26AS shows ₹1,20,000 of TDS credited against you. Your debtors ledger accounts for ₹96,000 of it. The ₹24,000 flagged before the return is filed.

Either revenue you never invoiced or credit you're about to forfeit. No reconciliation run surfaces this on its own.

ON EVERY ONE

A flag is a proposal, not an action. Nothing is paid, held, or filed because LZR said so — your accountant approves it, changes it, or rejects it, and the ledger records who decided. The same six shapes run across every other pair: GSTR-1 against 3B, salary slips and PF against the bank, Form 16A against the TDS you have already claimed.

04 · WHAT IT DOES NOT DO

The limits are the product. Four of them are worth stating before anything else.

It does not file anything and it does not sign anything.

Filing and sign-off stay where they already are, with the firm and the person qualified to do them. LZR prepares and evidences the review that comes before that.

It does not post an entry nobody accepted.

A proposal at 99% confidence and a proposal at 40% are both proposals. Neither reaches the books until a reviewer accepts it.

It does not overwrite a correction.

When a reviewer changes a category, the agent does not change it back on the next run. The correction becomes the rule for that payee.

It does not ask you to trust a number you cannot open.

Every proposal shows what it matched on. Every flag names the rule that raised it. A conclusion with no visible reasoning behind it is not shown at all.

ANSWER PENDING
Which ledger it reads from and writes back to.

This is the first question every firm asks and the page cannot answer it yet. The confirmed list of supported ledgers goes here before launch. A firm reading a vague answer to this question will assume the answer is no.

05 · WHAT YOU GET

Four things that change for you.

01

Speed to close

Days between the end of a period and books you can make a decision on.

MEASURED AGAINST YOUR OWN LAST FOUR PERIODS
02

Visibility

Categorised, current numbers instead of a three-month-old summary, without emailing your accountant to ask where things stand.

READ-ONLY VIEW, ENABLED BY YOUR CA
03

Money caught before it settles

The six shapes above (read across bank statements, invoices, GSTR-1, 2B and 3B, Form 16A and 26AS, payroll, creditors and debtors) surface while the period is open and the money is still recoverable.

COUNTED PER CLIENT FROM THE FIRST PERIOD
04

No added headcount

The review happens inside your accountant's practice. You do not hire an internal finance person to get any of the above.

THE REVIEW SITS INSIDE YOUR CA'S PRACTICE

Send this page to whoever keeps your books.

LZR reaches a business through its accounting practice. If yours already uses it, ask to be shown the ledger view for your own last period. If they don't, the button below writes the message for you.

Ask your CA about LZRTell us who keeps your books

Neither button creates an account. There is no self-serve signup, because there is no way for a business to buy LZR on its own.