Skip to content

SYSTEM

Entered once.
Read by everything.

Each sale, purchase and payment is entered once, and everything LZR does reads from that record.

01 · THE LOOP

The same loop under all four.

The agent proposes.
A person decides.
The trail records who.

All four offerings run on the same three steps. Here is one supplier payment going round.

  1. STEP 1

    The agent proposes

    Pay Kavro Facility Services ₹4,06,000

    Matched to work order WO-1182 and the goods receipt

    96% sure

  2. STEP 2

    A person decides

    First payment to a new bank account, so it waits for you.

    The person can approve it or change it.

  3. STEP 3

    The trail records who

    • Proposed, matched on WO-1182
    • Anjali M. approved
    • Paid from HDFC ••4471

Back to step 1. Next time, the agent already knows this account and this approver.

02 · FOUR PARTS

One workspace under all four offerings.

The agents do the reading.
People do the judging.

Every part of LZR is built around that split, whichever offering it serves.

  • AGENTS

    One job per agent.

    A reading agent turns statements, invoices and orders into ledger rows. Separate agents propose a category, a match or an action. None checks its own work.

  • REVIEW QUEUE

    One decision at a time.

    Anything outside your limits, or under 85% confidence, lands in a queue: approve, change, flag or skip, with undo in reach.

  • RULES & FLAGS

    Controls in plain language.

    Write “payments over ₹50,000 need a purchase order”. LZR tries it on the period, then runs it the same way every time.

  • TRAIL & ASK

    A record you can question.

    Every change is recorded against who made it, and nothing is deleted. Ask in plain English; the answer cites the transactions behind it.

03 · THE RULES

The rules every
offering runs by.

  • Nothing goes to your CA without your approval.

    Each month’s verified numbers are shown to you first, then shared with your CA to file.

  • Nothing posts without a rule or a person behind it.

    Agents propose. An entry reaches the books through a rule you’ve approved or a person who accepted it.

  • Nothing is signed by anyone not qualified to sign it.

    Audits, certifications and legal documents are signed by a practising CA, CS or advocate, who bills you.

  • Every number opens to the rows behind it.

    Every proposal shows what it matched on, and every flag names the rule that raised it.

04 · SYSTEM OF RECORD

One graph of the business.

Every event, traced to everything it touched.

Contracts link to their invoices, authorisations, approvals, payments and tax, so the record can answer why something happened.

The record for one supplier

  • Contract: Facility services, Kavro, ₹4,06,000 a month, pay in 30 days. Linked to it:
    • Authorisation: signed by two directors.
    • Tax: TDS ₹8,120, deposited 7 Oct.
    • October invoice: Bill 2041, ₹4,06,000.
      • Approval: Anjali M., 30 Sep.
      • Payment: paid 2 Oct, on time.
    • November invoice: Bill 2047, ₹4,06,000, 12 Nov.
      • Approval: waiting since 12 Nov.
      • Payment: missed, due 14 Nov.

TRACE AN EVENT

Why was Kavro’s November payment missed?

  1. 12 NovBill 2047 arrived and matched the contract.
  2. 12 NovSent to Anjali M., as your matrix requires above ₹2 lakh.
  3. 13 NovNo answer. She was marked away.
  4. 14 NovDue date passed. Now with the alternate approver.

The answer cites the contract, the bill, the approval request and the bank line, so nothing rests on memory.

Who can see what

See your own month on one record.

The entry review reads one month of your bank, invoices, GST and payroll against each other, and maps what agents could run. Free for applicants who qualify.