Last reviewed: July 2026.
An accounting package is software that records, processes and reports financial transactions. It may be installed on a computer, hosted on a private server, or delivered as a cloud service. Although the interface is faster than manual books, the underlying logic is still double-entry bookkeeping.
Good use of accounting software depends on more than knowing which button to press. The user must understand source evidence, account classification, access control, reconciliation and review. ACCA notes that modern accounting education now assumes the use of computerised systems because businesses have moved strongly toward desktop and cloud-based software.
1. Set up the accounting package correctly
Before entering routine transactions, configure the organisation name, reporting period, base currency, chart of accounts, tax codes, invoice numbering, bank accounts and user permissions. Opening balances should be supported by the previous period’s closing records and independently reviewed.
A poorly designed chart of accounts creates reporting problems later. Accounts should be detailed enough to support decisions and compliance, but not so fragmented that staff choose inconsistent codes. Lock dates can prevent accidental changes to completed periods.
2. Give each user appropriate access
Users should have individual accounts rather than sharing a common login. Access should match job responsibilities: a sales clerk may create customer invoices, while only an authorised manager can approve refunds or change bank details. Administrative access should be limited and reviewed regularly.
Passwords alone are not the strongest protection for sensitive systems. NIST recommends multi-factor authentication for important business accounts. Access should be removed promptly when an employee or contractor leaves, and unusual login activity should be investigated.
3. Record transactions from reliable evidence
Enter sales invoices, supplier bills, receipts, payments and expenses from approved source documents. Use clear descriptions, dates, references and attachments. Avoid posting everything to a miscellaneous account because that weakens reporting and can hide errors.
Routine transactions may be posted automatically by a module. For example, a customer invoice can debit trade receivables and credit revenue, while a supplier bill can debit an expense or asset and credit trade payables. Manual journals should be reserved for transactions that genuinely require them and should have supporting calculations and approval.
4. Use the accounting workflow
| Stage | Main action | Control question |
|---|---|---|
| Initial setup | Create organisation details, financial year, chart of accounts, tax settings and opening balances. | Who reviewed the setup before live use? |
| Daily entry | Record invoices, bills, receipts, payments, expenses and journals from approved evidence. | Can each entry be traced to a source document? |
| Bank processing | Import or enter bank transactions and complete reconciliations. | Are unmatched and old items investigated? |
| Month end | Post accruals, prepayments, depreciation, inventory and correction journals. | Are journals authorised and supported? |
| Reporting | Review trial balance, receivables, payables, profit, financial position and cash flow. | Do reports agree with control accounts and reconciliations? |
| Protection | Back up data, update software, review access and retain an audit trail. | Can the business recover and identify who changed data? |
5. Reconcile instead of trusting the dashboard
A dashboard can look convincing even when transactions are duplicated, omitted or incorrectly coded. Bank reconciliation compares the system’s cash records with the bank statement. Trade receivables and trade payables should also be reviewed for old, negative or unusual balances. Tax reports should be reconciled to the underlying transactions.
Exception reports are valuable. Look for duplicate invoice numbers, transactions posted to closed periods, negative inventory, inactive suppliers receiving payments, round-sum journals and changes to supplier bank details.
6. Understand reports before using them
Common reports include the general ledger, trial balance, aged receivables, aged payables, inventory valuation, tax summaries, income statement, statement of financial position and cash-flow reports. The software produces the report, but management remains responsible for whether the data and classifications are reasonable.
Review the worked trial balance example, the explanation of control accounts, and the guide to accounting software modules to understand how records flow into reports.
7. Protect data and preserve an audit trail
- Enable multi-factor authentication where available.
- Apply role-based access and segregation of duties.
- Keep software and connected applications updated.
- Back up data and test whether it can be restored.
- Retain an audit trail showing who created, edited or approved entries.
- Review connected bank feeds, add-ons and unused user accounts.
- Export essential reports and records according to legal retention requirements.
ACCA’s guidance on internal controls explains that general controls support the reliability of system-generated data. Its material on computerised accounting systems also emphasises that the move away from paper records does not change fundamental accounting principles.
8. Avoid common mistakes
- Sharing one password among several employees.
- Posting opening balances without a reconciliation.
- Connecting bank feeds but never completing a formal reconciliation.
- Deleting transactions instead of using controlled corrections or credit notes.
- Giving every user administrator rights.
- Relying on default tax codes without checking the transaction.
- Ignoring backups because the system is cloud-based.
- Assuming an automated report is automatically correct.
Month-end checklist
- Complete bank and control-account reconciliations.
- Review outstanding receivables and payables.
- Post approved accruals, prepayments, depreciation and inventory adjustments.
- Check suspense, clearing and miscellaneous accounts.
- Review user activity and unusual journals.
- Run the trial balance and analytical reports.
- Lock the completed period after approval.
Key takeaway
An accounting package is a controlled information system, not merely an electronic calculator. Reliable results require accurate setup, authorised evidence, correct coding, regular reconciliation, secure access and informed review. For related foundations, see source documents and the purpose of financial accounting.
Security reference: NIST guidance on multi-factor authentication.