Collections

Collections is what happens after an issued invoice passes its due date without being paid. Alguna moves the invoice to overdue, an automation sends the customer a reminder cadence, and the dashboard and API show you how much is outstanding and for how long. Use this page to understand that flow, tune the cadence, and read accounts-receivable ageing. It applies whether the customer was meant to pay by card, by wallet, or by bank transfer. Two neighbouring flows are documented separately: Dunning recovers a failed payment attempt, which can happen before the due date; Agentic Collections (beta) replaces the fixed cadence with AI-run collection cases. Collections has no configuration endpoints in the public API — cadences are automations set up in the dashboard — but everything it produces (statuses, ageing, payments) is readable. For where invoices and payments sit in the wider model, see How Alguna Works.

How it works

A scheduled job looks at every issued invoice whose due date has passed and moves it to overdue. The transition emits an invoice_status_updated automation trigger, which any matching automation picks up. Invoices with indefinite payment terms have no due date and never become overdue. See payment terms.

The default template

Every organization starts with a built-in automation template called Overdue Invoice Reminder. It waits, re-fetches the invoice, checks that it is still overdue, and sends a reminder — twice.

Property	Value
Trigger	`invoice_status_updated`
Condition	`status == 'overdue'`
Execution policy	`always` — each transition into overdue starts a fresh run
Steps	Wait 3 days → get invoice → check `status == 'overdue'` → `send_invoice_reminder` → wait 3 days → get invoice → check → `send_invoice_reminder`

So with the defaults the customer hears from you 3 and 6 days after the invoice went overdue. Each reminder is preceded by a status check: if the invoice has been paid or voided by then, the reminder is skipped and the run ends.

Status transitions

From	To	Triggered by
`issued`	`overdue`	Scheduled job, once the due date has passed
`overdue`	`paid`	A payment, wallet charge, credit note, or mark-as-paid settles the balance
`overdue`	`void`	`POST /invoices/{id}/void` or the dashboard

A partial payment does not change the status; the invoice stays overdue until amount_remaining is zero. Connected accounting integrations receive the overdue state through the normal invoice sync.

Configuration

Payment terms — when invoices go overdue

The number of days from issue to due date comes from the organization default under Settings → Invoices, overridable per subscription with billing.payment_terms (net_30, net_60, …). See Invoicing Configuration and Recurring Invoices.

Reminder cadence — when emails go out

Open Automations.
Enable the built-in Overdue Invoice Reminder template, or Clone it to get an editable copy.
Adjust the wait durations and add or remove reminder blocks. A block is Wait → Get invoice → Condition → Send invoice reminder; add as many as you need.
Optionally change the email used by send_invoice_reminder under Settings → Emails. The overdue reminder uses the invoice_reminder_overdue template.
Activate the automation.

Reminders before the due date are a different template: Invoices Due Reminders runs on a daily schedule, lists issued invoices, and sends the invoice_reminder_due email ahead of the due date. Both are described with the rest of the actions in Automations.

Seeing what is outstanding

Dashboard

Invoices → A/R Aging buckets open balances by days past due and lists them per customer.
Invoices, filtered to overdue, lists every outstanding invoice.
Revenue Insights → Accounts Receivables shows the same ageing as a report.

API

GET /insights/ar-aging returns the organization-wide picture in the base currency; GET /insights/ar-aging/by-customer returns one row per customer (filterable by customer_id or customer_alias). See Get accounts receivable aging summary and by customer.

curl https://api.alguna.io/insights/ar-aging \
  -H "Authorization: Bearer $ALGUNA_API_KEY" \
  -H "Alguna-Version: 2026-04-01"

import os

import requests

response = requests.get(
    "https://api.alguna.io/insights/ar-aging",
    headers={
        "Authorization": f"Bearer {os.environ['ALGUNA_API_KEY']}",
        "Alguna-Version": "2026-04-01",
    },
    timeout=10,
)
response.raise_for_status()

aging = response.json()
print(aging["currency"], aging["overdue_balance"], aging["buckets"])

const aging = await alguna.insights.arAging();

The response carries total_open_balance, overdue_balance, open_invoice_count, overdue_invoice_count, avg_days_overdue, avg_days_to_pay, and buckets:

Bucket	Meaning
`current`	Not yet due
`days_1_to_30`	1–30 days past due
`days_31_to_60`	31–60 days past due
`days_61_to_90`	61–90 days past due
`days_90_plus`	More than 90 days past due

The buckets sum to total_open_balance; overdue_balance is every bucket except current. To list the invoices themselves: GET /invoices?status=overdue&sort=due_date:asc. See Invoicing Configuration.

What the system does automatically

Moves issued invoices to overdue when the due date passes, on a recurring schedule.
Re-checks the invoice before every reminder and skips the send if it is no longer overdue.
Starts one run per transition into overdue.
Stops a run the moment the invoice is paid or voided — the next status check ends it.

What it does not do

Send reminders before the due date (that is the Invoices Due Reminders template).
Charge the customer. Collections is a notification flow; charging is AutoPay on issue, or a retry_invoice_payment step in a dunning automation.
Apply late fees.

Edge cases

Invoice paid between reminders. The status check before the next reminder sees paid and the run ends. Invoice voided while overdue. Same — the check sees void and stops. Invoice without a due date. indefinite payment terms mean no due date, so the invoice stays issued. Partial payment. The status stays overdue and reminders continue until the balance is zero. Several invoices for one customer. Each invoice runs its own reminder workflow. Agentic Collections can consolidate them per account instead. Subscription cancelled while an invoice is overdue. The workflow continues against the outstanding invoice. Add a condition step on subscription status if you want it to stop.

Example

A $1,800 invoice with net_30 terms is issued on April 1, so it is due May 1.

Date	What happens
April 1	Issued, status `issued`
May 1	Due date passes
May 2	Scheduled job sets `overdue`; `invoice_status_updated` fires; Overdue Invoice Reminder starts and waits 3 days
May 5	Status check: still overdue → first reminder sent; wait 3 days
May 8	Status check: still overdue → second reminder sent; run ends

Had the customer paid on May 6, the May 8 check would have seen paid and skipped the second reminder.

Impact on other parts of Alguna

Revenue reporting: an overdue invoice is still recognised revenue. Collections affects cash, not recognition. See Revenue Recognition.
Dunning: fires on payment_failed, collections on the issued → overdue transition. They are independent and can both run on the same invoice.
Customer portal: the hosted portal shows the overdue status with a payment link, and the reminder email links there.
Agentic Collections: when enabled, opens a collection case per invoice or per account and manages the outreach itself. See Agentic Collections.

FAQ

Can I send more than two reminders? Yes. Clone the template and add more reminder blocks. There is no upper limit. Can I attach a payment link to the reminder email? The default reminder email already includes a hosted payment link. What stops the reminders? Any of: the invoice is paid or voided, the run reaches its last step, or you cancel the run from the automation’s execution view. Does an overdue invoice affect recognised revenue? No. Overdue is a collection state, not a recognition state. Can I customise the email copy? Yes, under Settings → Emails: the invoice_reminder_overdue and invoice_reminder_due templates. Is there an API to configure collections? No. Cadences are automations configured in the dashboard. The API exposes the results: invoice statuses, payments, and A/R ageing.

Overview

Guides

Getting Started

Customers

Pricing & Packaging

Quotes (CPQ)

Subscriptions

Entitlements

Invoices

Credits & Wallets

Usage Metering

Approval Workflows

Automations

Tax Management

Hosted Pages

Revenue & Accounting

Multi-Currency

Data & Exports

AI

Collections

How it works

The default template

Status transitions

Configuration

Payment terms — when invoices go overdue

Reminder cadence — when emails go out

Seeing what is outstanding

Dashboard

API

What the system does automatically

What it does not do

Edge cases

Example

Impact on other parts of Alguna

FAQ

​How it works

​The default template

​Status transitions

​Configuration

​Payment terms — when invoices go overdue

​Reminder cadence — when emails go out

​Seeing what is outstanding

​Dashboard

​API

​What the system does automatically

​What it does not do

​Edge cases

​Example

​Impact on other parts of Alguna

​FAQ

How it works

The default template

Status transitions

Configuration

Payment terms — when invoices go overdue

Reminder cadence — when emails go out

Seeing what is outstanding

Dashboard

API

What the system does automatically

What it does not do

Edge cases

Example

Impact on other parts of Alguna

FAQ