Invoice Payment Terms: Net 30, Due Dates, and Fees

Payment terms determine when a client should pay and what happens around that date. A vague phrase can create two interpretations; a clear due date, schedule, and approval rule turns the invoice into an actionable request.

Net 30 means payment is due 30 calendar days after the invoice date unless the agreement defines a different starting point. Show the calculated due date on the invoice as well as the term. Use shorter or milestone-based terms when project risk, cash flow, or client process calls for them.

Quick glossary

Net usually refers to the full invoice amount after discounts and adjustments. Do not assume every client interprets the starting date the same way. Put the issue date and explicit due date on the document.

Net 7, Net 15, Net 30, Net 45, and Net 60

Longer terms give the client more time but increase your exposure. They are not a measure of professionalism. Choose them based on the client's approval process and your ability to finance the wait.

• Net 7: useful for short projects and small amounts
• Net 15: gives a client two weeks without stretching a solo business too far
• Net 30: common where invoices pass through formal accounts payable
• Net 45 or 60: sometimes required by larger organizations, but worth pricing and planning deliberately

If a large client insists on Net 60, ask when their clock starts. Some systems count from invoice receipt, approval, or month-end rather than your issue date. Put the accepted rule in the contract.

Due on receipt

Due on receipt means the invoice is payable when delivered. It does not guarantee instant payment. The client still needs time to approve and execute it.

Use it for:

• A kickoff deposit
• A final small balance
• A product or service delivered immediately
• A client with an established same-day process

Avoid using it as a substitute for planning. If the client needs ten business days internally, a realistic explicit date is clearer.

Explicit due date vs free-text terms

Use both:

• Payment terms: Net 30
• Due date: August 31, 2026

The term explains the policy. The date tells a human what to do. Reminder automation also usually relies on the due-date field, not a sentence in the notes.

1. Aug 1

   Invoice issued and delivered

2. Aug 15

   Client approval is still in progress

3. Aug 28

   Friendly reminder before due date

4. Aug 31

   Payment due

Date calculations, weekends, and holidays

If an invoice is issued on August 1 with Net 30, a common calculation produces August 31. But contracts, billing systems, and local rules can define counting differently.

Decide how to handle:

• Due dates that land on weekends
• Bank holidays in either party's country
• Cross-border transfer time
• Client cutoff times
• Delayed receipt caused by an incorrect billing address

A practical clause is: If the due date falls on a non-business day, payment is due on the next business day. Confirm that this matches local requirements and your agreement.

Deposits, milestones, and partial payments

One due date is not always the right structure.

Deposit

Example: 40 percent due on acceptance; 60 percent due on final delivery. Issue separate invoices or clearly record amount paid and balance due. See the deposit invoice guide.

Milestones

Example:

• 30 percent at kickoff
• 40 percent after approved design
• 30 percent at production handoff

Define what counts as completion and who approves it.

Partial payments

Record each payment date and amount. The invoice should continue to show the remaining balance. Do not mark the full invoice paid after the first installment.

Early-payment discounts

2/10 Net 30 commonly means the client may deduct 2 percent if payment arrives within 10 days; otherwise the full amount is due in 30 days.

Discounts can improve predictability, but they reduce revenue and add reconciliation work. State:

• The exact percentage or amount
• The deadline
• Whether tax is calculated before or after the discount
• The full amount after the discount window

Ask an accountant about tax treatment.

Late fees

A late fee should never appear as a surprise punishment. It should be allowed by the contract and local law, reasonable, and explained before the invoice becomes overdue.

Do not copy a statutory rate from another country. GOV.UK's late commercial payment guidance is one example of a jurisdiction defining when payment becomes late and what remedies may apply.

Possible wording:

Amounts not disputed in good faith may incur a late fee of 1 percent per month after 10 days overdue, where permitted by law.

That example is not universally valid. Some jurisdictions cap fees, require specific disclosures, or treat business and consumer clients differently. Get local advice before using a rate.

Operationally:

1. Confirm the invoice was delivered.
2. Check for approval or billing-detail problems.
3. Send a courteous reminder.
4. Resolve genuine disputes.
5. Apply a contracted fee only after the stated grace period.

The unpaid invoice guide provides a complete escalation sequence and copy-ready messages.

Terms by project and client type

Risk is not only whether a client intends to pay. It also includes purchase orders, recipient details, approval routing, and transfer timing. Ask about those before work starts.

International invoices

For cross-border clients:

• State the currency using a clear code, such as USD or EUR
• Name who pays transfer and intermediary bank fees
• Allow for bank-processing time
• Provide accurate payment details
• Decide how exchange-rate changes affect fixed fees
• Account for local tax and withholding rules

NeatInvoice does not process payments or currency conversion. It displays the bank details and payment links you configure.

Copy-ready payment-term examples

Standard Net 15

Payment due within 15 calendar days. Due date: August 16, 2026. Please include the invoice number with payment.

Deposit and balance

40 percent deposit due on acceptance. Remaining 60 percent due within 7 days of final delivery.

Retainer

Monthly retainer is invoiced on the first day of the service period and due within 7 days. Additional work requires written approval.

Milestone project

Invoices are issued at kickoff, design approval, and production handoff according to the signed statement of work. Each milestone invoice is due within 10 days.

Late fee notice

Late fees apply only as stated in the signed agreement and where permitted by law. Please contact us before the due date if an invoice detail needs correction.

Worked date examples

Net 15 from issue

Invoice issued August 1. Add 15 calendar days. The due date is August 16, subject to the agreed weekend and holiday rule.

Net 30 from receipt

Invoice issued August 1 but accepted into the client's AP system on August 4. If the contract explicitly starts the clock at receipt, the due date is September 3. This is why the trigger belongs in the agreement.

End-of-month processing

Some clients pay invoices received before a cutoff on the next scheduled run. An invoice dated August 28 may not be processed until September. Ask for the cutoff before promising your own cash-flow date.

Deposit plus Net 15 balance

A 40 percent deposit is due before kickoff. The remaining 60 percent is invoiced on final delivery with Net 15. These are two different payment events and should have explicit dates.

Purchase orders and approval workflows

Payment terms do not fix a missing purchase order. Before starting work for an organization with formal AP, ask:

• Who owns the purchase request?
• Must the PO number appear on the invoice?
• Is a vendor form required?
• Which email or portal receives invoices?
• Who approves the deliverable?
• When does the payment clock start?
• Which days does the client run payments?

Put process answers in the contract or project record. Put only the relevant reference and due date on the invoice.

Choosing terms by risk

Consider four factors:

1. Relationship history: a reliable repeat client may justify a longer window.
2. Project exposure: custom work and long delivery periods increase risk.
3. Client process: a large AP department may need more time than a solo buyer.
4. Your cash flow: do not finance long terms by accident.

Writing terms that a client can act on

Good terms are short enough to scan:

Due September 15, 2026. Pay by bank transfer in USD and include INV-0264 as the reference.

Supporting clauses belong in the contract. Avoid pasting a page of legal text into every invoice. The invoice should surface the operational facts while the agreement defines remedies, disputes, confidentiality, intellectual property, and governing law.

Changing terms for an existing client

Do not shorten a payment window retroactively. Discuss the change before the next engagement or renewal, obtain written agreement, and apply it from a clear effective date.

If the client asks for longer terms, evaluate the cost. Options include a deposit, milestone billing, a different price, or declining the change. Keep issued invoices under the terms that governed them when sent.

Terms and reminder timing

Reminder timing should follow the due date, not replace it. A useful pattern is:

• Three days before due: confirm the invoice is ready for payment
• Due date: concise reminder
• One day after: ask for payment status
• Seven days after: request a firm date
• Fourteen days after: escalate according to the agreement

Do not schedule an overdue reminder before the invoice can legally or contractually be considered overdue.

Terms on recurring invoices

For a stable monthly retainer, keep the due-date offset consistent. Each generated invoice should calculate its own date from the new issue date. Review the schedule when a renewal changes price, cadence, service period, tax, or payment window.

Variable expenses, usage, and hours deserve a draft review before delivery. Recurring generation should not turn an estimate into an automatic charge.

Client-side clarity check

Before sending, ask someone unfamiliar with the project to identify:

1. The amount due
2. The currency
3. The due date
4. The payment method
5. The reference to include
6. The contact for corrections

If any answer requires reading the email thread, the invoice terms are not self-contained enough.

What not to write

Avoid:

• Payment ASAP
• Standard terms apply
• Late fees may be added when no agreement defines them
• A due date that conflicts with Net terms
• Payment details only in an earlier email

Replace ambiguity with one explicit date and one actionable instruction.

When a client requests custom portal wording, ensure the portal, PDF, email, and contract still show the same deadline. Conflicting surfaces create disputes even when each sentence looks reasonable by itself. Test the final client view rather than relying only on the editor.

Keep the approved wording with the project record.

Frequently asked questions

What does Net 30 mean on an invoice?

It usually means the full payment is due 30 calendar days after the invoice date. Show the explicit due date and confirm whether the contract uses a different trigger.

Is Net 30 the same as one month?

No. Thirty calendar days and one calendar month can produce different dates.

Should freelancers offer Net 30?

Only when it fits the client's process and the freelancer's cash flow. Net 7, Net 15, deposits, or milestones may be more appropriate.

Can I add a late fee after sending the invoice?

Do not add an unagreed fee after the fact. Late-fee rules should be disclosed in the contract and comply with local law.

What due date should I put on an invoice?

Use the date produced by the agreed terms, adjusted according to any written weekend or holiday rule. Always show it explicitly.