Can I invoice clients for work completed before onboarding in the US?

Can you invoice clients for work completed before onboarding in the US?

If you run a service business, freelance, consult, or operate an agency, you’ve probably faced this situation: you started work for a client, delivered value, and only afterward did the “official” onboarding happen. Maybe the client wanted a quick win before committing, maybe procurement dragged its feet, or maybe everyone agreed verbally and you jumped in to help. Then the practical question hits: can you invoice for work completed before onboarding in the US?

The short, useful answer is usually “yes”—but only if you can clearly establish that the client requested or accepted the work and that you’re charging a fair, agreed-upon amount under terms that make sense. The longer answer is where it matters, because the risks aren’t only legal. They’re also operational: delayed payment, disputes, damaged relationships, and accounting/tax issues. This article walks through how it typically works in the US, what can go wrong, and how to invoice pre-onboarding work in a clean, professional way that clients are more likely to pay without friction.

What “onboarding” really means in billing terms

“Onboarding” can mean different things depending on the company. For a solo client, onboarding might just be an email that says “Go ahead.” For a larger business, onboarding might include vendor registration, W-9 collection, a signed master services agreement (MSA), a statement of work (SOW), insurance certificates, security questionnaires, purchase orders (POs), and approval workflows.

From a billing standpoint, onboarding is not a magic switch that determines whether you can charge. What matters is whether there was an agreement—written, verbal, or implied by actions—and whether the client accepted the benefit of your work. In other words, invoicing pre-onboarding work is usually about contract formation and proof, not about the onboarding checklist.

Is a contract required to invoice for pre-onboarding work?

In the US, you do not always need a formally signed contract to bill for work. Many agreements are enforceable even if they are not in a single signed document. A contract generally requires an offer, acceptance, and consideration (something of value exchanged). That can happen through email threads, chat messages, proposals the client approved, or even through conduct—like the client asking you to deliver something and then using what you delivered.

That said, the absence of a signed agreement increases your risk. It doesn’t always stop you from invoicing, but it can make disputes harder to resolve. If the client later claims they didn’t authorize the work or didn’t agree to the price, you may have to rely on your documentation, industry norms, and the reasonableness of your fee.

Common scenarios where pre-onboarding invoicing is normal

Pre-onboarding invoicing is more common than people think. Here are situations where it often happens without issue:

Emergency or rush support. A client’s system breaks, a deadline is imminent, or a crisis needs immediate attention. They ask you to start now and deal with vendor paperwork later.

Paid discovery or audit. The client wants a small paid assessment before committing to a longer project. They may not want full onboarding until they decide to proceed.

Trial period or pilot. You do a limited pilot, then transition into a longer engagement. The pilot is still billable work.

Scope creep before the paperwork catches up. You start with an informal request, then a formal SOW comes later. The earlier work can still be billed if it was requested or accepted.

Procurement delays. The business wants you, the stakeholders approve, but procurement onboarding takes weeks. Many vendors bill for time worked during the delay, as long as the stakeholder authorized it.

Key question: did the client authorize or accept the work?

The most important issue is not “Were we onboarded?” It’s “Did the client authorize the work or knowingly accept it?” Authorization can be explicit (“Yes, start this now”) or implicit (they give you access credentials, schedule calls, provide requirements, review deliverables, request revisions, or deploy what you delivered).

Acceptance can also show up in client behavior. If they used the deliverable, incorporated your recommendations, published the content, shipped the code, ran the campaign, or benefited financially from your work, they’ve effectively acknowledged value was delivered. That strengthens your position when you invoice for it.

Why pre-onboarding invoices get disputed

Even if you’re entitled to bill, pre-onboarding invoices can cause friction for practical reasons. Understanding the common causes helps you prevent them.

They can’t pay without a vendor record. In large companies, accounts payable often cannot process payment until you’re set up in their system. A stakeholder may approve your invoice, but finance still rejects it until onboarding is complete.

No purchase order was issued. Some organizations require a PO before any work starts. If you worked without one, the stakeholder might need special approval to pay you.

Rate or scope wasn’t pinned down. If the client didn’t clearly agree to your pricing or expected a different scope, they may push back.

Internal politics. The person who asked you to start may not be the person who controls payment approvals. If leadership didn’t expect the expense, they might challenge it.

Confusion about “free” work. Some clients assume early work was part of a sales process and therefore free, unless you stated it was billable.

How to protect yourself before you start work

If you anticipate onboarding delays, you can take steps upfront that dramatically reduce payment issues later—even if you start work tomorrow.

1) Confirm scope and pricing in writing

You don’t need a 20-page contract to be professional. A simple email can be enough if it clearly states:

• What you will do (scope)
• What you will deliver (deliverables)
• When you will deliver it (timeline)
• How you will charge (hourly, fixed fee, retainer)
• What the rate or fee is
• When payment is due

Ask the client to reply with approval. That reply becomes strong evidence of authorization.

2) Use a short “pre-onboarding work authorization” message

If you’re starting quickly, send a short note like: “Confirming you’d like us to begin work immediately while your onboarding is in progress. We will invoice for time spent and deliverables completed during this period at the agreed rate.”

This makes it hard for anyone later to claim they assumed it was free.

3) Track time and deliverables meticulously

Pre-onboarding disputes often come down to details. Keep a clear log of:

• Dates worked
• Hours spent (if hourly)
• Tasks completed
• Files delivered or meetings held
• Client requests and feedback

This doesn’t just help with disputes—it also makes your invoice easier for the client to approve.

4) Clarify who has authority to approve work

When possible, identify the person who can approve spend. Ask: “Who should approve the invoice for this initial work while onboarding is underway?” If you get that answer in writing, you reduce the risk of “I didn’t approve this.”

5) Consider a deposit or upfront payment

If you have any doubt, requesting an upfront payment for the initial phase can be the cleanest solution. Many freelancers and agencies treat pre-onboarding work as a paid kickoff or paid discovery with payment due before delivery.

Clients who are serious usually understand this, especially if onboarding is going to take time.

What if the client says they can’t pay for pre-onboarding work?

This happens most often with enterprise clients that have strict procurement rules. If they truly can’t process payment until onboarding is complete, you still have options:

Option A: Delay invoicing but document the work. Continue working (only if you trust the client), track everything, and issue the invoice once onboarding is complete. Make sure the client confirms in writing that the work will be paid once the vendor setup is done.

Option B: Pause work until onboarding is complete. This is the safer approach if you’re not comfortable carrying the risk. You can say: “Happy to continue as soon as vendor setup is approved so we can invoice properly.”

Option C: Break the work into a paid micro-engagement. Offer a small fixed-fee engagement (e.g., a diagnostic report) that the client can pay through a simpler method or quicker approval path. Sometimes smaller amounts don’t require the same approvals.

Option D: Use a credit card payment for the initial phase. Some businesses can pay by card even when vendor onboarding is pending. If you can accept card payments, this can bypass some procurement delays.

How to structure the invoice for pre-onboarding work

The way you present the invoice matters. Clear, organized invoices get approved faster and are less likely to be disputed.

Include a clear billing period

State the dates the work was performed. For example: “Service Period: January 5, 2026 – January 19, 2026.”

Label it as “Initial services” or “Pre-onboarding services”

Use a line item label that frames the context without sounding defensive. Examples:

• “Initial consulting services (pre-onboarding)”
• “Kickoff and discovery (authorized prior to vendor setup)”
• “Emergency support and stabilization”

Use line items that match client expectations

If the client expects a PO-style breakdown, mirror that. If they prefer a deliverable-based invoice, list deliverables. If they prefer time-based billing, provide time entries or a summarized timesheet.

For hourly work, consider grouping time by workstream (e.g., “Strategy,” “Implementation,” “Meetings”) rather than listing every tiny entry, unless the client specifically requests detail.

Add concise supporting notes

A brief note can prevent confusion. For instance: “Work performed at client request while onboarding and vendor registration were in progress.” Keep it factual and short.

Use consistent payment terms

Include payment terms (Net 7, Net 15, Net 30) and a due date. If you want payment earlier because the work happened before onboarding, be explicit: “Due upon receipt” or “Net 7.”

Just remember: setting an aggressive due date doesn’t guarantee faster payment if the client’s internal process is slow. Clear terms help, but process constraints still apply.

Send invoices promptly

Invoice as soon as the milestone is complete. Delayed invoicing increases the chance someone forgets the context, changes roles, or questions why the invoice is “so late.”

How to communicate the invoice to the client

When you send the invoice, include a short email message that reminds them what it covers. For example:

“Attached is the invoice for the initial work completed between [dates], including [high-level tasks]. This work was completed at your request while vendor onboarding was in progress. Please let me know if you’d like the invoice addressed to a specific entity name or if you need it formatted to match your accounts payable requirements.”

This reduces back-and-forth and signals that you’re used to professional billing workflows.

Handling purchase orders and enterprise procurement rules

Purchase orders can complicate pre-onboarding billing. Many large organizations require a PO before they can legally or procedurally pay an invoice. If you do work without a PO, you might still be able to get paid, but it can become a “retroactive PO” request, which some finance teams resist.

If you’re dealing with a company that uses POs, try these approaches:

Ask for a PO number before starting. Even if vendor onboarding is pending, sometimes the business can issue a PO quickly.

Request written confirmation that a retroactive PO will be issued. If they insist you start without it, ask them to confirm they will issue a PO covering the initial period.

Keep the initial scope small. The bigger the invoice, the harder it may be for someone internally to justify a retroactive approval.

Align invoice descriptions with PO line items. If the PO uses specific language, match it in your invoice line items to reduce rejection risk.

What about independent contractor classification and onboarding paperwork?

Onboarding often includes tax forms (commonly a W-9 for US persons) and sometimes onboarding questionnaires. Clients may delay payment until they have your paperwork, not because the work is invalid, but because they need it to comply with their accounting and tax reporting obligations.

To avoid delays:

• Provide your W-9 promptly when requested
• Ensure your legal name or business name matches what you put on invoices
• Use consistent address details
• If you operate as an LLC or corporation, invoice under the correct entity name

Inconsistent vendor details cause payment holds even when the invoice itself is fine.

Is it legal to invoice retroactively?

In general, invoicing after work is completed is normal—most invoices are “retroactive” in that sense. The legal risk is not the timing; it’s whether the charge is legitimate and authorized.

If you performed work without authorization and then invoice later, the client can argue they never agreed to pay. But if the client asked for the work, knew you were performing it as a paid professional, and accepted the benefit, invoicing after the fact is generally a routine business practice.

What if there was no agreement on price?

This is where problems arise. If you start work without confirming rates or fees, you may still have a claim for reasonable compensation, but “reasonable” can be argued.

To reduce this risk, always document one of the following before starting:

• An hourly rate (and any minimums)
• A fixed fee for a defined deliverable
• A retainer amount and what it covers

If you didn’t do that and you’re already past the point of no return, be practical: propose a fair amount that aligns with industry norms, show a clear breakdown, and communicate openly. Many clients will pay if your invoice is reasonable and the value is obvious.

How to deal with disputes about pre-onboarding work

If a client disputes a pre-onboarding invoice, keep your response calm and documentation-based. The goal is to resolve the issue quickly, not “win an argument.”

Step 1: restate the authorization and scope

Reply with the specific email or message where the work was requested or approved. Keep it factual: “On [date], you requested [task] and confirmed we should proceed.”

Step 2: show evidence of delivery and acceptance

Point to deliverables, meeting notes, shared files, or outcomes. If they used your work, mention that gently: “The deliverable was provided on [date] and feedback was incorporated on [date].”

Step 3: offer a reasonable path forward

If the dispute is about process (PO missing, vendor setup incomplete), propose solutions: reissue the invoice with vendor details, add a PO number once issued, or split the invoice into smaller parts if that helps their internal approvals.

Step 4: decide whether to pause work

If you’re still working with the client, consider pausing until the billing issue is resolved. Continuing to work while an invoice is disputed can compound your risk.

Cash flow and accounting considerations for pre-onboarding invoices

Even when everything is above-board, pre-onboarding work can stress cash flow. If you frequently face onboarding delays, consider building your process around it.

Use milestones. Break work into smaller, invoiceable phases so you’re not carrying long periods of unpaid labor.

Use shorter payment terms for early phases. A Net 7 kickoff invoice is easier to justify than waiting months to bill a large amount.

Keep your invoicing consistent. Consistency signals professionalism and reduces the chance your invoice gets flagged as unusual.

Track receivables actively. Pre-onboarding invoices sometimes fall into a “nobody owns it” gap inside the client organization. Follow up with the stakeholder and accounts payable.

Best practices for invoicing pre-onboarding work with invoice24

When you’re billing for work completed before onboarding, the goal is to make the invoice effortless to approve. invoice24 is designed for exactly this kind of professional invoicing workflow—clear line items, organized billing periods, consistent client details, and easy sharing.

Create a dedicated client profile

Even if the client’s vendor onboarding isn’t complete, you can create a client profile with the best-known billing details. When the client later provides official billing information (legal entity name, address, AP email, PO requirements), you can update the profile and keep everything consistent going forward.

Use line-item detail that matches the engagement

For hourly work, list hours and rates clearly, grouped by category. For fixed-fee work, list deliverables with short descriptions. invoice24 lets you structure the invoice so it’s readable and professional, which reduces approval friction.

Add a service period and project reference

Include the date range of the work and a project reference or internal label the client recognizes (for example, “Q1 Kickoff,” “Security audit,” or “Website stabilization”). This helps the stakeholder route the invoice internally without confusion.

Set clear payment terms and due dates

When invoicing pre-onboarding work, you want clear expectations. With invoice24 you can set payment terms, display a due date, and keep your terms consistent across invoices. This is especially helpful when you later move into a recurring cadence.

Duplicate templates for recurring engagements

If the client becomes ongoing, you can reuse invoice templates so each invoice has the same structure and wording. That consistency helps accounts payable process payments faster over time.

Maintain an audit-friendly record

Keep your invoices, notes, and billing history organized. If a client later asks for clarification—“What was this for?”—you can quickly provide a clean breakdown of the services performed and the dates involved.

Practical invoice wording you can use

Here are invoice-friendly descriptions that are professional and non-confrontational:

Hourly consulting:
“Initial consulting services provided at client request during vendor onboarding period (Service Period: [dates]).”

Discovery phase:
“Kickoff and discovery: requirements review, stakeholder interviews, and written recommendations (Service Period: [dates]).”

Emergency support:
“Emergency support and remediation: diagnosis, stabilization, and follow-up guidance (Service Period: [dates]).”

Implementation deliverables:
“Implementation services: configuration and deployment of agreed deliverables (Service Period: [dates]).”

You can adapt these to your industry while keeping the framing consistent: authorized work, clear time window, clear deliverables.

When you should not invoice for pre-onboarding work

There are times when invoicing is risky or simply not appropriate. Consider not invoicing (or renegotiating) if:

• The client never asked for the work and you did it proactively without clear agreement
• The work was explicitly positioned as a free sample or part of a sales pitch
• The deliverables were never delivered or the client did not accept them
• You cannot reasonably document what you did or when you did it
• The amount is far higher than what the client could have expected based on prior discussions

In these situations, you may need to treat the work as business development, negotiate a smaller amount, or use it as a lesson to tighten your authorization process next time.

How to prevent this problem going forward

If you frequently run into “work before onboarding,” build it into your standard workflow.

Create a simple kickoff authorization step

Before starting any work, require one of the following:

• A signed proposal, or
• A written approval email, or
• Payment of a kickoff invoice, or
• A PO number (for PO-based clients)

This single step eliminates most disputes later.

Use paid discovery as your default entry point

Paid discovery is a structured way to start quickly without long contracts. It’s a small engagement with clear scope and price. Once complete, you roll into a longer agreement. Clients often prefer this because it reduces their risk and speeds up decisions.

Set expectations about procurement delays

If you suspect a client’s procurement process will be slow, address it early: “We can begin immediately, but invoices are still due based on work performed. If your internal process can’t pay until vendor setup is complete, we can either pause work or structure the kickoff as an upfront payment.”

This is professional, direct, and saves you from surprises.

Keep your invoice-ready details consistent

Make sure your business details are stable across invoices: your business name, address, and contact information. Inconsistent details are one of the most common reasons invoices get stuck in accounts payable systems.

Frequently asked questions

Can I invoice a client if the contract was signed later?

Often, yes. If the work was authorized or accepted and the later contract does not explicitly exclude earlier work, it’s common to invoice for the earlier services. It’s even better if the contract includes language that it covers services starting from a specific date, including work already performed.

What if the client says the earlier work wasn’t covered?

Then treat it as a separate mini-engagement. Provide the documentation showing authorization and deliverables, and offer to issue a separate invoice for the pre-contract period. If needed, ask the client to confirm in writing that they accept the earlier invoice as valid.

Do I need to change the invoice date to match the work date?

No. The invoice date is typically the date you issue the invoice. The work date is captured through the service period or line-item descriptions. Keep both clear: invoice date for billing, service period for what you did.

Should I add late fees for delayed onboarding payments?

Late fees can be appropriate, but use them carefully with enterprise clients. Often, delays come from process rather than unwillingness to pay. If you use late fees, state them clearly in your payment terms and be prepared to waive them as a relationship tool when delays are procedural.

Can I require payment before starting work if onboarding isn’t complete?

Yes. Many service providers require a deposit or kickoff payment before beginning, especially for new clients. It’s one of the simplest ways to avoid being stuck waiting on procurement.

Conclusion: yes, but invoice smart

In the US, you can usually invoice clients for work completed before onboarding as long as the work was authorized or accepted and the amount is reasonable and consistent with what was agreed. The bigger risk is not whether invoicing is “allowed,” but whether the client’s internal process and documentation are strong enough to approve and pay without friction.

Your best protection is simple: confirm scope and pricing in writing, document what you do, invoice promptly with clear service periods, and communicate like a professional. When onboarding delays happen, structure early work as a paid kickoff or discovery phase, or request a deposit so you’re not financing the project yourself.

With invoice24, you can present pre-onboarding work in a clean, approval-friendly invoice format—clear line items, clear dates, consistent client details, and professional terms—so you get paid faster and keep the relationship strong from day one.