The short answer on Flint
Flint builds the aging report from your invoices for you. One request with report_type: "receivables_aging_v1" and an as_of_date returns a CSV with one row per unpaid invoice and the five standard buckets, aged from each due date, with installments, partial payments, credit notes, write-offs, and late fees already counted. The same invoices answer live queries, so the oldest bucket becomes a list you can send reminders to. The Flint requests are below.
An aging report, by example
This is a summary aging report as of November 1 for a business with four customers. Each cell is what that customer owes in that bucket:
| Customer | Current | 1-30 | 31-60 | 61-90 | 91+ | Total |
|---|
| Acme Supply | $4,200.00 | $1,800.00 | | | | $6,000.00 |
| Birch & Co | | $2,500.00 | $1,250.00 | | | $3,750.00 |
| Cobalt Studio | $1,500.00 | | | $900.00 | | $2,400.00 |
| Dune Retail | | | | | $3,100.00 | $3,100.00 |
| Total | $5,700.00 | $4,300.00 | $1,250.00 | $900.00 | $3,100.00 | $15,250.00 |
| Share | 37.4% | 28.2% | 8.2% | 5.9% | 20.3% | 100% |
A detailed aging report has the same columns with one row per invoice instead of per customer, which is what you work from when you pick up the phone.
The aging buckets
Each amount goes in exactly one bucket, by the number of days between its due date and the report date:
- Current: not due yet, or due on the report date.
- 1-30: 1 to 30 days past due.
- 31-60: 31 to 60 days past due.
- 61-90: 61 to 90 days past due.
- 91+: 91 days or more past due.
Age from the due date, not the invoice date. An invoice on Net 30 terms issued yesterday isn't late, and putting it in 1-30 makes every customer on longer terms look like a collections problem. An invoice paid in installments has an amount in each bucket its installments fall in.
How to read an aging report
- Start with the share past due. In the example, 62.6% of receivables is late. Track that number every month; a rising share is the earliest sign that cash will run short.
- Look at the oldest bucket. 20.3% is over 90 days, and it is all one customer. Money that old rarely arrives on its own.
- Read across each customer. Birch & Co has amounts in 1-30 and 31-60: they are paying, but later each month. Cobalt Studio is mostly current with one old invoice, which often means a single disputed bill rather than a cash problem.
- Compare with last month. An amount that moved from 31-60 to 61-90 went another month unpaid. An amount that left the report was paid, credited, or written off.
Two figures often come from the same data. Days sales outstanding (DSO) is your receivables divided by credit sales for a period, times the days in that period: how long, on average, you wait to be paid. And the aging method of estimating bad debt applies a larger expected-loss percentage to each older bucket.
What to do in each bucket
| Bucket | What it usually means | What to do |
|---|
| Current | Not due yet, or due today | Nothing, beyond a reminder a few days before the due date. |
| 1-30 days | Late, usually by oversight | Send a reminder with the payment link, and confirm the invoice reached the right person. |
| 31-60 days | A pattern, or a dispute you haven't heard about | Call or email the person who approves payment. Ask whether anything on the invoice is in question, and apply the late fee your terms allow. |
| 61-90 days | At risk | Put new orders on hold or require payment up front, offer an installment plan, and get a payment date in writing. |
| 91+ days | Likely uncollectible without escalation | Send a final notice, then decide between a collections agency, a legal claim, or writing the balance off. Talk to your accountant before a write-off. |
The cheapest collection work happens before the report: clear payment terms on every invoice, a payment link the customer can use from their phone, reminders on a schedule, and a late fee the customer agreed to up front.
Where aging reports go wrong
Aging reports on Flint
Flint invoices carry their own due dates, payment schedules, payments, credit notes, late fees, and write-offs, so the aging report is a request, not a spreadsheet. Ask for receivables in one currency as of a date:
curl -X POST https://api.withflintpay.com/v1/reports \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Idempotency-Key: ar-aging-2026-11-01" \
-H "Content-Type: application/json" \
-d '{
"report_type": "receivables_aging_v1",
"as_of_date": "2026-11-01",
"timezone": "America/New_York",
"currency": "USD"
}'
The report starts pending. Subscribe to report.succeeded, or poll GET /v1/reports/{report_id}, then download the CSV from download.url within 24 hours:
curl https://api.withflintpay.com/v1/report-downloads/rdl_01KB4R9W3N5P7Q8R2S4T6V8X0Y \
-H "Authorization: Bearer YOUR_API_KEY" \
--location \
--output ar-aging-2026-11-01.csv
Each row is one unpaid invoice:
| Columns | What they hold |
|---|
invoice_id, invoice_number, customer_id, customer_name, customer_email | Who owes it, for the phone call and the accounting import |
due_date, days_past_due | The earliest unpaid due date and how late it is |
total_money, paid_money, credited_money, written_off_money, late_fee_money | How the balance was reached, as of the cutoff |
current_money, past_due_1_30_money, past_due_31_60_money, past_due_61_90_money, past_due_91_plus_money | The five buckets |
outstanding_money | The sum of the five buckets |
The rules that usually take a spreadsheet are built in:
- Each unpaid installment ages from its own due date, and late fees from the day Flint assessed them.
- Payments and credits assigned to an installment reduce that installment; the rest reduce the oldest amount due first.
- Credit note allocations, write-offs, and waived late fees are subtracted, so the report never ages money the customer no longer owes.
- Due dates stay the calendar dates the buyer saw on the invoice, whatever time zone you run the report in.
A report for today reconciles to the live receivables on your invoices and customers when nothing changes between the two reads, so your accounting import and your dashboard agree.
Turn the oldest bucket into a chase list
The CSV is for month-end. For daily collections, query the invoices directly. These are overdue invoices that were due before August 3, so more than 90 days late on November 1, biggest balance first:
curl -G https://api.withflintpay.com/v1/invoices \
-H "Authorization: Bearer YOUR_API_KEY" \
--data-urlencode "is_overdue=true" \
--data-urlencode "due_date_to=2026-08-03" \
--data-urlencode "sort_by=settlement_amounts.outstanding_money" \
--data-urlencode "sort_direction=desc"
has_outstanding_balance, customer_id, due_date_from, and status narrow it further. For one customer's balance and how much of it is overdue, expand their receivables:
curl "https://api.withflintpay.com/v1/customers/cus_1kmn0aExample?expand=receivables" \
-H "Authorization: Bearer YOUR_API_KEY"
Then act on each invoice from the same API:
- Remind: a reminder schedule on your invoice settings sends emails before and after the due date on its own. To send one now:
curl -X POST https://api.withflintpay.com/v1/invoices/inv_1kmn0aExample/send-reminder \
-H "Authorization: Bearer YOUR_API_KEY"
- Charge a late fee: payment terms with a late fee policy add the fee to the same invoice after a grace period, automatically or with
POST /v1/invoices/{invoice_id}/late-fees. See invoice late fees. - Credit it: a credit note lowers the balance when part of the bill is in dispute.
- Write it off:
POST /v1/invoices/{invoice_id}/mark-uncollectible moves the balance to written_off_money. If the money arrives later, record it, and Flint lowers the write-off.
Flint doesn't sync to QuickBooks, Xero, or NetSuite, so import the CSV and join on the invoice and customer IDs. The reporting guide covers the cutoff, inclusion rules, and reconciliation in full.
Who Flint is built for
US businesses invoicing customers in USD, such as wholesalers, agencies, and service companies, that want payment terms, reminders, late fees, credit notes, and receivables reporting on the same orders as the rest of their sales. See Flint invoices. Invoices are an add-on at 0.40% of the payments collected through them, with no monthly fee.
Questions, answered
What is an accounts receivable aging report?
An accounts receivable aging report lists what customers owe you on unpaid invoices as of a date, split into buckets by how far past due each amount is: usually current, 1 to 30 days, 31 to 60 days, 61 to 90 days, and over 90 days. It shows who owes what and how late it is.
What are the buckets in an aging report?
The standard buckets are current (not yet due), 1 to 30 days past due, 31 to 60, 61 to 90, and 91 or more. Some businesses use 15-day buckets or add a 120+ column, but 30-day buckets are the common default.
How do you read an AR aging report?
Read the totals row first to see what share of receivables is past due and how much is over 90 days. Then read across each customer to find who drives the late buckets, and down the oldest columns to decide who to call first. A rising share in the older buckets month over month is the warning sign.
Is aging calculated from the invoice date or the due date?
Either, but the due date is more useful because it measures lateness rather than age. On a due-date report, an invoice on Net 30 terms stays current for 30 days after it is issued. Flint's receivables_aging_v1 report ages from the due date, and from each installment's own due date.
What should I do about invoices over 90 days?
Contact the customer directly, stop extending new credit, and offer a payment plan with a date in writing. If that fails, choose between a collections agency, a legal claim, or writing the balance off as uncollectible, and talk to your accountant about how the write-off is recorded.
How do I get an AR aging report from an API?
On Flint, create a report with report_type receivables_aging_v1, an as_of_date, and a currency through POST /v1/reports. When it succeeds, download the CSV: one row per unpaid invoice, with payment, credit, write-off, and late fee totals and five aging buckets.