From Finished Work to Cash: A Freelancer's Invoice, Due Date, Discount and ACH Timeline Through the 2026 Holidays

Priya is a freelance backend developer in Austin. Since Monday, 26 October 2026 she has been on a retainer with a logistics startup in Denver: $8,400 per billing cycle, invoiced every 30 days, Net 30, with a 2% discount if the client pays within 10 days. The contract is ordinary. What makes this winter awkward is the calendar: the first four due dates fall around Thanksgiving, Christmas and New Year, which is exactly when accounts payable teams are short-staffed and banks are shut.

This guide follows her money from finished work to cleared funds using four of the site's calculators in the order she actually needs them. Each tool answers one question well and ignores the question the next tool answers, so most of what follows is about the hand-offs.

The schedule at a glance

Here is where the whole chain ends up. The columns are explained step by step below; every date comes from running the calculators, and one issue date has been moved by hand for reasons covered in step 1.

Invoice	Issued	Due (raw day 30)	Due (next business day)	2% discount window ends	Lands if paid by standard ACH on the due date
1	Mon 26 Oct 2026	Wed 25 Nov	Wed 25 Nov	Thu 5 Nov	Mon 30 Nov
2	Wed 25 Nov	Fri 25 Dec	Mon 28 Dec	Mon 7 Dec (day 10 is Sat 5 Dec)	Wed 30 Dec
3	Wed 23 Dec (moved by hand from Fri 25 Dec)	Fri 22 Jan 2027	Fri 22 Jan	Mon 4 Jan (day 10 is Sat 2 Jan)	Tue 26 Jan
4	Mon 25 Jan 2027 (scheduled for Sun 24 Jan)	Wed 24 Feb	Wed 24 Feb	Thu 4 Feb	Fri 26 Feb

Read across any row and you can see the gap between "due" and "money in the account". On invoice 2 it is five calendar days, and none of them are the client being late.

Step 1: lay out the cycle with the Freelance Invoice Scheduler

The Freelance Invoice Scheduler takes a start date, a number of invoices, the gap between them and the net term, plus a holiday calendar. Priya entered 26 October 2026, 5 invoices, a 30-day interval, Net 30 and the US calendar, and left both of its date options ticked (they are the defaults): send an invoice scheduled for a weekend or holiday on the next business day, and move a due date that lands on one to the next business day. It returned:

• Invoice 1 issued Oct 26, 2026, due Nov 25, 2026
• Invoice 2 issued Nov 25, 2026, due Dec 28, 2026
• Invoice 3 issued Dec 28, 2026, due Jan 27, 2027
• Invoice 4 issued Jan 25, 2027, due Feb 24, 2027
• Invoice 5 issued Feb 23, 2027, due Mar 25, 2027

Underneath, the schedule is plain calendar arithmetic: each issue date is the start plus a multiple of 30 days, and each due date is the issue date plus 30. Three of those raw dates land on days nobody is at a desk, and the scheduler lists all three: invoice 2's due date moves from Christmas Day to Monday 28 December, invoice 3's issue date from Christmas Day to Monday 28 December, and invoice 4's issue date from Sunday 24 January to Monday 25 January. Each due date runs from the day the invoice actually goes out, and the schedule stays anchored to 26 October, so invoice 5 is still 23 February. Untick both options and you get the raw arithmetic: invoice 3 issued on Christmas Day, invoice 4 on a Sunday, and invoice 2 due on Christmas Day.

Issuing on the next business day is a sensible default, but it is not the only choice. Priya would rather not open the new year with an invoice dated 28 December, so she sends invoice 3 early instead, on Wednesday 23 December, her last working day of the year. Moving an issue date by hand moves its due date with it, so she re-ran that one through the next tool rather than trusting the scheduler's due date for the 28th.

One more thing the scheduler will not tell you: a 30-day interval is not "monthly". Billing on the 26th of each month would have put invoice 2 on Thanksgiving (Thursday, 26 November) and invoice 3 on Saturday, 26 December. A 30-day cycle drifts through the month by a day or two at a time, which is fine if the contract says "every 30 days" and a slow source of disputes if it says "monthly". Match the interval to the contract wording. The guide to scheduling recurring freelance invoices covers why staggering clients helps; this walkthrough stays with the single client and the holidays.

Step 2: turn each due date into a payable day

The Net 30 Invoice Due Date calculator does the same 30-day count for a single invoice: with the US holiday calendar selected and the next-business-day box ticked (both are the defaults), a due date that lands on a weekend or a holiday moves to the next business day, and the result says which day it moved from.

• Invoice date Nov 25, 2026: the raw due date is Christmas Day, so the calculator returns Monday, December 28, 2026. Christmas is a Friday this year, so the roll crosses the whole weekend.
• Invoice date Dec 23, 2026: due Friday, January 22, 2027, no roll needed.
• Invoice date Jan 25, 2027: due Wednesday, February 24, 2027.
• For comparison, the original Christmas-Day issue date gives a raw due date of Sunday, January 24 (shown with the roll unticked) and a rolled one of Monday, January 25.

Here is the first hand-off question. Invoice 2's thirtieth day is Christmas Day, and both tools say 28 December by default. That is the usual legal default rather than a courtesy: New York's General Construction Law § 25, for example, lets a payment that a contract makes due on a Saturday, Sunday or public holiday, or at the end of a period that ends on one, be made on the next business day “with the same force and effect”, unless the contract says otherwise, and California Civil Code § 11 does the same for holidays. A client paying on 28 December has paid on time unless the contract says the calendar date is final. Untick the box in either tool to see the raw 25 December. Either way, write the convention into the contract ("if a due date falls on a non-business day, payment is due the next business day") and the argument never happens. The Net 30 explainer goes deeper on day zero, which is the other half of that dispute.

Invoice 1 does not roll at all: 25 November is the Wednesday before Thanksgiving. That is a different kind of risk. Plenty of finance teams take the Wednesday afternoon off, so a due date that is technically a business day can still be a day nobody approves a payment. Priya sends a short reminder on Monday 23 November rather than chasing on the 30th.

Step 3: the discount window, which moves too

Next, the Payment Terms (2/10 Net 30) calculator. Entering each issue date with its defaults of 2%, 10 days and the US calendar gives the discount cutoff and the net date side by side:

• From Oct 26, 2026: discount window until Nov 5, 2026; net due Nov 25, 2026
• From Nov 25, 2026: discount window until Dec 7, 2026 (day 10 is Saturday Dec 5); net due Dec 28, 2026 (day 30 is Christmas Day)
• From Dec 23, 2026: discount window until Jan 4, 2027 (day 10 is Saturday Jan 2); net due Jan 22, 2027
• From Jan 25, 2027: discount window until Feb 4, 2027; net due Feb 24, 2027

Two of the tenth days are Saturdays (5 December and 2 January), and the calculator moves both to the following Monday. The discount date is a deadline for paying within a period, and the same next-business-day rule that moves the net date covers it: New York's § 25 applies expressly to a payment due “within” a period that ends on a weekend or holiday. The Net 30 calculator's optional discount fields now do the same, so the two tools agree. Until October 2026 neither tool moved the discount date, which put a rolled due date next to an unrolled discount date. A supplier can still insist on the calendar date, but only by saying so. Priya does: she would rather not give away a weekend, so her invoice text says "discount applies to payments initiated by" a stated weekday date, which for invoice 2 is Friday, 4 December. Stating it in the terms is what overrides the default.

The money side is simple. The calculator reports "Saved per $1000" as $20.00, which at Priya's $8,400 cycle is $168: the client pays $8,232 instead. It also shows the annualised cost of not taking the discount: 37.2%. That is giving up 2% to be paid 20 days earlier, 2/98 for 20 days, scaled to a year. For the client, taking the discount is almost always the right call. For Priya, it is worth offering only if 21 days of earlier cash matters more to her than $168 a month. The supplier-side view of 2/10 Net 30 works through that decision; what matters for this chain is when the early money actually arrives, which is the next step.

Step 4 (optional): when the payment actually lands

A due date is the day the client should pay. It is not the day Priya can spend the money. Most of her clients pay by ACH, so the last link is the ACH Settlement calculator. It counts banking days on the US calendar, which excludes weekends and Federal Reserve holidays, including Veterans Day and Columbus Day, which plenty of businesses work through. Its default class is standard ACH, which it models as settling two banking days after the file is submitted. Results for a file sent on each due date:

• Submitted Wed Nov 25, 2026: settles Monday, November 30. Thanksgiving is skipped, and Friday 27 November counts as the first banking day.
• Submitted Mon Dec 28: settles Wednesday, December 30.
• Submitted Fri Jan 22, 2027: settles Tuesday, January 26.
• Submitted Wed Feb 24: settles Friday, February 26.

And for the discount payments: a file sent on Thursday 5 November settles Monday 9 November; one sent on Friday 4 December settles Tuesday 8 December (on the default Monday 7 December cutoff it would settle Wednesday 9 December); one sent on Monday 4 January 2027 settles Wednesday 6 January. A discount payment for invoice 3 sent on New Year's Eve would settle Tuesday 5 January, because 1 January is a Fed holiday.

Put invoice 1 side by side. Paid at the discount on 5 November, Priya has $8,232 on 9 November. Paid on the net date, she has $8,400 on 30 November. That is the real cost-benefit pair: $168 against three weeks, measured on settlement dates rather than due dates. The settlement figure is a planning number, not a promise. Same-day and next-day ACH exist, and the client's bank decides which it uses; Nacha's operating rules (nacha.org/rules) set the windows. The ACH settlement explainer covers the classes.

Where the steps interact

• Use the same calendar everywhere. The scheduler, Net 30 and Payment Terms all move dates off weekends and the holidays of the country you select. Run them with the same country and the same box ticked or unticked, or a due date in one can sit a long weekend away from the same due date in another (25 December against 28 December for invoice 2).
• A moved issue date does not re-anchor the schedule. The scheduler sends invoice 4 on 25 January but keeps invoice 5 on 23 February, 29 days later, so the cycle stays tied to 26 October. If your contract counts each cycle from the previous invoice, re-run the scheduler from the new anchor. A date you move by hand, like Priya's 23 December, is outside the tool, so re-run its due date separately.
• Payment Terms gives the discount figure. Use it for the discount cutoff and the dollar amounts, and the Net 30 calculator or the scheduler for the due date. With the same settings they agree.
• "Paid" means different things at each step. The terms usually mean "payment initiated"; your bank balance means "settled". Over Thanksgiving the gap is five calendar days.

What none of these tools do

They do not track whether an invoice was paid, chase it, or compute late fees. They use the holiday calendar you give them, so a client abroad with different bank holidays needs a separate run with their country selected. They do not know your client's payment-run day: if AP pays on Thursdays only, a Monday due date effectively becomes the previous Thursday or the next one. And while they apply the usual next-business-day default, they cannot tell you whether your contract overrides it. That is a contract term.

Checklist for the next cycle

1. Run the scheduler with the interval the contract actually uses.
2. Read the scheduler's list of moved dates, and decide whether any issue date should go out earlier instead.
3. Put any issue date you moved by hand through the Net 30 calculator with your client's country selected.
4. Check each discount cutoff in Payment Terms and state the weekday cutoff on the invoice.
5. Add two banking days (or whatever the client's bank uses) to get the date the money lands, and plan spending against that.
6. Send reminders before holiday weeks, not after.

General information about invoice scheduling and payment timing, not financial or legal advice. Payment terms, late-fee rules and settlement times depend on your contract and the banks involved, so confirm the dates with your client and your bank before relying on them.