Extract contracts, performance obligations, transaction price, recognition method, cumulative and current-period revenue from an ASC 606 rev-rec schedule.
The full guide: Deferred revenue, or RPO, on an ASC 606 schedule
Need to scale? Create an API key, then run this from your own code or an agent.
Create an API keyFree account required
Upload a file or pick a sample, and see the fields come back.
No signup · nothing stored
It is the schedule that shows how revenue is recognized over the life of a contract under ASC 606 / IFRS 15. The extractor reads the entity name, fiscal period and year, the customer name, contract number, and contract start and end dates, and the revenue stream (product, services, licensing, subscription).
The performance obligation description, the recognition method (point in time or over time), the transaction price, the contract value, cumulative revenue recognized to date, current-period revenue, the remaining performance obligation, and the completion percentage all come back as fields.
A revenue items table with one row per contract (customer, revenue stream, performance obligation, recognition method, contract value, transaction price, current-period and cumulative revenue, remaining obligation, and completion percentage) and a performance obligations table with each obligation's description, satisfaction status, satisfaction date, and transaction price.
Yes. The total revenue recognized during the period, the cost of revenue, and the gross profit come back as aggregate fields, in the currency (ISO 4217) declared on the schedule, along with any disclosure notes.
PDF only, up to 10MB and 100 pages. Processed via the Talonic API for extraction only, not retained for training, and not shared. Download as CSV, XLSX, or JSON.
The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.
See invoice data extraction if you run this for finance and AP teams, or the extraction API if you are building it in.