Consulting Invoices: Purchase Orders and Approval Handoffs

Consulting invoices usually get delayed for administrative reasons, not because the client disputes the work. The fix is to manage the handoff from accepted engagement to client approval to accounts payable, then make sure the invoice carries the exact reference the client needs. If a purchase order is required, use it exactly as issued. If approval comes from one person but invoices are processed by another team, treat those as separate steps. A PO can help route an invoice, but it does not guarantee payment.

Confirm the billing route when the work is accepted

The best time to ask billing questions is at setup, before delivery starts. A signed proposal or statement of work tells you what was bought, but often not how the client routes invoices internally.

Confirm these points in writing:

Keep a simple operational record outside the invoice itself: client name, engagement, accepted date, PO required yes or no, PO number if issued, approver, AP contact, submission channel, and required support. The IRS business recordkeeping guidance supports keeping records in a system that clearly shows income and expenses, along with supporting records. While it does not prescribe one template, it supports maintaining organized operational records so invoices and related support can be retrieved together.

Use a two-contact handoff, not one informal approval

A common mistake is relying on a single client contact. In many consulting engagements, you need two contacts:

• Service approver: the person who confirms the work was authorized and delivered.
• Accounts-payable contact: the team, inbox, or portal that actually receives and processes invoices.

Those roles may overlap in a small business, but often they do not. A sponsor can say, “Please invoice,” and AP can still reject the invoice because the PO is missing, the billing entity name is wrong, or the invoice went to the wrong place.

A practical handoff looks like this:

If you want a consistent way to prepare invoices with saved client details, line items, currency, payment instructions, PDF export, and status tracking, see consultant invoicing software built for clear client records. The invoice tool supports the document; it does not replace your approval trail.

Match the invoice to the client's references

The most effective consulting invoice is the one AP can route without asking follow-up questions. That usually means including:

• your business name and the client billing entity
• invoice number and invoice date
• service period or milestone dates
• line items that match the engagement language
• payment instructions
• the client reference requested, such as a PO number, cost center, or engagement code

Keep the wording close to the underlying agreement. If the statement of work says “discovery workshop and recommendation memo,” avoid billing a vague line like “professional services.” Matching the original phrasing reduces unnecessary queries.

Also remember what an invoice is not: it is a request for payment and a business record, not proof that payment was made. If a client pays in part, you still need to check actual payment records before marking the invoice paid or partially paid.

For consultants who bill in different ways, related workflows are covered in Consulting Invoicing Software for Retainers, Expenses and Payment Tracking and How to Invoice Consulting Clients: Projects, Day Rates and Retainers. If your engagement is on a retainer, the same document rules still apply: confirm the billing entity, any required PO or reference, the billing period covered, and where recurring invoices must be sent.

Worked example: PO handoff from approval to invoice

Assumptions for illustration only: fictional U.S. consulting engagement, USD, tax excluded, actual tax treatment varies by situation.

A consultant completes a short operations review for North Peak Labs. The client required a PO before billing.

Engagement setup

Invoice calculation

Submission packet

The consultant sends a PDF invoice to AP with:

• PO-4817 in the reference field
• service dates matching the completed work
• line items that mirror the engagement description
• payment instructions
• a short note copying Maya, or stating that Maya approved delivery on the relevant date if that matches the client process

That is the real handoff: accepted work, approval confirmed, correct reference included, invoice delivered to AP.

A short pre-send checklist

Before sending any consulting invoice that depends on internal client approval, check:

If you regularly invoice the same clients, consultant invoicing software for organized client details and invoice tracking can make repeat preparation cleaner. Keep your approval log and supporting evidence as separate operational records.

Polite email when the PO or reference is missing

Sometimes the work is complete, but the billing reference was never issued. Keep the message calm and specific:

Subject: Invoice reference needed for [project name]

Hi [Client name],

I’m preparing the invoice for the completed [project or milestone name]. Before I send it to accounts payable, could you please confirm the required purchase order number or billing reference, and the correct AP submission email or portal?

For convenience, the completed work covered [brief description] for [service dates]. Once I have the reference, I can send the invoice in the format your team needs.

Thank you,
[Your name]

This works because it focuses on following the client’s process rather than pushing blame.

Two edge cases that still cause delays

The approver changes mid-project

If your original sponsor leaves or the budget owner changes, AP may want approval from a new person. Ask for written confirmation of the new approver before submitting or resubmitting the invoice, then update your records so the next invoice does not repeat the delay.

One PO covers only part of the work

A sponsor may approve extra workshops verbally while procurement never increases the PO value. In that case, AP may hold the amount above the PO cap. The safest approach is to separate what clearly fits the existing PO from what needs revised authorization, then ask the client how they want that billed.

Follow through after submission

Sending the invoice is not the end of the process. Record the submission date, recipient address, attachments, and any AP ticket or portal reference. If there is no acknowledgment after a few business days, ask AP to confirm receipt. If AP confirms receipt but status is pending, ask whether any support or approval is missing.

The core habit is simple: confirm the route before billing, use the exact client reference provided, send the invoice where AP actually processes it, and keep a clean confirmation trail. That turns consulting invoicing from a hopeful send into a documented handoff.