billable.dev

Net 60 Payment Terms: What a Freelance Developer Can Do

By Mark Fulton · · 13 min read

Last verified:

Net 60 Payment Terms: What a Freelance Developer Can Do

Net 60 means the client has 60 calendar days from the invoice date to pay, and a freelance developer who is handed it has five moves, in this order: counter at net 30, accept net 60 but take a deposit on signing, invoice on delivery instead of on approval, add a late fee to the contract, or walk away. Most large clients will move on at least one of the first three if you ask before you sign, in writing, with a reason. After you sign, every invoice follows the term, so the conversation has to happen now.

Net 60 usually arrives inside a vendor agreement written for suppliers who ship pallets, not for one developer billing one project. The term is not personal and it is not a verdict on your work. It is a template field. That is useful, because a template field can sometimes be changed by someone who asks the right person the right way. This post gives you the ladder, the exact wording for each rung, and a cash-flow timeline on a $6,000 invoice so you can see what each choice does to your bank balance. All of the money math below is arithmetic on stated assumptions, not a forecast and not advice about your finances.

Why do large clients ask for net 60?

Because the longer they hold the cash, the better their own numbers look. J.P. Morgan's treasury team explains the trade-off from the buyer's side: moving from net 30 to net 60 lets a buyer hold cash twice as long, which extends what finance teams call days payable outstanding. The same move extends the vendor's days sales outstanding, which vendors want to keep short. Your gain and their gain are the same number with the sign flipped.

The U.S. Chamber of Commerce lists net 60 as common when selling to large corporations, hospitals, universities and government agencies, organizations that use payment terms as a working capital tool. That matches what developers see: the term comes from the client's size and process, not from how they feel about contractors.

There are three practical reasons behind it, and they matter because each one points to a different counter.

  • Fixed payment runs. Accounts payable teams often pay in batches on set dates. Your invoice joins the next batch after it clears approval, so the term is a ceiling on a process, not a promise of day 60.
  • Matching. Many invoices must match a purchase order and a record that the work was received before anyone releases payment. This is why "when does the clock start" matters so much, and it gets its own section below.
  • Template inertia. Net 60 sits in the standard agreement and nobody has been asked to change it for a one-person supplier. This is the reason a polite request works more often than you would expect.

If you are choosing terms for clients where you hold the leverage, that is a different decision, covered in net 15 vs net 30 vs due on receipt. This post is for the other situation: the term is already on the page and you want the work.

What does net 60 cost you? A $6,000 timeline

Here is the project used for every example below. It is fictional, chosen only so the dates are easy to follow.

  • Fee: $6,000 fixed price for a small web app.
  • Kickoff: Monday, 2 November 2026.
  • Delivery: Friday, 11 December 2026.
  • Terms: the client's contract says net 60 from the invoice date.

The arithmetic, with nothing assumed beyond those dates:

Structure Cash in before delivery Unpaid on delivery day Last dollar due
Single invoice at delivery, net 60 $0 $6,000 9 Feb 2027
Single invoice at delivery, net 30 $0 $6,000 10 Jan 2027
30% deposit on signing, balance net 60 $1,800 $4,200 9 Feb 2027
50% deposit on signing, balance net 60 $3,000 $3,000 9 Feb 2027
Three $2,000 invoices (kickoff, staging, delivery), all net 60 $0 $6,000 first due 1 Jan 2027, last 9 Feb 2027

Two facts in that table are easy to miss.

The wait is longer than 60 days. From kickoff on 2 November to the last due date on 9 February is 99 days. You do the work first, and the 60 days start only when you invoice. If you pay your own bills monthly, you have funded about three and a half months of the project before the last payment is due.

Splitting into milestones does not fix net 60 by itself. The last row is the surprising one. Three invoices on net 60 each still leave you with $0 in hand on delivery day, because each invoice carries its own 60 days. Milestone billing earlier in the project only helps cash if the early invoices are due sooner than the final one. The milestone billing guide covers how to structure that. A deposit due on receipt is what changes the table, because it is the only line that pays you before delivery.

One more number, because it shows what the term is worth in plain money. Suppose carrying $6,000 for 60 days costs you 12% a year in interest or opportunity cost. That is a stand-in rate, so replace it with your own. The arithmetic is $6,000 x 12% x 60 / 365, which is about $118, or roughly 2% of the invoice. That is the price of the wait at that rate, and it is the number to keep in mind when someone says net 60 is "just a formality."

Can you counter without losing the contract?

Usually yes, if you counter early, in writing, and with a reason that is about your constraints and not their policy. Procurement contacts hear "your terms are unreasonable" all day. They rarely hear "I'm a one-person business and a 60-day term means I fund your project for three months," and they have no standard answer to it.

Here is the ladder, in order. Move down a rung only when the one above has been declined.

Rung 1. Counter at net 30. Ask whether net 60 is required or only the default.

Thanks for sending the agreement. I'm happy to work with your process. As a one-person business, I'm set up for net 30. Is net 30 possible for this engagement, or is net 60 fixed for all vendors?

The second sentence matters. "Fixed for all vendors" is a question they can answer yes or no, and a no tells you which of the next rungs you need.

Rung 2. Accept net 60 with a deposit. If the term is fixed, ask for money upfront to bridge it.

Understood on net 60. To keep the schedule without carrying two months of costs, my standard is a 30% deposit invoice due on receipt, with the balance on your net 60 terms. Can we add that to the agreement?

A deposit due on receipt is a separate request from the long term on the balance, and some clients will agree to one while keeping the other. How much to ask for is covered in how much deposit to charge for freelance dev work.

Rung 3. Invoice on delivery, not on approval. Covered in detail in its own section below.

Rung 4. Add a late fee or interest clause. Net 60 without a consequence for day 61 is a 60-day suggestion. Wording is in late fee wording on an invoice, and the wider set of terms is in net terms, deposits and late fees.

Rung 5. Walk, or price it in. Covered at the end.

How do deposits and milestones soften a long term?

They change when the first dollar arrives, which is the only thing that matters for cash flow. Look at the table again: the 30% deposit row brings $1,800 in before you deliver, and the 50% deposit row brings $3,000. The last due date does not move, but the amount you are exposed to on delivery day drops from $6,000 to $4,200 or $3,000.

Milestones help in a narrower way. They help when the earlier invoices carry shorter terms than the final invoice, or when each milestone is paid on receipt. A realistic version of that ask:

Deposit of 30% due on receipt at signing. Then two milestone invoices of 30% each on net 30. Final 10% on your net 60 terms.

You are not asking the client to abandon its process, only to apply the long term to the smallest part of the project. For a $6,000 project that is $600 on net 60 instead of $6,000. Clients with a strict "all invoices are net 60" rule will say no. Clients whose rule exists to protect their payment runs will often say yes, because the amount on the long term shrank by 90%.

Two cautions. First, do not deliver the final files before the final payment unless the contract gives you another form of protection. Second, a deposit is not a favor to you. It is the reason the client's project has a start date at all, so say it that way: "the deposit reserves the schedule."

When does the net 60 clock actually start?

Not always when you think. Net 60 can be counted from several different points, and the difference between them can be weeks:

  • Invoice date. The common default and the best for you, because you choose it.
  • Date the client receives the invoice. Common in procurement departments.
  • Date the invoice is approved. This is where the clock quietly stops while the invoice waits in a queue.
  • Date of "satisfactory completion" or acceptance. The least predictable, because the client controls it.

To see how much this matters, take the same project with one extra assumption: the client's approver takes 17 days to approve the 11 December invoice, and the contract says net 60 from approval. That is 28 December plus 60 days, a due date of 26 February 2027, which is 77 days after the invoice date and not 60. The 17 days is an invented figure to show the mechanism. The mechanism itself is real: if the clock starts at approval, the approver sets your due date.

Three edits keep the clock under your control.

  1. Date the invoice on the day the work is delivered, and state the due date as a calendar date on the invoice.
  2. Add an acceptance deadline to the contract. For example: "Deliverables are deemed accepted 5 business days after delivery unless the Client gives written notice of specific defects."
  3. Send the invoice the same day it is dated. An invoice dated the 11th but emailed on the 20th looks like a clock you started late.

The same rules apply under local law, and they differ by country. In the UK, government guidance on late commercial payments says an agreed payment date must usually fall within 60 days for business transactions, and a longer period is allowed only if it is fair to both businesses. That guidance is a reason to ask about net 60 where it applies, not a promise it will be changed. This is general information, not legal advice, so check the rules where you and your client are based.

Can you invoice before the work is approved?

Yes, and for net 60 clients it is usually the single highest-value change. Invoicing on delivery means the invoice goes out when you hand over the work, not when the client confirms they like it. The contract has to allow it, so the wording matters:

Invoices are issued upon delivery of each deliverable and are payable within 60 days of the invoice date. Acceptance does not affect the invoice date or the payment due date. Any defects will be corrected under the warranty provisions of this Agreement.

This separates two things clients often bundle: "is the work good?" and "when does the money move?" The warranty clause handles the first one. If you also use a statement of work, the SOW guide shows where acceptance criteria belong, so "approved" has a definition before anyone needs it.

Should you raise your rate to cover a long term?

You can, but do it in the open and in numbers the client can follow. The $118 figure above, about 2% of the invoice at a 12% stand-in rate, is the honest size of the adjustment. Two ways to present it:

  • A finance line in the quote. "Fixed fee $6,000 on net 30, or $6,120 on net 60." The client sees the price of its own term and can choose.
  • A deposit-or-uplift choice. "Net 60 with a 30% deposit at the quoted rate, or net 60 with no deposit at the quoted rate plus 2%."

The early-payment discount flips this same arithmetic. A 2% discount for payment within 10 days on a net 60 invoice is 2 / 98 x 365 / 50, about 15% annualized. That is far cheaper than the roughly 37% the same 2% costs on a 2/10 net 30 term, and it is why 2/10 net 30 is usually a poor trade while 2/10 net 60 can be worth offering to a client with a payment run you want to catch. It is arithmetic on the terms, not a promise the client will take it.

Can you charge a late fee after 60 days?

Only if the agreement says so, or if the law where you are provides interest by default. Writing "late fees apply" on an invoice after the fact, when the contract says nothing, gives you a complaint and not a charge. For a $6,000 invoice, a clause of 1.5% per month is $90 per month, so a late fee clause is more an incentive for the client's payment team than a source of income. Put it in the agreement before signing, and make the start date explicit: day 61 from the invoice date, not "when overdue."

When is net 60 a reason to walk away?

Walk, or at least decline the term, when the term combines with one or more of these:

  • The invoice is large compared with your monthly costs. If one invoice is more than you could comfortably carry for 90 days, the real term is 90 days once a slow approval or a missed payment run is added.
  • There is no deposit, no milestones and no late fee, and the client has refused all three. At that point you are extending unsecured credit for two months to a company that already declined to compensate you for it.
  • The clock starts at an event the client controls, such as satisfactory completion, with no deemed-acceptance date.
  • The client pays you last. If you learn the company routinely pays vendors late, net 60 is a floor, not a plan.

Walking away does not have to be dramatic. "Thanks for the offer. With net 60 and no deposit I can't take this one on, but I'd love to if the terms change" keeps the door open and is often the message that gets the term changed.

If you stay, price the wait in. A project on net 60 with a deposit is a different business decision from one on net 60 without one, and your quote should say so.

What should you do before you sign?

  1. Ask for the payment terms before you quote, not after.
  2. Counter at net 30 in writing.
  3. If that fails, ask for a deposit due on receipt.
  4. Put the invoice date, the due date and a deemed-acceptance period in the contract.
  5. Add the late fee clause.
  6. Keep the arithmetic: write down the due date for every invoice the day you send it.

The contract sets the terms and the invoice enforces them. Pick a due-date preset or type your own terms and generate the invoice free, with the exact due date printed on it. It runs in your browser with no account.

FAQ

Is net 60 normal for enterprise clients?

It is common. The U.S. Chamber of Commerce lists net 60 as typical when selling to large corporations, hospitals, universities and government agencies. "Normal" does not mean fixed, though. For a one-person supplier the term is often a template default, and asking whether it is required costs you one email.

Can I charge a late fee after 60 days?

Only if your agreement provides for it, or if local law gives you interest on late commercial payments. A fee added to an invoice after the fact, when the contract was silent, is a request and not a right. State the fee and the day it starts in the contract before you sign. This is general information, not legal advice.

Should I raise my rate to cover long terms?

You can, and the honest size is small. On a $6,000 invoice, a 12% stand-in cost of money over 60 days is about $118, roughly 2%. Show it as a visible choice in the quote, for example a lower price on net 30 and a higher price on net 60, so the client sees what its term costs.

Can I invoice before the work is approved?

Yes, if the contract says the invoice date is the delivery date and that acceptance does not move the due date. Pair it with a deemed-acceptance clause and a warranty for defects, so the client has a defined way to raise problems without stopping the clock. Without those clauses the client's approval process controls your due date.


Billable is a free, client-side invoice generator for developers. Your data stays in your browser.