A software demonstration makes everything look straightforward. The invoice is created in seconds, the chart is colourful and the bank feed appears to do the bookkeeping by itself.
Then your first real transaction arrives: a customer deposit, a part payment, a refund or a job that spans two months. Whether the system helps now depends on how well it fits your business and how carefully it was set up.
Choose the accounting process before choosing the subscription. That means understanding how work is sold, delivered, invoiced, paid and reported. The software should support those steps without turning every exception into a spreadsheet beside the spreadsheet.
Take your real transactions to the demonstration
Write down the activities the system must handle. A trades business may need job costing, progress invoices and mobile receipt capture. A consultancy may need project margins and recurring billing. A retailer may need a reliable connection between sales, stock and the accounts.
Ask the provider or implementation adviser to demonstrate a handful of realistic transactions from start to finish. Include an ordinary sale, a credit note, a payroll run if relevant, and one awkward transaction you regularly encounter.
Check the report at the other end. A feature is less useful if the team can enter the data but cannot extract a dependable answer. Business Victoria’s software guidance highlights payroll, stock, jobs, multiple accounts and integration needs as considerations when choosing a package.
Decide what you want to see each month
Before building the chart of accounts, list the management questions. Which services earn enough? Which jobs absorb unexpected time? How much is owed to us? What tax and payroll amounts are waiting to be paid?
Keep the chart of accounts detailed enough to answer those questions without creating a separate account for every minor expense. Use project, department or tracking features where suitable instead of forcing all reporting detail into account names.
For example, a fictional maintenance business earns income from installations and ongoing servicing. Recording both under a single “Sales” account may be enough for a basic total, but it makes their different economics harder to understand.
Separate the revenue streams and capture relevant direct costs consistently. If employees work across both activities, decide how time will be recorded or allocated. A split revenue report with all labour in one undifferentiated bucket will not establish which service is more profitable.
A bank feed still needs a thinking person
A feed brings transactions into the system. It does not prove that the transaction has been classified correctly, that GST has been treated appropriately or that the underlying document supports the entry.
Bank rules can speed up recurring work, but an overly broad rule can repeat the same mistake for months. Review rules against real supplier descriptions and establish who will check unusual items.
Reconcile the ledger to the actual bank and other control accounts. Review loans, payment-clearing accounts, payroll liabilities and transfers between accounts. A dashboard can look complete while an integration has duplicated a week of sales or omitted a payment.
Test the connections and the responsibilities
Map each integration and identify which system is the source of truth for customers, invoices, stock and payroll. If two applications can create the same transaction, work out what prevents duplication.
Check current payroll and reporting capability where required. The ATO software product register identifies products and supported functionality; appearance on a register does not establish that a particular package suits your operational needs.
Ask who fixes an integration problem and what happens while it is unavailable. Consider the total cost of the arrangement: subscriptions, add-ons, implementation, training, support and the internal time needed to run it. The lowest monthly fee may be expensive if it leaves the team doing the same manual reconciliation every Friday.
Own the account and control access
Keep the subscription and recovery details under business control, with named access for advisers and employees. Give each person permissions appropriate to their role. Someone entering bills does not necessarily need authority to release payments or change account ownership.
Enable multi-factor authentication and establish a process for removing access when somebody leaves. The Australian Cyber Security Centre’s small-business guidance recommends MFA, software updates and backups as practical protective measures.
Confirm what data can be exported, including transaction history and attachments, and how records remain accessible if you change providers. An adviser relationship can change; the business still needs its accounting history.
Make the first month a controlled handover
Choose a clear conversion date. Preserve the old records, verify opening balances and agree the treatment of outstanding invoices, bills, payroll balances and bank transactions around the cut-off.
Reconcile the first month in the new system to supporting records. Train the team on the transactions they will actually handle and document the few rules that matter most. Keep a short issue log until the recurring processes settle.
A good setup becomes fairly unremarkable in daily use: invoices move, records reconcile and reports answer the owner’s questions. That dependable routine is a better measure of success than how impressive the demonstration looked.
Target Advisory 