IRC §409A for Freelancers: How a Deferred-Payment Deal With One Dominant Client Can Trigger a 20% Additional Tax Before You've Been Paid

Published: October 2, 2026 · Reading time: 13 min

TL;DR: IRC §409A — the "nonqualified deferred compensation" rules most people associate with corporate stock options and executive pensions — can reach a freelancer's deferred-payment deal with a single client, because §409A(d)(3) defines a "plan" to include "an agreement or arrangement that includes one person." Most freelancers escape it one of two ways: the independent-contractor exclusion in Treas. Reg. §1.409A-1(f)(2), which requires "significant services" to two or more unrelated clients (automatically satisfied only if no single client exceeds 70% of your revenue for the year, and unavailable at all to anyone providing actual "management services" to a client), or the separate "short-term deferral" rule in Treas. Reg. §1.409A-1(b)(4), which rescues a payment actually made by 2½ months after the end of the taxable year in which the right to it vests — for a calendar-year freelancer, generally March 15 of the following year, not a flat 2½ months after the vesting date itself — meaning most merely slow-paying clients are not a §409A problem at all. In the worked example below, a freelance engineer whose dominant client is 85% of his revenue loses the 70% safe harbor, and a payment clause that gives the client open-ended discretion with no outer date limit both misses the short-term-deferral window and fails §409A's six permitted payment events outright — pulling a deferred $30,000.00 milestone payment into this year's income: a flat $6,000.00 additional tax under §409A(a)(1)(B)(i)(II), plus $5,891.60 of incremental income tax, for $11,891.60 combined — before interest, and before the client has paid him anything.

Nearly everything written about §409A is aimed at employees of companies that offer nonqualified pensions, deferred bonuses, or stock rights. That's where the rule is used most often, and it's a reasonable place to assume it stops. It doesn't. The regulations define "service provider" broadly enough to include any cash-method independent contractor, and the statute's definition of "plan" is deliberately written to catch an arrangement as small as a single clause in a single contract between a freelancer and one client. For most freelancers, a specific regulatory exclusion keeps this irrelevant. For a freelancer who is unusually dependent on one client — which describes a lot of freelancers, especially early in a relationship with a major account — that exclusion can quietly fail to apply, and the consequences of a §409A failure are unusually severe.

What Makes an Arrangement a "Plan" in the First Place

IRC §409A(d)(1) defines a nonqualified deferred compensation plan as "any plan that provides for the deferral of compensation," other than a qualified employer plan or certain leave/disability/death benefit plans. §409A(d)(3) then defines "plan" itself:

"The term 'plan' includes any agreement or arrangement, including an agreement or arrangement that includes one person."

There's no minimum number of participants, no requirement that an employer sponsor it, and no requirement that the parties call it a "plan" anywhere in the contract. What matters is whether, at some point, you obtain a legally binding right to a payment that will be made in a later taxable year. §409A(d)(4) separately defines when that right is still contingent rather than vested: "The rights of a person to compensation are subject to a substantial risk of forfeiture if such person's rights to such compensation are conditioned upon the future performance of substantial services." Once a milestone is certified complete and no further substantial services are required to earn that specific payment, the risk of forfeiture is gone — even if the cash itself is still sitting with the client.

Treas. Reg. §1.409A-1(f)(1) defines who counts as a "service provider" this broadly applies to:

"The term service provider includes an individual, corporation, subchapter S corporation, partnership... for any taxable year in which such individual... accounts for gross income from the performance of services under the cash receipts and disbursements method of accounting."

That's the ordinary definition of a cash-basis freelance sole proprietor. Nothing about §409A's scope exempts you for being self-employed rather than salaried.

The Exclusion That Saves Most Freelancers — and Its Three Conditions

The reason this doesn't blow up every freelance retainer, royalty, or holdback arrangement in the country is Treas. Reg. §1.409A-1(f)(2)(i), the independent-contractor exclusion. Its operative text:

"Except as otherwise provided in paragraph (f)(2)(iv) of this section, section 409A does not apply to an amount deferred under a plan between a service provider and service recipient with respect to a particular trade or business in which the service provider participates... if during the service provider's taxable year in which the service provider obtains a legally binding right to the payment of the amount deferred each of the following applies: (A) The service provider is actively engaged in the trade or business of providing services, other than as an employee or as a member of the board of directors... (B) The service provider provides significant services to two or more service recipients to which the service provider is not related and that are not related to one another... (C) The service provider is not related to the service recipient."

Condition (C) borrows its definition of "related" from existing related-party rules, with a deliberate tightening: the regulation applies the relationship tests in IRC §267(b) and §707(b)(1) (family relationships, controlling ownership of corporations and partnerships, common control) but "the language '20 percent' is used instead of '50 percent' each place it appears" — a much lower ownership threshold than those sections normally use elsewhere in the Code. An individual freelancer is also treated as related to a client-entity if the freelancer is "an officer of an entity that is a corporation, or holds a position substantially similar to an officer" with a noncorporate client.

Every freelancer needs to clear all three conditions, in the specific year the legally binding right arises — not merely in general, and not based on how the business usually operates.

The 70% Rule: What Losing the Safe Harbor Does and Doesn't Do

Condition (B) — "significant services to two or more... unrelated" clients — sounds like a facts-and-circumstances judgment call, and the regulation says exactly that as its baseline: "Whether a service provider is providing significant services depends on the facts and circumstances of each case." But Treas. Reg. §1.409A-1(f)(2)(iii) then supplies a bright-line safe harbor that does almost all the real work in practice:

"A service provider who provides services to two or more service recipients to which the service provider is not related and that are not related to one another is deemed to be providing significant services to two or more of such service recipients for a given taxable year, if the revenues generated from the services provided to any service recipient or group of related service recipients during such taxable year do not exceed 70 percent of the total revenue generated by the service provider from the trade or business of providing such services."

Stay under 70% concentration from any one client (or related group of clients) in the relevant year, and you're automatically deemed to satisfy condition (B) — no further analysis needed. There's also a lookback alternative for an established business: if in each of the prior three consecutive years no client exceeded 70%, and at the time of the deferral you don't know or have reason to anticipate the current year will exceed it either, you can rely on that history instead of the current year's number.

Exceeding 70% does not automatically mean §409A applies. It means you lose the deeming rule and fall back to the regulation's general, fact-intensive test — a materially weaker position to be in, but not a per se failure. In practice, very few freelancers want to rely on an unresolved facts-and-circumstances argument against a 20%-additional-tax exposure if there's any way to avoid it, which is why advisors generally treat crossing 70% as the trigger to start treating the arrangement as §409A-covered and design its payment terms accordingly — even though the regulation itself doesn't compel that conclusion.

One category of freelancer can't use this exclusion at all, regardless of how diversified their client base is. Treas. Reg. §1.409A-1(f)(2)(iv):

"This paragraph (f)(2) does not apply to a service provider to the extent the service provider provides management services to a service recipient. For purposes of this paragraph (f)(2)(iv), the term management services means services that involve the actual or de facto direction or control of the financial or operational aspects of a trade or business of the service recipient, or investment management or advisory services provided to a service recipient whose primary trade or business includes the investment of financial assets..."

A freelance fractional CFO or COO who actually directs a client's finances or operations falls outside the exclusion entirely on this ground alone — the 70% test never even comes into play for that engagement.

The Six Payment Triggers §409A Allows

If the exclusion doesn't apply, the arrangement has to be designed like any other nonqualified deferred compensation plan. IRC §409A(a)(2)(A) limits when a compliant plan may pay out to exactly six events:

"Compensation deferred under the plan may not be distributed earlier than— (i) separation from service... (ii) the date the participant becomes disabled... (iii) death, (iv) a specified time (or pursuant to a fixed schedule) specified under the plan at the date of the deferral of such compensation, (v)... a change in the ownership or effective control of the corporation, or in the ownership of a substantial portion of the assets of the corporation, or (vi) the occurrence of an unforeseeable emergency."

A clause letting the client decide the payment date at its own discretion after some future event — "payable upon final acceptance review," with no date or fixed schedule written down at the time the deferral arose — doesn't match any of the six. It's not "a specified time... specified under the plan at the date of the deferral," because nothing was actually specified; the client simply reserved discretion. And despite a common assumption, it's not "separation from service" either — but not because contractors lack that trigger. They don't; see below. It fails this event for a narrower reason: the clause isn't keyed to the end of the engagement at all, only to one deliverable's acceptance review while the underlying relationship continues. IRC §409A(a)(3) adds a second, independent requirement: "the plan does not permit the acceleration of the time or schedule of any payment under the plan, except as provided in regulations by the Secretary." A plan that lets either party move the date around after the fact — earlier or later — fails this requirement even if it also happened to specify a schedule.

Independent Contractors Do Get a "Separation From Service" — Just Not the Employee Version

It's a common assumption that "separation from service" is an employee-only concept and that freelancers simply have no version of it to use as a payment trigger. That's wrong. Treas. Reg. §1.409A-1(h)(2)(i) defines one specifically for contractors:

"An independent contractor is considered to have a separation from service with the service recipient upon the expiration of the contract (or in the case of more than one contract, all contracts) under which services are performed for the service recipient if the expiration constitutes a good-faith and complete termination of the contractual relationship."

The trigger is the end of the contractual relationship itself, not anything resembling an employee's termination-of-employment test — and the regulation immediately narrows it with a real anti-abuse condition:

"An expiration does not constitute a good faith and complete termination of the contractual relationship if the service recipient anticipates a renewal of a contractual relationship or the independent contractor becoming an employee. For this purpose, a service recipient is considered to anticipate the renewal of the contractual relationship with an independent contractor if it intends to contract again for the services provided under the expired contract, and neither the service recipient nor the independent contractor has eliminated the independent contractor as a possible provider of services under any such new contract."

So a contract's expiration date can be a valid, usable §409A(a)(2)(A)(i) payment trigger for a freelancer — but only if the client genuinely isn't planning to keep using you for the same work. A freelancer whose "expiring" contract is really just a formality before the next renewal doesn't get a separation-from-service event out of it, even on the expiration date itself. This is why the clause in this post's worked example still fails the six-events test: it isn't tied to contract expiration at all, so whether Marcus's relationship with Meridian is actually ending is beside the point.

The Short-Term Deferral Exception: Why Most Late-Paying Clients Aren't a §409A Problem

Before the six-events test even matters, there's a threshold question worth asking first: does §409A's deferral machinery apply to this payment at all? Often it doesn't. Treas. Reg. §1.409A-1(b)(4)(i), the "short-term deferral" rule, says so directly:

"A deferral of compensation does not occur under a plan with respect to any payment... that is not a deferred payment, provided that the service provider actually or constructively receives such payment on or before the last day of the applicable 2 1/2 month period."

The "applicable 2½-month period" runs to the 15th day of the third month after the end of the taxable year in which your right to the payment stopped being subject to a substantial risk of forfeiture (technically the later of your own taxable year-end or the client's, though for a calendar-year freelancer with a calendar-year client those are the same date) — for a calendar-year freelancer whose right vests sometime in 2026, that's March 15, 2027. Get the money by then, and §409A treats the arrangement as though no deferral ever happened: no six-events test, no acceleration rule, no 20% additional tax, no matter how loosely the contract describes the payment date. This is the rule that keeps an ordinary "my client is a little slow to pay" problem from being a §409A problem — late by weeks or a few months, paid inside the window, and the short-term deferral rule swallows the whole scenario.

It has a real limit, though, and the limit is what matters for this post's worked example. The same regulation treats a payment as a "deferred payment" — outside the short-term deferral exception regardless of when it's actually paid — if it's made under a plan provision tied to a date or event "that will or may occur later than the end of the applicable 2 1/2 month period... regardless of whether an amount is actually paid as a result of the occurrence of such a payment date or event during the applicable 2 1/2 month period." An open-ended "whenever the client gets around to it" clause, with no outer date at all, is exactly that kind of provision — the triggering event can occur later than the window, so the payment is a "deferred payment" by its own terms even apart from how it actually plays out in practice.

What Happens When the Plan Fails

Two consequences, both measured against the deferred amount, and neither one waits for the money to actually change hands. IRC §409A(a)(1)(A)(i):

"If at any time during a taxable year a nonqualified deferred compensation plan... fails to meet the requirements of paragraphs (2), (3), and (4), or is not operated in accordance with such requirements, all compensation deferred under the plan for the taxable year and all preceding taxable years shall be includible in gross income for the taxable year to the extent not subject to a substantial risk of forfeiture and not previously included in gross income."

And §409A(a)(1)(B)(i):

"If compensation is required to be included in gross income under subparagraph (A) for a taxable year, the tax imposed by this chapter for the taxable year shall be increased by the sum of— (I) the amount of interest determined under clause (ii), and (II) an amount equal to 20 percent of the compensation which is required to be included in gross income."

The interest in clause (ii) is "the amount of interest at the underpayment rate plus 1 percentage point on the underpayments that would have occurred had the deferred compensation been includible in gross income for the taxable year in which first deferred" — so if the legally binding right arose in an earlier year than the one in which the defect is caught, interest runs the whole distance between those two years, compounding on a hypothetical underpayment. If the right arises and the defect is identified in the same year, as in the worked example below, there is no such gap and no interest component at all — the clock only starts once there's a year to run interest from.

How This Gets Reported: Form 1099-MISC, Boxes 12 and 15

The current Instructions for Forms 1099-MISC and 1099-NEC (Rev. 12-2026) give this its own dedicated reporting lines, confirming the IRS treats this as a routine, expected occurrence rather than an edge case:

"Box 12. Section 409A Deferrals... If you complete this box, enter the total amount deferred during the year of at least $2,000 for the nonemployee under all nonqualified plans."

"Box 15. Nonqualified Deferred Compensation. Enter all amounts deferred of at least $2,000 (including earnings on amounts deferred) that are includible in income under section 409A because the NQDC plan fails to satisfy the requirements of section 409A."

Box 12 is informational — the client reports what's deferred under a plan each year regardless of whether anything has gone wrong. Box 15 is where a client reports the specific dollar amount pulled into your income because the plan failed §409A — the exact number this post's worked example computes. The instructions separately note that correction procedures exist for certain failures (see IRS Notice 2008-113, as the instructions themselves cross-reference), which may reduce or avoid the inclusion in some circumstances; whether your facts qualify for a correction is a question for a tax professional, not something to assume either way from this post.

Worked Example: One Freelancer, One Dominant Client, One Bad Clause

Facts. Marcus is a single freelance backend/data engineer — he builds and maintains data pipelines for clients, with no financial or operational control over any client's business, so the "management services" carve-out in Treas. Reg. §1.409A-1(f)(2)(iv) doesn't apply to him. In 2026, his largest client, Meridian Analytics, is 85% of his total 1099 revenue for the year. His contract with Meridian includes a $30,000.00 milestone bonus that becomes a legally binding, no-longer-forfeitable right in June 2026, once a specific deliverable is certified complete — but the contract lets Meridian choose the exact payment date at its own discretion following a "final acceptance review," with no date or fixed schedule written down anywhere, and no language tying the payment to the end of the Meridian engagement. That discretion isn't hypothetical: Meridian's accounts-payable process has paid Marcus's two previous milestone bonuses under this identical clause 11 and 16 months after certification, respectively, and on that same pattern he doesn't expect this $30,000.00 payment until around August 2027 — roughly 14 months after certification. His 2026 Schedule C net profit (unrelated to the bonus) is $120,000.00, and he has no other income.

Does the short-term deferral exception rescue this before anything else matters? No, on two independent grounds. The right became non-forfeitable in 2026, so the short-term deferral deadline under Treas. Reg. §1.409A-1(b)(4)(i) is March 15, 2027 — the 15th day of the third month after the end of that taxable year. First, the clause's open-endedness alone takes it outside the exception: because Meridian's discretion has no outer date, the payment is made under a provision that "will or may occur later than" the 2½-month window, which Treas. Reg. §1.409A-1(b)(4)(i)(D) treats as a deferred payment regardless of when it's actually paid. Second, as the payment history above shows, the money is in fact expected around August 2027 — about five months past the March 15, 2027 deadline. Either fact alone would be enough; both apply here. That's what makes the rest of this analysis live rather than moot.

Because Meridian is 85% of his 2026 revenue — above the 70% safe-harbor threshold in Treas. Reg. §1.409A-1(f)(2)(iii) — Marcus can't automatically rely on the independent-contractor exclusion for this deferral. And independent of that, the payment clause itself doesn't match any of the six permitted events in §409A(a)(2)(A). It isn't "a specified time (or pursuant to a fixed schedule) specified... at the date of the deferral," because nothing was actually specified — Meridian simply reserved discretion. And it isn't "separation from service," either: contractors do get that trigger under Treas. Reg. §1.409A-1(h)(2)(i), but only when a payment is keyed to "the expiration of the contract... under which services are performed," and Marcus's clause isn't keyed to the end of his Meridian engagement at all — only to one deliverable's acceptance review, with the underlying relationship continuing. The plan fails on its terms the same year the right arises, so the $30,000.00 is includible in Marcus's 2026 gross income under §409A(a)(1)(A) — reported, once Meridian catches the issue and corrects his Form 1099-MISC, in Box 15.

node -e "
// ============================================================
// IRC Sec. 409A failed-plan inclusion -- 2026 worked example
// ============================================================
const STD_DEDUCTION_SINGLE_2026 = 16100;   // Rev. Proc. 2025-32 Sec. 3.14
const QBI_THRESHOLD_SINGLE_2026 = 201750;  // Rev. Proc. 2025-32 Sec. 3.26 ('All Other Returns')
const DEFERRED_AMOUNT = 30000;             // Sec. 409A(a)(1)(A) inclusion amount

function seTax(netProfit) {
  const earnings = netProfit * 0.9235;
  const tax = earnings * 0.153;
  return { earnings, tax, half: tax / 2 };
}

function bracket2026Single(taxableIncome) {
  // Rev. Proc. 2025-32 Sec. 3.01, TABLE 3 -- Unmarried Individuals, 2026
  const b = [
    [0, 12400, 0.10, 0],
    [12400, 50400, 0.12, 1240],
    [50400, 105700, 0.22, 5800],
    [105700, 201775, 0.24, 17966],
    [201775, 256225, 0.32, 41024],
    [256225, 640600, 0.35, 58448],
    [640600, Infinity, 0.37, 192979.25],
  ];
  for (const [lo, hi, rate, base] of b) {
    if (taxableIncome > lo && taxableIncome <= hi) return { rate, tax: base + (taxableIncome - lo) * rate };
  }
}

// otherIncome = the Sec.409A(a)(1)(A) inclusion -- reported as other income (1099-MISC Box 15),
// NOT as Schedule C / QBI, since it is not yet actually or constructively received.
function compute(netProfit, otherIncome) {
  const se = seTax(netProfit);
  const qbiBase = netProfit - se.half;
  const tentative = qbiBase * 0.20;
  // Sec.199A(e)(1): taxable income for the cap is computed 'without regard to any deduction
  // allowable under this section' -- i.e. before the QBI deduction itself.
  const tiBeforeQBI = netProfit - se.half - STD_DEDUCTION_SINGLE_2026 + otherIncome;
  const cap = Math.max(0, tiBeforeQBI) * 0.20; // Sec.199A(a)(2): 20% of (taxable income - net cap gain); no cap gain here
  const qbi = Math.min(tentative, cap);
  const ti = Math.max(0, tiBeforeQBI - qbi);
  const { rate, tax } = bracket2026Single(ti);
  return { se, qbiBase, tentative, tiBeforeQBI, cap, qbi, ti, rate, tax };
}

const NET_PROFIT = 120000;
const base = compute(NET_PROFIT, 0);
const withFailure = compute(NET_PROFIT, DEFERRED_AMOUNT);

console.log('=== BASELINE -- Schedule C profit only, no Sec.409A issue ===');
console.log('Net profit:', NET_PROFIT.toFixed(2));
console.log('SE tax:', base.se.tax.toFixed(2), '| half (above-the-line):', base.se.half.toFixed(2));
console.log('Taxable income before QBI:', base.tiBeforeQBI.toFixed(2), '< Sec.199A threshold ($' + QBI_THRESHOLD_SINGLE_2026 + ')?', base.tiBeforeQBI < QBI_THRESHOLD_SINGLE_2026, '-> SSTB status & W-2 wage/UBIA cap both irrelevant in both scenarios below');
console.log('Tentative QBI deduction (20% of QBI base):', base.tentative.toFixed(2));
console.log('20%-of-taxable-income cap (Sec.199A(a)(2)):', base.cap.toFixed(2), base.qbi < base.tentative ? '<- BINDS' : '<- does not bind');
console.log('QBI deduction allowed:', base.qbi.toFixed(2));
console.log('Taxable income:', base.ti.toFixed(2), '| tax:', base.tax.toFixed(2), '| marginal bracket:', (base.rate * 100) + '%');
console.log();
console.log('=== WITH the $' + DEFERRED_AMOUNT.toFixed(2) + ' Sec.409A(a)(1)(A) inclusion (failed plan) ===');
console.log('Taxable income before QBI:', withFailure.tiBeforeQBI.toFixed(2), '< Sec.199A threshold?', withFailure.tiBeforeQBI < QBI_THRESHOLD_SINGLE_2026);
console.log('Tentative QBI deduction (unchanged -- the inclusion is not QBI):', withFailure.tentative.toFixed(2));
console.log('20%-of-taxable-income cap (now LARGER because the cap base grew):', withFailure.cap.toFixed(2), withFailure.qbi < withFailure.tentative ? '<- still binds' : '<- NO LONGER BINDS, full tentative QBI deduction allowed');
console.log('QBI deduction allowed:', withFailure.qbi.toFixed(2));
console.log('Taxable income:', withFailure.ti.toFixed(2), '| tax:', withFailure.tax.toFixed(2), '| marginal bracket:', (withFailure.rate * 100) + '%');
console.log();

const incomeTaxDelta = withFailure.tax - base.tax;
const additionalTax20 = DEFERRED_AMOUNT * 0.20;
const qbiUnlocked = withFailure.qbi - base.qbi;

console.log('Incremental ORDINARY INCOME TAX from the Sec.409A inclusion:', incomeTaxDelta.toFixed(2));
console.log('Flat 20% additional tax, Sec.409A(a)(1)(B)(i)(II):', additionalTax20.toFixed(2));
console.log('TOTAL cost of the failed plan (excluding interest -- see note below):', (incomeTaxDelta + additionalTax20).toFixed(2));
console.log('Extra QBI deduction unlocked because the cap loosened (side effect, already included above):', qbiUnlocked.toFixed(2));
console.log();
console.log('Interest under Sec.409A(a)(1)(B)(i)(I)/(ii): $0.00 in THIS example, because the legally binding');
console.log('right and the inclusion both fall in 2026 -- there is no prior year for underpayment interest to');
console.log('run from. Had the right instead arisen in an earlier year with the same defective clause, interest');
console.log('at the federal underpayment rate plus 1 percentage point would run from that earlier year forward,');
console.log('and the inclusion itself would belong on that earlier year\\'s return, not this one.');
"

Output:

=== BASELINE -- Schedule C profit only, no Sec.409A issue ===
Net profit: 120000.00
SE tax: 16955.46 | half (above-the-line): 8477.73
Taxable income before QBI: 95422.27 < Sec.199A threshold ($201750)? true -> SSTB status & W-2 wage/UBIA cap both irrelevant in both scenarios below
Tentative QBI deduction (20% of QBI base): 22304.45
20%-of-taxable-income cap (Sec.199A(a)(2)): 19084.45 <- BINDS
QBI deduction allowed: 19084.45
Taxable income: 76337.82 | tax: 11506.32 | marginal bracket: 22%

=== WITH the $30000.00 Sec.409A(a)(1)(A) inclusion (failed plan) ===
Taxable income before QBI: 125422.27 < Sec.199A threshold? true
Tentative QBI deduction (unchanged -- the inclusion is not QBI): 22304.45
20%-of-taxable-income cap (now LARGER because the cap base grew): 25084.45 <- NO LONGER BINDS, full tentative QBI deduction allowed
QBI deduction allowed: 22304.45
Taxable income: 103117.82 | tax: 17397.92 | marginal bracket: 22%

Incremental ORDINARY INCOME TAX from the Sec.409A inclusion: 5891.60
Flat 20% additional tax, Sec.409A(a)(1)(B)(i)(II): 6000.00
TOTAL cost of the failed plan (excluding interest -- see note below): 11891.60
Extra QBI deduction unlocked because the cap loosened (side effect, already included above): 3220.00

Interest under Sec.409A(a)(1)(B)(i)(I)/(ii): $0.00 in THIS example, because the legally binding
right and the inclusion both fall in 2026 -- there is no prior year for underpayment interest to
run from. Had the right instead arisen in an earlier year with the same defective clause, interest
at the federal underpayment rate plus 1 percentage point would run from that earlier year forward,
and the inclusion itself would belong on that earlier year's return, not this one.

Four things worth noticing, in order:

1. The $30,000.00 is real money owed on money Marcus hasn't received. Meridian still has sole discretion over when the $30,000.00 actually gets paid — that's the very defect that caused the failure — yet Marcus owes $11,891.60 in tax on it for 2026 regardless.

2. The §199A 20%-of-taxable-income cap moves in the opposite direction from a deduction. This site's HSA last-month rule post shows an above-the-line deduction shrinking that cap's base and reducing the QBI deduction allowed. Here, the §409A inclusion is ordinary income that isn't QBI, so it grows the cap's base instead — in this example, enough to stop the cap from binding at all, unlocking an extra $3,220.00 of the QBI deduction Marcus was already entitled to from his regular Schedule C profit. That partial offset is real, but it's nowhere close to covering an $11,891.60 bill.

3. The flat 20% additional tax is the one piece of this that never depends on a bracket. Whatever rate Marcus's income is taxed at, §409A(a)(1)(B)(i)(II) is a flat 20% of the included amount — $6,000.00 here — layered on top of whatever the regular income tax works out to.

4. This example has zero interest only because the timing happens to line up. The legally binding right and the discovery of the defective clause both fall in 2026, so there's no earlier year for the statute's underpayment-rate-plus-1-point interest to run from. That's the favorable case. The more common real-world version of this mistake is a multi-year contract where the defective clause sat unnoticed for a year or more after the right became binding — in which case the inclusion belongs on that earlier year's return, and interest compounds from then until the correction, on top of everything computed above.

This Is Not the Same as Simply Billing Late

It's worth being precise about the boundary, because the two are easy to blur. This site's guide to deferring freelance income to next year describes a completely different, lower-risk move: a cash-method freelancer simply delays invoicing, so no legally binding right to a specific future payment exists yet, and the constructive-receipt doctrine governs when the income counts. Nothing in that move creates a "plan" — there's no enforceable right to anything until you actually bill for it and get paid or have payment made available to you.

A §409A "plan" requires the opposite: an enforceable, specific commitment to pay you later, created now. The milestone bonus in this post's example, the deferred half of a project fee, a royalty or earn-out payable over several years, a retainer's "holdback" released on a later date — any of these can be a §409A plan the moment the contract gives you that enforceable right, regardless of what either party calls it. Freelancers who negotiate these terms (or have them handed to them by a larger client's legal team) should treat a written deferred-payment clause as a design question subject to §409A's rules, not as a bigger version of the ordinary year-end invoice-timing move.

What This Doesn't Resolve

• Whether the inclusion is also immediately subject to self-employment tax. As the FAQ above lays out, there's no provision parallel to the employee-side FICA timing rule in IRC §3121(v)(2) written for self-employed independent contractors here. Treat this as an open question for your preparer, not a settled one either way.
• Correction procedures. The current 1099-MISC instructions reference IRS Notice 2008-113 for certain operational-failure corrections. Whether a given fact pattern qualifies, and what it would change, is specific enough to need a professional's review rather than a general answer.
• Employee and public-company arrangements. This post addresses the independent-contractor exclusion specifically. Deferred compensation for actual employees, equity compensation, and the separate rules for certain foreign and offshore deferred arrangements under IRC §457A are outside its scope.
• Exactly where the short-term-deferral/six-events line falls on an ambiguous clause. This post explains the short-term deferral rule (Treas. Reg. §1.409A-1(b)(4)) and the six permitted payment events in general terms and works through one clear-cut example of each failing. A clause with real ambiguity about how "open-ended" its timing actually is — as opposed to Marcus's clearly unbounded one — is a drafting question for a professional to read against the specific contract language, not something this post's generalizations resolve for you.

Common Mistakes to Avoid

1. Assuming §409A is strictly a corporate-executive problem. The regulations reach any cash-method independent contractor with a legally binding right to a future payment — there's no employee-status floor.
2. Treating client diversification alone as sufficient. The independent-contractor exclusion requires both the 70% revenue-concentration test and payment terms that match one of the six permitted events. Passing one without the other still leaves you exposed.
3. Treating "over 70% from one client" as an automatic §409A trigger. It removes the automatic safe harbor and shifts you to a harder facts-and-circumstances test — it does not, by itself, mean the exclusion has failed.
4. Accepting or writing a payment clause that leaves the payment date to the client's discretion. "Upon final acceptance" or similar open-ended language, with no date or fixed schedule written down when the deferral arises, doesn't satisfy any of §409A(a)(2)(A)'s six permitted events.
5. Assuming the tax lands in the year the mistake is caught rather than the year the right became binding. A document that was defective from inception can mean an earlier, already-filed return needs to be amended — with interest running from that earlier year.
6. Forgetting that the 20% additional tax and the income-tax inclusion are owed regardless of whether the client has actually paid. Both are triggered by the plan's failure, not by receipt of the cash.
7. Overlooking the "management services" carve-out. A freelancer who actually directs or controls a client's finances or operations — a fractional CFO or COO, for example — can't use the independent-contractor exclusion at all, no matter how diversified their other clients are.
8. Treating every late or deferred client payment as a §409A problem. The short-term deferral exception in Treas. Reg. §1.409A-1(b)(4) rescues a payment made by 2½ months after the end of the taxable year in which the right to it vests — for a calendar-year freelancer, generally March 15 of the following year, not a flat 2½ months after the vesting date itself — no matter how informal the contract language is. The real exposure is a clause with no outer time limit at all, not lateness by itself.
9. Assuming a freelancer has no "separation from service" trigger to design around. Treas. Reg. §1.409A-1(h)(2)(i) gives independent contractors a real one, tied to good-faith expiration of the contract — it's just not available if the client anticipates renewing the relationship.

How CentSense Helps

CentSense doesn't draft or review your client contracts — that's a job for a CPA, EA, or attorney who can read the actual payment clause — but it solves the side of this that's a recordkeeping and visibility problem:

• Every client payment is tracked and dated as it's scanned, so you can see at a glance exactly what percentage of your year-to-date revenue is coming from any one client — the number the 70% safe harbor in Treas. Reg. §1.409A-1(f)(2)(iii) actually turns on
• A clean, categorized income history makes it straightforward to pull the prior-three-years revenue breakdown the lookback version of the 70% test asks for, instead of reconstructing it from old invoices at tax time
• Year-round visibility into your actual Schedule C profit means you can model what a forced income inclusion like the one in this post's example would do to your bracket and your QBI deduction before it happens — not just after a corrected 1099-MISC shows up

For the mechanics this post assumes elsewhere, see deferring freelance income to next year for the ordinary cash-method timing move this is not, client deposits, retainers & prepayments for how upfront and deferred client payments are generally taxed, the QBI deduction for the taxable-income cap this example works through, and self-employment tax explained for the 15.3%/92.35% mechanics behind the SE-tax figures above.

Authoritative References

• 26 U.S.C. §409A — Inclusion in gross income of deferred compensation under nonqualified deferred compensation plans, especially subsections (a)(1) income inclusion and additional tax, (a)(2) permitted distribution events, (a)(3) acceleration, and (d) definitions (Cornell LII, current text)
• 26 CFR §1.409A-1 — Definitions and covered plans, especially subsection (f) "Service provider," including the independent-contractor exclusion, the 70% significant-services safe harbor, and the management-services carve-out (Cornell LII)
• 26 U.S.C. §199A — Qualified business income, especially subsection (a) the deduction and its 20%-of-taxable-income cap and (e)(1) the definition of taxable income for that cap (Cornell LII)
• Rev. Proc. 2025-32 — 2026 inflation-adjusted standard deduction, individual tax rate tables, and Section 199A threshold amounts (IRS)
• Instructions for Forms 1099-MISC and 1099-NEC (Rev. 12-2026) — Box 12 "Section 409A Deferrals" and Box 15 "Nonqualified Deferred Compensation" (IRS)
• About Form 1099-MISC (IRS)

Whether a deferred-payment clause in your next contract is a routine business term or a §409A trap comes down to two things: how concentrated your client base is that year, and exactly how the payment date is worded. Start a free CentSense account to keep your client-by-client revenue tracked and current all year, so the concentration percentage this post's safe harbor depends on is a number you already know, not one you're reconstructing after a client's attorney flags a problem. Free tier includes 10 AI scans a month, no credit card required — or upgrade to the Solo plan for $5/month for unlimited scans, mileage tracking, and a CPA-ready CSV export. Start free →

This guide is general education for U.S. self-employed freelancers filing in 2026. It is not personalized tax advice. Whether a specific contract clause creates a "legally binding right" for Section 409A purposes, whether your own client mix satisfies the independent-contractor exclusion, and how a plan failure would be computed and reported on your own return are fact-specific legal and tax determinations that depend on the exact contract language. Consult a CPA, EA, or attorney before relying on any figure in this post for your own return or before signing a contract with a deferred-payment clause.