Invoice Customer: How the Process Runs Step by Step

Invoicing a customer starts with clean customer and product records. It moves through building and checking the bill, then issues it and books the receivable. It ends only when the customer accepts the charge or a credit note settles the dispute. Billing staff own most steps, with sales and collections feeding in.

The steps in order

1. Maintain customer and product master records. A master data team or the billing lead owns this. Sales submits new accounts, and the commercial team supplies price lists. The record holds bill-to and ship-to addresses, tax status, payment terms, the required purchase order format and how the customer wants invoices delivered. Errors here travel into every invoice that follows.

1. Capture the billable event. Operations, project managers or the order system raise this trigger. It might be a shipment confirmation, a signed-off milestone, a contract schedule date or a usage reading. Nothing gets billed until someone outside finance says the work happened.

1. Generate billing data. A billing analyst runs the billing job or builds the draft manually. The system pulls open events, applies the agreed price and discounts, and calculates tax. Items it cannot price, or that lack a purchase order number, drop into an exception queue for the analyst to clear.

1. Review and approve the draft. The billing lead checks drafts against contracts and orders. Large or unusual charges usually go to the account owner in sales for a second look. This is the cheapest point to catch a mistake, since nothing has reached the customer yet.

1. Transmit the invoice. The analyst sends it, or an automated run does. Delivery may be email, upload to a customer portal, an electronic data feed or paper post. Portals and electronic feeds often reject documents for small format faults, so someone has to watch for bounce-backs and resubmit.

1. Post the receivable. Issuing the invoice normally creates the receivable entry in the subledger automatically. A general ledger accountant confirms that the subledger agrees with the control account. Where revenue is recognised on a different basis from billing, the revenue accountant moves amounts to or from deferred revenue.

1. Resolve billing inquiries. Questions reach the billing team directly, though collections staff frequently hear about problems first when chasing payment. Each query gets logged, investigated against the source documents and answered. Some turn out to be the customer's own error. Others reveal a genuine fault upstream.

1. Issue credit memos or adjustments. When a charge proves wrong, the analyst prepares a credit memo or rebill and links it to the original invoice. An approver signs off according to the delegation policy. The customer is told what changed, and the adjustment posts against the open receivable.

1. Reconcile at period close. The revenue accountant compares billable events with invoices issued. Work delivered but not yet billed gets accrued. Anything billed before delivery is checked against contract terms.

Where the handoffs tend to break

Most invoicing pain sits between steps, not inside them. The handoff from operations to billing is the usual weak spot. Teams outside finance rarely see an unconfirmed shipment or an unsigned milestone as urgent, so billing waits on them.

A second gap appears between billing and collections. Disputes raised during a collection call can sit in a collector's notes without ever reaching the person able to fix the invoice.

Master data changes are a quieter risk. A sales representative who agrees a new price by email, and never updates the price list, sets up a dispute weeks before anyone notices.

Questions to ask the people who run it

Written procedures describe the intended path. The people doing the work know the detours. Before redesigning anything, ask them:

• What do you do when a billable event arrives without a purchase order number?
• Which customers get special handling, and where is that written down, if anywhere?
• How often do you edit an invoice by hand after the system generates it, and why?
• Who actually approves drafts when the billing lead is away?
• Which portal or delivery channel causes the most rejections?
• When a customer disputes a charge, how does the query reach you, and who tells collections to pause?
• Do credit memos ever get issued without a link to the original invoice?
• Are there spreadsheets kept alongside the billing system? What do they track that the system cannot?
• What gets billed late at period close, and what holds it up?
• If you could change one upstream habit, which would it be?

The answers to the spreadsheet and manual edit questions usually show where the real process lives. Any change that ignores those workarounds will break something the team quietly depends on.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.