ACC 682 Topic 2 backlog extraction workpaper example

Accounting and Data Analytics Core Grand Canyon University Free custom sample in 24 to 48h

This ACC 682 Topic 2 sample paper builds a remaining performance obligation disclosure from contract data the ledger does not hold. It belongs to GCU ACC 682, Accounting and Data Analytics Core, the course listed as ACC-682 in the Grand Canyon University MS in Accounting. The extract joins subscription rows to their amendment history for 4,812 active contracts, keeping the latest version of each. It excludes 118 terminated contracts worth $1.4 million and limits 212 cancellable contracts to their notice period. The roll-forward runs from $61.0 million to $63.4 million, $39.8 million within twelve months, and ties to the ledger with usage fees excluded.

CourseACC 682 Accounting and Data Analytics Core
TopicTopic 2
Paper typeBacklog extraction workpaper
LengthAbout 950 words, 2 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramMS in Accounting
UpdatedSeptember 2026

Free sample paper for ACC 682 Topic 2

1

Extracting a $63.4 Million Backlog the Ledger Cannot See: A Remaining Performance Obligation Workpaper From Source Tables to Note

[Author Name]

Colangelo College of Business, Grand Canyon University

ACC-682: Accounting and Data Analytics Core

Topic 2 Assignment

[Instructor Name]

[Date]

The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.

What this page is doingThe title states the disclosure figure and the reason it must be built outside the general ledger. The company and figures are illustrative composites; the standards and sources are real.
2

Extracting a $63.4 Million Backlog the Ledger Cannot See: A Remaining Performance Obligation Workpaper From Source Tables to Note

The Requirement and Why the Ledger Cannot Answer It

Nimbus Workflow, a composite software company, must disclose the transaction price allocated to performance obligations not yet satisfied at year end and when it expects to recognize that amount as revenue (Financial Accounting Standards Board, 2014). The general ledger cannot supply this figure. Revenue accounts record what has been earned; deferred revenue records only what has been billed in advance. Neither records what customers have committed to pay for service not yet delivered or billed. That commitment lives in the contract data, so the figure has to be extracted from it.

Sources

Two systems supply the data. The billing system's subscription table, owned by the revenue operations team, holds one row for each contract version, with contract ID, customer, start and end dates, monthly fee, amendment sequence number and billing status. When a contract is amended, for an upsell, a downsell or a renewal, the system adds a new row rather than overwriting the old one, so every contract's history is preserved. The sales system's contract register, owned by sales operations, records the commercial status of each contract, including terminations negotiated by account managers. Both were drawn on January 12 by the revenue operations analyst, with the queries stored in the engagement folder.

Extraction Logic

Each step is numbered, with the count after it, so a reviewer can retrace the path.

Table 1

Extraction Steps

StepActionContracts remaining
1Draw all rows from the subscription table, including amendment rows7,390 rows
2Keep the latest version of each contract by amendment sequence number5,026
3Keep contracts with billing status active at year end4,812
4Remove contracts shown as terminated in the sales system4,694
5Limit 212 contracts with free cancellation to the 30-day notice period4,694, with 212 limited
6Compute unbilled contract value by month to the end of each enforceable term4,694

Two Exclusions

Terminated contracts. Comparing the two systems found 118 contracts that the sales system shows as terminated but the billing system still shows as active, because billing had not been updated. Their remaining value, $1.4 million, is not an enforceable commitment and is excluded. The mismatch has been reported to revenue operations as a control issue, since it would also cause invoices to be issued for canceled service.

Free cancellation. Of the remaining contracts, 212 allow the customer to terminate on 30 days' notice without penalty. For these, the contract is enforceable only for the notice period, so only 30 days of fees are included in remaining performance obligations, even though the stated term runs longer. This is a judgment about the contract term under the revenue standard, documented with the clause from each contract template.

Roll-Forward

The extracted balance is tied to last year's disclosed figure through a roll-forward.

Table 2

Remaining Performance Obligations Roll-Forward

$ millionsAmount
Opening remaining performance obligations61.0
Add bookings: new contracts and upsells38.4
Less revenue recognized from these contracts(33.9)
Less downsells and cancellations(2.1)
Closing remaining performance obligations63.4
Of which expected within twelve months39.8

Reconciliation to the Ledger

Revenue recognized from these contracts, $33.9 million, plus $2.3 million of usage-based fees, gives $36.2 million, which agrees to subscription and usage revenue in the general ledger. The usage fees are excluded from remaining performance obligations under the optional exemption for variable consideration that relates entirely to a wholly unsatisfied service period, and the note states that the exemption is used. The reconciliation confirms that the extract captures every contract that produced revenue in the year, which is the evidence that the population is complete (American Institute of Certified Public Accountants, 2017).

Timing Bands

The timing bands come from step 6 of the extraction. For each contract, the monthly fee is multiplied by the months remaining in the enforceable term and assigned to the month in which it will be earned. Summing by month gives $39.8 million in the first twelve months, $17.1 million in months thirteen to twenty-four, and $6.5 million beyond. Because subscription revenue is recognized evenly over the service period, the monthly assignment matches the expected pattern of recognition closely. For the 212 contracts limited to their notice periods, all of the included value falls in the first band.

Table 3

Expected Timing of Recognition

Band$ millions
Within 12 months39.8
13 to 24 months17.1
Beyond 24 months6.5
Total63.4

Review Points

Three points were raised in review and resolved. First, whether renewals signed before year end but starting after it belong in the balance: they do, because the customer is committed, and 31 such renewals worth $2.9 million are included. Second, whether contracts in collections should be excluded: they remain enforceable, but 14 contracts where collection is not probable were removed, since a contract without probable collection does not meet the revenue standard's criteria. Third, whether the figures should be discounted: the disclosure is of the allocated transaction price, which contains no significant financing component for these monthly-billed contracts, so no discounting applies. Each resolution is referenced to the supporting query or contract.

The Draft Note

The draft disclosure states: remaining performance obligations at year end were $63.4 million, of which about $39.8 million is expected to be recognized as revenue within the next twelve months and the remainder over the following one to three years. It notes the exclusion of usage-based fees under the optional exemption and explains that contracts cancellable without penalty are included only for their notice periods. A reader comparing the figure with last year's $61.0 million can see from the roll-forward that the $2.4 million of growth came from bookings exceeding revenue and downsells (Kieso et al., 2019).

References

American Institute of Certified Public Accountants. (2017). Guide to audit data analytics. AICPA.

Financial Accounting Standards Board. (2014). Revenue from contracts with customers (Topic 606) (Accounting Standards Update No. 2014-09). FASB.

Kieso, D. E., Weygandt, J. J., & Warfield, T. D. (2019). Intermediate accounting (17th ed.). Wiley.

Reading the GCU ACC 682 Topic 2 instructions

The Topic 2 instructions in ACC-682 ask students to extract remaining performance obligations from source systems. Weak submissions start from deferred revenue. The assignment rewards workpapers that explain why the ledger cannot answer the requirement, name each source table and how amendments are stored, and number each extraction step with counts. Students should document exclusions for terminated and freely cancellable contracts, roll the balance forward, reconcile recognized revenue to the ledger, apply any optional exemption and draft the note with timing bands a reader can use.

How the ACC-682 Topic 2 example is put together

The finished workpaper starts from the disclosure it feeds, the transaction price allocated to obligations not yet satisfied and when it is expected to become revenue, all figures illustrative. The ledger holds none of that, so the extract joins the billing system's subscription table to its amendment history for 4,812 active contracts, keeping only the latest version of each. Two exclusions follow. The sales system shows 118 contracts terminated but still active in billing, worth $1.4 million, and 212 contracts allow termination on 30 days' notice without penalty, so only the notice period counts as enforceable. The roll-forward then ties: $61.0 million opening, plus $38.4 million of bookings, less $33.9 million recognized and $2.1 million of downsells, gives $63.4 million, of which $39.8 million is expected within twelve months.

Where the marks sit in the ACC 682 Topic 2 rubric

Faculty grading the backlog workpaper reward a path a reviewer can retrace. Excellent workpapers keep only the latest version of each amended contract. Credit goes to finding terminated contracts by comparing systems. The rubric values limiting freely cancellable contracts to their enforceable term. The highest level reconciles recognized revenue to the ledger and explains the usage fee exemption. Workpapers that report deferred revenue as backlog, or that keep every version of an amended contract, tend to earn partial credit. Documenting who ran each query and when is also expected.

Common ACC 682 Topic 2 mistakes, and how to avoid them

A backlog figure pulled from the billing system with no reconciliation is where this workpaper loses the most, since nothing shows that the extract covers every contract or counts each once. Papers that sum every amendment row count superseded terms beside current ones and overstate the disclosure. Stated contract terms used without reading cancellation clauses report commitments the customers never made enforceable. Terminated contracts left in the figure because billing still lists them are a common miss, and only a comparison between systems finds them. Some papers build a clean extract and never reach the note, reporting a total without the timing explanation the disclosure calls for. The exclusion of usage fees costs credit when it is applied without stating the optional exemption relied on, because a reader is entitled to know which amounts are missing and why.

Get an ACC-682 Topic 2 example written to your instructions

Send the ACC-682 Topic 2 instructions, the rubric and the data or system description your section provided. We write a custom example to them, with the ledger's gap explained, each source table named, extraction steps counted, judgments on contract terms documented, the roll-forward reconciled and the disclosure drafted, in 24 to 48 hours. The first one is free.

More ACC 682 papers and MS in Accounting samples

ACC 682 Topic 2 questions, answered

What are remaining performance obligations?

The portion of the transaction price in existing contracts that has not yet been recognized as revenue, because the goods or services have not yet been delivered. ASC 606 asks companies to disclose that amount and when they expect to recognize it, using time bands or a qualitative explanation. For a subscription business it is often the nearest disclosed measure of contracted future revenue.

Why does a cancellation clause shorten the contract?

Under ASC 606 the contract term is the period in which both parties have enforceable rights and obligations. If a customer can walk away on 30 days' notice without a substantive penalty, the months beyond that notice period are not enforceable, however long the stated term. Counting them would disclose commitments the company cannot compel, so the workpaper limits those contracts to the notice period.

Why are usage fees left out?

Because the standard offers optional exemptions from this disclosure, including for certain variable consideration allocated entirely to performance obligations not yet satisfied, and many usage-based fees fall within them. A company electing an exemption must say so and describe what was excluded. The workpaper records the $2.3 million recognized from usage fees in the reconciliation so the omission from backlog is visible, not silent.

Where can I find a free ACC 682 Topic 2 sample paper?

Everything is above: the requirement, the sources, the extraction logic, two exclusions, the roll-forward, the reconciliation, timing bands, review points and the draft note. Send your contract data layout for a free worked workpaper.

Why are 212 contracts limited in ACC 682 Topic 2?

Customers can cancel them on 30 days' notice without penalty, so only the notice period is an enforceable commitment.