The Cash-Flow Manifesto: Why Net-00 (Due Upon Receipt) is the Only Invoicing Term That Makes Sense for New Clients

Set your invoice terms deliberately.

For a new, unverified client, Due Upon Receipt can be one of the strongest default payment terms you can use, particularly for small starter projects where you can reasonably separate review work from final delivery.

You do not need to apologize for it.

You do not need to pretend that your freelance business is a bank.

And you do not need to automatically accept Net-30 simply because a client’s accounting department prefers it.

But there is an important distinction:

Due Upon Receipt is a powerful commercial strategy—not a universal legal rule, and not automatically the right answer for every client, project, or jurisdiction.

That distinction matters.

If a large established company has a mandatory 30-day procurement cycle, walking away from a valuable, low-risk engagement may make less sense than accepting Net-30 with appropriate contractual protections.

If an unknown client wants a $1,500 starter project completed immediately but refuses to pay until 30 days after delivery, however, you should stop and think before giving that client unsecured credit.

You are providing a service.

You are carrying business expenses.

You are allocating your time.

And once the final deliverables are released, your practical leverage can become dramatically weaker.

That is the real reason to think carefully about Net-00.

A quick definition: What does “Due Upon Receipt” actually mean?

“Due Upon Receipt” generally communicates that payment is expected when the invoice is received rather than after a stated 15-, 30-, 45-, or 60-day credit period.

But do not confuse the phrase with a magic legal formula.

The safest approach is to make the payment obligation precise in your contract, proposal, statement of work, and invoice.

If the exact timing matters to your business, consider using language such as:

Payment due upon receipt of invoice and before release of final deliverables.

Or, where appropriate:

Payment is due immediately upon receipt. Final commercial-use files, source files, credentials, or other agreed deliverables will be released after cleared payment.

The exact language should match your contract and the law governing the relationship.

For a broader explanation of freelancer payment structures, see Freelancer Payment Terms Guide: Avoid Net 60 & Late Payments.

---

1. Why New Clients Create a Different Payment Risk

There is an enormous difference between:

“A client has paid me reliably for 18 months.”

and:

“A company I met last Tuesday wants $2,500 of work and wants 30 days of credit.”

The second situation contains uncertainty.

You may not know:

• whether the client pays contractors reliably;
• how long its Accounts Payable process takes;
• whether the person hiring you actually has authority to approve payment;
• whether the company has cash-flow problems;
• whether the project will be disputed after delivery;
• whether procurement will reject your invoice;
• whether the client will ask for additional work before paying;
• or whether the person who hired you will disappear.

That does not mean every new client is dangerous.

It means you do not yet have payment history.

And payment history is valuable information.

A sensible payment policy therefore distinguishes between new relationships and established relationships.

A new client may receive stricter terms.

An established client who has paid 12 invoices on time may receive more flexibility.

That is not hostility.

It is ordinary risk management.

If you want to understand the broader difference between Net-15, Net-30 and Net-45, read Net 15 vs. Net 30 vs. Net 45: Which Payment Terms Protect Your Cash Flow?.

---

2. Net-30 Is Credit—and Freelancers Should Recognize What They Are Giving

When you agree to Net-30 after completing and delivering the work, you are effectively agreeing to wait for payment for a period of time.

Commercially, that creates a form of trade credit.

You have performed.

The client has received the benefit of your performance.

But your money remains outstanding.

That is not necessarily bad.

Businesses routinely use negotiated payment terms.

In fact, the legal framework in many jurisdictions recognizes that commercial parties can agree on payment periods. For example, the Uniform Commercial Code contains rules dealing with payment timing where the parties have not otherwise agreed, illustrating why the actual contract terms matter.

The point is not that Net-30 is illegal.

It is not.

The point is that you should understand the economic consequence before agreeing to it.

If you complete a $2,000 project on June 1, deliver everything on June 2, and receive payment on July 2, you have financed the client’s use of your work for approximately a month.

Meanwhile, you may still have:

• software subscriptions;
• contractor payments;
• rent;
• taxes;
• payment-processing costs;
• equipment expenses;
• and your own household obligations.

That is why cash flow matters.

If you regularly struggle with invoices after delivery, your problem may not be your collection strategy.

It may be your payment architecture.

---

3. The “Floating Credit” Problem Can Quietly Destroy a Freelance Business

Imagine this cycle:

Project A → deliver → wait 30 days → Project B → deliver → wait another 30 days.

Now imagine that Project B starts before Project A has been paid.

You are constantly producing new work while older receivables remain outstanding.

That creates a dangerous illusion.

Your calendar looks full.

Your workload looks healthy.

Your pipeline looks excellent.

But your bank account tells a different story.

This is the floating-credit problem.

You can reduce it by structuring your engagements around:

• deposits;
• milestones;
• Due Upon Receipt invoices;
• payment before final delivery;
• shorter Net terms for trusted clients;
• and clear suspension rights for overdue accounts.

For example, a $6,000 project could potentially be structured as:

40% upfront → 30% milestone → 30% before final delivery.

That can be considerably safer than:

$6,000 work completed → everything delivered → Net-30 invoice.

If you already have a retainer system, you should also consider what happens when the client’s balance reaches zero. Our guide on The Retainer Exhaustion Warning: How to Auto-Notify Clients When Their Balance Hits $0 explains how to build that warning system.

---

4. The $800 Starter Project: How Payment Terms Change Your Leverage

Consider a hypothetical developer named Mark.

Mark is approached by an agency that wants an $800 bug-fix sprint.

The work takes three days.

Mark completes the work, pushes the code to the client’s environment, and sends a Net-30 invoice.

The agency now has the functional benefit of the work.

Mark has the invoice.

Thirty days later, there is no payment.

At Day 40, Accounts Payable says the invoice is being processed.

At Day 50, the project manager says the accounting department needs additional documentation.

At Day 60, Mark is still waiting.

The problem is not simply that the client is late.

The problem began when Mark gave away the most valuable practical leverage he had before receiving payment.

Now change the structure.

Mark completes the work on a staging environment.

He gives the client a reasonable opportunity to review and test it.

He sends the invoice.

The invoice says:

Due Upon Receipt.

The contract states that final production deployment occurs after payment.

Now the conversation is different.

The client can evaluate the work.

Mark has demonstrated performance.

But the final transfer of the agreed deliverable remains tied to the contractual payment structure.

That is a much more deliberate commercial position.

If a client already has your work and refuses to pay, the situation changes. See What to Do When a Client Uses Your Work But Refuses to Pay You for a broader recovery framework.

---

5. The Most Important Rule: Do Not Confuse “Review” With “Final Delivery”

This is where many freelancers make their biggest mistake.

They believe the client needs the final files in order to review the work.

Often, that is not true.

Depending on the project, you may be able to provide:

• a staging URL;
• a watermarked design;
• a low-resolution preview;
• a limited-access prototype;
• a demo environment;
• a review copy;
• or another agreed evaluation method.

Then final delivery can occur after the agreed payment condition is satisfied.

For visual projects, see How to Watermark Your UI/UX Deliverables Without Ruining the Presentation.

For source files, see Client Asking for PSD Files Before Payment or AI Files Before Payment? Here’s What to Do.

For Figma projects, see How to Revoke Access to Figma Files After Non-Payment (Safe & Legal Method).

The exact approach depends on the contract and the nature of the work.

Do not simply delete a client’s production files, shut down infrastructure, or interfere with systems because an invoice is unpaid.

Your contract and applicable law should determine what you can suspend, withhold, revoke, or enforce.

---

6. Due Upon Receipt Works Best When the Contract Says the Same Thing

An invoice should not be the first place where the client discovers your payment terms.

Ideally, your payment structure should appear consistently across:

1. Proposal
2. Statement of work
3. Contract
4. Invoice
5. Payment reminder
6. Final-delivery notice

This creates a coherent paper trail.

For example:

Proposal:
“Initial projects are payable upon receipt.”

Contract:
“Payment for the initial project is due upon receipt of invoice.”

Invoice:
“Payment Terms: Due Upon Receipt.”

Delivery notice:
“Final production assets will be released following cleared payment in accordance with the agreement.”

That is much stronger than sending a surprise invoice with “Due Upon Receipt” after the project has already been completed.

For a deeper look at structuring proposals as protective contractual documents, read How to Structure a Proposal So It Functions Like a Real Legal Defense Contract.

And if your agreement exists primarily through email, see How to Turn an Email Trail into a Legally Defensible Invoice Statement.

---

7. How to State Your Net-00 Policy Without Sounding Difficult

You do not need to write:

“I refuse to work with anyone who doesn’t pay immediately.”

That sounds combative.

Instead, make your policy sound routine.

For example:

“Because this is our initial engagement, my standard payment policy for starter projects is payment upon receipt. Once we’ve established a successful payment history, I’m happy to discuss alternative terms for larger engagements.”

That sentence accomplishes several things.

It:

• establishes a boundary;
• explains the reason;
• avoids accusing the client of being untrustworthy;
• leaves room for a future relationship;
• and sounds like a business policy rather than a personal demand.

That is the tone you want.

---

8. Procurement Pushback: What If the Client Says “Our Policy Is Net-30”?

This is where good freelancers sometimes panic.

The Accounts Payable representative says:

“Our company policy requires Net-30 for all vendors.”

Your first response should not be:

“Fine.”

But it should not be:

“Your policy is ridiculous.”

either.

Ask questions.

Ask whether the policy is mandatory

Sometimes the project manager genuinely has no ability to change the terms.

Sometimes there are different payment methods available.

Sometimes a small project can be processed differently.

Sometimes the vendor system requires onboarding regardless of invoice size.

And sometimes Net-30 really is non-negotiable.

The important thing is to find out before you perform substantial work.

Ask when the payment clock starts

This question is often more important than the label “Net-30.”

Ask:

“Does the 30-day period begin when I submit the invoice, when Accounts Payable approves it, or after the work is accepted?”

That distinction can materially affect cash flow.

Ask about invoice requirements

Some companies will reject an otherwise valid invoice because it lacks:

• a purchase order;
• vendor information;
• tax information;
• a project number;
• a billing contact;
• or a required submission method.

Government contracting rules, for example, can contain detailed invoice requirements and specific payment calculations. The federal regulations illustrate why payment timing can depend on proper invoice submission and contract requirements rather than simply the date printed on an invoice.

If your invoice enters an accounting system incorrectly, “Net-30” can become Net-30 plus another administrative delay.

That is exactly what you want to prevent.

---

9. When You Should Accept Net-30 Anyway

This is the section that turns a manifesto into an authoritative guide.

Due Upon Receipt should not become a religion.

There are legitimate situations where Net-30 may make commercial sense.

Consider accepting Net-30 when:

• the client is established and has a strong payment history;
• the project value is comfortably within your cash-flow capacity;
• the client has a documented procurement process;
• the contract clearly defines acceptance and payment;
• you receive a meaningful upfront payment;
• you retain appropriate contractual protections;
• the engagement is strategically valuable;
• or refusing Net-30 would create more business risk than accepting it.

For example:

$20,000 project

Could be:

• $8,000 upfront;
• $6,000 milestone;
• $6,000 Net-30.

That is very different from:

$20,000 project → 100% delivered → Net-60.

Payment terms should therefore be evaluated together with project size, counterparty risk, leverage, and delivery structure.

---

10. The Three-Question Net-30 Decision Test

Before accepting delayed payment from a new client, ask:

Question 1: Can my business comfortably survive a total default?

Not “Will they probably pay?”

Ask:

“If they don’t pay, what happens to my business?”

If a $1,000 invoice is inconvenient but survivable, your risk is different from a $20,000 invoice that would disrupt payroll, rent, taxes, or essential operating expenses.

Question 2: What leverage remains after delivery?

Can you:

• retain source files?
• delay final commercial rights?
• suspend future services?
• withhold a milestone?
• stop further work?
• enforce a contractual remedy?

The answer depends on the contract and applicable law.

Do not assume that you automatically own every right simply because an invoice is unpaid.

Question 3: What do I know about the client?

Look at:

• business age;
• public presence;
• references;
• previous payment history;
• procurement requirements;
• contract clarity;
• and the identity and authority of the person hiring you.

This is risk assessment—not paranoia.

---

11. Payment Terms Risk Matrix

Payment structure	Practical control	Typical cash-flow risk	Best fit
Due Upon Receipt	High when final delivery remains outstanding	Lower	New clients and small starter projects
50% upfront / 50% Due Upon Receipt	High	Lower	Mid-sized projects
Milestone billing	Medium to high	Moderate	Multi-week projects
Net-15	Medium	Moderate	Clients with some payment history
Net-30	Medium to low	Higher	Established clients or procurement-driven companies
Net-60/90	Low	High	Only where the commercial upside justifies the financing risk

This is not a universal legal ranking.

It is a commercial risk framework.

The right structure depends on your industry, client, contract, jurisdiction, project value, and ability to withhold future work.

---

12. What the Law Says: Due Upon Receipt Is a Contractual Term, Not a Universal Escape Hatch

This distinction is critical.

A payment term can be contractually meaningful without overriding every applicable statute.

For example, New York’s Freelance Isn’t Free Act provides specific protections to covered freelance workers, including written-contract and timely-payment requirements. The New York Department of Labor provides a model freelance worker agreement and enforcement information.

The New York Attorney General also explains that, for covered freelance work, payment must be made on or before the contractual payment date; if no payment date is specified, a statutory deadline can apply.

That is why you should never tell a freelancer:

“Just put Due Upon Receipt on the invoice and the law guarantees immediate payment.”

It does not work that way.

The contract, applicable law, and facts of the engagement all matter.

---

13. United States: Do Not Assume There Is One Federal Freelancer Payment Rule

The United States does not have one universal commercial-freelancer payment rule that makes every private invoice due immediately.

Payment rights can depend on:

• contract terms;
• state law;
• the nature of the transaction;
• whether the client is a government entity;
• whether a specific freelancer-protection statute applies;
• and the remedies available in the relevant jurisdiction.

New York is a good example of a jurisdiction with specific freelance-worker protections. The New York Department of Labor provides official information about the state’s Freelance Isn’t Free Act.

For federal contracting, payment rules can be different again. Federal regulations prescribe specific payment processes and invoice requirements for government contracts.

That is why this article recommends commercial risk management, not a one-size-fits-all legal conclusion.

---

14. United Kingdom: Late Payment Rights Can Add Leverage

The UK has a statutory regime for qualifying commercial debts.

The official GOV.UK guidance states that statutory interest on qualifying late commercial payments is generally 8% above the Bank of England base rate, subject to the applicable contractual and statutory conditions. The government also provides information about fixed compensation for recovery costs.

That does not mean a freelancer should deliberately allow every invoice to become overdue.

The better strategy is still to structure the transaction so payment risk is controlled from the beginning.

For UK work, read the relevant official government guidance before relying on statutory interest or recovery compensation.

GOV.UK: Interest on late commercial payments

---

15. European Union: Payment Rules Are Not the Same as “Everything Is Due in 30 Days”

The EU Late Payment Directive establishes a framework intended to combat late payments in commercial transactions.

Official EU material states that businesses generally have a maximum 60-day period unless a different period is expressly agreed and is not grossly unfair, while public authorities generally have a 30-day period, subject to specified exceptions. The framework also provides for interest and compensation for qualifying late payments.

That does not mean every freelancer in every EU member state has identical rights in every transaction.

National implementation matters.

So if you are working with an EU client, identify the governing law and the relevant national rules instead of relying on a generic “EU law says 30 days” statement.

---

16. Why Your Contract Should Define Payment Before Your Invoice Does

An invoice records a payment obligation.

It should not be the only document creating that obligation.

Your contract should ideally identify:

• the price;
• payment schedule;
• invoice timing;
• payment method;
• late-payment consequences;
• milestone requirements;
• acceptance procedures;
• ownership or licensing provisions;
• suspension rights;
• termination rights;
• dispute procedures;
• and governing law where appropriate.

If you want to change payment terms later, do not simply change the invoice and assume the new term automatically applies.

The parties may need to agree to the change.

For contractless arrangements, read Can You Sue a Client Without a Contract? Real Legal Answer (2026).

And if the agreement exists through Slack, see Client Ghosted Final Invoice But We Only Agreed Via Slack. Can I Sue?.

---

17. Protecting Intellectual Property: Be Precise

A common freelancer strategy is:

“I retain copyright until payment.”

That can be useful.

But the legal effect depends on the contract, the type of work, applicable copyright law, and the rights already granted.

Do not assume that simply writing “copyright remains mine” on an invoice automatically reverses rights that were already granted by contract.

If intellectual-property ownership matters, put the provision in the agreement before the work is performed.

For work that has already been used without payment, see:

Client Stole My Website Code: Legal Steps to Respond, Prove Ownership, and Recover Access

Can You File a Copyright Infringement Claim for Unpaid UI Wireframes?

Client Used My Video Script Without Permission? How to Protect Your Explainer Video Copyright

The objective is not to threaten the client.

It is to ensure that your agreement clearly defines what the client receives, when the client receives it, and what happens if payment is not made.

---

18. What You Should Never Do Just Because an Invoice Is Unpaid

Strong payment boundaries do not mean you can take unilateral action against a client’s systems.

Do not assume that non-payment gives you permission to:

• delete production databases;
• shut down a client’s server;
• change passwords;
• lock the client out of infrastructure;
• delete website content;
• destroy project files;
• revoke essential business access;
• or interfere with third-party services.

Those actions can create serious legal and contractual problems.

For example, see Can I Shut Down a Client’s Server for Non-Payment? (Legal + Safe Method for Freelancers).

For hosting and domain disputes, see Can You Be Sued for a Client’s GoDaddy Account Dispute?.

A payment dispute is not permission to engage in digital self-help that violates your contract or applicable law.

---

19. The Evidence Checklist: Build Your File Before You Need It

If you decide to enforce a payment obligation, your documentation should tell a clean story.

Before starting work

Keep:

• the proposal;
• signed contract;
• statement of work;
• agreed price;
• agreed payment terms;
• client identity;
• billing information;
• and relevant communications.

During the project

Keep:

• milestones;
• approvals;
• revision requests;
• delivery records;
• screenshots;
• staging links;
• project-management records;
• and important email or messaging communications.

When invoicing

Keep:

• invoice number;
• invoice date;
• amount;
• payment terms;
• payment method;
• delivery status;
• and proof that the invoice was received.

When payment becomes overdue

Keep:

• follow-up emails;
• promised payment dates;
• AP responses;
• dispute notices;
• partial-payment records;
• and copies of every material communication.

For a structured follow-up system, see Unpaid Invoice Follow-Up Email Templates: Day 1 to Day 30 System.

And for corporate AP problems, see Client Says Your Invoice Was Lost? How to Get Paid by Corporate Accounts Payable.

---

20. Make Your Invoice Easy for Accounts Payable to Process

A surprising number of payment delays are administrative.

The invoice may be perfectly legitimate but still fail because it does not contain what the client’s accounting department needs.

At minimum, consider including:

• your legal/business name;
• client legal name;
• invoice number;
• invoice date;
• description of services;
• amount due;
• currency;
• payment terms;
• due date where appropriate;
• payment instructions;
• tax information where applicable;
• purchase-order information where required;
• and a reliable contact.

Federal contracting rules provide a useful illustration of how detailed invoice requirements can become in structured procurement systems.

For practical invoice design, see How to Design an Invoice That Accounts Payable Teams Can’t Ignore.

The easier you make payment, the fewer excuses your client has to delay it.

---

21. Give Clients a Fast Payment Path

Do not create unnecessary friction.

If your client can legally and commercially pay by:

• card;
• ACH;
• bank transfer;
• or another agreed method,

make the preferred method obvious.

The goal is not merely to demand immediate payment.

The goal is to make immediate payment easy.

That is a much more professional position.

You can even combine a standard Due Upon Receipt policy with an optional early-payment incentive.

For example, read Early Payment Discounts for Freelancers: How to Get Clients to Pay 5 Days Early.

---

22. The Net-00 Justification Email

Here is a cleaner way to explain the policy:

Hi [Client Name],

Thanks for reaching out about the starter project.

Because this is our initial engagement, my standard payment policy for starter projects is payment upon receipt. This allows me to keep the initial engagement straightforward while we establish a payment history together.

I have included a secure payment option with the invoice.

Once payment is confirmed, I will release the final deliverables in accordance with our agreed project terms.

For future larger engagements, I’m happy to discuss alternative payment schedules once we’ve established a successful working relationship.

Best regards,
[Name]

Notice what this email does not say.

It does not accuse the client of being untrustworthy.

It does not threaten legal action.

It does not say Net-30 is immoral.

It simply establishes a business policy.

---

23. Handling a Client Who Demands Net-30

If the client says:

“We only work on Net-30.”

You have four realistic options.

Option A: Accept the client’s terms

Do this when the client and project justify the cash-flow risk.

Option B: Negotiate a deposit

For example:

50% upfront + 50% Net-30.

This reduces your exposure.

Option C: Reduce the initial scope

Instead of accepting a $10,000 unsecured engagement, propose a $1,500 starter phase.

Then reassess.

Option D: Walk away

If the project creates unacceptable financial exposure, declining it is a legitimate business decision.

There is no rule saying every client must be converted.

---

24. What If the Client Already Has the Deliverables?

Now the situation is different.

If you already delivered everything and the invoice is overdue, do not pretend you can simply recreate your original leverage.

You need a recovery process.

Start with:

1. Confirm the invoice and contract.
2. Confirm whether the client disputes the debt.
3. Request a specific payment date.
4. Preserve the entire paper trail.
5. Stop additional work if your agreement permits suspension.
6. Consider a formal demand if appropriate.
7. Evaluate collection, small claims, arbitration, or litigation based on the contract, amount, jurisdiction, and economics.

For the broader recovery process, see The Freelancer’s Legal Guide to Recovering Unpaid Invoices (Without Expensive Lawsuits).

You can also read How to Recover an Unpaid Invoice Yourself (Without Hiring a Lawyer).

And when escalation becomes appropriate, see When Is It Officially Time for a Freelancer to Take Legal Action?.

---

25. What If the Client Says the Invoice Was Lost?

Do not immediately assume fraud.

Corporate accounting systems can genuinely be complicated.

Ask:

“Could you please confirm the correct invoice-submission process and whether the invoice requires a purchase order or vendor reference?”

If this happens repeatedly, however, document every occurrence.

For the specific recurring-AP problem, read What to Do When a Corporate Client Claims Your Invoice Was Lost in Accounting for the Third Time.

The objective is to turn:

“Where is my money?”

into:

“Here is invoice #1047, submitted on August 4, acknowledged by AP on August 5, and confirmed as approved on August 7. Please confirm the scheduled payment date.”

Documentation changes conversations.

---

26. What If the Client Pays Only 10%?

Be careful.

A partial payment can be useful evidence that the client recognizes some obligation, but accepting a partial payment does not automatically preserve every legal remedy or prevent disputes over the balance.

The legal consequences depend on the agreement and applicable law.

Before accepting a partial payment as a settlement or releasing claims, understand what you are agreeing to.

For a deeper discussion, see The Partial Payment Trap: Why Accepting 10% of a Late Invoice Can Sometimes Erase Your Legal Leverage.

---

27. When Should You Suspend Work?

If a client has not paid and you have additional work scheduled, the answer depends heavily on your contract.

A well-drafted agreement can specify when services may be suspended following non-payment.

That is much safer than inventing a suspension right after the dispute begins.

If your agreement permits suspension, communicate it professionally.

For example:

“Because Invoice #1047 remains outstanding, services scheduled after [date] will be paused until the account is brought current.”

For the broader strategy, read How to Use the Notice of Suspension of Services Without Ruining the Client Relationship Permanently.

---

28. What If the Client Suddenly Demands Something That Was Never Contracted?

This is another reason payment architecture matters.

A client may say:

“We need you to sign this NDA before we release payment.”

Or:

“Can you also provide the source files?”

Or:

“We need five more revisions before Accounts Payable can approve this.”

Do not automatically accept the new condition.

First compare it against the contract.

For example, if a client retrospectively demands an NDA that was never agreed, see How to Handle a Client Who Retrospectively Demands an Uncontracted NDA Before Clearing an Invoice.

For scope expansion, see Client Asked for “One Quick Fix”? Here’s How to Charge for Scope Creep Without Losing the Client.

Payment disputes often begin as scope disputes wearing an accounting costume.

---

29. Should You Charge Late Fees on a Due-Upon-Receipt Invoice?

Potentially—but only when your contract and applicable law permit it.

Do not assume that writing “2% per month” on an invoice automatically creates an enforceable late fee.

The contract, governing law, statutory limits, and circumstances matter.

For a broader jurisdictional discussion, see How to Charge Late Fees Legally (US, UK & India Guide).

You can also read Can You Legally Charge Interest on Late Invoices? (US, UK & India Rules).

The objective of Due Upon Receipt should be better cash-flow control, not building a business model around collecting penalties.

---

30. When Due Upon Receipt Is NOT the Best Choice

This is the most important balancing section in the entire article.

Do not use Due Upon Receipt mechanically.

A different structure may make more sense when:

The client has a mandatory procurement process

Large organizations may have established vendor systems.

The project is large

A $50,000 enterprise project may require milestones rather than one immediate invoice.

The client has a strong payment history

If the client has paid you reliably for years, there may be little reason to treat them like a brand-new counterparty.

The industry normally uses credit terms

Some sectors operate around established commercial payment cycles.

The project requires substantial client review

If acceptance genuinely needs time, your contract should define the acceptance process rather than pretending “Due Upon Receipt” eliminates it.

The commercial opportunity justifies the financing cost

Sometimes you knowingly accept Net-30 because the client is valuable.

That is not weakness.

It is a business decision.

The key is to choose the financing risk rather than accidentally inherit it.

---

31. The Strongest Payment Policy for Most Freelancers Is Actually a Tiered Policy

Instead of:

“Everyone must pay immediately.”

consider:

Tier 1: New or unverified client

Due Upon Receipt or meaningful upfront payment.

Tier 2: Client with a successful payment history

Net-15 may be reasonable.

Tier 3: Established commercial client

Net-30 may be acceptable if the engagement economics support it.

Tier 4: Large enterprise with mandatory procurement

Negotiate deposits, milestones, acceptance procedures, and payment protections.

This approach gives you something better than a rigid rule.

It gives you a risk-based payment policy.

---

32. A Practical Freelancer Payment Policy

You could structure your internal policy like this:

New clients: Payment upon receipt for starter projects under $3,000.

Projects above $3,000: Deposit plus milestone payments.

Established clients: Net-15 may be available after successful payment history.

Large enterprise clients: Net-30 considered after reviewing procurement requirements and project economics.

Overdue accounts: No additional work unless the contract permits otherwise and the account is brought current or a written payment arrangement is reached.

This is far more defensible than:

“I never accept Net-30.”

Your business can be firm without being inflexible.

---

33. Frequently Asked Questions

---

34. The Net-00 Justification Email Generator

Use this simple template when a new client asks why your starter project is not Net-30:

The important point is not the wording itself.

It is the policy behind the wording.

You are communicating a standard business process rather than making a personal accusation.

---

35. A Final Decision Tree for New Clients

New client wants a starter project

↓

Is the client verified and established?

No

→ Prefer Due Upon Receipt or a meaningful upfront payment.

Yes

→ Continue evaluating the payment terms.

↓

Is the project financially significant to your business?

Yes

→ Consider deposits and milestones.

No

→ Due Upon Receipt may be commercially appropriate.

↓

Does the client require Net-30?

Yes

→ Ask whether the policy is mandatory.

↓

Is Net-30 mandatory?

No

→ Negotiate.

Yes

→ Evaluate client risk, project economics, procurement requirements, and remaining leverage.

↓

Can your business comfortably carry the receivable?

Yes

→ Consider accepting Net-30 with appropriate contractual protections.

No

→ Negotiate a deposit, smaller starter phase, milestone structure, or walk away.

That is the real strategy.

Not:

“Net-30 is always evil.”

And not:

“Every client gets whatever terms they demand.”

The professional position is:

“I choose payment terms based on risk.”

---

36. The Cash-Flow Manifesto

Stop acting like your freelance business has an unlimited credit line.

You do not have to finance every client.

You do not have to accept Net-30 simply because someone in Accounts Payable says:

“That’s our standard.”

And you do not have to turn every payment discussion into a confrontation.

The smarter approach is simpler.

New client? Assess the risk.

Small starter project? Consider Due Upon Receipt.

Large project? Use deposits and milestones.

Established client? Earned flexibility can make sense.

Enterprise procurement? Understand the payment process before starting.

Overdue invoice? Follow the contract and build the paper trail.

Your goal is not to make every invoice due immediately.

Your goal is to stop accidentally giving away unsecured credit.

That is the real lesson.

Due Upon Receipt is powerful because it can keep the exchange closer to:

work → payment → final delivery

instead of:

work → delivery → hope → follow-up → Accounts Payable → 30 days → another excuse.

And if you have already handed over the work and the client is ignoring your invoice, move from prevention to recovery. Start with My Client Ghosted Me After I Sent the Invoice—What Do I Do Now?.

If you need a formal escalation strategy, see Final Notice Before Legal Action: Copy-Paste Script That Forces Payment.

And if the client has entered financial distress, read What Happens to Your Invoice If Your Corporate Client Goes Bankrupt?.

The strongest freelancer is not the freelancer who threatens clients.

It is the freelancer who structures the transaction so that getting paid does not depend on threats in the first place.

Protect your cash.

Protect your time.

Protect your leverage.

And most importantly:

Choose your payment terms before the project chooses them for you.

---

Author

Adv. Sagar Haribhau Shirsat is a legal professional writing about commercial contracts, freelancer payment disputes, invoice recovery, digital work, and cross-border business risks. His work focuses on practical legal and commercial frameworks that help freelancers and independent contractors reduce payment risk and respond to unpaid invoices.

For professional information and updates, connect through his Official Professional LinkedIn Profile.

Disclaimer

This article is provided for educational and general informational purposes. It is not a substitute for legal advice based on the specific facts, contract, jurisdiction, and applicable law of an individual matter. Payment rights, intellectual-property rights, late fees, collection remedies, suspension rights, and enforcement procedures can vary substantially between jurisdictions and contracts. If a significant dispute is developing, consult a qualified lawyer or attorney in the relevant jurisdiction.

Official sources and further reading

• New York Department of Labor — Freelance Isn’t Free Act
• New York Department of Labor — Freelance Worker Agreement
• GOV.UK — Interest on late commercial payments
• EUR-Lex — Combating late payment in business dealings
• Cornell Law School Legal Information Institute — UCC § 2-310
• Cornell Law School Legal Information Institute — UCC § 2-301