How to Write an Invoice: A Step-by-Step Checklist (With Examples)
A clear invoice does more than request payment. It removes friction: your client immediately sees who’s billing, what they’re paying for, when it’s due, and how to pay. That clarity reduces back-and-forth, prevents disputes, and typically shortens time-to-payment—especially in busy accounts payable workflows.
What an invoice is (and what it isn’t)
An invoice is a formal billing document that requests payment for specific goods or services delivered. It creates a shared record of scope, price, and payment timing. It isn’t a quote (estimate), a purchase order, or a receipt—those documents serve different steps in the buying and payment process.
What to include on an invoice: key fields at a glance
These fields cover what most US and English-speaking clients need to approve and pay an invoice without delays.
| Field | Why it matters | Example |
|---|---|---|
| Seller (your) legal name | Matches contracts and accounting records; avoids vendor setup issues. | Acme Design Studio LLC |
| Seller address | Often required for AP systems and documentation. | 123 Market St, Suite 400, San Diego, CA 92101 |
| Buyer name + address | Ensures the correct entity pays and routes correctly inside finance teams. | Northwind Media Inc., 456 Pine Ave, Austin, TX 78701 |
| Invoice number | Unique identifier for tracking and reconciliation. | INV-2026-0148 |
| Issue date + due date | Sets the payment timeline and avoids “when does Net 30 start?” confusion. | Issued: Jan 30, 2026 • Due: Feb 14, 2026 |
| Line items | Defines scope and price; prevents “what is this for?” questions. | Website audit — 8 hours × $120/hr |
| Subtotal + taxes/fees/discounts | Transparency builds trust and keeps totals consistent. | Subtotal $960 • Sales tax $0 • Total $960 |
| Payment terms | Sets expectations and reduces follow-ups. | Net 15 (Due Feb 14, 2026) |
| Payment methods | Removes friction so clients can pay immediately. | ACH details, card option, mailing address for checks |
| Notes / references | Connects invoice to a PO, project, or milestone. | PO #10491 • Project: Q1 Creative |
Step-by-step invoice checklist
This checklist is designed for fast approvals in typical US accounts payable workflows. If you follow it in order, you’ll cover the information finance teams need to code the expense, match it to a PO or contract, and release payment on schedule.
-
1) Seller details
Start by making it easy to identify who is billing.
- Include legal business name, “doing business as” (DBA) if applicable, and primary contact email.
- Add business address and phone (many AP systems require them).
- Optional tax identifiers if your industry or client requires them (for example, EIN on request).
Pro move: keep your seller block consistent across invoices. Finance teams often create a vendor profile once; inconsistent naming can cause duplicate vendor records and delays. -
2) Buyer details
Make sure the invoice is addressed to the correct paying entity and routing contact.
- Include company/legal entity name and billing address.
- Add “Bill to” email or AP portal reference if the buyer uses one.
- If relevant list a department name (Marketing, IT, Facilities) or cost center the client provided.
If your client requires a specific format (vendor code, PO field, portal upload), consider linking to your internal guide on sending invoices (topic #5): How to send an invoice the right way.
-
3) Invoice number + issue date + due date
These fields drive tracking, approval, and payment scheduling.
- Invoice number use a unique, sequential format (avoid reusing numbers across clients).
- Issue date when you send or generate the invoice.
- Due date the calendar date payment is expected (not just “Net 30”).
Quick clarity: “Net 30” is clearer when you also include a due date (e.g., “Net 30 • Due Mar 1, 2026”). -
4) Line items (description, quantity, rate, subtotal)
This is where most disputes start—so be specific and consistent with your scope of work.
- Description name the deliverable or service and (when helpful) the timeframe (e.g., “January 2026”).
- Qty hours, units, or milestones—whatever your pricing uses.
- Rate per hour, per unit, or fixed amount.
- Subtotal for each line item so totals are transparent.
For services, a good line item reads like a mini-receipt: what + how much + at what rate.
-
5) Taxes, fees, and discounts (show them clearly)
Even if taxes are $0, explicitly stating them prevents confusion—especially for cross-state or mixed taxable/non-taxable work.
- If tax applies show the rate and the taxable base (e.g., “Sales tax 7.75% on $500”).
- If no tax list “Sales tax: $0.00” to avoid “did you forget tax?” emails.
- Discounts show as a separate line (not baked into unit prices) so the client sees the concession.
Consistency matters: if the contract says “10% discount,” make it a separate discount line, then compute totals from a clean subtotal. -
6) Payment terms + payment methods
This is the “pay me” section. Make it unmissable and easy to execute.
- Terms Net 7/15/30, Due on receipt, or milestone-based terms. If you use late fees, state them plainly.
- Methods ACH/bank transfer, card, check—offer at least one low-friction option for B2B (ACH is common).
- Instructions provide the exact details the payer needs (routing/account for ACH, address for checks, portal link if used).
If you want deeper wording examples for terms (Net 15, deposits, partial payments), link to your payment terms guide (topic #4): Invoice payment terms explained.
A filled invoice example (mini example + field notes)
Below is a compact example you can copy and adapt. It’s intentionally short (the goal is clarity), but it includes the fields that typically prevent delays in US AP workflows.
How to read the example
- Invoice # is unique and appears in the payment memo instruction to prevent misapplied payments.
- Line item includes scope + timeframe + pricing math (hours × rate), which reduces questions.
- Sales tax is explicitly shown as $0.00 to avoid ambiguity.
- Payment method is actionable: it includes what the payer needs and what to put in the memo field.
- Reference ties the invoice to a PO and a routing contact.
Common mistakes that delay payment
Most late payments aren’t intentional. They happen because the invoice can’t be processed quickly: missing data, unclear scope, mismatched totals, or a format that doesn’t fit the client’s workflow. Here are the most common blockers (and how to avoid them).
- No invoice number (or reusing the same number). AP can’t track or reconcile your bill reliably.
- Unclear “what”: vague line items like “Services” without timeframe, deliverable, or quantity.
- Mismatched totals: subtotal math doesn’t match the total, or discounts are hidden inside rates.
- Missing due date: “Net 30” alone can trigger questions about the start date.
- No payment method: a buyer may approve the invoice but still can’t execute payment.
- Missing PO / reference when the client requires it. Many systems auto-reject invoices without a PO.
- Wrong entity: billing the parent company when the contract is with a subsidiary (or vice versa).
- Sending to the wrong place: the invoice goes to a project manager instead of AP/portal.
Send-before-you-send QA (final check)
Run this quick QA checklist before you email or upload your invoice. It takes two minutes and prevents most avoidable delays.
If you frequently bill the same clients, consider saving a standard format and reusing consistent field placement. Consistency helps AP teams process you faster because they know where to look every time.
FAQ
Do I need to include an EIN or tax ID on a US invoice?
Often, no—many clients collect tax information during vendor onboarding (for example, via a W-9). Some industries or large enterprises may request an EIN for their records, but it’s typically not required on every invoice unless the client’s process demands it.
What’s a good invoice numbering system?
Use something simple and unique, like INV-YYYY-#### or ClientCode-####. The key is uniqueness and consistency. Avoid resetting numbers too frequently unless you can guarantee no duplicates.
Should I put “Due on receipt” or “Net 15/30”?
Choose what matches your agreement and your client type. Many B2B clients prefer Net terms because they run scheduled payment cycles. If you use Net terms, always include a calendar due date to prevent confusion.
How detailed should line items be?
Detailed enough that accounting understands the value without additional explanation. For services, include deliverable + timeframe + quantity + rate. For products, include SKU or product name, quantity, unit price, and any shipping/handling as separate lines.
What format should I send: PDF, Word, or a portal entry?
PDF is the most universal and tamper-resistant for email. If a client uses an AP portal, follow their portal requirements—even if you also send a PDF copy to your contact. The fastest payment usually comes from matching the client’s preferred workflow.