| Course | ACC 497 Advanced Topics in Accounting Research (ACC/497) |
|---|---|
| Week | 2 |
| Paper type | Revenue recognition research memo |
| Length | about 1,032 words, 4 double-spaced pages plus title page and references |
| Format | APA 7 student paper |
| School | University of Phoenix |
| Program | BS in Accounting |
| Updated | September 2026 |
Free sample paper for ACC 497 Week 2
Is the Implementation a Separate Promise? A Research Memo on a Composite Veterinary Software Company's Three-Year Subscription With Onboarding Services
[Student Name]
University of Phoenix
ACC/497: Advanced Topics in Accounting Research
Week 2 Assignment
[Instructor Name]
[Date]
The company, its customer and all figures are composites written for a model paper; standards and research findings come from the sources listed.
MEMORANDUM
To: Controller. From: Technical accounting staff. Re: Performance obligations in multi-year subscription contracts with implementation services.
Facts
A composite company sells cloud software that veterinary clinic groups use for scheduling, medical records, inventory and billing. A typical contract, such as one signed in July with a group of 14 clinics, provides three years of access for $360,000, billed annually, and implementation for a fee of $45,000. Implementation includes migrating records from the customer's old system, configuring templates, fee schedules and user permissions and training staff over about three months. The software itself is not changed; configuration uses standard settings available to all customers. Several independent consultants offer the same implementation services, and some customers use them.
Issue
Is implementation a performance obligation distinct from the subscription, and how should the contract price be allocated and recognized?
Guidance
Under Topic 606, a good or service is distinct if two criteria are both met: the customer can benefit from it alone or with resources readily available to it, and the promise to provide it can be told apart from the contract's other promises (FASB ASC 606-10-25-19). Paragraph 606-10-25-21 lists factors indicating that promises are not separately identifiable, including that the seller combines the promised items into a single integrated output the customer bought, that one significantly modifies or customizes another and that they are highly interdependent or interrelated. The FASB clarified these criteria in 2016 (Financial Accounting Standards Board, 2016).
Analysis: Capable of Being Distinct
The customer can benefit from implementation together with readily available resources. The subscription is a resource the customer has obtained under the same contract, and data migration and configuration make that subscription usable. That independent consultants sell the same services confirms that implementation has value apart from being performed by the software company. The first criterion is met.
Analysis: Separately Identifiable
The software company does not integrate implementation and the subscription into a combined output that the customer contracted for; the customer contracted for access to standard software and help getting started. Implementation does not modify or customize the software, since configuration uses settings available to every customer and leaves the code unchanged. The two are not highly interdependent: the company could fulfill the subscription without performing implementation, as it does for customers who use consultants, and implementation does not change the software's functionality. The second criterion is met. Implementation is a distinct performance obligation.
Allocation
The transaction price is $405,000. Standalone selling prices are observable: the company sells three-year subscriptions without implementation at a list price of $132,000 a year, $396,000, and has sold implementation alone to customers who later switched platforms for about $60,000. Total standalone value is $456,000. The discount of $51,000 is allocated proportionally, since there is no evidence it relates to only one obligation. The subscription receives about $351,700 and implementation about $53,300.
Timing
The subscription is a service transferred over time as the customer receives access, so its allocated amount is recognized evenly over 36 months, about $9,770 a month. Implementation is also satisfied over time as the work is performed, and the company measures progress by hours incurred against the estimated total of 300 hours. With 180 hours performed by September 30, about $32,000 of implementation revenue is recognized in the quarter.
Financing and Contract Costs
Two related questions were checked. Because the customer pays each year's subscription in advance and implementation within 30 days of invoice, the timing difference between payment and performance is never more than a year for any obligation, so the practical expedient applies and no financing component is recognized. The sales representative earned a commission of $20,250, 5% of the contract. Incremental costs of obtaining a contract are capitalized if the entity expects to recover them (FASB ASC 340-40-25-1), and the company amortizes the asset over the three-year term, consistent with the pattern of transfer of the subscription, since renewals earn a separate commission.
Journal Entries
On signing, the company records no entry for amounts not yet billed. On invoicing the first year's subscription and the implementation fee, it debits receivables for $165,000 and credits contract liabilities. Each month it moves the recognized portions to revenue: about $9,770 for the subscription and implementation revenue based on hours. At September 30, the unearned balance of billed amounts remains a contract liability.
Alternative View
Some may argue that implementation should be combined with the subscription because the customer would not buy implementation without the software. Under that view, the implementation fee would be recognized over the subscription term. The standard does not make usefulness only with other products decisive; it asks whether the customer can benefit with readily available resources and whether the promises are separately identifiable. If implementation involved writing custom code or building interfaces that changed the software's function for this customer, the combined view would be correct. On these facts it is not.
Applying the Conclusion Across Contracts
The company signs about 200 contracts a year, so the conclusion becomes a policy. Contracts with standard configuration will follow this memo. Contracts that include custom interfaces to a clinic group's laboratory or accounting systems will be reviewed individually, because building an interface that changes how the software functions for that customer could make implementation and the subscription a single obligation. The controller asked sales operations to flag any contract with custom development work so that it reaches the technical accounting team before revenue is recorded.
Why Judgment Matters
Schipper (2003) described principles-based standards as requiring more judgment from preparers and auditors, with the benefit of reflecting economic substance and the cost of reduced comparability. The implementation question illustrates both: two contracts that look alike on paper can reach different answers depending on how much the software is actually customized.
Conclusion and Disclosure
Implementation is a distinct performance obligation. The company allocates the price by relative standalone selling prices, recognizes the subscription ratably and recognizes implementation as hours are incurred. It will disclose its judgment about performance obligations and the amount of transaction price allocated to remaining obligations, as Topic 606 requires (Financial Accounting Standards Board, 2014).
References
Financial Accounting Standards Board. (2014). Revenue from contracts with customers (Topic 606) (Accounting Standards Update No. 2014-09).
Financial Accounting Standards Board. (2016). Revenue from contracts with customers (Topic 606): Identifying performance obligations and licensing (Accounting Standards Update No. 2016-10).
Schipper, K. (2003). Principles-based accounting standards. Accounting Horizons, 17(1), 61-72. https://doi.org/10.2308/acch.2003.17.1.61
What the ACC 497 Week 2 instructions ask
The ACC 497 Week 2 assignment typically asks students to research an accounting issue involving revenue recognition or measurement and write a memo. Common requirements include stating the facts and the issue, locating the relevant guidance in the Codification, applying it to the facts, considering alternatives, reaching a conclusion and citing paragraphs correctly. Revenue cases often involve identifying performance obligations, principal versus agent, variable consideration, licenses or contract modifications. Some prompts include journal entries or disclosure. The memo should follow a professional format that a reviewer can scan quickly, show how the guidance leads to the conclusion and reference the Codification and relevant research in APA style.
How this ACC 497 Week 2 example is built
Implementation fees in software contracts are a genuine judgment area, and many companies face the question of whether setup services are separate from the subscription. The memo uses the research format a firm would expect: facts, issue, guidance, analysis, alternative view, conclusion and disclosure. The analysis works through both criteria for a distinct good or service, capability of being distinct and separately identifiable, and the factors the standard lists for the second. Because the answer depends on whether implementation changes the software itself, the memo looks closely at what the onboarding team actually does. The allocation and timing then follow, with a brief note on disclosure of remaining performance obligations.
ACC 497 Week 2 grading rubric: where the points go
The grading for this research memo usually rewards a precise issue statement, correct identification of the governing paragraphs, careful application of the distinct criteria to the facts, consideration of the opposing view and a conclusion with correct entries or timing. Faculty check that both criteria are addressed, that the factors indicating a single obligation are considered, that standalone selling prices are used to allocate any discount and that timing reflects when each obligation is satisfied. Paragraph-level citations in Codification format and a professional memo structure, with the issue stated in one sentence, are expected. Research supporting the role of judgment adds depth, and so does a brief look at contract costs.
ACC 497 Week 2 help: mistakes to avoid
One recurring ACC 497 Week 2 error is concluding that implementation is distinct simply because it is listed separately in the contract. The contract's labels do not decide the question; the criteria do. Another is addressing only whether the customer could benefit from the service and skipping whether it is separately identifiable in the context of the contract. Look at whether implementation significantly modifies or customizes the software. Students also allocate the whole discount to one obligation. Use relative standalone selling prices. Recognize subscription revenue over time and implementation as it is performed if distinct. Finally, write the conclusion so a reviewer can follow it without the rest of the memo, and state the entries it implies.
Related ACC 497 sample papers
Other ACC 497 week samples
- ACC 497 Week 1: Researching the Codification
- ACC 497 Week 3: Acceptable Alternatives in GAAP
- ACC 497 Week 4: A Nonprofit Reporting Dilemma
- ACC 497 Week 5: A Comprehensive Research Memo
More BS in Accounting sample papers
- ACC 456 Week 2: Gross Income and Exclusions
- ACC 460 Week 2: Budgets and Budgetary Control
- ACC 491 Week 2: Audit Evidence and Documentation
- ACC 492 Week 2: Auditing Inventory
ACC 497 Week 2 questions, answered
What does ACC/497 Week 2 usually ask for?
It usually asks for a research memo on a revenue recognition or measurement issue, with facts, the issue, Codification guidance, analysis, alternatives and a conclusion.
Where can I find a free ACC 497 Week 2 sample paper?
The veterinary software company memo on this page applies the distinct criteria to an implementation fee, with margin notes, at no cost to read. Send the issue from your own course and the first memo we write is free.
When is a service a distinct performance obligation?
When the customer can benefit from it on its own or with readily available resources and the promise is separately identifiable from other promises in the contract.
Is software implementation always a separate performance obligation?
No. It is separate if it is distinct; if it significantly modifies or customizes the software or is highly interdependent with it, it is combined with the software or subscription.
How is a contract discount allocated?
In proportion to the standalone selling prices of the performance obligations, unless observable evidence shows the discount relates to only some of them.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official University of Phoenix document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
Request this one custom, free · All ACC 497 week samples · All courses