Invoicing checklist for finance teams

Invoicing converts approved work into a receivable with enough detail for the customer to approve and pay it. A poor process produces duplicate invoice numbers, rejected portal submissions, or payments that finance cannot match to the right customer balance.

This invoicing checklist covers the cycle from an approved billable event through invoice validation, customer delivery, receivable recording, payment application, and overdue handoff. It is written for finance teams coordinating account owners, delivery leads, tax reviewers, customer accounts payable contacts, and collections staff.

The 17-step checklist

0 of 0 done

Frequently asked questions

What information should every business invoice include?

An invoice should identify the seller and customer, carry a unique invoice number and date, describe the goods or services, show the amount and applicable tax, and state payment instructions and terms. Contract, purchase order, and local tax requirements may add fields, so finance should maintain a billing profile for each customer and jurisdiction.

Who should approve an invoice before it is sent?

Finance should control numbering, arithmetic, tax treatment, and ledger coding, while the account or delivery owner confirms that the work is billable and accepted. Higher-value or unusual invoices may need a controller or legal reviewer. The approval record should identify the reviewed invoice version so later edits cannot bypass the original check.

When should a finance team send an invoice?

Send it as soon as the contract's billing trigger is complete and the required evidence is available. For milestone work, that may be the acceptance date; for recurring services, use the agreed monthly schedule. Waiting until month end can shorten the customer's approval window, so finance should process approved billing events on a defined daily or weekly cadence.

What should happen when a customer rejects an invoice?

Record the rejection reason, owner, and resubmission deadline against the original invoice. Correct the specific issue, such as a missing purchase order or unsupported charge, and retain both versions. If the customer disputes the underlying work or price, route the matter to the account owner before finance changes the invoice or issues a credit.

How long should a business keep invoices and billing evidence?

Keep invoices and supporting records for the period required by tax law, contract, audit policy, and any industry rule that applies to the transaction. The IRS expects records that support business income and deductions, but retention periods vary by record and circumstance. Finance should use an approved retention schedule and suspend deletion when litigation or audit holds apply.

Related checklists

Does your team use Slack?

If your team’s in Slack, you can run this checklist there. Chaser assigns each step to the right person and follows up automatically until it’s done.

Works with everyone in your Slack — no logins, no onboarding.

1
Build a checklist
Start from scratch, or use a template like the client onboarding checklist.
2
Customize it for your team
Add or remove tasks and set who owns each one.
3
Run it in Slack
Your team gets their tasks in Slack and checks them off there, and Chaser follows up on anything that’s not done.
Try Chaser Free

Does your team use Slack?

If your team’s in Slack, you can run this checklist there. Chaser assigns each step to the right person and follows up automatically until it’s done.

Works with everyone in your Slack — no logins, no onboarding.

1
Build a checklist
Start from scratch, or use a template like the client onboarding checklist.
2
Customize it for your team
Add or remove tasks and choose who each one goes to.
3
Run it in Slack
Your team gets their tasks in Slack and checks them off there, and Chaser follows up on anything that’s not done.
Try Chaser Free