Rebuild Linden Peak's monitoring-contract file

Assignment context

Linden Peak Instruments, Inc. is a fictional US manufacturer with a December 31 year end. It prepares general-purpose financial statements under US GAAP. You are the revenue-accounting senior. The controller has stopped release of the draft statements because the current file says only, “Recognize the $126,000 invoice at signing; cash collection confirms the sale.”

Use whole US dollars unless an exhibit says otherwise. Treat amounts marked stipulated for schedule work as controlled exercise inputs, not as evidence that the underlying accounting conclusion is correct. Treat every other unsupported assertion as open.

Authority-access gate

Perform the live research in a current, authorized FASB Codification view. Log the exact locator, scope, effective-date status, access date, and how the criterion applies; do not paste protected source text into the submission. The provided source records orient the research but do not replace it.

Use the locator model in L:financial-reporting-environment-and-framework/01-institutions-authority-and-codification and the memo model in L:financial-reporting-environment-and-framework/05-research-memo-from-issue-to-conclusion. A usable log row reads across one issue: contract-criteria question → exact current locator and paragraph role → entity, transaction, and period scope → access date and amendment status → case fact supporting or failing each criterion → conclusion or open-item owner. The instructor should demonstrate one completed row in the authorized interface before learners research the remaining issues.

Exhibit A — parties, approval, and termination

On January 2, Year 1, Linden Peak and Northwind Warehousing signed a master agreement for one monitoring device, installation, and support. Northwind uses the outputs in its warehouse operations. Both parties approved the written agreement, which identifies payment terms and ordinary remedies. The agreement's stated term is three years.

The sales file does not contain counsel's enforceability assessment. A clause allows Northwind to terminate before device delivery without compensating Linden Peak for work performed. After delivery, Northwind may terminate only for uncured material breach. A January 3 email from the sales vice president says, “We will waive the first invoice if their financing is not approved,” but no executed amendment or credit approval is attached. The credit team rated Northwind within normal limits on January 5.

A second statement of work for warehouse-layout consulting was signed the same day by the same parties. Its price was negotiated by a different team. An email mentions that Northwind wanted “one launch,” but neither file explains whether the prices or performance obligations depend on one another.

Apply the combination indicators from L:revenue-from-contracts-with-customers/00-establish-scope-and-contract: common commercial objective, price interdependence, and whether the promised goods or services form one performance obligation. A shared date or customer is not another indicator.

Exhibit B — promise inventory

The master agreement and operating file identify:

1. one standard monitoring device, which Linden Peak sells separately;
2. installation using standard mounting and configuration procedures;
3. three years of continuous monitoring support beginning after activation;
4. one setup activity performed inside Linden Peak's system before activation;
5. a one-year promise to repair manufacturing defects;
6. an optional fourth year of support for $5,000; and
7. periodic reports that Northwind can access only with the monitoring service.

Other vendors can install the device without significantly modifying it. Northwind can benefit from the delivered device with another provider's monitoring service. The file does not explain whether setup transfers a service or only enables Linden Peak to fulfill its other promises. The usual standalone price for one support year is $10,000. Comparable customers receive renewal discounts of no more than 10 percent. The legal agreement labels all seven items “deliverables”; the invoice has only “hardware” and “service” lines.

Exhibit C — consideration and estimate controls

The agreement states fixed consideration of $120,000 and a $12,000 activation bonus if the system passes a 30-day performance test. Management's controlled estimate at inception is that $6,000 of the bonus may be included without a significant reversal; this $6,000 constrained-in amount is stipulated for the base schedule only. The contract owner must still document the method, probability evidence, factors that could cause reversal, excluded amount, reporting-date update, and approval.

Northwind also promises 200 hours of identifiable warehouse-process data. No fair-value workpaper is in the file. Linden Peak agrees to pay Northwind $4,000 for a launch advertisement, but the file lacks evidence of a distinct service and its fair value. The stated payment dates broadly follow transfer in the base contract. A proposed alternative gives Northwind four years to pay the device amount; no present-value schedule or business-purpose analysis exists.

Exhibit D — allocation schedule

For the base schedule, use these stipulated standalone selling prices:

Use relative SSP allocation for this stipulated version and carry full precision before rounding. Your broader memo must separately test the option, noncash consideration, customer payment, financing alternative, and whether an allocation exception applies. Use the downloadable Python and spreadsheet models to reperform the base arithmetic; neither tool decides those judgments.

Exhibit E — performance, billing, and cash

For the base schedule, assume the following facts are established:

• the device and installation each transfer at activation at the beginning of Year 1;
• monitoring support is a stand-ready series satisfied evenly over three years;
• the Year 1 invoice creates an unconditional right to $100,000, while the unbilled consideration for transferred activation performance becomes billable only after Linden Peak completes the next support milestone; and
• the allocated amounts are $84,000, $16,800, and $25,200, respectively.

The controlled ledger extracts are:

Build separate revenue, billing, cash, receivable, and net contract-position rollforwards. Identify when a right remains conditional and when only passage of time remains. Do not record revenue again when a receivable is billed or collected. Route the allowance on an unconditional receivable to the separate credit-loss analysis rather than changing Topic 606 revenue by default.

The routing boundary is simple before its later measurement becomes complex: an expected price concession changes the consideration Linden Peak expects to be entitled to and can affect revenue; expected noncollection of an established receivable or contract asset ordinarily creates a Topic 326 allowance and credit-loss expense. The receivable and contract asset keep separate gross balances, and neither allowance represents new or reversed performance. The next receivables module builds the actual estimate.

Exhibit F — competing year-end facts

The file also contains six unapproved notes. Analyze each independently; do not force all of them into the base schedule.

• Bill-and-hold: Northwind asked Linden Peak to retain a completed spare device until its secure room is ready. The device is tagged to Northwind, but the request's business reason and Linden Peak's remaining ability to use or redirect it are undocumented.
• Return: A reseller channel permits 60-day returns. The draft records full revenue and ignores expected returns, inventory recovery, and value loss.
• Warranty: Sales calls the one-year defect coverage a service. No separate price, extra service, claim history, or legal requirement analysis exists.
• Repurchase: A side letter says Linden Peak “may assist with resale near original price.” Counsel has not determined whether this is a substantive option, obligation, guarantee, or marketing statement.
• Intermediary: ChannelCo invoices the customer and remits cash net of 8 percent. Linden Peak specifies the device and support, but inventory risk, pricing discretion, acceptance, and control before transfer are disputed.
• Consignment: A shipment to a distributor may be returned at will, and the distributor has no unconditional payment obligation before resale.

For each note, identify the governing question, decisive facts, plausible accounting branches, evidence owner, and release stop. Cash flow or invoice direction alone does not establish control or gross presentation.

Exhibit G — change order and contract costs

At the start of Year 2, Northwind requests an additional device plus expanded support. The unsigned change order states a $34,000 price. Current standalone prices and the relation of the added services to remaining promises are absent. Prepare a decision tree for separate-contract, prospective, and cumulative- catch-up paths. Calculate only a path whose missing inputs you explicitly stipulate; do not invent an approved modification.

Linden Peak paid a $7,500 sales commission only because the base contract was obtained. It also incurred $4,200 of sales salaries regardless of success, $3,000 of device inventory handling, and $6,000 of configuration labor. The file contains no expected-recovery, other-Topic, fulfillment-criteria, amortization-period, renewal-commission, impairment, or practical-expedient analysis. Build the classification and control matrix before posting an asset.

Exhibit H — draft note and RPO bridge

The draft revenue note says:

Revenue is recognized when earned. Deferred revenue was $13,000 at year end. Backlog is guaranteed to become future revenue.

Replace it with an evidence map for disaggregation, contract balances, performance obligations and payment terms, significant judgments, assets from contract costs, and remaining performance obligations. Reconcile each reported amount to the same entity, period, population, currency, and units as the statements.

For the base schedule, derive ending RPO from allocated consideration not yet recognized and explain expected recognition timing. Then list what may be excluded, constrained, cancelled, modified, remeasured, or outside the measure. RPO is neither guaranteed cash nor management backlog. For any public-filing or XBRL comparison, retain registrant, form, accession, period, note/table, units, scale, sign, tag, context, dimensions, decimals, and extension status.

The base bridge begins with a controlled calculation: $126,000 allocated consideration less $109,200 recognized through Year 1 leaves $16,800 of RPO, expected at $8,400 in each of Years 2 and 3 under the supplied support pattern. After Year 2 revenue, $8,400 remains. Those amounts do not establish that cash is guaranteed or that another backlog population has the same scope.

The rejected invoice shortcut would call all $126,000 Year 1 revenue. The obligation schedule instead recognizes $84,000 for the transferred device, $16,800 for installation, and $8,400 for the first support year: $109,200 in total. The remaining $16,800 is allocated to two years of unsatisfied support, so it is RPO. It is not a $13,000 “deferred revenue” balance: billings and performance follow different timelines, and this base schedule ends Year 1 with a contract asset rather than a contract liability.

Required contract file

Build the packet in lesson order; do not wait until the end to confront all ten deliverables:

Complete each section and its open-item list before assembling the final index.

Submit one indexed packet with:

1. a fact-status and authority-clock sheet;
2. contract-scope, combination, and collectibility conclusions;
3. a clause-to-promise and performance-obligation map;
4. transaction-price, constraint, financing, noncash, customer-payment, SSP, allocation, and option workpapers;
5. obligation-level transfer and progress conclusions with alternatives;
6. special-arrangement and change-order decision tables;
7. journal entries plus revenue, billing, cash, receivable, contract-balance, contract-cost, allowance-handoff, and RPO rollforwards;
8. a draft note tied to controlled schedules;
9. an issue-by-issue current-authority log; and
10. an open-item register and signed recommendation to release, release with specified corrections, or stop release.

Every conclusion must distinguish established fact, exercise stipulation, estimate, assumption, interpretation, and unresolved evidence. A reconciled model with an unsupported contract judgment is not controller-ready.