​
Overview

The Aged Receivables Report shows all unpaid Invoices for a Business, grouped by how long they have been overdue. An Invoice is considered outstanding only after its due date has passed and payment has not been applied. The report shows which customers owe money, the overdue duration of their payments, and the total outstanding balance. Key components (per customer):
  • Customer ID – Unique identifier for the customer.
  • Customer Name – Display name of the customer.
  • Overdue 0–30 – Amount past due by up to 30 days.
  • Overdue 31–60 – Amount past due by 31–60 days.
  • Overdue 61–90 – Amount past due by 61–90 days.
  • Overdue 90+ – Amount past due by more than 90 days.
  • Total Outstanding – Sum of all overdue Invoices for the customer.

​
How to Generate an Aged Receivables Report

  1. Call the Retrieve the Aged Receivables Report endpoint with:
    • Business ID
    • start_datetime (ISO‑8601) — the reference date used to calculate aging buckets
Example request: 
curl --request GET   --url "https://api.sandbox.getasset.com/v0/business/{business_id}/reports/aged-receivables?start_datetime=2025-01-01T00:00:00Z"   
--header 'Authorization: Bearer <token>'
  1. Use the response to display customer-level balances across the standard aging buckets:
    • 0–30 days overdue
    • 31–60 days overdue
    • 61–90 days overdue
    • 90+ days overdue
    • Total Outstanding

​
Aged Receivables Best Practices

  • Use today’s date for most cases. Passing today’s date as start_datetime ensures aging buckets reflect overdue balances as of the current day, which aligns with standard collections workflows.
  • Provide drill-downs. Users may need to inspect overdue Invoices for a specific customer. Use the Invoice Reconciliation guide and Invoice endpoints to retrieve details.
  • Handle time zones carefully. The start_datetime parameter anchors aging buckets. Use UTC consistently or clearly state how local time zones are applied.
Questions? Reach out via our Contact form.