Say your company signs a 12-month SaaS contract and bills the customer the full annual fee upfront. Under revenue recognition rules, you can't book that as revenue on day one — you have to earn it as you deliver the service. But you do have an unconditional right to collect the cash, because nothing but the passage of time stands between you and payment. Now suppose you need working capital and sell that receivable to a factoring company for 90 cents on the dollar.
What did you just do, accounting-wise? Did you sell an asset — the kind of clean, off-balance-sheet transaction covered by the transfers-and-servicing rules? Or did you just take out a loan against future revenue, the kind of arrangement that shows up as debt?
For years, the honest answer from most accountants was "it depends who you ask." The Financial Accounting Standards Board (FASB) has now closed that gap. Buried inside a routine-sounding cleanup bill — Accounting Standards Update (ASU) 2025-12, Codification Improvements — is a fix that matters a lot if your business ever sells, factors, or otherwise monetizes receivables that were billed before the underlying work was finished.
The Ambiguity FASB Just Killed
In December 2025, FASB issued ASU 2025-12, a bundle of 33 unrelated technical corrections to the accounting codification. Most of them are genuinely boring housekeeping. Issue 20 is not — it addresses a real gap that had been generating inconsistent practice for years.
Here's the underlying problem, in plain English. Revenue recognition rules (ASC 606) say a receivable exists once you have an "unconditional right to consideration" — meaning only time, not further performance, stands between you and getting paid. That can happen before you've finished delivering the goods or service: think annual SaaS billed upfront, a professional-services retainer paid in advance, or a construction contract where a progress payment becomes unconditionally due before the milestone is fully complete.
FASB had been fielding a specific question from preparers and auditors: when a company transfers (sells, factors, securitizes) one of these early-recognized receivables, which rulebook governs?
- ASC 860, Transfers and Servicing — the framework for selling financial assets, which lets you take the receivable off your balance sheet entirely if the sale meets "true sale" criteria.
- ASC 470, Debt — the framework for financing arrangements, under which the cash you received looks less like a sale and more like a loan collateralized by future revenue, meaning it stays on your balance sheet as a liability.
That's not a technicality. It's the difference between your balance sheet showing a clean asset sale and your balance sheet showing new debt — which affects your leverage ratios, your loan covenants, and how a lender or investor reads your financials.
What the New Rule Actually Says
Issue 20 amends the implementation guidance in Subtopic 860-10 (specifically paragraph 860-10-55-5 and new paragraph 860-10-55-14A) to add "receivables from contracts with customers" to the explicit list of instruments whose transfer is governed by ASC 860's transfer-of-financial-assets rules — the same list that already includes things like lease receivables and litigation judgments.
The new text is direct: an entity may have an unconditional right to consideration from a customer before it has transferred control of the underlying good or service, and if that receivable meets the definition of a financial asset, its transfer is subject to the requirements of ASC 860. FASB considered going further — clarifying whether a seller's ongoing performance obligations count as "continuing involvement," and whether these transfers could instead be recharacterized as sales of future revenue under ASC 470 — but ultimately kept the fix narrow. It answers which framework applies, not every downstream question about how the sale is measured.
Why "Which Framework Applies" Isn't the Whole Story
This is the part worth flagging for any business owner about to celebrate: Issue 20 tells you that ASC 860 governs the transfer. It does not automatically hand you off-balance-sheet treatment.
To actually get sale accounting under ASC 860, the transfer still has to clear the "true sale" test — the transferor must have surrendered control, which generally means:
- The transferred receivable is legally isolated from the seller, even in bankruptcy.
- The buyer has the right to pledge or exchange the receivable (or an interest in it) without restrictions that provide the seller more than a trivial benefit.
- The seller doesn't maintain effective control over the receivable — for example, through an agreement to repurchase it before maturity, or through recourse provisions that shift the credit risk back to the seller.
A factoring or revenue-based-financing deal with recourse, a repurchase obligation, or heavy seller involvement can still land you in secured-borrowing territory — meaning the cash you got shows up as a liability, not a sale, regardless of what Issue 20 clarified. What's changed is that you no longer have to guess whether you're even asking the right question. Before Issue 20, some preparers were analyzing these transfers under ASC 470's "sales of future revenue" guidance by default, simply because it wasn't clear ASC 860 applied at all.
A Worked Example
Picture a consulting firm that just signed a $240,000, 12-month retainer with a client, billed and unconditionally due in full at signing under the contract terms, even though the work will be delivered month by month. Under ASC 606, the firm can't recognize $240,000 of revenue yet — that gets earned as the engagement progresses. But the firm does record a $240,000 receivable, because the client owes the money regardless of how the work unfolds from here.
Cash-strapped and waiting on that money, the firm sells the receivable to a finance company for $220,000 upfront, agreeing to a 30-day repurchase window if the client disputes the invoice.
- If the deal clears the ASC 860 true-sale test (no effective control retained, receivable legally isolated, buyer free to resell it), the firm records $220,000 in cash, derecognizes the $240,000 receivable, and books the $20,000 discount as a financing expense. The transaction disappears from the liability side of the balance sheet entirely.
- If the 30-day repurchase obligation is broad enough to count as retained effective control, the transfer fails the true-sale test. The $220,000 shows up as a secured loan — a liability — and the receivable stays on the books until it's collected or the repurchase window lapses.
Before Issue 20, some firms in this exact situation were unsure whether to even run the ASC 860 test in the first place, since it wasn't settled that a pre-performance receivable like this one qualified as the kind of "financial asset" the transfers-and-servicing rules were built for. Now that question is off the table — the only analysis left is whether the deal's specific terms pass true-sale muster.
Who This Actually Affects
The businesses most likely to run into this aren't limited to traditional invoice factoring on completed work — that's a more straightforward fact pattern most CPAs already handle consistently. The ambiguity Issue 20 fixes shows up specifically where a receivable becomes unconditional before performance is complete:
- SaaS and subscription businesses that bill annually or multi-year upfront and later monetize that receivable stream for working capital.
- Professional services firms — agencies, consultancies, law firms — with retainers or milestone billing schedules that create an unconditional right to payment ahead of finishing the engagement.
- Construction and long-term contractors using percentage-of-completion accounting, where progress billings can become unconditionally due before the corresponding work is finished.
- Any business exploring revenue-based financing, where a lender advances cash against a slice of future receivables — an arrangement that sits right at the ASC 860 / ASC 470 boundary this issue addresses.
If your factoring or financing arrangement only ever involves fully earned, already-invoiced trade receivables for completed work, the practical accounting for you probably doesn't change much — that fact pattern was less contested. The real value of Issue 20 is for the messier cases in between.
Effective Date and What to Do Before Then
The amendments in ASU 2025-12 are effective for all entities for annual reporting periods beginning after December 15, 2026, and interim periods within those years. FASB is permitting early adoption — in either an interim or annual period, as long as financial statements haven't yet been issued — and critically, adoption can be elected issue-by-issue, meaning you can adopt the Issue 20 clarification on its own timeline without being forced to adopt all 33 corrections in the ASU at once. Transition can be applied either prospectively (to transactions on or after the adoption date) or retrospectively (adjusting the opening balance of retained earnings for the earliest period presented), and that choice can also be made issue-by-issue.
Practical steps if you factor or plan to factor receivables that were recognized before performance was complete:
- Pull your existing factoring or revenue-based-financing agreements and check for recourse clauses, repurchase obligations, or servicing arrangements that could keep the receivable on your books regardless of which framework applies.
- Ask your CPA or auditor directly whether any past transfers were analyzed under ASC 470 by default — Issue 20 gives you grounds to revisit that classification going forward.
- If you're negotiating a new financing arrangement, structure it with the ASC 860 true-sale criteria in mind from the start if off-balance-sheet treatment matters to your lenders or investors.
- Don't wait until the 2026 fiscal-year effective date if the clarification resolves an ambiguity you're already living with — early adoption is available issue-by-issue specifically for cases like this.
Keeping the Paper Trail Straight
Whichever side of the ASC 860 line your receivable transfers fall on, the accounting only holds up if your records show clearly what happened: which receivables were sold, on what terms, with what recourse provisions, and how the resulting cash and any retained obligation were booked. That's easier to defend to an auditor when your ledger is plain text, version-controlled, and auditable line by line rather than buried in a black-box spreadsheet. Beancount.io gives you exactly that kind of transparent record — every entry traceable, every change diffable — which matters most when a rule like this one asks you to reclassify how a transaction has been sitting on your books. Get started for free and see how plain-text accounting keeps you ready for the next codification cleanup, not scrambling after it.