The accounts team should not be re-typing what the counter already recorded. In ambar 27 every sale, purchase, return, expense and receipt posts to the ledger as it happens — and every outflow passes through an approval lifecycle before the money leaves.
The daybook is the day’s truth: opening, receipts, payments, closing, per ledger and per branch. Multi-daybook puts several branches side by side, and view-day reopens any past date exactly as it stood.
Most retail cash loss is not theft — it is untracked handoffs. ambar 27 makes every handoff a document: counter settles to cashier, cashier balances, cash moves to the manager, manager deposits to bank. Each step reconciles against the last.
Cheques are still how wholesale textile pays. ambar 27 treats them as instruments with a lifecycle: issued from a numbered book, held, deposited, cleared or bounced — and printed on your bank’s layout from a stored template.
A payment planner turns an intention to pay into a document that must be approved before it becomes a payment. The same pattern covers receipts, expenses, income and TDS — so the owner sees the pipeline, and the auditor sees the trail.
Expenses are where control usually disappears. Here they are ledgered, drafted, approved, paid and reportable — including advances given against future expenses, and void handling that leaves a record rather than a gap.
Purchase orders, purchase plans, purchases, returns and supplier payments run through the same approval discipline as everything else — and land on the same inventory the counter sells from.
Nothing here is a roadmap item. Every screen below ships in the product and is controlled by the same role permissions.
Finance reporting is not an export to Excel. Every view is filterable by branch, period and ledger, permissioned separately from the transaction screens, and reads from the same ledger the counter wrote to.
For operations, yes — sales, purchase, inventory, cash, banking and receivables live here. Most clients keep Tally as the statutory book and push mapped vouchers to it from ambar 27, so their CA’s workflow is unchanged.
Planners have explicit draft and approved states, with permissions deciding who can draft, who can approve, and who can release payment. Every transition is recorded with user and timestamp, and the pending queue is visible by role.
Yes. Channels and warehouses scope data per branch, users are restricted to their own channel, and multi-daybook and branch reports consolidate across them.
A cheque moves through issued, deposited and cleared or bounced states. A bounce reverses the receipt against the customer ledger and leaves both the original entry and the reversal visible.
A 45-minute working session on your store data — your categories, your GST profile, your counters. No slideware.