A statement of work describes what was actually done: the scope, the deliverable, or the service category, written in enough detail that anyone reading the invoice later understands what was purchased without asking. On an invoice, it usually appears as the line item description next to the amount charged.
The level of detail matters more than it might seem. A description like consulting services or professional services is technically accurate but tells an accounts-payable reviewer almost nothing, which is exactly the kind of line that gets held for a follow-up question. A description like backend API development for a checkout flow, three-week engagement, or copywriting for a product launch email, ten pieces, gives the reviewer enough to classify the expense and move on.
Precision also matters for compliance reasons that have nothing to do with the client: a platform issuing an invoice on a vendor's behalf generally screens the statement of work before the invoice goes out, to confirm it describes a real, permitted category of service. A vague title is more likely to need a clarifying question at that stage too, before the invoice is even sent.
Write the statement of work the way you would explain the job to a colleague who was not there. PANORAMA payments screens the work description before issuing an invoice, and a specific one, naming the deliverable, the scope and the period, moves through that step and later through the client's accounting review with fewer questions than "IT services". A useful pattern: what was delivered, for which project or order, over which dates, and which stage of the agreed total it closes.
The statement of work also travels with the payment: every paid invoice carries its agreement and payment receipt, which is what your client's auditor and your own bookkeeper will look for later. The fee is one, 10% of each paid invoice (7% with a partner or promotional code); see how you get paid for the documents each side receives, and invoicing a US client without a company for the whole route.
How detailed should a statement of work be on an invoice?
Detailed enough that someone unfamiliar with the project can tell what was delivered: the type of work, the specific deliverable or scope, and the time period covered. A one- or two-word category is rarely enough on its own.
Can a vague statement of work delay payment?
It can. Both the platform issuing the invoice and the client's own accounts-payable reviewer may need to ask a clarifying question before a vague line item is accepted, which adds time that a specific description would have avoided.
Does the statement of work need to match a formal contract?
It should be consistent with whatever work was actually agreed and delivered. It does not need to be a full legal document. On most freelance invoices it is a clear, specific description rather than a separate formal exhibit.