Finance & Accounting
Create an accounts receivable aging report from a CSV
Upload open invoices with due dates and balances, pick the as-of date, and get them grouped into current, 1–30, 31–60, 61–90 and 90+ days, with totals.
or drop it here
- CSV
- Up to 50,000 open invoices
1 prepared source file · 141 bytes
- Invoices: 3
- Open total: 1524.9
- As of: 2026-03-01
result.csv · findings.csv · manifest.json
One clear job, from source to download
- 1
Add the source
Supported formats and limits are visible before the upload.
- 2
Confirm the settings
Review the exact source, options, units and access before processing.
- 3
Inspect and download
Check the preview and warnings, then unlock the complete package.
An aging report from your list of open invoices
What you bring
You upload a CSV of open invoices. Each row needs an open balance and a due date, because the aging buckets are calculated from those two fields. One job takes up to 50,000 invoice rows. Split larger exports by entity or period first. Rows that cannot be read are not dropped quietly. They are listed separately so you can fix them and run the file again.
What you get back
The download contains result.csv, findings.csv and manifest.json. In result.csv each invoice sits in current, 1 to 30, 31 to 60, 61 to 90 or 90 plus days past due, with totals. findings.csv lists the rows that could not be read and other problems. The manifest records the as-of date and a fingerprint of your source file. Compare the totals in the preview with your ledger before you download.
The as-of date and mixed currencies
The one setting is the date you age the balances against. Set it to a past month-end, such as 31 March, and a rerun gives the same buckets. Balances in different currencies are never added together without rates you supply. A mixed-currency file is reported so you can split it or convert it yourself. The report supports your review. Collection steps and accounting decisions stay with you and, where needed, your accountant.
Questions before you run it
Which columns does my invoice CSV need?
Each row needs an open balance and a due date, because the buckets are calculated from those two fields. Rows that cannot be read are listed in findings.csv rather than dropped quietly.
Which aging buckets does it produce?
Current, 1 to 30, 31 to 60, 61 to 90 and 90 plus days past due, measured against the as-of date you set.
Can I age the ledger as of a past month-end instead of today?
Yes. The as-of date is a control you set before the run, so a 31 March position reproduces the same buckets whenever you rerun it.
What happens if the file mixes several currencies?
Balances are not consolidated across currencies without rates you supply. A mixed-currency file is reported so you can split it or provide the conversion yourself.
How many open invoices can one run handle?
One CSV job takes up to 50,000 open invoice rows. Larger exports should be split by entity or period before upload.