How to Invoice When You Work on Multiple Projects for One Client

One client, many projects—each with its own budget owner, PO, and sometimes tax treatment. If you dump everything into a single undifferentiated total, you get delayed approvals, misallocated payments, and frustrated sponsors who thought their budget was safe.

Enterprise procurement guidance from sources like Gartner on P2P best practices stresses matching invoices to purchase orders and cost objects. Your layout should make that matching trivial.

Decide: one invoice or many

Separate invoices per project

Best when:

• Each project has a different PO
• Budget owners pay from different cost centers
• You need clean milestone narratives per stream

Consolidated statement with sections

Works when a single AP desk pays everything but internal sponsors still need visibility. Use bold section headers, subtotals, and per-project summaries.

What to show on every multi-project bill

• Project name / code and PO number per section
• Period covered (especially for hourly or retainer blends)
• Expenses tagged to the project that incurred them (expense invoicing)
• Payment instructions once—not repeated per section unless required

Anchor legal and tax fields using how to write an invoice.

Allocation and partial payments

When clients pay one wire for multiple invoices, request a remittance breakdown. Until then, allocate by oldest due date unless contract says otherwise—document your rule in the master agreement. See partial payments.

Approvals inside the client org

Large buyers run approval workflows. Put the approver’s name or department in the memo line when known—it speeds routing.

Reminders without spamming

Automate follow-ups per invoice, not per client blast, so Project A’s delay does not feel like harassment to Project B’s healthy payer. Tools like payment reminders help segment.

Reporting for yourself

Track revenue and margin per project code even if the client pays in one lump. That surfaces which streams suffer scope creep or chronic late pay.

Reporting you should run internally

Monthly, pivot revenue and gross margin by project code—even if the client pays one wire. Flag projects where DSO exceeds portfolio average; often one sponsor is the bottleneck. Compare budget versus actual hours if you track time; drift predicts future invoice fights. Keep a change log when codes or POs update mid-year. Align external PDFs with internal dashboards so leadership never argues with finance about what was really billed.

Closing checklist

Each quarter, reconcile project codes between your PSA and accounting system. Delete obsolete codes only after closing open AR. Sample five invoices for PO accuracy versus client portals. Discuss chronic late sponsors with account leads using facts, not vibes. Update approval workflows when new cost centers appear. Publish a one-page billing map internally so everyone knows which code to use.

Metrics and cadence

Monthly, chart DSO by project code inside large accounts—one bad code hides inside a “healthy” parent. Track invoice revision count; frequent edits mean unclear scopes or weak templates. Measure time from send to sponsor acknowledgement; slow acknowledgement predicts slow pay. Review discount leakage per code if commercial teams override pricing. Align metrics with hourly versus fixed models so blended deals stay interpretable.

---

Invoice complex client portfolios with clarity. Get started with InvoiceQuickly.

Managing multiple projects per client (2026)

The default rule: one invoice per project per billing period. Combining multiple projects on one invoice creates reconciliation friction without saving meaningful effort.

Step-by-step: Invoicing multiple projects efficiently

Step 1: Use project codes consistently

Bad: "Web design — $5,000". Good: "Project ACM-2026-WEB-001 — Marketing site redesign — $5,000". Project code on every invoice and time entry. Allows tracking even when client name appears on multiple projects.

Step 2: Create project-specific invoice numbers

Standard pattern: INV-2026-001 for first invoice; if you bill multiple projects per period, use sub-numbers (INV-2026-001-PROJ-A, INV-2026-001-PROJ-B). Or simpler: separate invoice number per project regardless of period.

Step 3: Bill projects as they complete or hit milestones

Don't wait to combine multiple projects' billing into one. Bill Project A when its milestones hit; bill Project B when its milestones hit; bill Project C when complete. Forced batching = stale data + confused clients.

Step 4: Use project-aware reporting tools

Most modern invoicing/accounting platforms (InvoiceQuickly, FreshBooks, QuickBooks) support project tracking. Configure projects per client; assign each invoice to its project. End-of-month: client P&L shows revenue by project.

Step 5: Issue consolidated statements (not invoices) monthly

For clients with many concurrent projects, send a monthly statement showing: "Projects in flight: ACM-WEB, ACM-BRAND, ACM-EMAIL. Outstanding invoices: $X. Recent payments: $Y. Balance: $Z." Provides visibility without creating a single super-invoice.

Common scenarios

Solo consultant with 2 clients, 1 retainer + 1 project: Bill Client A monthly retainer ($X). Bill Client B project milestones as they hit. Two separate billing streams; never combine. Both could be on the same date but different invoices.

Agency with single client, multiple workstreams: Marketing client has SEO project + email project + social project. Three separate invoices monthly. Each shows project-specific work. Same client, different revenue streams.

Freelancer with retainer + ad-hoc projects for same client: Retainer covers up to 20 hrs/month. Ad-hoc projects (separate scope) billed separately when delivered. Don't blend them — confuses tracking.

Project that spans multiple billing periods: Long project (e.g., 6-month engagement). Issue progress invoices monthly aligned to milestones. Each invoice references same project code; numbered sequentially within that project.

Frequently Asked Questions

Can I send one invoice for multiple unrelated projects?

Technically yes, but creates issues. Different projects often have different payment terms, different stakeholders, different cost-codes. Separate invoices = simpler operations.

How do I handle a client who insists on consolidated invoicing?

Some enterprise clients require monthly consolidated invoices for AP efficiency. Comply if their AP requires it; provide detailed breakdown by project within the consolidated invoice. Maintain your internal tracking by project regardless.

What about retainers covering work I do on multiple projects?

Audit at month-end: "April retainer 20 hrs / Hours used: 18 (5 hrs Project A, 8 hrs Project B, 5 hrs Project C)." Document the allocation transparently for client visibility. Don't worry about per-project billing within a single retainer.

Should I include all projects on a single invoice for tax purposes?

For tax purposes: each invoice is its own document. Separate invoices = cleaner audit trail. Combined invoices fine if separated by line item; don't bury different projects in one mystery line.

How do I handle a consolidated invoice's tax treatment?

Tax applies to the underlying transactions, regardless of how they're billed. Sales tax on each line item per its taxability. VAT/GST per its rate per item. Consolidated billing doesn't affect tax mechanics; just makes them invoice-level vs. transaction-level.