---
name: revenue-recognition-assessment
description: Assesses contract arrangements by identifying promised goods or services, transaction price, performance obligations, transfer evidence, timing, modifications, and proposed recognition treatment from cited contract and finance records. Use for revenue recognition assessment, evidence review, management reporting, and decision support.
license: Apache-2.0
metadata:
  adlass.categories: "finance-accounting/accounts-receivable"
  adlass.industries: ""
  adlass.tags: "revenue,contract,performance-obligation,transaction-price,modification,cutoff"
  adlass.adaptation: "reference-doc"
  adlass.source: "original"
  adlass.version: "1"
---

# Revenue recognition assessment

## Purpose

Assesses contract arrangements by identifying promised goods or services, transaction price, performance obligations, transfer evidence, timing, modifications, and proposed recognition treatment from cited contract and finance records.

## Scope

Work only on the named source records and the deliverable fields described here. Preserve source wording, identifiers, dates, amounts, statuses, and citations. **Excluded:** contacting people, changing source systems, making approvals, or presenting a conclusion as a completed business action. The assessed unit is a contract arrangement and its distinct promised items, not a general ledger total without contract evidence.

## Data basis

- The process-specific documents, spreadsheets, and record tables in the skill scope.
- The company policy, rubric, control matrix, template, or prior-period output named by this process.
- Run-specific period, audience, project, or decision brief when supplied.
- The assessed unit is a contract arrangement and its distinct promised items, not a general ledger total without contract evidence.

## Result

Contract facts, obligation analysis, timing, and proposed treatment with citations. Revenue recognition memo {date}

## Quality criteria

- Every material fact and finding cites its document section, page, timestamp, table row, or record ID.
- Counts, amounts, dates, and statuses reconcile to the named source population.
- Rule outcomes show the rule and preserve source values beside normalized values.
- Missing, conflicting, excluded, and estimated items have explicit statuses.
- The written result and structured output use the same row-level findings.
- The assessed unit is a contract arrangement and its distinct promised items, not a general ledger total without contract evidence.

## Instructions

Contract treatment follows the supplied accounting policy and the arrangement’s promised items, price terms, transfer evidence, and modification history.

## Adapt before use
Use the contract’s obligation and transfer wording as evidence and record the exact clause or finance-policy paragraph supporting each proposed treatment.
Keep contract language, policy conclusion, and proposed journal timing in separate fields. Flag variable consideration, acceptance clauses, termination rights, renewals, and contract modifications for explicit assessment when present.

- Add the company policy, rubric, control matrix, or approved format named in the Data basis.
- Map source column names, identifiers, status values, and date or currency conventions.
- Define the process threshold, escalation vocabulary, responsible review role, and retention rule.