What Should Be Included on an Invoice?

Requirements vary by country and industry, but the list below covers what most small businesses need for fast approval and clean books. When in doubt, mirror what your largest customer's AP portal asks for—that reduces rejections.

• •Invoice number and issue date: unique, sequential IDs for tracking, reminders, and reconciliation; never reuse numbers.
• •Seller and customer details: legal business name, address, tax ID where applicable, and bill-to contact so mail and portals route correctly.
• •Line items: description, quantity, unit rate, and extended amount—tied to quote or contract language when possible.
• •Totals: subtotal, taxes, fees, discounts, and total due in the invoice currency.
• •Due date and terms: Net 30, Due on Receipt, or milestone language—consistent with the signed agreement.
• •Payment instructions: accepted methods, bank details if relevant, and a secure online payment link when available.

Missing payment instructions is one of the most fixable causes of late pay. If you accept cards or ACH on invoices, explain how they work in how online invoice payments work.

Optional does not mean unnecessary for every business. If you sell to mid-market or enterprise buyers, these fields are often required for their internal controls—even when not legally mandatory on the invoice itself.

• •PO and job codes: tie the invoice to procurement records; without them, payment may sit in “pending approval” indefinitely.
• •Payer and approver contacts: name and email for the person who can unblock questions—reduces ghosting in AP queues.
• •Supporting attachments: timesheets, delivery proofs, or signed completion docs for milestone and T&M work.
• •Discounts and late fees: only when disclosed in contract and applied consistently—see terms guidance in invoice terms explained.
• •Reference to prior documents: quote or contract number so totals match what procurement approved.

Capture these fields in your CRM or project tool at kickoff so they are available at invoice time—chasing a PO number after delivery is a common source of delay.

Invoicing software with locked templates and required fields helps prevent invoice defects before they reach the customer. Define one default template per invoice type (standard, progress, recurring) so preparers are not rebuilding layout each time.

Pair templates with a pre-send checklist: PO present, terms match contract, tax correct, payment link live. For multi-person teams, add approval only where risk warrants it—see how invoice approval workflows work.

Review rejected or disputed invoices monthly and update templates when the same correction repeats. That feedback loop is how operations teams improve faster than relying on individual memory.

If defects persist, audit against common invoice mistakes and your A/R aging report—patterns usually point to one missing field or handoff.

Treat the invoice as part of the customer deliverable, not an afterthought. The best teams capture billing metadata at project kickoff and validate it again at completion—before anyone hits send.

• •Mirror quote line descriptions on the invoice so approvers recognize scope instantly.
• •Send to the AP email or portal the customer specified—not only the project contact.
• •Include online payment options when margin allows; convenience often beats a few days of terms.

For lifecycle context beyond the document itself, see what is invoice management.