Invoicing Process: Invoicing Procedures, Steps & Flow Chart

The invoicing process is the sequence of steps a business follows to bill a customer and collect payment: confirm the work is done, create an accurate invoice, send it to the right person, track it until the due date, follow up if it slips, record the payment, and archive the record. Companies that write this down as a procedure get paid faster and argue with customers less. Companies that leave it in one person's head rediscover the process, badly, every time that person takes a vacation.

This guide covers both directions the phrase gets used in. If you send invoices, the first half walks the accounts receivable workflow step by step, plus the procedures worth putting in writing. If you receive invoices from vendors, the accounts payable section covers invoice processing steps and 3 way matching. And because this is a customer experience site, we will keep returning to a point finance guides skip: your invoice is a customer touchpoint, and a sloppy one costs you trust along with cash flow.

What is the invoicing process?

The invoicing process is the end-to-end workflow that turns completed work into recorded revenue. It starts the moment a product ships or a service milestone lands, runs through invoice creation, delivery, tracking, and follow-up, and ends when the payment is matched to the invoice in your books and the record is filed. A complete process also defines what happens on the unhappy paths: a disputed line item, a payment that never arrives, a customer who insists the invoice never showed up.

One clarification saves a lot of confusion. "Invoicing process" usually means the seller's side, billing customers, which accountants call accounts receivable. "Invoice processing" usually means the buyer's side, handling the invoices your vendors send you, which is accounts payable. The two workflows mirror each other, and most businesses run both at once. This guide covers the receivable side first because that is where the customer experience lives, then the payable side, where the discipline of matching and approval lives.

The invoicing process step by step

Here is the receivable-side workflow in eight steps. Small firms compress some of these into a single sitting; larger ones assign each to a different owner. The steps do not change, only who holds them.

1. Confirm the work is billable. Check the contract or purchase order before anything else: what was delivered, at what rate, against which terms. Invoices that get disputed are usually wrong at this step, not at the arithmetic. If the customer issued a PO, the invoice must reference it, because their AP team will match against it.
2. Create the invoice. A complete invoice carries your business details, the customer's billing contact, a unique invoice number, the issue date, itemized lines with quantities and rates, subtotal, tax, the total due, payment terms, the due date, and exactly how to pay. Every missing element is a reason for the customer's AP process to park it.
3. Review before sending. A second look, ideally by a second person for large invoices. Thirty seconds of review is cheaper than a credit memo, a reissued invoice, and two weeks of delay.
4. Send it to the right person, promptly. Invoice as soon as the work is complete or the milestone hits. Every day between delivery and invoice is a day added to your cash cycle before the payment clock even starts. And confirm where invoices are supposed to go; a perfect invoice sent to the project contact instead of the AP inbox is functionally unsent.
5. Record and track it. The invoice enters your receivables ledger with its due date. Someone, or something, watches the aging report weekly. An invoice nobody is tracking is a donation with paperwork.
6. Follow up on schedule. A polite nudge a few days before the due date, a firmer note the day after it passes, and a defined sequence from there. Consistent, professional persistence is what separates firms that get paid in 30 days from firms that get paid in 60. We cover the failed-payment version of this in our guide to dunning emails and payment recovery.
7. Record the payment. Match the payment to the invoice, handle short payments and overpayments explicitly, and close the invoice. Unmatched payments become reconciliation archaeology at month end.
8. Archive the record. The IRS expects supporting records for income to be kept at least three years, and most accountants advise seven. Storage is cheap; recreating a paper trail during an audit is not.

Invoicing procedures: what to put in writing

The steps above describe the flow. Invoicing procedures are the documented rules that make the flow survive contact with real staff, real customers, and real exceptions. A procedures document does not need to be long; one page that answers the following questions beats a binder nobody opens.

• Timing. When do we invoice: on delivery, on milestone, on a monthly cycle? Same-day invoicing after completion is the strongest default.
• Numbering. What is the invoice number format, and what guarantees uniqueness? Sequential numbering with no gaps is also what your accountant and any auditor want to see.
• Required fields. The full checklist from step two, so an invoice cannot leave the building incomplete.
• Payment terms. Your default terms (net 30 is the US standard, but net 15 is increasingly normal for services), who may approve exceptions, and whether you offer early-payment discounts or charge late fees, stated on the invoice itself.
• Delivery and confirmation. Which channel each customer gets, where the AP contact is recorded, and how delivery is confirmed for large invoices.
• Escalation. The exact follow-up cadence, who sends each touch, and at what point a human calls instead of emailing. Write the sequence down; improvised collections are inconsistent collections.
• Disputes and credits. Who may issue a credit memo, at what threshold approval is needed, and how a disputed line is investigated without freezing the undisputed remainder.
• Roles. Who creates, who reviews, who sends, who chases. In a three-person company this is one name three times, and writing it down still matters, because it makes the handoff explicit when the company becomes a ten-person company.

The reason to formalize this is not bureaucracy. Billing is one of the few operational processes every single customer experiences on a repeating schedule, and we have argued before that the billing experience quietly decides how much customers trust you. A written procedure is how the fifth invoice a customer receives feels exactly as professional as the first.

Invoicing process flow chart

If you prefer the whole workflow as a picture, the logic of the flow chart looks like this. Each row is a stage; the decision column is where the path branches.

Stage	Action	Decision point
1. Trigger	Work delivered or milestone reached	Billable against contract or PO? If unclear, resolve before invoicing
2. Create	Draft invoice with all required fields	Passes review? If not, correct and re-review
3. Send	Deliver to the customer's AP contact	Delivery confirmed for large invoices?
4. Track	Log in receivables ledger, watch aging weekly	Paid by due date? If yes, skip to stage 6
5. Follow up	Run the written reminder sequence	Payment received, dispute raised, or escalate to a call
6. Close	Match payment to invoice, resolve any difference	Short paid? Investigate before closing
7. Archive	File the invoice and payment record	Retention clock starts; keep at least three years, ideally seven

That table is the honest version of every invoicing process flow chart template you will find: a straight line through seven stages, with three loops (correction, follow-up, dispute) that a good procedure keeps short. If you draw it for your team, draw the loops too. The main path is easy; the loops are where untrained staff improvise.

Invoice processing steps in accounts payable

Now the mirror image: what happens when an invoice arrives at your company from a vendor. Invoice processing in accounts payable runs through five steps.

1. Capture. The invoice arrives by email, portal, or occasionally still by mail, and its data is entered or extracted into your AP system.
2. Verification and coding. The invoice is checked for completeness and coded to the right general ledger account and cost center.
3. Matching. The invoice is compared against the purchase order (2 way matching) and, where goods were received, against the receiving report as well (3 way matching). Quantities, prices, and totals must agree within tolerance before the invoice moves forward.
4. Approval. The invoice routes to the person with authority for that amount and category. This step is where most AP delay lives, and we broke down how to fix it in our guide to the invoice approval workflow.
5. Payment and archiving. The approved invoice is scheduled for payment against its terms, paid, and archived with its match and approval history.

3 way matching deserves the extra sentence it always gets, because it is the single control that stops most invoice fraud and most duplicate payments: an invoice is paid only when the invoice, the purchase order, and the goods receipt all tell the same story. Manual matching is tedious at any volume, which is why it is usually the first step companies automate; our accounts payable automation software guide covers the options honestly, including when a small team should not bother yet.

Common invoicing mistakes that slow payment

Across both sides of the workflow, the same handful of mistakes cause most of the pain.

• Invoicing late. The most expensive mistake is the quietest one. Work finished on the 3rd and invoiced on the 28th adds most of a month to your cash cycle with zero customer involvement.
• Wrong or missing PO references. If the customer runs matching and your invoice does not reference their purchase order, it will sit in an exception queue until a human rescues it.
• Vague line items. "Services rendered, $8,400" invites a dispute. Itemized lines that mirror the proposal get approved without a phone call.
• No stated due date or payment instructions. "Net 30" printed with no date and no payment link is an invitation to interpret. State the date and make paying take one step.
• Inconsistent follow-up. Customers learn your real terms from your behavior. Chase invoices on a schedule and they pay on a schedule; chase them when cash gets tight and they pay when they feel like it.
• Treating the invoice as a finance artifact only. The invoice, the reminder, and the statement are customer communications, often the only ones a quiet account receives all quarter. Larger organizations put them under the same template governance as everything else they send; that discipline is the core of customer communication management software, and the principle scales down to a two-person shop with a good template.

When to automate the invoicing process

Manual invoicing is fine at low volume. A services firm sending eight invoices a month from templates, tracked on a spreadsheet, is not leaving much on the table. The math changes with volume and repetition: once you send more than a couple dozen invoices a month, bill on recurring cycles, or spend real hours on reconciliation, invoicing software earns its subscription quickly. Automation handles the mechanical steps, generation from time or usage data, scheduled delivery, payment links, automatic reminders, and payment matching, while your written procedure still governs the decisions: terms, exceptions, escalation, credits.

The order matters. Automate a documented process and you speed it up; automate an undocumented one and you industrialize its defects. Write the one-page procedure first, run it manually for a month, then buy software that matches it.

Frequently asked questions about the invoicing process

What are the steps in the invoicing process? The invoicing process runs through eight steps: confirm the work is billable against the contract or PO, create a complete invoice, review it, send it promptly to the right contact, record and track it in receivables, follow up on a written schedule, match and record the payment, and archive the record for at least three years.

What is invoice processing in accounts payable? Invoice processing in accounts payable is the buyer-side workflow for handling vendor invoices: capturing the invoice data, verifying and coding it to the general ledger, matching it against the purchase order and receiving report, routing it for approval, and paying and archiving it. It mirrors the seller's invoicing process from the other side of the transaction.

What is the difference between billing and invoicing? In everyday business use the words overlap almost completely. Where a distinction is drawn, invoicing refers to creating and sending the individual payment request, while billing is the broader function: pricing, invoicing, payment collection, dunning, and account statements together. A billing process contains the invoicing process as its central step.

How to invoice a client for services? Send an itemized invoice as soon as the work or milestone is complete. Include your business details, a unique invoice number, the issue date, line items that mirror your proposal, the total with tax, explicit payment terms with a due date, and one-step payment instructions. Then track it and follow up on a fixed schedule rather than when you happen to remember.

What is an invoicing procedure example? A simple example: invoices are created within one business day of delivery, numbered sequentially, reviewed by a second person above $2,000, sent to the customer's AP contact by email with net 30 terms, reminded three days before due and one day after, escalated to a phone call at 15 days past due, and archived for seven years. That single sentence, expanded into a page, is a working procedure.

None of this is glamorous, which is exactly why it works as a competitive advantage: most of your competitors have not written theirs down. Billing is one of the clearest cases of the argument this site keeps making, that customer experience is won in the back office, in the systems that decide whether the most routine touchpoint a customer has with you, the invoice, arrives accurate, clear, and on time.