Planned
Invoicing on live documents
Invoices raised from the same dispatch and delivery data your operations team already works in, rather than re-keyed at month end.
Loading...
Loading...
Pradrava Product • In development
The books and the GST returns, inside Pradrava rather than beside it. This is where filing belongs — the parts of a return Fluids deliberately stops short of: the GSTN file itself, the B2C, export and HSN-summary sections, and 2B matching against your input credit. It is being built on the same separation, permissions and record-keeping foundation as Fluids — and it is not available yet. Here is exactly where it stands.
Everything below describes what Accounting is being built to do. None of it is available today. We would rather say that plainly than let you plan around it. If you need finance functionality now, the section that follows lists what is live in Fluids.
Available today
Fluids is designed to sit alongside your existing accounts package, not to hold your operations hostage until we finish ours.
In development
Invoices raised from the same dispatch and delivery data your operations team already works in, rather than re-keyed at month end.
Customer receipts, vendor payments and running balances against the ledgers Fluids already maintains.
Profit and loss, balance sheet and cash position generated from posted transactions instead of exported and rebuilt in a spreadsheet.
Log, categorise and approve spend with the same approval and budget controls used in procurement.
Match statement lines against ledger entries, clear the matches and surface only the exceptions for review.
Every entry timestamped and attributed, on the same activity and change-log foundation the rest of the platform uses.
Party-wise ledgers that reconcile to the operational documents they came from, not a parallel set of books.
Accountants, approvers and auditors see exactly their scope, using the same permission model as Fluids.
Design partners get to shape this list against their own chart of accounts before general release.
FAQ
No. It is in active development. What is available today is the accounting hand-off in Fluids — a durable queue that pushes invoices, credit notes and payments into whatever accounts system you already run, with retry and voucher write-back.
No. Fluids is designed to sit alongside an existing accounts package rather than replace it. The sync bridge and the inbound payment endpoint are built and tested; we point them at your accounts system and switch them on during implementation.
It is being built on the same separation, permissions and record-keeping foundation as Fluids, so branch isolation, roles and change history carry over unchanged rather than being re-implemented.
Talk to us. Design partners get to shape the module list and the reporting formats against their own chart of accounts before general release.
Get involved
If your finance team is willing to sit with us on the design, you get the module list and the report formats built around how you actually close a month.