Freelance Invoicing & Net Terms: How to Actually Get Paid
By Andrew James Flores, Nathan Management · Updated September 23, 2026 · Editorial Standards
An invoice turns finished work into cash only when you and the client agree on when the clock starts, how the days are counted and which date the money is due. This guide puts the common payment terms side by side on one $6,000 project, shows how a deposit and milestones change when that money arrives, and walks through a filled invoice, a receivables ledger and a partial-payment log you can copy. The line items and payments are example inputs, the rate floors come from the calculator, and the due dates and totals that follow from them are worked out on the page, so you can check the arithmetic and swap in your own numbers.
What “net” means on an invoice
“Net 30” means the full invoice amount is due 30 days after a starting event. “Net” refers to the amount after any agreed discount or credit, and the number is the count of days. Two details make the phrase less precise than it looks. The first is the starting event: it can be the invoice date, the day the client receives the invoice, the day it approves the work, or the day its system matches the invoice to a purchase order. The second is the day count: calendar days or business days, and whether a due date that falls on a weekend moves to the next business day.
The cure is to print all three on the invoice: the trigger, the term and the calendar date that results. “Net 15 from invoice date, due Wednesday, September 16, 2026” leaves nothing to interpret. End-of-month terms need the same care. In this guide, “EOM” means due on the last day of the month the invoice is dated, and “net 30 EOM” means 30 days after that month ends. The two are easy to confuse, so ask a client which one it means before you accept either.
Table 1 applies each common term to the same example: a $6,000 project delivered on Monday, August 31, 2026 and invoiced the next day.
| Term | Due date | Days after invoice | Cost of waiting at 24%/yr |
|---|---|---|---|
| Due on receipt | Tue, Sep 1 | 0 | $0.00 |
| Net 7 | Tue, Sep 8 | 7 | $27.62 |
| Net 10 | Fri, Sep 11 | 10 | $39.45 |
| Net 15 | Wed, Sep 16 | 15 | $59.18 |
| EOM | Wed, Sep 30 | 29 | $114.41 |
| Net 30 | Thu, Oct 1 | 30 | $118.36 |
| Net 45 | Fri, Oct 16 | 45 | $177.53 |
| Net 30 EOM | Fri, Oct 30 | 59 | $232.77 |
| Net 60 | Sat, Oct 31 | 60 | $236.71 |
Each day of terms on this invoice costs about $3.95 at the example rate. Accepting net 60 instead of net 15 pushes $6,000 back 45 days and costs $177.53, close to 3% of the project fee. Two rows hide traps. EOM and net 30 differ by one day here, but on an invoice dated September 30 they differ by 30 days, because EOM would be due that same day. And the net 60 date lands on a Saturday, so the agreement should say whether payment is due the Friday before or the Monday after.
Deposits and milestones matter more than the net term
The term on the final invoice matters less than how much of the fee is still unbilled when the work ends. Table 2 bills the same project four ways and assumes every invoice is paid on its due date; the three single-invoice rows bill the full $6,000 at delivery. The split schedule bills 40% ($2,400) when work starts on July 20 at net 10, 30% ($1,800) when the draft is delivered on August 13 at net 15, and the last 30% ($1,800) at final delivery, also at net 15.
| Billing setup | Jul 31 | Aug 31 | Sep 30 | Oct 31 | Avg. days |
|---|---|---|---|---|---|
| 40/30/30 split | $2,400 | $4,200 | $6,000 | $6,000 | 33.1 |
| One invoice, net 15 | $0 | $0 | $6,000 | $6,000 | 58.0 |
| One invoice, net 30 | $0 | $0 | $0 | $6,000 | 73.0 |
| One invoice, net 60 | $0 | $0 | $0 | $6,000 | 103.0 |
The split schedule collects its last dollar on the same day as a single net 15 invoice, September 16, yet the average dollar arrives almost 25 days sooner (58.0 − 33.1 = 24.9) because $4,200 is already in hand before final delivery. It also caps what you can lose: if the client stops paying after the draft, $1,800 is at risk instead of $6,000. In the receivables ledger further down, where the deposit arrived early and the final payment arrived seven days late, the actual average was 32.8 days: ($2,400 × 4 + $1,800 × 39 + $1,800 × 65) ÷ $6,000.
Recommended defaults (author’s practice)
These are the author’s starting terms for a new client. Adjust them to your field and to the client’s payment process.
- A deposit of 30% to 50% before work starts on any project longer than two weeks, invoiced at net 10 or sooner.
- A milestone invoice at each named deliverable, net 15, with the milestone defined in the scope so there is no argument about whether it happened.
- Net 30 at most for a new client. Net 45 or net 60 only when a larger client’s accounts payable process requires it, and then with a deposit or a price that covers the wait; Table 1 shows what the wait costs.
- The calendar due date printed on every invoice, next to the term.
- The invoice sent on the day of the trigger event, or the next business day at the latest. Every day you wait to invoice is a day added to the term.
- The client’s accounts payable contact, purchase-order number and invoicing rules collected before work starts, not after the first invoice bounces.
Invoice fields that prevent processing delays
Accounts payable teams hold back invoices that are missing something they need to match against a contract. Include:
- An invoice number, unique and sequential, so both sides can refer to one document.
- The invoice date, the service period, the payment term and the calendar due date.
- Your legal business name, address and billing contact; the client’s legal name, billing address and accounts payable contact.
- The contract, statement of work or purchase-order reference.
- Each deliverable or time entry with quantity, rate and line total.
- The subtotal, any sales tax or adjustments, prior payments credited, and the amount now due.
- Payment instructions sent through a channel you have confirmed with the client, plus any agreed late-charge or discount terms.
Download the invoice fields and receivables CSV. It holds the worked examples below, marked example in the scenario column: invoice INV-2026-026 field by field, the three receivables from Table 4 and the three partial payments from Table 5. Rows marked blank are ready for your own invoices and payments; filter record_type to invoice_field, receivable or payment. Amounts and days late are typed values rather than spreadsheet formulas, so recalculate after every payment and keep the invoice-field rows out of receivables totals.
Worked example 1: the final invoice after a deposit and a milestone
This is the third of three invoices on the example project. It lists the whole fee, credits the two earlier payments and asks only for what is left.
| Invoice field | Value |
|---|---|
| Invoice number | INV-2026-026 |
| From | Example Copy Studio LLC, 100 Example Lane, Anytown, ST 00000, billing@example.com |
| Bill to | Example Trail Supply Co., Attn: Accounts Payable, 200 Sample Road, Anytown, ST 00000, ap@example.org |
| Contract reference | Statement of work SOW-01, fixed-fee website content package |
| Service period | July 20 – August 31, 2026 |
| Invoice date | September 1, 2026 |
| Terms | Net 15 calendar days from the invoice date; invoice issued the day after final delivery on August 31 |
| Due date | Wednesday, September 16, 2026 |
| Discovery and content plan | 1 × $1,200.00 = $1,200.00 |
| Draft content | 1 × $2,400.00 = $2,400.00 |
| Final content delivery | 1 × $2,400.00 = $2,400.00 |
| Project total | $6,000.00 |
| Sales tax and adjustments | $0.00 |
| Deposit received July 24, 2026 (invoice INV-2026-019) | −$2,400.00 |
| Milestone payment received August 28, 2026 (invoice INV-2026-023) | −$1,800.00 |
| Amount now due | $1,800.00 |
| Payment method | ACH bank transfer to the account confirmed by phone when the contract was signed; bank details are never changed by email |
| Late charges | None; this agreement has no late-charge clause |
The billing split is 40% deposit, 30% at the draft and 30% at final delivery. The line items describe the work ($1,200.00 + $2,400.00 + $2,400.00), while the installments split the $6,000.00 total 40/30/30 ($2,400.00, $1,800.00 and $1,800.00), so the two do not line up item for item. Those percentages decide when money is billed, not how much: the three installments add up to the $6,000 fee, and the final invoice asks for $1,800 rather than another $6,000. The deposit invoice (INV-2026-019) was issued July 20 at net 10, so it was due July 30. The draft invoice (INV-2026-023) was issued Thursday, August 13, the day the draft was delivered, at net 15, so it was due Friday, August 28. This final invoice also uses net 15. The numbers skip because the same sequence covers every client.
A receivables ledger that reconciles
| Invoice | Issued | Terms | Due | Amount | Paid | Days late |
|---|---|---|---|---|---|---|
| INV-2026-019 | Jul 20 | Net 10 | Jul 30 | $2,400.00 | Jul 24 | 0 |
| INV-2026-023 | Aug 13 | Net 15 | Aug 28 | $1,800.00 | Aug 28 | 0 |
| INV-2026-026 | Sep 1 | Net 15 | Sep 16 | $1,800.00 | Sep 23 | 7 |
Billed $6,000.00, paid $6,000.00, outstanding $0.00. The final payment arrived seven days late: September 23 minus September 16. For a paid invoice, days late is the paid date minus the due date, or zero if it was paid on time. For an open balance, use the date you run the report in place of a paid date, and sort open balances into aging bands: current, 1–30, 31–60, 61–90 and over 90 days past due. An invoice counts as paid only when the payments recorded against it add up to its full amount, which is what the next example shows.
Worked example 2: one invoice paid in three parts
A different client, Example Home Services Inc., receives invoice INV-2026-014 for $3,000.00 on Monday, June 1, 2026, at net 30, so it is due Wednesday, July 1. The client pays it in three pieces.
| Payment date | Amount received | Balance after payment | Days after invoice | Days past due |
|---|---|---|---|---|
| Fri, Jun 26 | $1,000.00 | $2,000.00 | 25 | 0 |
| Tue, Jul 14 | $1,200.00 | $800.00 | 43 | 13 |
| Wed, Aug 5 | $800.00 | $0.00 | 65 | 35 |
The same log answers three different questions. On an aging report run July 31, the invoice shows $800.00 open and 30 days past due, in the 1–30 day band. It became fully paid on August 5, 35 days after its due date, so the ledger records 35 days late, not 13. And weighted by dollars, the client took 42.9 days to pay a net 30 invoice: ($1,000 × 25 + $1,200 × 43 + $800 × 65) ÷ $3,000. That last figure is the one to track across a client’s invoices. If it keeps landing well past the term, a deposit or smaller milestones will do more for you than another reminder.
Following up on a late invoice
A fixed schedule keeps follow-up polite, consistent and easy to hand off. The author’s practice, counted from the due date:
- Day 1 past due: resend the invoice and ask whether anything is holding it up. For example: “Hi Jordan, invoice INV-2026-026 for $1,800.00 was due yesterday, September 16. I’ve attached it again. Is it with accounts payable, and is there a payment date I can note?”
- Day 7: ask for a specific payment date, and ask whether any part of the amount is disputed so the undisputed part can be paid while the rest is sorted out.
- Day 14: send a statement of account listing every open invoice, and copy the person who signed off on the work.
- Day 21: reread your agreement for a pause or late-charge clause, then say in writing what happens next, for example that new work starts once the balance is paid.
Keep the scope, delivery confirmations and every message for each client in one folder, so you can answer a dispute with documents instead of memory. Past day 21, formal demand letters and small-claims filings depend on your agreement and your state’s rules.
Late fees: put them in the agreement first
Write any late charge into the signed agreement before work begins. A charge that first appears on an overdue invoice is hard to collect and tends to sour the relationship.
The clearest way to write one is as a monthly percentage of the overdue balance. If this agreement had a 1.5%-a-month clause (18% a year), one month late on the $1,800.00 final invoice would add $27.00. The author’s practice is to state the rate, the day it starts and whether it compounds, and to waive the first late charge for a client who pays within a week of a reminder.
Montana, for example, lets a seller of goods at retail charge up to 1.5% a month on money due from 30 days after the buyer’s obligation to pay arises, and the same section says it does not apply to money due for intangible services (Montana Code Annotated 31-1-501). Look up the rule for your kind of work in your state before you put a rate in an agreement.
Early-payment discounts and the cost of waiting
“2/10 net 30” means the client may take 2% off by paying within 10 days; otherwise the full amount is due in 30. On the $6,000 invoice, the client could pay $5,880.00 by September 11 instead of $6,000.00 by October 1. You give up $120.00 to receive $5,880.00 twenty days sooner, which works out to ($120 ÷ $5,880) × (365 ÷ 20) = 37.24% a year. Borrowing the same $5,880 for 20 days at the example 24% rate would cost $77.33. A discount that expensive makes sense only when you need the cash and cannot borrow it; a deposit brings money in sooner without cutting the fee.
Late payment and non-payment are different costs. A late invoice is a timing cost, priced in Table 1. An invoice you expect never to collect belongs in the calculator’s “Invoices eventually collected (%)” field: with the calculator’s opening example, entering 95 there raises the rate floor from $66.67 to $70.18 an hour. Count any given invoice in one place, not both. Table 7 of the rate floor tables shows more combinations of collection rates and payment fees.
Laws and official pages worth knowing
- New York City. The Freelance Isn’t Free Act covers individuals hired or retained as independent contractors to provide services for compensation. The Department of Consumer and Worker Protection page explains who is covered and what rights apply.
- U.S. federal agencies. The Prompt Payment Act (31 U.S.C. 3901 and following sections) and Federal Acquisition Regulation subpart 32.9 govern when federal agencies pay their contractors, including interest on late payments. They apply to federal agency payments, not to invoices you send private clients.
- State late-charge limits. Montana Code Annotated 31-1-501 is one example of a state cap on late-payment charges: 1.5% a month on retail sales of goods, with intangible services excluded.
Run the calculator → · Raising rates with existing clients · More guides