Accounting and CA Practice Software
Accounting software fails in a particular way: the numbers are right in the ledger and wrong in the spreadsheet beside it, because the spreadsheet is where the real work happens. A practice with sixty clients runs sixty sets of deadlines, documents and reminders, and the partner carries most of them in memory.
We build the system that holds all of it: the ledger, the invoices, the statutory calendar, the documents a client still has not sent, and the trail of who changed what. For a business, that is accounting software built around its own flow of money. For a chartered-accountant practice, it is the practice itself as software.
Accounting software built around how money actually moves
Off-the-shelf accounting packages are good at accounting and bad at your business. These are the parts we build when the package is the thing holding you back.
Ledger and chart of accounts
Double-entry, period locks, multi-entity and multi-currency when you need them, and nothing you do not.
Invoicing and receivables
Invoices from orders or timesheets, tax lines computed by rules you approve, reminders that follow your tone, and a statement a customer can read.
Bank reconciliation
Statements imported, matched by rule, exceptions queued for a person. The unmatched list is the to-do list.
Purchasing and expenses
Approvals that route themselves, bills matched to orders, and expense claims with the receipt attached.
Reports that answer a question
Cash position this morning, receivables by age, margin by product. Built for the question, not exported to a spreadsheet to be rebuilt.
Integration with what you keep
Your shop, your payroll, your bank, your existing accounting package where it offers an API or a file exchange. We replace what hurts and connect the rest.
The practice as software
Sixty clients, sixty calendars. These parts take the calendar out of the partner's head.
Client portal
Clients upload documents, answer queries and download filings in one place. Every request has a status; nothing is lost in a message thread.
Document collection
A checklist per client per period, reminders that escalate, and a view of who still owes what.
Statutory calendar
Deadlines for GST, TDS, year-end and the rest, per client, per entity, with owners and status. The examples are yours to confirm; the engine is the same for any regime.
Work tracking and billing
Who is doing what for which client, time logged against it, and invoices that follow from the work.
Review and sign-off
Preparer, reviewer and partner stages on every filing, with the trail an audit would ask for.
Retention and access
Years of client records with the retention your regulator requires, and access that ends on the day someone leaves.
What the software never does
Numbers that are wrong with confidence are worse than numbers that are missing.
- It does not give tax or accounting advice. Rules and rates come from your practice.
- It does not file anything. Statutory formats are generated for your practice to verify and submit.
- It does not round silently. Every computed tax line shows its basis.
- It does not let a closed period change without a reversing entry and a name.
- Client data stays in the environment and region you choose, nowhere else.
- It does not replace a reviewer. Preparer and reviewer are different people, and the system enforces it.
How an accounting system is built
Discovery with the people who close the books comes first. Stop after it if you like; everything produced stays with you.
Map the flow of money
From quote to cash, from bill to payment, with every spreadsheet and workaround on the map. Discovery ends with a scope, a data model and a cost range.
Build the ledger first
The chart of accounts, periods and the import of opening balances. Reconciled against your current books before anything else is built.
Add one flow at a time
Invoicing, then receivables, then purchasing. Each one runs beside the old method for a period before it replaces it.
Prove the numbers
Trial balance, tax summaries and bank balances reconciled between old and new. Your accountant checks the accounts they know best.
Hand over
Source code, data, documentation and a tested backup and restore. Kept running by us on a retainer, or by your team.
What we build it with
Chosen so that another firm could maintain it.
- Application
- PHP / Laravel.NETPython / Django
- Data
- PostgreSQLMySQL / MariaDBAudit logs
- Exchange
- Bank statement importsAPI connectorsStatutory file formats
- Front end
- ReactVue.jsMobile app for approvals
- Operations
- DockerYour cloud accountTested backups
What accounting software costs
Our rates are published. Pick the role and move the sliders for an indicative budget.
Rate card
| Role | Hourly | Monthly* |
|---|---|---|
| Frontend / WordPress | $30 | $4,800 |
| Backend / API | $32 | $5,120 |
| Full-stack | $35 | $5,600 |
| Mobile (React Native / Flutter) | $35 | $5,600 |
| DevOps / Cloud | $40 | $6,400 |
| AI / Automation engineer | $45 | $7,200 |
| QA / Test engineer | $25 | $4,000 |
| UI / UX design | $28 | $4,480 |
*160 hrs/month full-time. Rates are indicative for planning, in USD (other currencies are converted at an indicative rate), and depend on seniority, contract length and timezone overlap. Longer engagements and multi-role teams are discounted — ask.
Build it, or buy a package?
Building makes sense when
- The package is right about accounting and wrong about your business, and the gap lives in spreadsheets.
- You run several entities, currencies or regimes and the package charges you for each.
- The practice calendar, the documents and the billing need to be one system.
- Someone who closes the books can give a few hours a week to the build.
Buy a package instead when
- A standard package fits and the pain is training, not the software.
- You need it live before the next filing deadline.
- Nobody on your side can own the rules after hand-over.
- There is money for the build but none for the rule changes that follow every year.
Asked by finance teams and practices
Will it replace our existing accounting package?
Only where it hurts. Many clients keep the package as the ledger of record and put the practice system, the portal or the reconciliation around it, connected by API or file exchange.
Who keeps the tax rules current?
Your practice. Rates, thresholds and formats are data that your named people edit and approve. We build the engine and the trail; we do not decide what the rate is.
Can it produce the statutory file formats?
Yes, as output for your practice to verify and submit. We do not file on your behalf and the system does not submit automatically.
Where is the data stored?
On your own cloud account or server, in a region you pick; nothing of yours runs under an account of ours.
Can you take over accounting software someone else built?
Yes. We start by reading it and reconciling its numbers, then agree what to fix first. See software modernisation.
What does it cost?
Hours are billed at the published rate for each role on the job. Discovery gives a cost range for the first release so you decide with numbers in front of you.
Describe how the money moves today
Which package you use, where the spreadsheets are, how many entities or clients, and which deadline hurts most. No account numbers or client records; we sign an NDA before those change hands. We reply within one business day.