Finance
General ledger, receivables and payables, bank reconciliation, finance books per unit and year, and posting rules an accountant can read.
Ledger · Vouchers · Reconciliation
The Tathven ERP home screen — open Inventory, Production, Sales, Payroll and the rest from one place, each writing to the same authoritative record.
Begin a record. Open a module.
Select to enterTathven ERP gives Indian businesses a single, authoritative record of finance, inventory, sales, purchase, production and GST. Every module writes to the same record. Post a sale and the stock, the ledger and the GST return move together.
General ledger, receivables and payables, bank reconciliation, finance books per unit and year, and posting rules an accountant can read.
Multi-unit, multi-department stock with every movement documented — the count on screen is the count on the shelf.
Quotations to orders to dispatch and invoice, with per-channel pipelines and outstanding tracked against every customer.
Purchase orders, supplier mapping and goods receipts that carry the vendor's bill — the payable is what you were actually charged.
Bills of material to production orders to job orders, costed at every step, received back into stock.
Tickets with a lifecycle, an owner and an SLA clock, raised against the same customer you invoice.
One master for everyone you trade with, and Indian tax built into the model rather than added on top.
Customers, suppliers and agents in one master with one code — so a name is never spelled two ways in two modules.
HSN catalogue, place of supply resolved from the two GSTINs, and return sheets prepared from the transactions you posted.
Subscriptions and distribution, multi-channel sales, the government e-Marketplace connector, and publishing configured as the trade's own workflow.
A permission in Tathven is not a checkbox that hides a menu. It is one named operation, granted at one of four levels, checked by the server on every request. Around sixty of them ship across the modules.
The operation does not exist for this user.
See the screen and its records. Nothing more.
Create and change, within the module's own rules.
Act on it — post, approve, run the process.
Permissions are enforced at the server, not just hidden in the interface. The same declaration that removes a button refuses the request behind it. A scoped identity with no grant is refused by default.
Not your rows in a shared table. Each customer gets its own databases with its own credentials, minted when the tenant is provisioned. The tenant is resolved before any user is identified, and there is no fallback to a default database.
Passwords hashed with PBKDF2-SHA256, salted, over 210,000 iterations. Stored SMTP and SMS credentials encrypted with AES-256-GCM, the key held outside the database. Machine secrets are shown once and stored only as a digest — we cannot recover one, only replace it.
A scoped identity can never exceed the rights of the person who sponsors it. The clamp is applied when rights are written, and re-applied if the identity moves to a different sponsor.
People are deactivated, never deleted, and keys are revoked, never removed. Every business write carries who made it, so a row written years ago still resolves to a name.
Deactivating a person ends their sign-in, invalidates their access keys and drops their live sessions within about a minute — while every row they wrote still carries their name. Deactivating a sponsor cascades to the identities beneath them.
Tathven routes a document to approvers by its value. A ₹40,000 purchase order takes one signature; the same order at ₹4,00,000 takes two, in sequence, each within its own deadline. The bands are yours to set, per document type.
Checked server-side, not in the interface — which is where most systems are weaker than they sound.
Escalation is visibility, not surrender. A missed deadline notifies the pending approver and makes the request visible to the level above. It never auto-approves and it never transfers authority.
Banded approvals govern purchasing, stock and production documents, and are switched on per document type — deliberately, so a new authority schedule can be written and reviewed before it takes effect.
Matches level 2. One request opens, needing both levels in sequence. The header moves to waiting — stock does not move yet.
Recorded with the band that matched. The clock resets to 12 hours for the next level.
Acting out of turn is rejected at the server, whoever is signed in.
The request completes, the header consolidates to approved, and stock is received exactly once.
Corrections are recorded, not overwritten. Requests, approvals, rejections, delegations, escalations and missed deadlines all append to a log with no update or delete path.
Tell us what you run today. We will show Tathven ERP working on a sample of your own data, then send a written scope and quotation — not a brochure.