Invoice narrative for clients
Short email that ties hours/line items to outcomes without sounding defensive.
Overview
Billing surprises erode trust even when the work was valuable. A structured explanation connects scope changes to what shipped, invites questions early, and sets habits that prevent the same disconnect next cycle.
Who should use it
Finance partners and project leads who jointly own client-facing AR conversations in SMB services.
Use it for
Monthly invoices after active sprints with multiple change requests.
Phase closes where burn differed from the plan but value delivered is clear.
Following change orders that clients verbally approved but did not internalize numerically.
Inputs
Line items and hours pulled from your billing system—do not let the model invent totals.
Scope change history: what expanded, what traded off, and when clients were notified.
Client sentiment if known—adjusts tone from collaborative to extra-clear without drama.
Context
Ask for warm-professional tone, neutrality between teams, and explicit alignment to approved rates and terms. Anything touching credits, waivers, or legal concessions needs human approval before send.
Prompt Skeleton
Draft invoice explanation email. Facts: - Line items: ... - Variance drivers: ... - What changed vs original scope: ... Output: 150-220 words, warm-professional, with bullet breakdown and "how we prevent surprises next time" without sounding contractual.
Review checklist
Totals match the billing system and any referenced SOW or MSA language.
Legal or leadership approved any language on credits, discounts, or liability.
Common mistakes
Over-explaining internal staffing ratios the client does not need to see.
Apologizing in ways that invite renegotiation or dispute instead of conversation.
