Accounting Treatment Memo
You get a sourced technical memo on accounting for your transaction under your chosen standard. It cites authoritative guidance and peer disclosures from public filings.
Built for controllers and technical accountants documenting how to account for a transaction.
Why this work is hard
Controllers and technical accountants documenting how to account for a transaction spend hours on this by hand: finding the right sources, reading them, checking them against each other and writing up what matters. The work is repetitive, it is easy to miss something, and nobody can show where a claim came from.
Accounting Treatment Memo does that work as a GREP AI agent. It runs when you ask, and you can put it on a daily, weekly or monthly schedule. Every run delivers a Word document, with every claim linked to its source.
What you get
What Accounting Treatment Memo delivers
Accounting Treatment Memo: Three-year SaaS contract (platform access, implementation services, usage-based overage; billed annually in advance) under ASC 606
Prepared: October 6, 2026. Industry: enterprise software. Framework: US GAAP, ASC 606 (Revenue from Contracts with Customers).
Interpretation: The request names ASC 606 without a jurisdiction, so US GAAP is assumed. Paragraph text is quoted or paraphrased from Deloitte DART reproductions of the Codification because asc.fasb.org was not publicly readable (see Coverage note).
Bottom line
- Implementation: On the assumed facts (the vendor configures and integrates its own multi-tenant SaaS, the customer cannot use the platform without it, and the vendor does not sell the service separately), treat implementation as a promised service that is not distinct from the SaaS. Combine it with platform access into one stand-ready performance obligation and recognize the implementation fee ratably over the three-year term. If the facts change (third parties routinely perform the work, or the SaaS is sold on its own), implementation becomes a separate performance obligation. Practice diverges: not settled.
- Usage fees: Overage fees are variable consideration. If the overage rate is fixed and any included-usage allowance resets each period, allocate the fees to the distinct service period in which usage occurs and recognize them as usage happens, without estimating them at inception. If the allowance is annual and does not reset, or the rate changes during the term, the allocation exception may not be available and an estimate subject to the constraint is needed. Practice diverges: not settled.
Scope note: Research support, not an audit opinion. Confirm the facts and conclusions with your auditor.
1. Background and assumed facts
Given facts. A software vendor (the entity) signs a three-year contract with an enterprise customer. The contract bundles (a) access to a hosted software platform (SaaS), (b) implementation services, and (c) usage-based overage fees. Fees are billed annually in advance.
Assumed facts (labeled assumptions, carried into Section 8).
- A1. The platform is multi-tenant SaaS; the customer has no contractual right to take possession of the software and cannot run it on its own hardware or with another host.
- A2. Implementation is configuration, data migration and integration of the vendor’s platform with the customer’s systems, performed mainly by the vendor. It does not significantly modify the platform’s source code. The vendor does not sell the platform without implementation and does not sell implementation separately; no partner ecosystem routinely performs it.
- A3. Fixed fees: platform $400,000 per year; implementation $120,000, billed with the first annual invoice. Contract is non-cancelable and invoices are due within 30 days (so the right to consideration is unconditional once billed). All amounts are illustrative.
- A4. Overage: an included usage allowance resets each month; transactions above the monthly allowance are charged at a fixed per-unit rate that does not change during the three-year term. Year 1 overage is assumed to be $30,000.
- A5. Payment is due within 30 days of annual invoicing, so the gap between payment and service delivery is 12 months or less for each annual period. SaaS services are the same each day and provided continuously from go-live (assumed to coincide with contract start for simplicity).
2. Issues
- Is implementation a distinct performance obligation, or does it combine with SaaS access under ASC 606-10-25-19 to 25-22?
- How should the usage-based overage fees be treated as variable consideration (estimation, constraint, and allocation to the series)?
- Consequential presentation: how do annual advance billing, the implementation fee and contract costs affect the balance sheet and disclosures?
3. Analysis per issue
Issue 1: Is implementation distinct?
[Authoritative] A promised service is a performance obligation if it is distinct. It is distinct only if both criteria are met: the customer can benefit from it on its own or with readily available resources (capable of being distinct), and the promise is separately identifiable from other promises in the contract (ASC 606-10-25-19, as reproduced in Deloitte Roadmap 5.3). If a promise is not distinct, the entity combines it with other promises until it identifies a bundle that is distinct, which can mean a single performance obligation for the whole contract (ASC 606-10-25-22, same source).
[Authoritative] Promises are not separately identifiable when factors such as the following exist: the entity provides a significant service of integrating goods or services into a combined output; one or more goods or services significantly modifies or customizes another; or the goods or services are highly interdependent or interrelated (ASC 606-10-25-21(a) to (c), same Roadmap 5.3 page).
[Authoritative] Before the distinct test, the entity determines whether implementation is a promised service at all or merely a setup activity that transfers nothing to the customer (ASC 606-10-25-17 and 55-53; paragraph text not separately verified in this run, but the question is posed in the Deloitte alert below). Activities that do not transfer a good or service are not performance obligations.
[Interpretive] Deloitte’s technology alert on implementation services in cloud-based software frames three outcomes: an activity that does not transfer a service, a promise that is not distinct from the SaaS, or a distinct performance obligation. It lists factors to weigh: whether third parties can or do perform the services (a partner ecosystem points to distinct); whether the SaaS is frequently sold without the entity’s implementation service (points to distinct); whether the services significantly alter SaaS features or functionality; and whether the customer could use the SaaS without the services (Deloitte, Implementation Services in Cloud-Based or Hosted Software Arrangements, November 2019).
[Inference] Applying A1 and A2: the customer cannot obtain the platform’s benefit without the vendor configuring it, no third party routinely performs the work, and the platform is not sold without it. The factors point to implementation being an input to the combined SaaS service rather than separately identifiable. Conclusion: not distinct; combine with SaaS as one stand-ready obligation satisfied over time.
[Inference] Consequence. The $120,000 implementation fee joins the transaction price of the combined obligation and is recognized with a time-based measure of progress over the three-year term, rather than as work is performed. Peers have taken this position for hosting contracts (Section 5). Costs to fulfill the implementation are assessed separately under ASC 340-40 (paragraph not verified in this run).
Issue 2: Usage-based overage fees
[Authoritative] Variable consideration is estimated using the expected value or most likely amount method, whichever better predicts the amount to which the entity will be entitled (ASC 606-10-32-8, as cited in Deloitte Roadmap 6.3). The estimate is included in the transaction price only to the extent it is probable that a significant reversal of cumulative revenue will not occur when the uncertainty resolves (ASC 606-10-32-11, same page).
[Authoritative] Allocation exception. A variable amount is allocated entirely to a performance obligation, or to a distinct service within a series under ASC 606-10-25-14(b), if (a) the variable payment relates specifically to the entity’s efforts to transfer that distinct service (or to a specific outcome) and (b) allocating it entirely there is consistent with the allocation objective in 606-10-32-28 considering all performance obligations and payment terms. Remaining transaction price is allocated under 32-28 to 32-38 (ASC 606-10-32-40 and 32-41, as reproduced in Deloitte Roadmap 7.5). The series guidance in 606-10-25-14(b) is quoted at Roadmap 5.3; 25-15 text not separately verified.
[Interpretive] Deloitte’s alert on SaaS with variable consideration (December 2019) concludes that a stand-ready SaaS priced at a fixed rate per unit of usage can use the allocation exception because the usage fees relate to a specific outcome and allocating them to each service period satisfies the allocation objective (Example 5-1). With a fixed fee plus a fixed-rate usage component, the fixed fee is recognized ratably and the usage fees as usage occurs (Example 5-2). Overage fees with a minimum that resets monthly can also qualify (Example 5-3). An annual minimum that does not reset (Example 5-4) raises the problem that the overage may be better viewed as a fee tied to the whole year, so applying the exception to later periods may not be appropriate. The alert also warns that the conclusion may not hold if the usage rate varies during the term (Examples 5-1 and 5-2).
[Interpretive] The same alert discusses the invoice practical expedient (ASC 606-10-55-18) for usage-based fees and cautions it can be hard to use where there are fixed fees, substantive minimums, varying rates or up-front fees. The assumed contract has fixed annual fees, so do not rely on 55-18 for the overage. Rely on the allocation exception instead.
[Inference] Applying A4: the allowance resets monthly and the overage rate is fixed for the term, matching Example 5-3. The overage fee relates to usage in a specific month, and allocating it to that month is consistent with the allocation objective. Conclusion: do not estimate Year 2 and Year 3 overage at inception; recognize overage fees in the month usage occurs. Because the allocation exception removes the need to include overage in the transaction price at inception, the constraint analysis largely falls away, but the vendor must still assess price concessions or credits given for outages or disputes, which are separate variable consideration.
[Inference] Fixed consideration (platform $400,000 per year and, under Issue 1, the implementation fee) is recognized ratably. Annual advance billing is a payment-timing feature, not a pricing term for revenue timing.
Issue 3: Advance billing, financing and contract costs
[Authoritative] The practical expedient in ASC 606-10-32-18 lets an entity skip adjusting for a significant financing component when the period between transfer and payment is one year or less. Only a reference to the expedient was verified, in a worked example in Deloitte Roadmap 6.3; the full paragraph text is marked paragraph not verified.
[Inference] Under A5 each annual invoice is paid within 30 days and covers the next 12 months of service, so the gap for each annual period is 12 months or less and the expedient is likely available. The implementation fee billed up front but recognized over three years creates a longer gap (up to 36 months). Evaluate whether it is a significant financing component; in this example the amount is modest and the reason for the timing is operational, not financing, but confirm with the auditor.
4. Alternative views considered
View | Why considered | Why rejected, or what would tip it |
|---|---|---|
Implementation is distinct; recognize as performed | Peers that sell implementation separately recognize it as services are performed (Dynatrace, Section 5). Deloitte lists third-party availability and stand-alone sales as indicators of distinct. | Practice diverges: not settled. Rejected here because A1 and A2 (no third-party providers, no stand-alone sale, platform unusable without it). Tipping facts: a partner ecosystem routinely implements the platform, or the vendor sells the SaaS without implementation to a significant share of customers. |
Implementation is a setup activity with no promised service | The work is front-loaded and the customer receives no separate deliverable. | Rejected if the work benefits the customer (integration and configuration of its environment). If it is purely internal to the vendor’s own systems (behind the firewall), the fee is an advance payment for SaaS and is still recognized ratably, so the revenue result is the same as Issue 1; the label differs. |
Estimate all overage at inception and include it in the transaction price | Overage is variable consideration; the expected value method could be used. | Practice diverges: not settled. Rejected under A4 because the allocation exception in 606-10-32-40 applies (fixed rate, monthly reset). Tipping facts: an annual non-resetting allowance, a rate that steps down with volume, or committed minimums that make the rate variable across periods. |
Apply the invoice practical expedient (55-18) to overage | Overage is billed as usage occurs. | Rejected because the contract has fixed fees alongside usage fees, which Deloitte says makes it hard to show the invoiced amount corresponds to value delivered. |
5. Peer precedent
Policy notes were read from the registrants’ XBRL policy pages (R-files) of the 10-K, which carry the full note text. Dates are EDGAR filing dates. Tickers are inferred from the registrants’ EDGAR file names. Four registrants were verified; a fifth candidate (Rubrik, Inc.) was dropped because its policy page did not address implementation or usage fees.
Company | Filing and date | Treatment | Disclosure excerpt (verbatim) | Link |
|---|---|---|---|---|
Phreesia, Inc. (PHR) | 10-K, FYE 1/31/2025; filed 2025-03-13 | Certain implementation services not distinct from the solutions; recognized over the contract term. | “Certain professional services for implementation are not distinct from the Company’s solutions and are therefore recognized over the term of the contract.” | |
Bottomline Technologies, Inc. (EPAY) | 10-K, FYE 6/30/2021; filed 2021-08-30 | Hosting-arrangement implementation not distinct; ratable over non-cancelable term. | “We have concluded that the implementation services in our hosting arrangements with multiple performance obligations are not distinct and therefore we recognize fees for implementation services ratably over the non-cancelable term of the hosting contract.” | |
Dynatrace, Inc. (DT) | 10-K, FYE 3/31/2025; filed 2025-05-22 | Implementation, consulting and training sold with SaaS are services recognized as performed (contrasting practice). | “The Company offers implementation, consulting and training services for the Company’s software solutions and SaaS offerings. Services fees are generally based on hourly rates. Revenues from services are recognized in the period the services are performed…” | |
Bottomline Technologies, Inc. (EPAY) | 10-K, FYE 6/30/2021; filed 2021-08-30 | Usage-type variable consideration: allocate to distinct service periods in the series when requirements are met; otherwise estimate and recognize ratably. | “In circumstances where we meet certain requirements to allocate variable consideration to a distinct service within a series of related services, we allocate variable consideration to each distinct period of service within the series.” | |
Guidewire Software, Inc. (GWRE) | 10-K, FYE 7/31/2024; filed 2024-09-16 | Variable installments estimated with the expected value method on historical usage, subject to the constraint. | “When consideration is subject to variable installments, the Company estimates variable consideration using the expected value method based on historical DWP or GWP usage to the extent that a significant revenue reversal is not probable to occur.” |
Filing indexes (dates confirmed): Phreesia; Bottomline; Dynatrace; Guidewire.
Reading across the peers. Practice is split on implementation: Phreesia and Bottomline combine hosting-related implementation with the service, while Dynatrace recognizes services as performed. This supports the “practice diverges” flag; the deciding facts are those in Section 4. The Guidewire note shows a peer that estimates variable consideration rather than applying the exception, which fits a usage pattern that is not period-specific.
Comment-letter sub-table. No SEC UPLOAD/CORRESP letters on this issue were opened in this run, so no comment-letter rows are presented. One search surfaced an unopened 2024 EDGAR letter, which was not relied on.
6. Conclusion and illustrative journal entries
Conclusion (recommendation for you and your auditor to confirm): one stand-ready performance obligation covering platform and implementation, recognized ratably over 36 months; overage recognized as usage occurs under the allocation exception. Amounts below are illustrative and use the inputs in A3 and A4.
Inputs: platform $400,000 per year; implementation $120,000; term 36 months; Year 1 overage $30,000. Monthly ratable revenue in Year 1 = $400,000 / 12 + $120,000 / 36 = $33,333 + $3,333 = $36,667. Annual revenue (excluding overage) = $400,000 + $40,000 = $440,000.
Entry 1: Day 1 invoice (illustrative)
Account | Debit | Credit |
|---|---|---|
Accounts receivable | $520,000 | |
Contract liability (deferred revenue) | $520,000 |
Entry 2: Each month of Year 1 (illustrative)
Account | Debit | Credit |
|---|---|---|
Contract liability | $36,667 | |
Subscription revenue | $36,667 |
Entry 3: Year 1 overage, recognized as usage occurs (illustrative; monthly in practice)
Account | Debit | Credit |
|---|---|---|
Accounts receivable | $30,000 | |
Usage revenue | $30,000 |
Entry 4: Start of Year 2 invoice (illustrative)
Account | Debit | Credit |
|---|---|---|
Accounts receivable | $400,000 | |
Contract liability | $400,000 |
Revenue profile by year, excluding overage (illustrative)
Treatment | Year 1 | Year 2 | Year 3 |
|---|---|---|---|
Implementation not distinct (recommended) | $440,000 | $440,000 | $440,000 |
Implementation distinct, recognized as performed in Year 1 (alternative) | $520,000 | $400,000 | $400,000 |
Contract liability at end of Year 1, before Year 2 invoice: recommended / alternative | $80,000 / $0 | – | – |
Both treatments total $1,320,000 over the term; the choice moves $80,000 of revenue into Year 1. The $80,000 is the unrecognized implementation fee ($120,000 less $40,000).
7. Disclosure implications
- Disaggregation of revenue, contract balances (opening and closing contract liabilities and revenue recognized from opening balances) and remaining performance obligations are required by ASC 606-10-50; paragraph numbers not verified in this run.
- The remaining-performance-obligation disclosure may exclude variable consideration allocated entirely to a wholly unsatisfied or distinct service in a series (the usage fees under the allocation exception); the exclusion criteria are in ASC 606-10-50; paragraph not verified. State the use of the exclusion.
- Significant judgments: policy note on whether implementation is distinct, the measure of progress for SaaS, and the use of the allocation exception. Peers describe these in the revenue policy note (Section 5).
- Costs to obtain and fulfill the contract and amortization period (ASC 340-40); paragraph not verified.
8. Open questions and facts to confirm
- Who can perform implementation? If third-party partners routinely implement the platform, move toward distinct (revenue earlier, as performed).
- Is the platform sold without implementation? Regular stand-alone SaaS sales also point toward distinct.
- Does implementation significantly customize the platform? Significant modification supports not distinct; purely behind-the-firewall setup could be a non-service activity.
- Does the overage allowance reset monthly, or is there an annual or three-year commitment? A non-resetting commitment weakens the allocation exception; estimate and constrain overage instead.
- Is the overage rate fixed for the entire term? Tiered or step-down rates may fail the allocation objective.
- Is the right to bill unconditional? If annual invoices are not due until later or the contract is cancelable, record contract liability and receivable differently.
- Do service-level credits or price concessions exist? These are additional variable consideration to be estimated and constrained.
- Is there a termination-for-convenience clause? It can shorten the contract term for ASC 606 purposes, changing the ratable period.
Do next
- Obtain implementation statements of work and any partner-delivered implementations for the same product to test the third-party and stand-alone sale indicators.
- Read the contract’s overage clause: allowance reset, rate schedule and any commitments, then document the allocation-exception analysis against ASC 606-10-32-40.
- Pull the licensed Codification text for 606-10-25-17, 25-21, 32-18, 50-13 to 50-15 and 340-40 and replace the paragraph-not-verified items.
- Model Year 1 to Year 3 revenue under both implementation views and agree the preferred policy with your auditor before the first quarter-end close.
- Check peers’ latest 10-K policy notes and SEC staff correspondence for the same industry before finalizing the policy.
Coverage note
The FASB Codification (asc.fasb.org) was not publicly readable, so paragraph text comes from Deloitte DART reproductions; KPMG, PwC and EY handbooks and AICPA guides were not opened; no SEC comment letters were read; paragraphs marked “not verified” (606-10-25-17, 25-15, 32-18 full text, 50-x, 340-40) were not opened in primary text.
Sources
- Deloitte DART, Roadmap 5.3 Identifying Performance Obligations in a Contract (reproduces ASC 606-10-25-14, 25-19, 25-21, 25-22). Deloitte, n.d.. https://dart.deloitte.com/USDART/home/codification/revenue/asc606-10/roadmap-revenue-recognition/chapter-5-step-2-identify-performance/5-3-identifying-performance-obligations-in
- Deloitte DART, Roadmap 6.3 Variable Consideration (ASC 606-10-32-8, 32-11). Deloitte, n.d.. https://dart.deloitte.com/USDART/home/codification/revenue/asc606-10/roadmap-revenue-recognition/chapter-6-step-3-determine-transaction/6-3-variable-consideration
- Deloitte DART, Roadmap 7.5 Allocation of Variable Consideration (ASC 606-10-32-39 to 32-41; Example 35). Deloitte, n.d.. https://dart.deloitte.com/USDART/home/codification/revenue/asc606-10/roadmap-revenue-recognition/chapter-7-step-4-allocate-transaction/7-5-allocation-variable-consideration
- Technology Alert: Implementation Services in Cloud-Based or Hosted Software Arrangements. Deloitte, November 2019. https://dart.deloitte.com/USDART/home/publications/deloitte/industry/technology/technology-alerts-applying-revenue-standard/implementation-services-cloud-based-hosted-software
- Technology Alert: Accounting for Cloud-Based or Hosted Software Arrangements With Variable Consideration. Deloitte, December 2019. https://dart.deloitte.com/USDART/home/publications/deloitte/industry/technology/technology-alerts-applying-revenue-standard/cloud-based-hosted-software-variable-consideration
- Phreesia, Inc. 10-K FYE 1/31/2025, revenue policy note (R31). Phreesia, Inc., Filed 2025-03-13. https://www.sec.gov/Archives/edgar/data/1412408/000141240825000010/R31.htm
- Phreesia, Inc. filing index. SEC EDGAR, 2025-03-13. https://www.sec.gov/Archives/edgar/data/1412408/000141240825000010/0001412408-25-000010-index.htm
- Bottomline Technologies, Inc. 10-K FYE 6/30/2021, revenue policy note (R11). Bottomline Technologies, Inc., Filed 2021-08-30. https://www.sec.gov/Archives/edgar/data/1073349/000107334921000114/R11.htm
- Bottomline Technologies filing index. SEC EDGAR, 2021-08-30. https://www.sec.gov/Archives/edgar/data/1073349/000107334921000114/0001073349-21-000114-index.htm
- Dynatrace, Inc. 10-K FYE 3/31/2025, revenue policy note (R10). Dynatrace, Inc., Filed 2025-05-22. https://www.sec.gov/Archives/edgar/data/1773383/000177338325000065/R10.htm
- Dynatrace filing index. SEC EDGAR, 2025-05-22. https://www.sec.gov/Archives/edgar/data/1773383/000177338325000065/0001773383-25-000065-index.htm
- Guidewire Software, Inc. 10-K FYE 7/31/2024, revenue policy note (R21). Guidewire Software, Inc., Filed 2024-09-16. https://www.sec.gov/Archives/edgar/data/1528396/000152839624000105/R21.htm
- Guidewire filing index. SEC EDGAR, 2024-09-16. https://www.sec.gov/Archives/edgar/data/1528396/000152839624000105/0001528396-24-000105-index.htm
FAQ
What does Accounting Treatment Memo need to run?
Accounting Treatment Memo needs transaction or arrangement and standard or framework; industry (optional) and specific questions to resolve (optional) are optional.
How often does Accounting Treatment Memo run?
It runs when you ask, and you can put it on a daily, weekly or monthly schedule.
What does Accounting Treatment Memo deliver?
Every run delivers a Word document, with every claim linked to its source.
Can I change what Accounting Treatment Memo does?
Yes. Every GREP AI agent can be cloned into your workspace, where you can edit its instructions, add your own sources and files, and change its schedule.
More agents like this
- Runs on a schedule, daily
Exchange Filings & Disclosure Watch
You get a digest of new filings, material-fact notices and governance rule changes from your chosen exchange and regulator, scoped to your companies or topics.
Formatted briefView → - Runs over a list
Batch Business Verification
For each business, vendor, supplier, signup or invoice on your list, you get registry, address, domain, sanctions and fraud checks with a pass/review/block verdict.
Sourced reportView → - Runs on a schedule, daily
Catastrophe Loss Tracker
Get a brief on each active catastrophe: its path or footprint, the latest insured-loss estimates, and the listed insurers and reinsurers most exposed.
Formatted briefView → - Runs over a list on a schedule, weekly
Company Event Calendar
For each company you follow: upcoming earnings, investor days, conferences and renewals, with consensus expectations, latest KPIs and what to watch.
Formatted briefView → - Runs on demand
Comparable Deal Comps
A table of comparable public deals with parties, value, multiples and terms, plus ranges, medians, off-market flags and where your terms sit.
SpreadsheetView → - PremiumRuns on demand
Corporate Due Diligence
You get a due diligence report on one company: who runs and owns it, its financials, legal history, reputation and red flags.
Sourced reportView →
Run Accounting Treatment Memo in minutes.
Free to start. Run it once, put it on a schedule, or clone it and make it yours.