Unlimited companies, one login
Run every firm you own — or every client you serve — from a single account, with complete data isolation enforced at the database level rather than in application filters.
Most accounting products treat a second business as a second customer — a fresh subscription, a fresh login, a fresh place to forget a deadline. Finkitaabh assumes you run more than one, or that your clients do.
एक login, कई कंपनियाँ।
If you run one simple company, almost anything works. The pressure appears when reality gets more Indian: a second firm under the same promoter, a distribution arm that needs batch and expiry tracking, a partnership that files separately, or a practice where every new client is another billable organisation on somebody's subscription.
Finkitaabh is multi-tenant from the database up. Companies are isolated by PostgreSQL row-level security — enabled and forced at the table level, not filtered in application code — so adding one is an operation inside your account, not a purchase. Switching between them is a menu, and the walls between their books are enforced by the database itself.
The compliance surface travels with every company you add: GSTR-1, 3B and the GSTR-9 annual return from posted books, E-Way Bill Part A created automatically above ₹50,000 with validity and multi-leg tracking, per-transaction ITC-eligibility control so section 17(5) blocked credits are expensed rather than wrongly claimed, and statutory document titles chosen automatically — Tax Invoice, Bill of Supply, or a plain commercial invoice — from your registration status and the taxability of each line.
Isolation where it matters, one place to work from.
Run every firm you own — or every client you serve — from a single account, with complete data isolation enforced at the database level rather than in application filters.
Eight roles — owner, manager, accountant, assistant, store keeper, practitioner, read-only accountant and auditor — across 50 granular permissions, so counter staff can bill without seeing margins or fee contracts.
Batch numbers, expiry dates and first-expiry-first-out consumption, with near-expiry and expired-stock alerts. Not a separate inventory plan.
Part A auto-created above ₹50,000, with validity countdown, extensions and multi-leg movement tracking on a dashboard that warns you before a bill lapses.
Tax Invoice vs Bill of Supply vs commercial invoice picked automatically per registration status, scheme and line taxability — including Rule 46A mixed supplies.
Client engagements with confidential fee contracts, government-fee disbursements booked as recoverable, and Rule 33 compliant fee-plus-reimbursement invoices.
What multiplies when you add a business — and what shouldn't.
| The job | The usual wayHow it tends to go | On FinkitaabhCloud + AI |
|---|---|---|
| Adding the third company | A third subscription, priced again from the top | An operation in your account; plans differ by how many are included |
| Switching between them | Log out, log in, remember which is which | A menu, with the active company always on screen |
| Keeping their books apart | Separate accounts, and trust that nobody crosses over | PostgreSQL row-level security, enabled and forced per table |
| Staff who work across two firms | A user seat bought twice | One person, roles assigned per company |
| Filing season across all of them | Each system exported and reconciled on its own | GSTR-1, 3B and 9 generated per company from posted books |
| Inventory depth for the trading arm | Usually a paid upgrade or a separate module | Batch, expiry, FEFO and stock alerts included |
“The usual way” describes common manual and desktop-era workflows we see in Indian businesses — not any particular product. Every Finkitaabh claim is a capability shipped today.
No. Finkitaabh is multi-tenant — several companies run under one login with complete isolation between them, enforced by PostgreSQL row-level security. Plans differ in how many companies and users they include rather than charging a fresh subscription per organisation.
Separation is enforced by the database, not by application code: row-level security is enabled and forced per company, and identifiers are type-safe so a company ID can never be used where a party ID is expected. Every action is written to an append-only audit log.
No. Real-time stock with weighted-average valuation, batch and expiry tracking with FEFO, low-stock and near-expiry alerts, bulk Excel import and bulk price updates are part of the product.
Yes. GSTR-1, GSTR-3B and the GSTR-9 annual return are all generated from your posted books, with the annual return consolidating the full year.
Yes — RCM is handled automatically for supplier-liable GST, and the composition scheme is supported, including choosing the correct document title for composition dealers.
A 30-minute personalised walkthrough with our product specialist — in Hindi or English, whatever you're comfortable with. We'll set up a sample company that looks like your business.