Last reviewed: July 2026.
Accounting software is usually organised into modules that capture specialised transactions and feed controlled summaries into the general ledger. Examples include sales, purchases, inventory, payroll, fixed assets, cash and project accounting.
The accounting quality of an integrated system depends on configuration, master data, interface rules, access controls and reconciliation. Automation removes repetitive posting, but it does not remove the need for accounting judgement.
General ledger as the financial reporting core
The general ledger holds the chart of accounts and the balances used to prepare financial statements. Subledgers retain detailed transactions, such as individual customer invoices or specific assets.
A well-designed integration posts summarised or transaction-level entries to the correct accounts, periods, entities and dimensions while preserving a drill-down path to source evidence.
Sales and receivables module
The sales module records customers, quotations, orders, deliveries, invoices, credit notes, receipts and collection activity. Posting rules normally debit receivables and credit revenue and tax accounts when an invoice is recognised.
Controls include customer approval, credit limits, price authorisation, duplicate invoice prevention, sequential documents, cut-off checks and receivables-to-ledger reconciliation.
Purchases and payables module
The purchase module can connect requisitions, purchase orders, goods receipts, supplier invoices, credit notes and payments. Three-way matching compares the order, receipt and invoice before payment.
Supplier master changes, bank details and payment batches require strong approval and segregation because they create direct fraud and error risks.
Inventory module
Inventory modules track quantities, locations, standard or actual costs, transfers, production, write-downs and counts. Their accounting entries affect inventory, cost of sales, purchase variances and production accounts.
Negative quantities, backdated transactions and uncontrolled unit-of-measure conversions can distort both operational and financial information.
Cash and bank module
Cash modules import bank transactions, create payment files, allocate receipts and support reconciliations. Automated matching should use controlled rules and leave exceptions for review.
The bank balance in the general ledger must reconcile to the bank module and external statement. Unmatched items should have owners, ageing and resolution dates.
Fixed asset module
The fixed asset module stores asset identity, location, class, cost, in-service date, useful life, method, accumulated depreciation, impairment and disposal information.
Additions should link to approved capital expenditure and invoices. Depreciation and disposal postings must reconcile to the fixed asset register and general ledger.
Payroll module
Payroll modules calculate gross pay, deductions, employer costs, net pay and liabilities. Integration posts payroll expenses, taxes, benefits, accruals and bank-clearing entries.
Access to personal data and pay rates should be restricted. Changes to employees, bank accounts and one-off payments require documented authorisation.
Project and job-costing modules
Project modules accumulate labour, materials, subcontractors and overheads by job, contract or grant. They can support billing, profitability, work in progress and capitalisation.
Accounting policies must define which costs are expensed, included in inventory, recognised as contract assets or capitalised. Software cannot make that policy decision without configured rules.
Master data governs every module
Customers, suppliers, products, tax codes, accounts, cost centres and asset classes are master data. An error in master data can repeatedly misclassify thousands of transactions.
Create, change and deactivate rights should be limited. Important changes should be approved, logged and periodically reviewed.
Posting rules and interface controls
Each transaction type should have documented debit and credit logic. Interfaces need control totals, sequence checks, rejection reports and protection against duplicate processing.
An interface marked successful is not enough. Finance should reconcile record counts and values between source, subledger and general ledger.
Period close and cut-off
Modules should follow an organised close calendar. Subledgers are reconciled and locked before the general ledger is finalised, with controlled procedures for late adjustments.
Backdated posting rights should be restricted. Reopening a period should require approval and leave a visible audit trail.
User access and segregation of duties
No user should control an entire high-risk process without review. Examples of incompatible access include creating a supplier and approving its payment, or entering a journal and approving it.
Role design, privileged access, multi-factor authentication and periodic access certification support both financial control and cybersecurity.
Audit trails, backups and resilience
Systems should preserve who created, changed, approved and posted a transaction, including timestamps and before-and-after values. Logs should be protected from ordinary users.
Backups must be tested, not merely scheduled. Recovery plans should address ransomware, unavailable cloud services, corrupted integrations and key-person dependency.
Monthly reconciliation matrix
| Reconciliation | Typical evidence |
|---|---|
| Receivables subledger to general ledger | Ageing total and control account |
| Payables subledger to general ledger | Supplier listing and control account |
| Inventory to general ledger | Valuation report and count adjustments |
| Fixed assets to general ledger | Register cost and accumulated depreciation |
| Payroll to general ledger | Payroll summary, bank and liability accounts |
| Bank module to statements | Completed bank reconciliations |
Each reconciliation should identify preparer, reviewer, date, exceptions and resolution status.
Related Accounting Support guides
- Accounting Software Modules: Complete Guide
- Accounting Software Packages: Selection, Controls and Setup
- Integrated Accounting Software: Architecture and Controls
Official sources
Key takeaway
Integrated modules create speed and detail only when posting rules, master data, access and interfaces are controlled. Reconcile every subledger to the general ledger and retain a clear path from financial statements back to source transactions.