Integrated Accounting Software: Architecture and Controls

Last reviewed: July 2026.

Integrated accounting software connects sales, purchases, inventory, payroll, fixed assets, banking and the general ledger so one authorised transaction updates related records automatically. Integration reduces duplicate entry, but it also spreads configuration and data errors across the system quickly.

A reliable design combines accurate master data, automated controls, reconciliations, access security and clear responsibility for every interface.

What integration means

Integration means modules share data and accounting rules rather than operating as isolated spreadsheets. A sales invoice can update customer balances, revenue, tax, inventory and cost of sales from one controlled event.

Core module architecture

Module	Typical output	General-ledger impact
Sales and receivables	Invoices, receipts, ageing	Revenue, tax and receivables
Purchases and payables	Orders, invoices, payments	Expense, inventory, tax and payables
Inventory	Quantities, cost and movements	Inventory, cost of sales and variances
Payroll	Gross pay, deductions and net pay	Employee cost, liabilities and cash
Fixed assets	Cost, depreciation and disposal	PPE, depreciation and gains/losses
Banking	Receipts, payments and reconciliation	Cash and settlement accounts

Single source of data

Shared customer, supplier, product, tax and chart-of-account records reduce repeated data entry. However, incorrect master data can affect every downstream process.

Automated double entry

Transaction rules generate debit and credit entries. Users still need to understand the accounting because automation cannot determine whether a business event was authorised, complete or economically correct.

Review the computerised general ledger guide.

Real-time versus batch posting

Some systems post immediately; others use approved batches. Real-time posting improves visibility, while batch posting can support review and control. The design should fit transaction volume, risk and reporting needs.

Master data controls

• independent approval of new suppliers and bank details;
• controlled chart-of-account creation;
• duplicate customer and product checks;
• effective dates for tax and price changes;
• audit trails for every amendment;
• periodic review of inactive records.

Interface controls

Where external systems feed accounting software, reconcile record counts and monetary totals. Monitor rejected, duplicated and missing transactions.

An interface marked “successful” does not prove every source transaction reached the correct account.

Role-based access

Users should receive only the access needed for their duties. Separate supplier creation, invoice approval, payment release, journal posting and reconciliation where practical.

Approval workflows

Configure approval by amount, type, department and risk. Prevent users from splitting transactions to avoid limits and review emergency overrides.

Audit trails

The system should retain the user, timestamp, source, original value and authorised changes. Direct database edits should be prohibited or independently controlled.

Subledger reconciliation

Integrated modules must still reconcile to control accounts. Compare customer, supplier, inventory and fixed-asset totals with the general ledger at each close.

The accounting modules guide explains module-to-ledger relationships.

Period close

• complete interfaces and resolve errors;
• reconcile cash and subledgers;
• post accruals, depreciation and estimates;
• review unusual journals and balances;
• lock the period after approval;
• control any reopening.

Cloud accounting risks

Cloud systems add vendor, availability, data-location, subscription and exit risks. Review service agreements, backups, recovery testing, encryption and administrator access.

API and automation risk

APIs can connect ecommerce, payroll, banking and payment platforms. Secure tokens, validate data, monitor failures and prevent repeated imports.

Three-way matching and transaction controls

Integrated purchasing should compare authorised orders, goods received and supplier invoices. Exceptions need investigation rather than automatic payment, and the system should prevent duplicate invoice processing.

Business continuity and recovery

Document recovery time objectives, backup frequency, alternative payment procedures and restoration testing. A cloud vendor's availability claim is not a substitute for the entity's own continuity plan.

Change management

Software updates, tax changes, new integrations and workflow amendments should be tested and approved before production. Emergency changes need retrospective review and evidence.

Reporting and dashboards

Integrated data enables faster reporting, but dashboards can mislead when mapping, cut-off or master data is wrong. Reconcile key metrics to the ledger and define every measure.

Implementation process

• document current processes and pain points;
• design the chart of accounts and dimensions;
• clean and validate master data;
• configure roles, approvals and posting rules;
• test normal and exception transactions;
• reconcile migrated opening balances;
• train users and monitor post-launch issues.

Data migration

Migration should preserve opening balances, outstanding documents, asset details and audit evidence. Reconcile source and target totals and retain a signed conversion record.

Internal control monitoring

Review access, failed interfaces, manual journals, overrides, duplicate payments and unusual master-data changes. Automated controls need periodic testing.

See the accounting software risks and controls guide.

Key performance and exception reports

Useful reports include overdue receivables, duplicate supplier invoices, negative inventory, failed interfaces, unusual journals and changes to supplier bank details. Review responsibility should be assigned and evidenced.

Common mistakes

• assuming integration eliminates reconciliation;
• giving administrators unrestricted transaction rights;
• migrating poor-quality data;
• failing to test exception scenarios;
• ignoring API failures and duplicates;
• allowing users to edit closed periods;
• relying on dashboards without ledger agreement.

Ownership and accountability

Every module, interface, master-data set and exception report should have a named business owner responsible for accuracy, access and timely remediation.

Key takeaway

Integrated accounting software can improve speed and control only when configuration, master data, access, interfaces and reconciliations are actively governed.

Official learning references: ACCA computerised accounting systems, ACCA computerised accounting and the auditor, and ACCA internal controls.

Advertisement