Chart of Accounts

A chart of accounts (COA) is the complete list of accounts used by a business to record financial transactions in its accounting system. Each account has a unique code and description, and is assigned to a category (asset, liability, equity, revenue, or expense). For accounts payable, the COA defines the expense accounts to which invoices are coded -- the coding choices made by the AP team determine what appears in the P&L under each cost category and, in turn, what the business understands about its cost structure.

A well-designed COA gives the AP team clear, unambiguous coding options for the invoices they process. A poorly designed COA -- with too few categories (everything ends up in "General Expenses"), too many categories (AP staff cannot distinguish between them), or badly named accounts (multiple accounts that sound similar) -- produces financial statements that mislead rather than inform management decision-making.

COA structure for AP

AP expense accounts typically sit in the 6000-9000 range in a standard COA numbering system (following assets in 1000s, liabilities in 2000s, equity in 3000s, and revenue in 4000-5000s). The expense accounts that AP teams code invoices to should be organised by function (cost of goods sold versus operating expenses), by cost type (labour, materials, professional services, utilities, etc.), and by cost centre or department where the business uses department-level reporting.

The level of granularity in the COA should match what management actually uses for decision-making. If management reviews a monthly P&L at the level of "advertising and marketing" as a single line, splitting it into 12 sub-accounts adds AP coding complexity without adding reporting value. Conversely, if management needs to separately track "cloud hosting" and "software subscriptions" to manage technology cost growth, collapsing them into a single "IT expense" account removes visibility that drives decisions.

GST treatment at the account level

Most accounting systems allow a default GST tax code to be assigned to each account in the COA. When an invoice is coded to that account, the default GST treatment is applied automatically. This is a useful efficiency feature but a meaningful risk if defaults are not configured correctly: an account set to "GST-free" will fail to record GST on taxable invoices coded to it, understating both the expense (by the GST amount) and the ITC claim. Account-level GST defaults should be reviewed whenever the COA is modified and as part of a periodic accounting controls review.

COA maintenance and AP accuracy

COAs are not static -- businesses add new cost categories as operations evolve, and old accounts become obsolete. Accounts that are no longer used should be marked inactive in the accounting system to prevent AP staff from mistakenly coding invoices to them. New accounts should be added with clear descriptions and correct GST defaults before they are available in the AP workflow. Ad hoc COA changes made without updating AP team training or system defaults are a common source of coding inconsistencies that accumulate into material P&L misstatements over time.

For businesses using AP automation, the COA also determines how well the system can auto-code invoices. Automation platforms learn coding patterns from historical transactions -- if the same supplier's invoices have been coded to "Repairs and Maintenance" consistently, the system will suggest that account for future invoices from that supplier. Inconsistent historical coding (the same supplier sometimes coded to Repairs and Maintenance, sometimes to Capital Equipment, depending on which staff member processed it) produces low-confidence auto-coding suggestions and increases the proportion of invoices requiring manual review.