Extract data from AR aging reports
Money that customers owe a company but have not yet paid sits on the balance sheet as accounts receivable, and the AR aging report is how a credit and collections team keeps track of it. Every open invoice is sorted by how long it has been outstanding, and the report answers the question a controller asks at month-end: how much of what we are owed is fresh, and how much has gone stale enough to worry about. This is the mirror of an accounts payable aging. Where an AP aging lists what the business owes its suppliers, an AR aging lists what its customers owe the business, so the direction of the money is the opposite. Meridian Software Solutions Inc. runs one dated 2026-06-30. The report groups every receivable into aging buckets by days outstanding, Current, 30-60, 60-90, and 90+ days, and the buckets sum to the total the company is owed. Here 210,000.00 USD is current, 78,500.00 USD has aged into 30-60, 34,250.00 USD into 60-90, and 20,000.00 USD sits at 90+, footing to 342,750.00 USD across the customer book. The aging drives real decisions: it feeds the days-sales-outstanding metric, it sets the collections queue for the invoices past due, and it informs the expected-credit-loss reserve that ASC 326 and IFRS 9 require against receivables that may never be collected. A single customer, Pinegrove Retail Ltd, sitting in the 90+ bucket at 20,000.00 USD is the line a collections lead escalates first. Talonic reads the report and returns the header, the reporting window, the currency, the total_outstanding, and the four-bucket summary as fields, alongside a per-invoice detail array carrying the customer name and number, the invoice number and date, the due date, the invoice amount, the amount paid, the outstanding balance, the days outstanding, and the aging bucket. The bucket totals are verified to roll up to the 342,750.00 USD owed, and the per-invoice balances are tied to their bucket, so the 20,000.00 USD in 90+ traces to the invoices behind it. Amounts stay in USD as printed and are typed as numbers, the invoice_date and due_date resolve to ISO 8601, and every value returns with a confidence score and a source-region pointer under DIN SPEC 91491. The result drops into a collections workflow or a receivables forecast without anyone re-typing it out of the PDF.
What gets extracted from AR aging reports
How extraction works for AR aging reports
An AR aging is only useful if the collections team can trust the buckets, and those buckets vary by system: one ledger cuts at 30, 60, and 90 days from the invoice date, another counts from the due date, and a NetSuite export labels the tail differently again. Talonic reads the report and binds it to the accounts-receivable model registered in the Field Registry, keeping the header, the reporting window, a bucket summary, and a per-invoice detail array as distinct structures instead of one flat grid. It maps each customer's outstanding balance to a canonical bucket set, types every amount as a number in the stated currency, and verifies that the invoice-level balances roll up to their bucket and that the buckets roll up to the total owed. Dispute notes and approval_status ride along per invoice, days_outstanding is captured as printed, and the invoice_date, due_date, and approver_date resolve to ISO 8601. Each figure carries a confidence score and pixel-region provenance so a credit manager can open the 90+ bucket, land on the exact overdue invoice, and start the call.
Sample extraction
A month-end AR aging with a by-bucket summary and a customer-invoice detail table
{
"document_number": "ARA-2026-06",
"document_date": "2026-06-30",
"reporting_period_start": "2026-06-01",
"reporting_period_end": "2026-06-30",
"company_name": "Meridian Software Solutions Inc.",
"currency": "USD",
"total_outstanding": 342750,
"payment_terms": "Net 30",
"preparer_name": "Jordan Ellis",
"approval_status": "approved",
"approver_name": "Nadia Rossi",
"approver_date": "2026-07-02",
"note": "Buckets foot: 210,000.00 (Current) + 78,500.00 (30-60) + 34,250.00 (60-90) + 20,000.00 (90+) = 342,750.00",
"aging_summary_by_bucket": [
{
"aging_bucket": "Current",
"invoice_count": 24,
"total_outstanding": 210000,
"percentage_of_total": 61.3
},
{
"aging_bucket": "30-60",
"invoice_count": 9,
"total_outstanding": 78500,
"percentage_of_total": 22.9
},
{
"aging_bucket": "60-90",
"invoice_count": 4,
"total_outstanding": 34250,
"percentage_of_total": 10
},
{
"aging_bucket": "90+",
"invoice_count": 2,
"total_outstanding": 20000,
"percentage_of_total": 5.8
}
],
"aging_details": [
{
"customer_number": "C-1042",
"customer_name": "Atlas Freight Corp.",
"invoice_number": "INV-3290",
"invoice_date": "2026-05-12",
"due_date": "2026-06-11",
"invoice_amount": 18500,
"paid_amount": 0,
"outstanding_balance": 18500,
"days_outstanding": 19,
"aging_bucket": "Current"
},
{
"customer_number": "C-1187",
"customer_name": "Pinegrove Retail Ltd",
"invoice_number": "INV-3312",
"invoice_date": "2026-02-16",
"due_date": "2026-03-18",
"invoice_amount": 20000,
"paid_amount": 0,
"outstanding_balance": 20000,
"days_outstanding": 104,
"aging_bucket": "90+"
}
]
}Frequently asked
How is an AR aging different from an AP aging?
The direction of the money is opposite. An accounts receivable aging shows what customers owe the company, an asset it is trying to collect. An accounts payable aging shows what the company owes its suppliers, a liability it has to pay. Talonic reads each on its own schema and states the receivable balance as owed to the company.
Do the buckets and invoice lines reconcile?
Yes. The per-invoice outstanding balances roll up to each aging bucket, and the buckets roll up to total_outstanding, so the 20,000.00 USD in the 90+ bucket ties back to the Pinegrove Retail invoice inside it. A report whose printed totals do not add up is flagged rather than silently accepted.
How does it handle different bucket definitions?
Reports age from either the invoice date or the due date and label the ranges differently. Talonic captures the bucket exactly as printed and maps it to a canonical set (Current, 30-60, 60-90, 90+), so an aging from SAP and one from Oracle NetSuite compare on the same axis.
Can it feed a DSO or bad-debt reserve calculation?
Yes. Because every invoice returns with its outstanding balance, days outstanding, and aging bucket as typed numbers, the structured output rolls straight into a days-sales-outstanding metric or the expected-credit-loss reserve under ASC 326 and IFRS 9. Talonic supplies the structured figures; the calculation stays with the finance team.
Ready to extract from your own AR aging reports?
Author note
Reviewed by Talonic engineering, finance schema review · last reviewed 2026-07-08
- Source: Talonic AR Aging schema (seeded)