One ledger, one version of the truth
Accounting software earns trust in the boring layer: whether every voucher lands in the same ledger, through the same rules, and whether a posted entry can quietly change afterwards. Acronix is opinionated about all three.
- One ledger
- 10 voucher types
- Immutable postings
- Bill-by-bill
- Period lock
- Audit chain
Where this usually goes wrong
Every voucher type with its own logic
When each voucher posts its own way, the trial balance becomes an act of faith and every new type is a new class of bug.
Posted entries that can be edited
If a posted voucher can be silently altered, the audit trail is decoration.
Closed periods that reopen themselves
A back-dated entry landing in a filed period is how a reconciled quarter stops reconciling.
How it works in the app you can download
Every capability below ships in the current build.
One canonical ledger
All vouchers post through a shared engine into a single ledger_entries table. Trial Balance, P&L and Balance Sheet read only from there — so they cannot disagree with each other.
The core voucher set
Sale, Purchase, Receipt, Payment, Contra, Journal, Credit Note, Debit Note, Stock Journal and Delivery Challan, all driven by one generic form rather than ten cloned ones.
DRAFT → POSTED → VOID
Posted rows are immutable. Voids happen through reversal vouchers, never by updating or deleting history.
Bill-by-bill from day one
Invoices become bills; receipts allocate against specific bills. Outstanding is per-bill and per-age, not a party-level lump sum.
Period lock
Freeze the books to a date. The engine then rejects posts, edits and voids that would land at or before it — and every lock and unlock is recorded.
Tamper-evident audit log
Privileged actions are hash-chained, so an out-of-app edit to the database is detectable rather than invisible.
Moving from older accounting software?
Where Acronix is genuinely different — and where the tool you have already does the job. No invented weaknesses.
- Data at restAES-256 encrypted file — unreadable if the disk is copiedUsually a plain local data folder
- Switching machinesSign in on the new device and your books sync downSurrender the licence, copy a backup, restore by hand
- Working offlineFully offline-first — no internet needed to runOffline too, but cloud backup is bolt-on
- Keyboard-first entryEvery action has a shortcut; hands never leave the keysKeyboard-driven — the one thing they got right
- The interfaceA modern, high-density UI built this decadeFunctional, but a 1990s screen
- GST suiteGSTR-1, 3B, e-invoice, e-way bill from the same vouchersPresent, often as paid add-ons
Questions
Accounting & Vouchers — questions, answered
Straight answers on what's in the current build and what it does not do.
Do all the different voucher types post the same way?
Yes. Sale, Purchase, Receipt, Payment, Contra, Journal, Credit Note, Debit Note, Stock Journal and Delivery Challan all post through one shared engine into a single ledger_entries table, driven by one generic form rather than ten cloned ones. New behaviour is a rule on the engine, not a new class of bug.
Can my Trial Balance, P&L and Balance Sheet ever disagree with each other?
They read from the same canonical ledger, so they are three views of one set of entries rather than three independent calculations. There is no second place for a figure to live, which is exactly why they stay consistent.
Can a posted voucher be edited or deleted?
No. A posted row is immutable and follows a DRAFT → POSTED → VOID lifecycle. You correct a posted voucher by voiding it through a reversal, never by updating or deleting history — so the audit trail is real, not decoration.
Then how do I fix a mistake in a posted entry?
You post a reversal, which cancels the original with a fresh entry and leaves both visible. The original stands, the correction stands, and anyone reading the books later can see exactly what happened and when.
Can I lock a filed period so nothing back-dates into it?
Period lock freezes the books to a date, after which the engine rejects any post, edit or void that would land at or before it. Every lock and unlock is itself recorded, so a reconciled quarter cannot quietly reopen.
Does it handle multiple companies and financial years?
Yes. Multi-company and multi-financial-year are built in, with company_id on every transactional and master row, so several businesses and several years live in one encrypted book without separate installs or files.
Try it on your own books
14 days, every feature unlocked, no credit card. Your data stays encrypted on your own machine.