GL coding: how to code invoices to the general ledger

The account says what the cost is: rent, software, freight. The dimensions say who or where: the sales team, the Chicago office, Project 214. Together they decide where the cost shows up in the general ledger and in every report built on it.

There is no single numbering standard. Most charts of accounts group accounts into the same five types (assets, liabilities, equity, income and expenses), and the number ranges vary by software and by company. A common pattern looks like this:

A fully coded line then reads like 6100 · Sales · New York: account 6100, department Sales, location New York. Some systems store this as one segmented string (for example 6100-20-03); others keep the account and each dimension in separate fields.

1. 1

   Step 1

   Check the invoice is valid: right vendor, your company as the customer, an invoice number, a date and a total that adds up.
2. 2

   Step 2

   If it references a purchase order, pull the PO and use the account and dimensions already on each PO line.
3. 3

   Step 3

   For a non-PO invoice, start from the vendor’s default coding, then read each line and confirm it fits what was actually bought.
4. 4

   Step 4

   Pick the GL account for each line from your chart of accounts. Ask: is this an expense for this period, an asset, or a prepayment for future periods?
5. 5

   Step 5

   Add the dimensions your company tracks, such as department, class, location or project. Split a line across them when the cost is shared.
6. 6

   Step 6

   Treat tax and freight consistently with your policy, either on the same account as the item or on their own lines.
7. 7

   Step 7

   Send the coded invoice to the budget owner for approval, so the person who knows the spend confirms the coding.

• PO invoices. The requester and approver chose the account and department when they raised the purchase order. When the invoice is matched to the PO, each invoice line takes the coding of the PO line it matches. AP should only change it if what was billed differs from what was ordered. See three-way matching.
• Non-PO invoices. Utilities, rent, subscriptions and one-off services rarely have a PO. Use the vendor's default coding as a starting point, check each line against it, and have the budget owner confirm it during approval.
• Mixed invoices. When a vendor bills ordered goods and an unplanned extra on one invoice, code the matched lines from the PO and code the extra line on its own, so it is visible to the approver.

Write the split basis down and reuse it every month. If the basis changes (a team grows, an office moves), update the vendor's default split rather than reworking each invoice by hand.

• US sales tax. Code the tax to the same account as the item it relates to, or to a separate tax expense account if that is your policy. For equipment you capitalize, the IRS treats sales tax, freight and installation as part of the asset's cost.
• Untaxed purchases. If a vendor did not charge sales tax on something taxable where you use it, you may owe use tax. Rules vary by state, so check with your tax adviser.
• VAT and GST. A registered business usually records reclaimable input tax in a tax account, not in the expense. VAT you cannot reclaim becomes part of the cost.
• Be consistent. Whatever your policy, apply it on every invoice. Mixed treatment makes expense accounts hard to compare month to month.

• QuickBooks Online classes. Available on the Plus and Advanced plans. You turn on class tracking under Account and settings, then choose whether a class applies to the whole transaction or to each row. You can also ask QuickBooks to warn you when a transaction has no class. Intuit describes classes as a way to track parts of the business such as departments or product lines.
• QuickBooks Online locations. Also on Plus and Advanced. Locations group data for offices, regions, outlets or departments of the same company. See our guide to QuickBooks Online class tracking for multiple locations.
• Xero tracking categories. Xero's tracking categories let you assign expenses to projects, departments or cost centers, so you can see spending by part of the business without creating a separate account for each one.

The rule of thumb in both: use accounts for what you spent on and dimensions for who or where. A chart of accounts with "Software – Sales" and "Software – Finance" as separate accounts is a sign that a dimension would do the job better.

• Vendor default coding. Give each recurring vendor a default account and dimensions. It removes guesswork for the bulk of invoices.
• Approver review. The approver confirms both the spend and the coding. Routing invoices by GL account or department sends each one to the person who can judge it. See invoice approval routing.
• Written capitalization policy. A dollar threshold and a list of asset classes, applied the same way every time.
• Lock down the chart of accounts. Limit who can add accounts, and retire unused ones, so coders cannot pick from a long list of near-duplicates.
• Periodic coding review. Before each month-end close, scan expense accounts for unusual amounts, catch-all balances and lines without a department.

Automation helps most with non-PO invoices from recurring vendors, where the same coding decision is made again every month. Look for three things: rules you control (vendor and line defaults), suggestions limited to accounts that actually exist in your chart of accounts, and a clear review step where a person can accept or change the coding. Avoid any tool that posts coding to your ledger without someone seeing it.

• Vendor coding defaults. Set a default GL account, department and cost center per vendor, and they apply automatically.
• Line-level AI suggestions. For lines without a default, AI suggests a GL account per line. A suggestion that is not in your chart of accounts is flagged for review rather than used.
• A person decides. Your team reviews the coding on each line and can change it before the invoice is approved.
• Approval by GL account or department. Approval rules can route invoices by GL code or department, so the right budget owner confirms the coding.
• Posts to your ledger. Approved bills sync to QuickBooks Online, Xero, FreshBooks, Zoho Books or Business Central with their coding, and the invoice history records who coded and approved each one.

Aequo AP does not pay vendors; payments stay in your existing process. See how invoice capture and coding work in Aequo AP.