From Client Intake to Filing-Ready Papers.
One Platform. Every Practice. Every Filing.
Whether you run your firm on TallyPrime, Zoho Books, Xero, or purely via client WhatsApp messages — GUARDIAN unifies your entire firm's operations. Capture leads, automate ledger mapping, host secure client video consultations, and prepare every return ready for filing — with your sign-off before anything is submitted.
See Exactly Where GUARDIAN Fits Into Your Day
Your existing systems stay in place. GUARDIAN connects them, reconciles the data, and prepares every filing — nothing is submitted until your CA signs off.
Engine
Engine
Layer
Oversight
Which best describes your practice?
Choose yours. In Step 2, the problems that apply to you are marked ✓ — and Step 3 shows how GUARDIAN connects to the systems you and your clients already use.
The problems GUARDIAN solves for CA practices
Pick a problem to see what happens today, how GUARDIAN fixes it, and where your CAs stay in control.
Your juniors type the same figures three times — from Tally, into Excel, into the return.
Every month, Sharma Textiles' purchase and sales vouchers sit in Tally at their office. A junior at your firm exports them, copies the figures into your Excel working papers, then types them again into the GST return — and, at year-end, into the ITR. Three copies of the same numbers, for this client and forty others, in the week before the 11th and the 20th.
Sound familiar?
- GST week means late nights spent copying figures
- Review comments that are really typo hunts
- Revised returns caused by a transposed number
- Juniors tempted to paste client figures into a public AI tool to go faster
Why it matters
- Every retyped figure is a chance for an error that can mean a notice, interest or a revised return.
- Senior time goes on checking transcription, not on the client.
- Client confidentiality is yours to protect. ICAI's Code expects it at every stage — a public AI tool makes that hard to show.
Where a person decides: the CA reviews every marked item and approves the return. GUARDIAN never files — your team uploads through the ERI and GST logins it already uses.
How GUARDIAN reads Tally on your client's PC
- Tally stays where it is. It runs on your client's PC, and nothing about how they use it changes.
- A small connector is installed on that PC once. It asks Tally for the period's vouchers — the same export Tally already supports — and sends them to GUARDIAN over an encrypted connection.
- It only connects outwards. No ports are opened on the client's network, and the connector keeps no copy of the data.
- Tally PC switched off? The connector tries again when it's back on, and your dashboard shows that client as waiting.
- Nothing is written back to Tally unless you approve it — and every entry carries a GUARDIAN reference, so a re-run can't post it twice.
What setup involves: your client's office installs the Tally connector once (we guide them) · you share your Excel working-paper template · we map each client's ledgers to it · your CA approves the mapping and tests on a past month before go-live.
What we'd measure in your pilot: hours per GST return, review comments caused by transcription errors, and revised returns filed compared with last year.
For your IT team — how it connects
- The Tally connector sends Tally's standard XML export request on the client's PC and forwards the result over TLS. It is outbound-only and keeps no data at rest.
- Ledger-to-template mapping is stored per client and approved by the CA; an unmapped ledger stops for review.
- PAN and bank account numbers are replaced with tokens before any AI model sees the data; amounts and ledger names stay usable.
- Outputs follow the official ITR JSON schema and GST return formats. Direct filing through a registered ERI and GST Suvidha Provider partner is on our roadmap.
Your juniors spend deadline week chasing clients for documents — on their own phones.
It's 25 July. Mr Mehta still hasn't sent his March bank statement or his Form 16. Your junior has messaged him four times from her own phone, called twice, and saved the photos he did send into a folder on her laptop — alongside a photo of his PAN card.
Sound familiar?
- A "documents pending" list that never seems to shrink
- The same client asked for the same statement three times
- Client photos saved from personal WhatsApp into personal folders
- Nobody else can pick up the chase when that junior is away
Why it matters
- Returns wait on documents, so the work bunches into the last week before every deadline.
- Chasing is paid staff time that produces nothing billable.
- Client identity documents on personal phones are hard to defend under ICAI's confidentiality duty and the DPDP Act.
Where a person decides: replies that aren't a document — a question, a complaint, a request for more time — go straight to a person with the conversation attached. After a set number of reminders, the chase passes to your staff.
What setup involves: you share your document checklist for each service (ITR, GST, audit) · your WhatsApp Business number is connected · you approve the reminder wording and how often it goes out · your team tests with a few real clients before go-live.
What we'd measure in your pilot: days from period end to "documents complete", chasing calls per client, and returns delayed by missing documents.
For your IT team — how it connects
- Reminders use pre-approved WhatsApp templates outside the 24-hour messaging window.
- Documents are read inside GUARDIAN's privacy layer; identity numbers are tokenised and originals stored encrypted.
- Password-protected PDFs: the client is asked for the password separately, and it is never stored with the file.
Every month, someone matches GSTR-2B against the purchase register by hand.
Reddy Agro Traders' August GSTR-2B is available on 14 September. Your team exports their purchase register, puts both into Excel and matches 380 invoices by hand. Suppliers type invoice numbers differently, so half the "mismatches" aren't real — and the real ones are found on the 19th, the day before the return is due.
Sound familiar?
- Two spreadsheets side by side, matched line by line
- "PB/457" and "PB-0457" flagged as different invoices
- Unfiled suppliers discovered the day before GSTR-3B
- Clients surprised later by credit that has to be reversed
Why it matters
- Credit claimed on invoices your client's supplier hasn't reported can be reversed later, with interest.
- Credit that isn't followed up can be lost — and your client's working capital with it.
- The matching is mechanical; the judgement about what to claim is the part that needs a CA.
Where a person decides: what to claim is always the CA's decision. Near-matches (an invoice number typed differently) are shown as "probable", for a person to confirm — never matched silently.
What setup involves: you choose the clients to start with · we connect their Tally or Zoho books · you set how close is "close enough" for amounts and dates · your CA tests on a past month before go-live.
What we'd measure in your pilot: hours per reconciliation, differences found before filing vs after, and credit reversed later compared with last year.
For your IT team — how it connects
- Matching uses supplier GSTIN, normalised invoice number, date and tax amount, with tolerances set by your firm.
- GSTR-2B is read from the official JSON download; when the GSP route is added, it will need the taxpayer's OTP consent on the GST portal.
- Every decision on a difference is logged with who made it.
Every July, your team types hundreds of returns from WhatsApp photos.
Priya, a schoolteacher, WhatsApps her Form 16, two bank interest certificates and her insurance receipt — as eight photos, over three days. Your assistant saves each one, types every figure into your tax software and checks it against her Annual Information Statement. Priya is one of 300 clients this July.
Sound familiar?
- Queues of clients in the last three weeks of July
- Figures typed from photos, one field at a time
- Income the AIS shows but the client forgot to mention
- PAN and Aadhaar photos sitting in a personal chat history
Why it matters
- Data entry takes most of the time — and it all lands in the same few weeks.
- A missed income line can mean a notice for your client and a revised return for you.
- Identity documents on a personal phone are hard to protect and hard to account for.
Where a person decides: the preparer approves every figure before the return is prepared, and uploads it through their own e-filing login. Income that appears in the AIS but not in Priya's documents is flagged — never silently added or dropped.
What setup involves: your WhatsApp Business number is connected · you share your intake questions and document checklist · your preparer tests on last year's returns before go-live.
What we'd measure in your pilot: minutes per return, returns completed per week in July, and returns revised after filing.
For your IT team — how it connects
- Consent and a privacy notice are captured at the start of each conversation and logged.
- Document reading runs inside the privacy layer; PAN, Aadhaar and account numbers are tokenised before any AI model sees them.
- Returns are generated against the Income Tax Department's published JSON schema for the relevant form and year.
Your clients hear from you at filing time — and problems that cost them money wait until year-end.
Your firm files Sharma Textiles' GST returns every month, so you already see its purchase register and GSTR-2B. Yet the owner mostly hears from you when something is due. He learns about credit at risk or an overdue supplier bill at year-end — when it's too late to fix, and your fee is the first thing he questions.
Sound familiar?
- Clients who see you as the person who files returns
- Revenue that peaks around deadlines and dips in between
- Year-end surprises you could have warned about
- Fee negotiations every year
Why it matters
- You already reconcile the data — it isn't being turned into advice.
- Problems found in time save clients money, which is what they remember when fees come up.
- A monthly service evens out your revenue across the year.
Where a person decides: every client-facing note is approved by a partner before it goes out. Nothing is sent to a client automatically.
What goes into the monthly note
- GST credit at risk: suppliers who haven't filed, and how much credit depends on them.
- Micro and small supplier bills: unpaid bills approaching the payment deadline that protects this year's deduction.
- Anything else you choose to add — cash position, upcoming deadlines, your own advice.
- Nothing to report? A short "all clear", or no note at all — your choice, per client.
What setup involves: you pick the clients to offer it to · you choose what the note covers and how it reads · your partners review a few sample notes before any go to clients.
What we'd measure in your pilot: clients who take up the service, notes sent per month, and client retention compared with last year.
For your IT team — how it connects
- The note is assembled from the outputs of the GST reconciliation and supplier-payment workflows; no new data source is needed.
- Notes are held for partner approval in the Multi-Consensus Gate, and delivery is logged.
Unpaid bills to micro and small suppliers surface at audit — too late to save this year's deduction.
It's February. Sharma Textiles owes ₹4.2 lakh to two Udyam-registered micro suppliers. The goods were accepted 38 days ago and there's no written agreement, so the 15-day limit has passed. If those bills aren't paid by 31 March, Sharma can't deduct that expense this year. Today, nobody notices until the audit in September.
Sound familiar?
- Overdue micro-supplier bills found at audit
- Supplier MSME status kept nowhere, or in someone's head
- Clients asking why nobody warned them
- The same conversation, every year
Why it matters
- The rule is strict: pay a micro or small supplier later than 15 days (or the agreed period, 45 days at most) and the expense is deductible only when paid.
- It's Section 43B(h) of the 1961 Act, carried into Section 37(2)(g) of the Income-tax Act, 2025.
- A warning in February is worth more than an explanation in September.
Where a person decides: which suppliers count is confirmed by your CA, not guessed by GUARDIAN. Every client message is approved before it's sent.
How GUARDIAN knows which suppliers count
- Your CA marks the suppliers once — micro, small, medium or not registered — from their Udyam details, and notes any written payment terms.
- Medium enterprises and traders are left out, as the rule excludes them.
- Acceptance date: taken from goods-receipt records where the client keeps them; otherwise the bill date is used and clearly marked as an assumption.
- The list is reviewed once a year, or whenever a supplier's status changes.
What setup involves: your CA marks each client's micro and small suppliers once · we connect the client's books (Tally or Zoho) · you choose when alerts go out · you test on last year's bills before go-live.
What we'd measure in your pilot: overdue micro/small supplier bills still unpaid at 31 March, compared with last year.
For your IT team — how it connects
- Supplier MSE classification and agreement terms are stored as confirmed by the CA; they are never inferred by the AI.
- Payment status comes from the books on each sync; partial payments are handled bill by bill.
Bank statements are matched to vouchers line by line, and month-end waits.
Lakshmi Hardware emails a 14-page bank statement each month. A junior goes through every line, finds the matching invoice or bill in Tally, and posts the receipts and bank charges the client never recorded — most of a day for one client, before any GST work can start.
Sound familiar?
- Statements worked through line by line
- Receipts that pay three invoices at once
- Bank charges and interest the client never recorded
- Unexplained balances carried forward
Why it matters
- Everything downstream waits — GST, management accounts, advice.
- It's hours of matching for minutes of judgement.
- Posting errors spread into every report built on the ledger.
Where a person decides: nothing is posted without approval. A match GUARDIAN isn't sure of — or an amount it couldn't read clearly — is never auto-matched.
What setup involves: you pick the clients to start with · we connect their books and learn their bank's statement layout · you set matching tolerances · your team tests on a past month before go-live.
What we'd measure in your pilot: hours per reconciliation, unreconciled items carried forward, and posting corrections.
For your IT team — how it connects
- Account numbers are tokenised; amounts read with low confidence are never auto-matched.
- Approved entries are written back through the Tally connector or the Zoho API, each carrying a GUARDIAN reference.
Every year, AOC-4 and MGT-7 are assembled from scattered records.
Anand Precision Pvt Ltd holds its AGM in September. Your team then pulls figures from the approved accounts, asks the client again for shareholding and director details, and keys everything into the AOC-4 and MGT-7 web forms — with the 30-day and 60-day deadlines running.
Sound familiar?
- The same director details requested every year
- Figures re-keyed from the accounts into web forms
- Resubmissions after a small error
- Additional fees when a deadline slips
Why it matters
- The work is assembly, not judgement — but it still needs a CA or CS to check it.
- There's no way to file automatically: MCA forms are web forms signed with your DSC.
Where a person decides: a professional checks every field, and your team files and signs on the MCA portal. MCA has no filing API, so this step always stays with you.
What setup involves: you share the client list and last year's filings · we set up the checklist per form · your CS reviews a sample pack before go-live.
What we'd measure in your pilot: hours per filing and resubmissions compared with last year.
For your IT team — how it connects
- MCA21 V3 forms are web-based and signed with the filer's DSC; there is no third-party filing API, so GUARDIAN prepares data only.
How GUARDIAN connects to your systems
Three Systems. Zero Automation Between Them. GUARDIAN Bridges All Three.
Pick a Template. Connect It. Teach It Your Rules.
Every problem on this page comes as a designed workflow template for CA firms and accountancy practices, set up with you in a pilot. You do not start from a blank page: choose one, give it your name, connect your systems and upload your own rules. Your team approves every important step.
- ChoosePick a template for your problem
- RenameGive it your own name
- ConnectLink your systems through NEXUS
- Set the startA new record, a file, a message or a time
- TeachUpload your rules, letters and FAQs to its expert
- TestRun it on your past cases
- ShadowIt runs on real work; your team checks every step
- LiveSteps go automatic only once your team agrees they are right
Every template has its own expert: the SME Agent
Each workflow step can ask its SME Agent (subject-matter expert) a question, such as "which documents does our policy accept here?". It answers from your material only, and always shows where the answer came from.
If it is not sure, it says so, and the step waits for your team. A step moves on by itself only when the rules are met and the confidence is high enough. Important decisions always go to a person.
- Current rulesRegulations and deadlines, kept up to date by Guideazy, with the date each rule starts
- Your policiesYour SOPs, limits and ways of working
- Your letters and formsThe wording and formats you already use
- Your historyPast tickets, customers and orders, read from your systems with personal details hidden
- Your team's decisionsWhat your approvers agreed or changed, so it learns your way
- Nothing sharedEach customer's expert is separate. The AI works on tokenised data, not real names or numbers.
Tally to Working Papers and Returns
Reads a client's Tally vouchers each month, fills your own Excel working papers using the ledger mapping your CA approved, marks anything unmapped, and prepares GST return data and the ITR JSON for your sign-off. You file through your usual logins.
What it needs
- Connects to
- Tally (NEXUS Local Agent), Firm working-paper template (Excel)
- Your team approves
- CA (reviewer), Partner
- Its expert learns from
- Your working-paper template(s) with a short note on each section, Your ledger grouping rules (what goes where), Last year's completed working papers and financial statements for 2–3 clients and 1 more
Client Document Chasing
Knows what each client still owes for each service and period, reminds them on your WhatsApp Business number or by email, reads and files what arrives, and hands any reply that needs a person to your staff.
What it needs
- Connects to
- Engagement checklists, WhatsApp Business Platform (via BSP)
- Your team approves
- Assigned staff member, Manager
- Its expert learns from
- Your document checklist for each service (ITR, GST, audit, MTD, bookkeeping), How you want clients addressed; tone, Answers to questions clients often ask while sending documents
GSTR-2B and IMS Reconciliation
Pairs each month's GSTR-2B with the purchase register, sorts every difference, proposes an IMS action per supplier invoice for your CA to decide, and prepares a supplier-wise list of credit at risk for the client.
What it needs
- Connects to
- GSTR-2B JSON (file drop), Purchase register (Tally agent / Zoho API)
- Your team approves
- CA, Partner
- Its expert learns from
- Your GST reconciliation SOP, Rules for which invoices you accept, reject or keep pending, Client-facing message wording for supplier follow-up
- Where there is no API
- GUARDIAN prepares the work; your team completes that step by hand, and it is recorded.
Individual ITR from WhatsApp
Runs individual return intake on your WhatsApp number: consent, questions, documents, a draft computation compared with the AIS, and — after your preparer approves every figure — the ITR JSON ready for upload.
What it needs
- Connects to
- WhatsApp Business Platform, AIS (uploaded by preparer)
- Your team approves
- Preparer / CA
- Its expert learns from
- Your intake questions, Your document checklist per income type, Your fee note and engagement terms (optional) and 1 more
Micro and Small Supplier Payment Alerts
Watches unpaid bills to suppliers your CA has confirmed as Udyam-registered micro or small, works out each legal payment deadline, and alerts your CA in time to keep the client's deduction.
What it needs
- Connects to
- Books (Tally agent / Zoho API), Supplier classification (CA input)
- Your team approves
- CA
- Its expert learns from
- Your note on how you classify suppliers, Client-facing wording for payment alerts
Bank Statement and Feed Matching
Reads bank statements or bank feeds, proposes a match or entry for each line, asks clients about unknown payments on WhatsApp, and posts only approved entries — never twice.
What it needs
- Connects to
- Bank statements (email / upload), Xero / QuickBooks / Sage bank feed, Books (Tally agent / Zoho / cloud ledger)
- Your team approves
- Staff / bookkeeper
- Its expert learns from
- Your posting rules for recurring items (charges, rent, loan EMIs), Chart-of-accounts notes per client
MCA Annual Filing Pack
From the AGM date, tracks AOC-4 and MGT-7 deadlines and assembles each form's data pack from the approved accounts and company record for your CA or CS to check. You file on MCA21 V3 with your DSC.
What it needs
- Connects to
- Approved financial statements (TAX-IN-TALLY-01), Company record
- Your team approves
- CA / CS
- Its expert learns from
- Last year's filed AOC-4 and MGT-7 for the client, Your MCA filing checklist
MTD Income Tax Quarterly Update Preparation
Checks every MTD client three weeks before each deadline, builds year-to-date totals by HMRC category from Xero, QuickBooks or Sage, flags gaps, and holds each update for your approval. Submission stays with the client's HMRC-recognised software.
What it needs
- Connects to
- Xero / QuickBooks / Sage (OAuth2), MTD client list
- Your team approves
- Accountant, Manager
- Its expert learns from
- Your category mapping notes and client-specific rules, Your MTD client communication templates, FAQs clients ask about MTD
AML Client Onboarding
Collects identity, address and ownership documents from new clients, runs the ID check through the provider you choose, drafts the risk assessment with your method, and waits for your MLRO's sign-off.
What it needs
- Connects to
- Onboarding form (webhook), WhatsApp / email, ID verification provider (API)
- Your team approves
- MLRO, Partner
- Its expert learns from
- Your firm-wide AML risk assessment, Your client risk-assessment method and form, Your CDD policy and document list
VAT Pre-Submission Check
At each VAT period end, runs your checks on VAT-coded transactions and flags what looks wrong for your accountant to resolve before the return is submitted from the client's software.
What it needs
- Connects to
- Xero / QuickBooks / Sage
- Your team approves
- Accountant
- Its expert learns from
- Your VAT review checklist, Client-specific VAT notes (partial exemption, schemes)
Monthly Client Review Note
Turns the month's findings from your GST, supplier-payment, MTD and VAT workflows into a short client note — action, deadline, money at stake — for a partner to approve before it is sent.
What it needs
- Connects to
- Other template instances
- Your team approves
- Partner
- Its expert learns from
- Two or three example notes in your firm's voice, Topics you want included or excluded
Client Data Requests and One-Click Erasure
Verifies the requester, lists the personal data held, applies your retention rules with Open Policy Agent, and after DPO and CISO approval erases the person's data in GUARDIAN by destroying their master key — keeping what the law requires under a legal hold.
What it needs
- Connects to
- Request channels
- Your team approves
- DPO / privacy lead, CISO / IT lead
- Its expert learns from
- Your privacy notice, Your retention schedule, Your request-handling procedure
12 templates. Each one is fully designed and documented for our engineering team. We set it up with you in a pilot, and it starts in shadow mode before any step runs on its own. Some steps, like final approvals, never run on their own.
We've Heard Every Objection. Here's the Real Answer.
Accountants are the most risk-averse professionals on earth. That's not a problem — it's a design requirement. GUARDIAN is built to address every concern at the architecture level, not by asking you to trust a policy document.
How the 4 Pillars Work Together — Tax & Accounting
AI Never Files a Return. Your Team Always Does.
ICAI Code of Ethics (India) and ICAEW/ACCA Code of Ethics (UK) both place professional judgment squarely with the accountant, not the system. GUARDIAN's Multi-Consensus Gate is built to keep it that way — by design, not by policy.
Three Deployment Models — Your Infrastructure, Your Choice
- No IT infrastructure investment — start with the problem that costs you most
- Secure partitioned data space per firm
- NEXUS connectors configured via encrypted dashboard
- Grows with your client list — no per-filing charges
- Audit trail of every sign-off included
- Dedicated GUARDIAN instance inside your private cloud
- NEXUS runs behind your corporate firewall
- Client data stays in infrastructure you control
- White-label, custom SLA, dedicated engineering
- Full compliance documentation kit (ICAI · ICAEW · GDPR · DPDP)
- Full client intake pipeline via WhatsApp Business API
- Document collection, KYC, approvals — all in WhatsApp
- No website or IT team required to go live
- Built for the DPDP Act and UK GDPR from day one
- India Type D + UK Type D use-case — identical deployment
Plans for Every Accounting Practice
All plans include unlimited staff seats, NEXUS data connectors, Multi-Consensus HITL gates, and a design built around ICAI and ICAEW confidentiality duties. No per-filing charges.
- NEXUS: TallyPrime connector (small on-site connector)
- NEXUS: Zoho Books webhook integration
- NEXUS: filing-ready ITR, GST & MCA outputs
- NEXUS: WhatsApp Business API (client intake)
- 2,000 AI Tasks/month · 5 GB Knowledgebase (KB) Cap
- Unlimited staff seats
- GSTR-2B vs purchase-register matching
- MSME payment deadline alerts · GST credit-at-risk list
- Multi-Consensus HITL gate (patent-pending GB2615329.6)
- Built for the DPDP Act — 1-click deletion
- Data Privacy Shield — FPE tokenisation (NIST SP 800-38G)
- NEXUS: Xero OAuth2 live webhook connector
- NEXUS: Sage / QuickBooks API integration
- MTD quarterly update preparation
- Companies House accounts preparation
- NEXUS: WhatsApp Business API (client intake / AML)
- 2,000 AI Tasks/month · 5 GB Knowledgebase (KB) Cap
- Unlimited staff seats
- MTD update preparation · VAT pre-submission checks
- AML document collection and ID checks (MLR 2017)
- Multi-Consensus HITL gate (patent-pending GB2615329.6)
- Built for UK GDPR — 1-click deletion
- Sovereign node inside your firm's private cloud
- Custom AI Task volume & storage
- Unlimited seats + white-label
- Multi-jurisdiction: India and UK together
- Big 4 / Top 20 audit network SLA
- Documentation pack for ICAI / ICAEW reviews
- Dedicated engineering support team
- Documentation for UK GDPR and DPDP Act reviews
- Dedicated integration team (HMRC, ITD ERI, GST GSP)
What a pilot looks like
You don't have to change your whole practice at once. Start with one problem and a few clients, prove it on real work, then decide.
Cut Manual Entry. Keep Every Decision. Win Back Your Day.
14-day free trial. We configure your NEXUS connectors — Tally, Zoho, Xero or QuickBooks — and your first workflow with you. No coding, no commitment. Connecting a client's Tally needs a small connector on their PC.
Built for UK GDPR, the DPDP Act and ICAI / ICAEW confidentiality duties. The AI cannot file a return — every output needs a human sign-off.