Invoice Aging Report

Turn a list of invoices into an aging report: how much is outstanding, how late it is, and which bucket it falls into.

What it does

Reads the invoices you supply and reports each one with the amount outstanding, the days past due and the standard aging bucket it lands in — so receivables can be worked in order rather than discovered at month end.

Output fields

Field	Description
invoiceId	Identifier of the invoice.
customer	The customer this invoice belongs to.
dueDate	The date the amount fell due.
amount	The invoiced amount.
paidAmount	The amount already paid.
outstanding	The amount still outstanding.
daysPastDue	How many days past due.
bucket	The aging bucket this invoice falls into.
status	The status recorded for this invoice.

Sample output

{
  "invoiceId": "inv_2201",
  "customer": "Acme Ltd",
  "dueDate": "2026-09-30",
  "amount": "1200.00",
  "paidAmount": "0.00",
  "outstanding": "1200.00",
  "daysPastDue": 46,
  "bucket": "31-60",
  "status": "overdue"
}

Use cases

• Month-end receivables review.
• Prioritising collections by amount and lateness together.
• Producing a report a finance team can act on without a spreadsheet.

Pricing

Pay per event: charged per invoice row written, plus a near-zero start event.

FAQ

Does it send reminders or contact customers?

No. It produces the report and stops there.

How are buckets defined?

Standard aging bands — current, 1-30, 31-60, 61-90 and 90+ — computed from the due date against a Clock, so a reinvestigated run is reproducible.

What if a payment is partial?

paidAmount and outstanding are reported separately, so a part-paid invoice still shows correctly.

Related Actors

• Bank Statement Reconciler
• CDR Invoice Reconciler

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• Invoice Aging Report declares all 6 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of Invoice Aging Report include customer, dueDate, amount, paidAmount, outstanding and status.
• Invoice Aging Report needs no API key, login or account of any kind before its first run.
• Every one of Invoice Aging Report's 3 inputs is optional, so it runs with no configuration at all.
• Invoice Aging Report documents amount as: The amount, in the currency given by the currency field.
• Every number published about Invoice Aging Report is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• Invoice Aging Report is filed under business and developer tools so that it is found by the people looking for that job, not by its internal name.

Limitations

• Invoice Aging Report reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.