Small Business Invoicing Workflow and Checklist

Short answer

The practical starting point

Use a unique sequence; identify supplier and customer; describe the goods, services, period, quantity, price, currency, tax, total, issue and supply dates; state payment terms and route; then track delivery, reminders, credits, payment, and reconciliation. Add jurisdiction-specific fields after checking official rules.

Decision frame

The invoice is one stage of a controlled workflow, not a decorative PDF created after the work is finished.

Before the document

Make the commercial agreement invoice-ready

Confirm the legal customer name, billing address, contact, purchase-order requirement, tax identifiers, currency, payment method, and approval process before work begins. For projects, define scope, milestones, expenses, acceptance, change control, and who can approve additional work.

A purchase order does not automatically replace a contract, and an invoice cannot repair a disputed scope. Keep the proposal, agreement, purchase order, delivery evidence, and customer communications linked to the invoice record.

Core anatomy

Use fields that explain the transaction without context

A robust invoice normally identifies the supplier and customer, uses a unique number, describes what was supplied, shows relevant dates, quantities or milestones, unit or fixed prices, discounts, taxes, total due, currency, due date, and payment instructions. Local rules can require registration numbers, legal form, addresses, VAT identifiers, specific wording, or other details.

Descriptions should be specific enough for the buyer to approve and for both parties to understand later. 'Consulting services' is weaker than a defined service, project, milestone, and period. Avoid exposing unnecessary personal or banking information; provide only what the transaction and law require.

Delivery

Send it to the person and system that can approve it

Confirm the required channel: email, customer portal, e-invoicing network, procurement system, or postal address. Record when it was sent and whether the receiving system accepted or rejected it. A document sitting in a salesperson's inbox is not in the payment queue.

Use a stable reply address and protect bank-detail changes. If payment instructions change, notify customers through a known channel and invite independent verification. Fraudulent invoice redirection often exploits urgent, last-minute changes.

Collections rhythm

Follow up before an invoice becomes a surprise

Send a courteous confirmation shortly after delivery, then a reminder before the due date when appropriate. On the due date, ask whether the invoice is approved and scheduled rather than assuming refusal. Escalate according to the agreement and local law, preserving a professional record of each contact.

Separate administrative problems from commercial disputes. A missing purchase order, wrong legal name, rejected portal format, or absent tax field needs correction. A scope or quality disagreement needs the contract and project record. Reissuing documents without preserving history can damage the audit trail.

Close the record

Preserve corrections and match the payment

Use the required credit-note, cancellation, or correction process instead of silently overwriting a finalized invoice. Keep links between original and corrected documents and explain the reason. Requirements differ for VAT and other tax systems.

When payment arrives, match it using the invoice number, customer, amount, currency, fees, and bank reference. Record partial payments and approved write-offs explicitly. Review aging regularly and investigate unexplained credits or duplicate payments.

Action checklist

Turn the guide into a controlled process

01
Confirm legal customer and billing route before work
02
Link the invoice to an agreement, order, milestone, or delivery
03
Use a unique controlled invoice number
04
Include supplier, customer, description, dates, amount, currency, tax, total, and due date
05
Add locally required legal and tax fields
06
Protect changes to payment instructions
07
Record delivery and portal acceptance
08
Schedule reminders and escalation
09
Use proper corrections or credit documents
10
Match payment and preserve the closed record

Common mistakes

What usually breaks the system

Sending to a contact who cannot approve payment
Using vague descriptions that cannot be matched to scope
Leaving currency, tax treatment, or due date implicit
Changing bank details only by email
Overwriting a finalized invoice
Posting a net payout without matching fees and underlying invoices
Using a U.S., UK, or EU template as if its legal fields applied everywhere

When this may not apply

Situations that need more specific advice

Retail receipts, marketplace statements, self-billing, public-sector e-invoicing, progress billing, and regulated sectors can use different documents and workflows
VAT-registered EU or UK businesses need jurisdiction-specific invoice fields and correction rules
The checklist is operational and does not determine whether an invoice is legally required for a particular transaction

Jurisdiction note

Local rules take priority

GOV.UK lists required UK invoice fields and additional rules for sole traders, limited companies, and VAT invoices. EU rules provide common VAT invoice requirements with national variations. U.S. requirements depend on federal, state, local, industry, and contract context.

Primary sources

Sources and review status

These links support the jurisdiction-specific statements above. Volatile requirements should be rechecked before a filing, purchase, or material decision.