Why Big Invoices Get Paid Last (And How to Fix It)

Title tag: Why Big Invoices Get Paid Last (And How to Fix It) | PayFly Meta description: Invoices over $20,000 are three times more likely to be paid late. Here is how to split large projects into smaller invoices that get paid on time. Keyword: freelancer invoice payment, late payment freelancer Word count target: 900-1,200

TL;DR

Invoices over $20,000 are three times more likely to be paid late than smaller ones, according to data from Bonsai. Large invoices trigger additional internal approvals, executive sign-offs, and budget reviews that small invoices skip entirely. The fix is to break large projects into milestone invoices of $3,000 to $5,000 each, due at project checkpoints rather of all at once. Smaller invoices move through client accounts payable faster, require fewer approvals, and give freelancers cash flow throughout the project instead of one lump sum at the end.

Why Big Invoices Sit the Longest

A client who pays a $1,500 invoice the day it arrives will let a $25,000 invoice sit for 45 days. The delay is not about willingness to pay. It is about what happens inside the client's company when an invoice crosses a certain dollar threshold.

Most companies have tiered approval processes. Invoices under $5,000 might go straight to accounts payable with a single manager sign-off. Invoices between $5,000 and $15,000 often need department head approval. Anything over $20,000 frequently requires executive sign-off from someone who was not involved in the project, has never met the freelancer, and has 40 other things on their plate.

Each approval layer adds days. A manager approves the invoice in two days. The department head takes another week. The controller sends it to the CFO, who reviews it during the next budget cycle. The $25,000 invoice that should have been paid in 30 days takes 55.

This is not a client problem. It is a structural problem with how large organizations process payments. The freelancer cannot change the client's internal approval chain, but the freelancer can structure invoices to avoid triggering it.

The $20,000 Tipping Point

Bonsai's payment data shows that invoices over $20,000 are three times more likely to be paid late than invoices under $5,000. The data tracks thousands of freelance invoices across multiple industries and client types, and the pattern holds regardless of client size, industry, or payment terms.

The reason is simple accounting mechanics. Large invoices get flagged for review. Someone in the client's finance department wants to verify the work was completed before approving payment. That verification step means scheduling a call with the project lead, confirming deliverables, and checking the original contract terms. Each step adds time.

Invoices under $5,000 routinely clear accounts payable without verification. The amount is small enough that the risk of paying for incomplete work is acceptable. The approval path is shorter, the review is lighter, and the payment moves faster.

How to Split Large Projects Into Milestone Invoices

Break projects into $3,000 to $5,000 chunks

A $15,000 website project should not be one $15,000 invoice. It should be four invoices: a $4,500 deposit, a $3,500 invoice at the design approval milestone, a $4,000 invoice at the development milestone, and a $3,000 invoice at launch. Each invoice stays under the threshold that triggers extended approval chains at most companies.

The deposit invoice goes out before work starts. This is the easiest invoice to collect because the client has already agreed to the project and has not yet received any work. A 2.9% card payment through a platform like PayFly clears the same day. On a $4,500 deposit, the fee is $130.50. The freelancer keeps $4,369.50 and starts the project with cash in the bank instead of waiting 30 days for the client to process a paper invoice.

Tie each invoice to a deliverable, not a date

Milestone invoices work best when they are tied to a specific deliverable the client has received and approved. "50% due at project start, 50% due at completion" is a common structure, but it leaves the freelancer waiting for the final payment with no leverage. A better structure: deposit due before kickoff, design invoice due when the design is approved, development invoice due when the staging site is live, final invoice due at launch.

Each milestone gives the client something they want before the next phase starts. The freelancer has something to invoice against. The client cannot delay the next phase without paying the current invoice. This structure turns payment from a request into a prerequisite.

Send invoices the moment the milestone is hit

The biggest mistake freelancers make with milestone invoicing is waiting. The design is approved on Tuesday, but the invoice goes out Friday. Those three days are three days of payment delay that compound across the project. Send the invoice the same day the milestone is approved. The sooner the invoice arrives, the sooner it enters the client's payment queue.

A $3,500 invoice sent on Tuesday arrives in the client's accounts payable system by Wednesday. The approval clears by Friday. Payment processes the following week. Total time from milestone to cash in bank: 10 to 14 days.

A $15,000 invoice sent at project completion arrives in the client's accounts payable system and immediately gets flagged for executive review. The approval takes two weeks. Payment processes the week after that. Total time from completion to cash in bank: 30 to 45 days.

The freelancer who splits the project into four $3,500 invoices collects all four payments in roughly the same time the lump-sum freelancer collects one.

The Math on Splitting vs. Lump Sum

Consider a $12,000 project with two payment structures.

Lump sum structure:

$0 deposit, $12,000 due at completion
Invoice sent on Day 30 (project completion)
Client processes through executive approval: 35 days
Cash in bank: Day 65

Milestone structure:

$3,000 deposit, due on Day 1
$3,000 at design approval, Day 10
$3,000 at development milestone, Day 20
$3,000 at launch, Day 30
Each invoice clears in 12 days on average
Deposit clears Day 13, design clears Day 22, development clears Day 32, launch clears Day 42

The milestone freelancer has $9,000 in the bank by the time the lump-sum freelancer sends their first invoice. The lump-sum freelancer waits until Day 65 for the full $12,000, assuming the client does not dispute the final amount after receiving all the work.

What to Put in the Contract

Milestone invoicing only works if the payment schedule is in the contract before the project starts. A freelancer who proposes milestone billing after the project has already begun will face resistance. Clients agree to payment structures during negotiations, not after work has started.

The contract should specify the dollar amount of each invoice, the milestone it is tied to, and the payment terms for each. "50% deposit due upon signing, 25% due upon design approval, 25% due upon project launch" is clear and enforceable. "Invoice will be sent at project milestones" is vague and gives the client room to argue about timing.

Include late fee terms in the contract as well. A standard clause: "Invoices unpaid after 15 days are subject to a 1.5% monthly late fee." Most clients will never trigger the late fee, but having it in the contract signals that payment timing is a serious expectation, not a polite suggestion.

When Lump Sum Invoices Make Sense

Not every project needs milestone invoicing. A $2,000 project is small enough that a single invoice will clear accounts payable without extended delays. A recurring monthly retainer is already structured as a small monthly payment. A project with a trusted long-term client who pays within terms every time does not need the protection of milestones.

Milestone invoicing is for the projects in the danger zone: $8,000 and up, with new clients or clients with a history of slow payment. Those are the invoices that sit. Those are the projects where splitting the bill into smaller chunks is the difference between getting paid in two weeks and getting paid in two months.

Frequently Asked Questions

How small should each milestone invoice be?

The sweet spot is $3,000 to $5,000 per invoice. This amount is large enough to be worth the administrative overhead of invoicing but small enough to avoid triggering extended approval chains at most companies. For projects under $5,000 total, a single invoice is fine.

What if the client refuses to pay a deposit?

A client who refuses to pay a deposit before work starts is a client who will be slow to pay at every other milestone. The deposit is a commitment signal. If the client will not commit before the project begins, the freelancer is taking on all the risk. Declining the project or requiring full upfront payment is appropriate when a client resists a reasonable deposit.

Does offering card payment speed up collection?

Yes. Invoices with a payment link get paid faster than invoices that require the client to process a bank transfer. A PayFly invoice with a one-click card payment option lets the client pay the moment they open the email. The 2.9% fee on a $3,500 invoice is $101.50. The freelancer keeps $3,398.50 and has the money the same day instead of waiting 14 days for a bank transfer.

How many milestones should a project have?

Three to five milestones is typical. Fewer than three and the invoices are too large. More than five and the project becomes an invoicing exercise. The right number depends on the project's natural phases. A website project has clear phases: kickoff, design, development, launch. A consulting engagement might have phases tied to deliverable submissions every two weeks.

Can milestone invoicing hurt the client relationship?

Milestone invoicing actually improves client relationships because the client never receives a surprise bill. Each invoice is expected, tied to a deliverable the client has already seen, and for an amount they agreed to in the contract. The alternative, a single large invoice at the end, is when clients feel surprised and start questioning the total.

Internal links:

JSON-LD: Article

JSON-LD: FAQPage