v1.8.1 2026-09-06

Adding a client by hand now works

Fixed: adding a client from Clients → New failed on the server. The record needs a portal account attached to it, and this one screen never created one — every other route into the system (checkout, converting a lead) already did.
A client added by hand now gets the same portal account as one who arrived any other way, and can sign in to see their own orders, documents and invoices.
If the phone number or email already belongs to someone, that account is reused rather than a second login being created for the same person.

v1.8.0 2026-09-06

Notifications on a phone or desktop, even when your site is closed

New in Settings: turn on browser notifications. Once on, a small prompt offers each person — your staff and your clients alike — the choice to switch them on for that device.
Nobody is ever subscribed without being asked, and the browser permission prompt only appears after they press Turn on. An unbidden prompt is the most-refused thing on the web, and a refusal is permanent.
Each device is separate: a laptop and a phone subscribe separately, and turning it off on one leaves the other working.
The message is encrypted here and decrypted inside the recipient browser. The push service in the middle carries something it cannot read.
When a browser throws a subscription away, that device is retired and the record kept, so the count on System status stays honest and the person can simply turn it on again.
A push service having a bad afternoon retires nothing. Only a definite "this subscription is gone" does — one outage must not quietly unsubscribe everybody.
Push is an addition, never the only route. Everything important still goes out by email and WhatsApp.
Fixed: the push channel previously reported every send as successful without sending anything. Nothing used it yet, but it would have reported deliveries that never happened the moment anything did.
The signing key is created once and is deliberately not editable afterwards. Replacing it would silently unsubscribe every device already registered against it.

v1.7.0 2026-09-06

Sort any list, and save the views you keep coming back to

Every list now sorts by any column shown. Click a heading to sort, click it again to reverse. The arrow shows which column is in use and which way.
Searching or paging keeps the sort you chose, rather than quietly throwing it away.
New: save a list the way you have set it up, name it, and it is one click away. A view remembers your search text and your sort.
Share a view with the team and everyone who can open that list sees it. This is safe by construction: a saved view is a bookmark, not a key. It carries the query and nothing about who may see what, so when a colleague opens it, it runs as THEM and shows only the records their own role allows.
You can delete your own views, including shared ones. You cannot delete somebody else view — sharing lets colleagues use it, not take it away from everyone.
Sorting is restricted to the columns a list actually shows, checked against a fixed list rather than trusted from the address bar. A column name cannot be a placeholder in a database query the way a value can, so this is the one place where care of that kind is load-bearing.

v1.6.0 2026-09-06

System status — proof that the work running on its own is running

New: System status, under Governance. Most of what this system does for you happens without anyone pressing anything — reminders go out, due dates age into overdue, renewals expire, quotations lapse, SLA deadlines are checked. If that schedule stops, nothing errors and no screen looks broken; reminders simply stop arriving. This page is how you find out, instead of hearing it from a client.
Every scheduled run is now recorded: when it ran, how long it took, what it did. Nine tasks, each with its own rhythm.
A run that starts and never reports back is shown as "did not finish". That is the failure that otherwise leaves no trace at all — recording only the runs that complete would hide exactly the ones you need to see.
Delivery failures in one place: notifications that failed in the last 24 hours, payment webhooks whose signature was rejected, and verified webhooks that were never processed.
Open incidents are worked out fresh every time the page loads and are never stored, so nothing on the board can be out of date.
Acknowledging an incident records that someone has seen it, with a note. It does NOT clear the alert — that happens on its own when the condition stops being true. Nothing on the page can silence a live problem.
A condition that clears and later returns is treated as a new incident, and the earlier acknowledgement does not carry over.
Administrators, managers, ops and auditors can see the board. Only administrators and managers can acknowledge.
Fixed: the outcome of a notification was never recorded — every attempt stayed marked "queued" whatever actually happened, so "how many failed?" was a question the data could not answer.
Fixed: a workflow stage that ran straight past its deadline was never marked as escalated. Only stages in the 80-99% warning band were, so the genuinely late ones — the ones that matter — carried no escalation flag at all. A second stage breaching on the same order was also passing in silence.

v1.5.1 2026-09-06

Search now covers documents and conversations, and can be exported

Documents are searchable: find a file by its title or by the name a client uploaded it under, and land on the order it belongs to.
Conversations are searchable by subject.
A superseded version of a document, and one that has been deleted, never appear in results — only the copy that is currently in force.
Conversations are matched on their subject only, and this is deliberate: some messages on a conversation are internal notes your client must never see, and matching on message text would put that one flag between an internal note and a client typing in a search box.
New: export a results page to CSV, if your role can export reports. It contains exactly the rows on screen, with a link to each, and the export is recorded in the audit log.
Clients cannot export from the portal. A client who wants a copy of their own records asks through the data-request process, which has its own approval and its own clock.
Fixed: the UDIN register CSV was served as plain text rather than as a spreadsheet file. It still downloaded, but the file type was wrong.

v1.5.0 2026-09-06

One search box for the whole practice

Press / from anywhere — or Ctrl+K — and search everything at once: orders, clients, businesses, invoices, quotations, leads, the UDIN register, filings, renewals, payments, services, website pages, blog posts and staff.
Search what you actually have to hand. An order number, part of a client name, a phone number a client just read out, a GSTIN, PAN, CIN, LLPIN, TAN or Udyam number, a UDIN, an SRN or ARN from a filing, an invoice number.
It recognises what you typed. Paste a GSTIN and the business comes first, ahead of anything else that merely mentions the same string; the screen tells you what it thought you were looking for.
It jumps to screens too — type "holiday" and the first result is your holiday calendar.
Arrow keys move, Enter opens, Esc closes. Enter with nothing highlighted opens the full results page, where chips along the top narrow to one kind of record.
Search never widens what anyone is allowed to see. A content or marketing role has no client data, so no client, order or invoice ever appears in their results — those areas are not offered at all.
An external partner CA finds only work routed to them, never your client list. A client in their portal finds only their own orders, businesses and invoices, and cannot ask for records belonging to anyone else — the request is refused on the server, not merely hidden in the page.
Honest about two limits: it searches records rather than the inside of uploaded documents, and it matches text rather than meaning, so "Pvt Ltd" will not find "Private Limited". Type less rather than more.
Every search is recorded in the audit log — the term and how many matches, never the results.

v1.4.0 2026-09-06

Deadlines that count your working hours, not the weekend

Stage deadlines can now be measured in your own working time. A stage that opens at 5pm on Saturday no longer burns most of its target before anyone is at a desk, and no longer breaches by Monday morning without a minute of work having been possible.
New in Settings, "How the SLA clock runs": choose working time or calendar time, tick your working days, and set when the office opens and closes.
The settings screen restates your own stage targets in both units before you save. This matters: 48 business hours is NOT two days — on a nine-hour day it is a little over five working days. It is a real change to the effective deadline, so the screen shows the arithmetic rather than letting you discover it later.
New: a Holiday calendar. Record the days your office is shut and deadlines skip them. Mark a day "note only" instead to record a festival you work through — it appears on the calendar without moving anything.
The calendar ships empty on purpose. Holidays vary by state, by year and by which ones your firm actually closes for, and a wrong holiday quietly moves a real deadline.
Pausing still works the way it did, but better: a stage held over a weekend now costs you no working time, so unblocking it no longer pushes the deadline out for hours nobody could have worked.
Escalation follows the same clock, so the overdue list stops filling up every Monday with work that was never late.
Only an administrator or a manager can change the calendar or the working week — one row here moves every deadline in the firm. Ops and auditors can see it, so they can tell why a date shifted.
Changing any of this never moves a deadline already set. Stages in flight keep the date they were given; the new arithmetic applies from the next stage that starts.
Working time is on by default, Monday to Saturday, 9:30 to 18:30. Switch to calendar time in Settings if you would rather count every hour.

v1.3.0 2026-09-06

The UDIN register

A register for every UDIN your firm issues: the number, what it covered, which member generated it, the client, the business and the order it relates to.
It records a UDIN, it does not generate one. A UDIN comes from ICAI at udin.icai.org, signed in as the member — no software can issue one, and a number invented here would mean nothing to a bank or a regulator.
The number is checked for shape only. Anything that does not look like a UDIN is still saved, and flagged for a second read — never refused, because ICAI owns that format.
A second pair of eyes: a reviewer can mark an entry checked, and a member cannot check their own. The dashboard leads with how many are still unchecked.
Revoke with a reason on the record, and point a superseded entry at the UDIN that replaced it so the chain stays followable. Revoking here does not revoke on the ICAI portal, and the screen says so.
A CA or an external partner sees only the UDINs generated under their own membership. Managers, reviewers and auditors see the whole register.
Every change is kept in an append-only history on the entry, and the register filters by member, client, type and date, and exports to CSV.

v1.2.0 2026-09-06

Your practice details, and a grievance officer who is actually published

New in Settings: your firm details — legal name, CIN, GSTIN, PAN, address, phone, WhatsApp, email and support hours. These print on every GST invoice and appear in your website footer.
New in Settings: your grievance officer and their email, with a warning while it is unset. Naming one is required of an online business under the consumer e-commerce rules and under the data-protection framework.
Fixed: none of the above could be entered at all. They existed only in the sample data, so a new installation had no way to put its own name on its own invoices — while the setup guide told you to set them in Settings.
Fixed: the Grievance Redressal page published the words "[set this in Settings]" to the public, and never showed the officer even once you had one.
A legal page can now carry {{grievance_officer}}, {{firm_legal_name}}, {{firm_email}} and similar placeholders, and they fill in from Settings — in the page text, in the search-result snippet and in the social preview.
Your social links appear in the footer only when you fill them in.

v1.1.0 2026-09-06

Sell your way — packages online, or quote every job

A new Settings choice, "How you sell", decides what the public website does. Catalogue publishes your prices and takes orders online. Indicative publishes prices as a guide but starts every order as an enquiry. Enquiry only publishes no price at all.
Enquiry mode turns the buy buttons into "Request a quote" and CLOSES the online checkout on the server, not just in the page — so the route holds even if someone types the address.
A price you do not publish is also left out of the structured data on the page, so a search result can never show a figure you never quoted.
Government fees stay published in every mode. They are statutory amounts your client owes regardless, and stating them plainly is the point of the fee table.
Switching mode never strands anyone mid-payment: orders already placed, quotations already sent and payment links already issued keep working.
The enquiry route was already here and is now the front door — enquiry to lead, lead to quotation at your own price, online acceptance, then a single-use expiring payment link.
Mobile: the package comparison is now stacked cards on a phone rather than a table that cut the last price in half, the footer collapses into sections, and the consent notice and small print are readable at a normal reading distance.
Fixed: the cookie notice would not dismiss — it stored your choice but stayed on screen.
Fixed: the address, phone, WhatsApp, email and grievance officer of the firm were not appearing anywhere on the public site.

v1.0.0 2026-09-05

First release

A public marketing site with 58 services across 8 categories, a mega menu, category pages, a blog, six free tools and a compliance calendar — all server-rendered so search engines can read it.
Online checkout: pick a package, verify your mobile with an OTP, and pay. Your professional fee, the government fee and GST are always three separate lines.
Government fees come from a dated rules table by state and authorised-capital slab, so a price change never rewrites what an old order was charged.
A configurable workflow engine runs every order through named stages with an SLA clock — and the clock PAUSES while you are waiting on the client.
Document vault with per-service checklists, conditional rules (a foreign director triggers the apostilled passport item), versioning that never overwrites, signed expiring download links and an access log.
Client portal: stage tracker, upload straight from a phone camera, answer expert queries, download certificates, see invoices and every upcoming statutory date.
Expert and partner console with a work queue, a filing log for every SRN and ARN, deliverable upload and an earnings statement. An external partner sees only the orders routed to them.
Compliance calendar built from what each business actually holds — no GSTIN means no GST reminders, no TAN means no TDS reminders.
Renewal register for FSSAI, DSC, trademark and ISO, with reminders before they lapse.
GST invoicing with a gap-free statutory series, the CGST/SGST/IGST split, and pure-agent treatment of government fees.
Lead pipeline, quotations and single-use expiring payment links, for the orders that close on a phone call rather than in a cart.
Data-protection tooling that actually works: a consent log, a data-request queue with the ninety-day clock, retention policies and an append-only audit trail.

Everything included 18

About CA & Business Compliance Services Platform

More from this store

Coaching and Tuition Centre Management Software

Course-selling LMS

Expense Claim & Reimbursement Software

NGO Donor & Fund Management