Invoicing Process
Invoicing Process
Invoice coding is the process of adding information to an invoice using a system of unique codes.
The codes connect the invoice items to the appropriate expenses in your company’s financial
records. For example, if your company buys a box of pencils, the invoice for stationery can be
assigned with the general ledger (GL) code.
Businesses use GL codes to track the account, department, location, project, or cost center
responsible for the incoming invoice. The codes help accounts payable departments allocate
vendor payments to the right budgets, track expenditures, calculate profitability and performance,
and produce financial reports.
Most businesses have a unique coding system based on their specific needs. Some common codes
include:
Part numbers
Locations
Vendor or customer
Department
Expense category
Non-PO invoice
A Non-PO invoice is for a purchase not associated with a purchase order. Non-
PO invoices are commonly used for services, recurring invoices, or unplanned
business expenses such as repairs. They differ from PO invoices because the
AP team must manually code them. Also, the costs associated with non-PO
invoices may not be approved, so the invoice needs to be coded correctly to
ensure it goes to the right approvers.
Coding non-PO invoices involves looking up the table items and other
information needed to code the invoice, then allocating the invoice to the
appropriate general ledger account and assigning a GL code.
With these differences in mind, let’s look at the steps in the invoice coding
process:
Once the AP team enters the invoice data, they manually code the invoice. As
mentioned above, the coding process differs for PO and non-PO invoices. To
simplify things, we’ll describe the next step as steps 2a (PO invoices) and 2b
(non-PO invoices).
2-way matching
The AP team tracks down the PO from purchasing so the invoice can be
verified and coded. Then, the invoice authorizer verifies the invoice by
ensuring the invoice details match the PO details and reconciles any
discrepancies or exceptions. For example, if the PO has 10 line items, and the
invoice has 8, the AP team contacts the procurement department to find out
what happened to the other two line items. After they have reconciled the
invoice they move to Step 3.
As your business grows, its expenditures will grow along with it, and so will the
number of GL codes you use to track those expenditures. You may face a
challenge scaling manual invoice processing workflows to handle this growing
workload and complexity while controlling errors and maintaining an efficient
workflow.
The process of identifying and coding expenses is also labor-intensive. For
example, identifying and correctly coding expenses for a non-PO invoice could
require tracking down codes in a spreadsheet, ERP, or even another
employee’s memory.