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.