Extract data from revenue recognition schedules

Under ASC 606 and IFRS 15, revenue is earned as a company satisfies its promises to a customer, not when the cash lands. A revenue recognition schedule is the document that tracks that: for each contract it lists the performance obligations, the transaction price allocated to each, the recognition method (over time or at a point in time), how much has been recognized to date, and how much remains. It is the bridge between a signed contract and the revenue line, and it is what an auditor reads to test that revenue was recognized in the right period. The schedule turns on a five-step model and a running total that must reconcile. A schedule prepared by Northgate Software Inc. for its customer Atlas Freight Corp. under contract CTR-2026-0087, fiscal period Q2 2026, might carry a contract_value of 1,200,000 USD split into two performance obligations: a 900,000 USD software subscription recognized over time and a 300,000 USD implementation service. If cumulative_recognized is 525,000 USD, then the remaining_performance_obligation (the RPO, or deferred revenue) is 675,000 USD, and the two add back to the 1,200,000 USD contract value, giving a completion_percentage of 43.75 percent. The current_period_revenue of 187,500 USD, against a cost_of_revenue of 60,000 USD, yields a gross_profit of 127,500 USD for the quarter. Aligned to the revenue schema, the schedule returns the entity, the customer, the contract, the transaction price, the recognition method, and the recognized-to-date and remaining figures as fields, while the revenue items and the performance obligations stay as tables. Inside a revenue system, a schedule where 525,000 USD recognized plus 675,000 USD remaining equals the 1,200,000 USD contract lets a controller read the recognized and deferred amounts from structured fields rather than a spreadsheet. The schedule is captured as written, and the ASC 606 judgment stays with the finance team.

What gets extracted from revenue recognition schedules

How extraction works for revenue recognition schedules

Revenue schedules are produced by billing systems and finance teams from signed contracts, and the ASC 606 concepts, performance obligations, transaction price, and remaining obligation, sit in columns that differ by company and system. Anchored to the revenue model in the Field Registry, which draws on the US-GAAP and IFRS statement taxonomy, the schedule has transaction_price, cumulative_recognized, current_period_revenue, and remaining_performance_obligation each resolved to their own numeric field in the contract currency. It checks the recognition math: cumulative_recognized plus remaining_performance_obligation equals the contract_value, and gross_profit equals total_revenue less cost_of_revenue, so a 1,200,000 USD contract with 525,000 USD recognized and 675,000 USD remaining is confirmed to reconcile. The revenue_items and performance_obligations tables come back as distinct structures, each obligation carrying its recognition method and satisfaction status, and the contract_start_date and contract_end_date parse to ISO 8601. Alongside each figure sits a confidence score and a source-region pointer under DIN SPEC 91491, so a revenue accountant can trace the recognized amount to the obligation it came from during a close or an audit.

Sample extraction

An ASC 606 revenue recognition schedule with two performance obligations

{
  "document_number": "REVREC-2026-Q2-014",
  "document_date": "2026-06-30",
  "entity_name": "Northgate Software Inc.",
  "fiscal_period": "Q2",
  "fiscal_year": 2026,
  "currency": "USD",
  "customer_name": "Atlas Freight Corp.",
  "contract_number": "CTR-2026-0087",
  "contract_start_date": "2026-01-01",
  "contract_end_date": "2027-12-31",
  "revenue_stream": "subscription and services",
  "contract_value": 1200000,
  "recognition_method": "over_time",
  "transaction_price": 1200000,
  "cumulative_recognized": 525000,
  "current_period_revenue": 187500,
  "remaining_performance_obligation": 675000,
  "completion_percentage": 43.75,
  "total_revenue": 187500,
  "cost_of_revenue": 60000,
  "gross_profit": 127500,
  "note": "Cumulative recognized 525,000 USD + RPO 675,000 USD = contract value 1,200,000 USD; gross profit = 187,500 - 60,000 = 127,500 USD",
  "revenue_items": [
    {
      "contract_number": "CTR-2026-0087",
      "customer_name": "Atlas Freight Corp.",
      "revenue_stream": "Software subscription",
      "performance_obligation": "Access to the platform over 24 months",
      "recognition_method": "over_time",
      "contract_value": 900000,
      "transaction_price": 900000,
      "current_period_revenue": 112500,
      "cumulative_recognized": 337500,
      "remaining_performance_obligation": 562500,
      "completion_percentage": 37.5
    },
    {
      "contract_number": "CTR-2026-0087",
      "customer_name": "Atlas Freight Corp.",
      "revenue_stream": "Implementation services",
      "performance_obligation": "Onboarding and data migration",
      "recognition_method": "over_time",
      "contract_value": 300000,
      "transaction_price": 300000,
      "current_period_revenue": 75000,
      "cumulative_recognized": 187500,
      "remaining_performance_obligation": 112500,
      "completion_percentage": 62.5
    }
  ],
  "performance_obligations": [
    {
      "contract_number": "CTR-2026-0087",
      "obligation_description": "Software subscription access",
      "satisfaction_status": "partially satisfied",
      "satisfaction_date": "2027-12-31",
      "transaction_price": 900000
    },
    {
      "contract_number": "CTR-2026-0087",
      "obligation_description": "Implementation services",
      "satisfaction_status": "partially satisfied",
      "satisfaction_date": "2026-09-30",
      "transaction_price": 300000
    }
  ]
}

Frequently asked