> ## Documentation Index
> Fetch the complete documentation index at: https://docs.custral.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Receivables and collections

> See what's been collected, what's still owed and what's overdue, and chase late invoices with a reminder sequence.

**Revenue → Receivables** shows the money your customers owe you, read live from your Stripe account. From the same tab, an admin can turn on **collections**: a reminder sequence that chases overdue invoices until they're paid.

Receivables needs Stripe connected. Until it is, the tab says "Stripe isn't connected" and points to [Settings → Payments](/revenue/payments).

## The Receivables tab

<Steps>
  <Step title="Pick a period">
    **30 days**, **90 days**, **12 months** or **All**. The tab lists the invoices created in that period, plus every invoice that is still open, whatever its date.
  </Step>

  <Step title="Read the stat cards">
    One row of four cards per currency. Amounts in different currencies are never added together.
  </Step>

  <Step title="Work the invoice table">
    Use **+ Filter** to narrow by status (Overdue, Open, Paid, Void, Uncollectible), customer, or due, paid or issued date, search by invoice number or customer, and copy a pay link to send a customer.
  </Step>
</Steps>

### Stat cards

| Card | Shows |
| - | - |
| **Collected** | What was paid in the period. |
| **Outstanding** | What's still owed on open invoices, with how many are open. |
| **Overdue** | The part of that past its due date, with how many invoices. |
| **Avg days to pay** | How long paid invoices took, counted from when they were sent. |

### Invoice table

Each row shows the invoice number, the customer, the amount, what's **due now** on an open invoice, its status (**Open**, **Overdue 3 days**, **Paid Oct 5**, **Uncollectible** or **Void**) and its due date. An open invoice has **Copy pay link**, which copies Stripe's hosted page where the customer pays it.

With a long period, the table may show only the most recent invoices; it says so, and a shorter period shows them all.

### Usage that wasn't billed

If you bill by usage, a line appears when some usage events couldn't be billed, for example "3 usage events weren't billed". That happens when the customer hasn't accepted a quote yet, so Stripe has no customer to bill. See [Usage products](/revenue/payments#usage-products).

## Collections

Collections is a ready-made automation that chases overdue invoices. Custral sets it up for you when payments are set up, and it starts **off**: nothing is sent until an admin turns it on.

It is made of two parts you can open and edit like any other:

* A [sequence](/automation/sequences/overview) named **Collections**, with the reminder steps.
* A [workflow](/automation/workflows/overview) named **Chase overdue invoices**: when an invoice goes overdue, it enrolls the customer's record in the sequence.

### What it does

Once a day, Custral checks your Stripe account for open invoices past their due date. Each overdue invoice is announced once, and its customer is enrolled:

| When | Step |
| - | - |
| Day 0 | **Friendly reminder**: an email naming the invoice number, the amount still owed and the due date, with the pay link. |
| Day 7 | **Follow-up**: the same details, "Following up on this". |
| Day 14 | **Call about the overdue invoice**: a task on the customer's record to call them. |

Paying the invoice stops the sequence: its goal is a successful payment, so the enrollment ends as soon as Stripe reports one. A failed autopay charge leaves the invoice open, so it is chased the same way once it's overdue.

The reminders go to the email field you mapped on your Customers object. If the record has no email, they go to the address Stripe billed the invoice to. A customer already being chased isn't enrolled a second time.

### Turn it on

<Steps>
  <Step title="Open Receivables">
    In **Revenue → Receivables**, choose **Turn on collections**.
  </Step>

  <Step title="Pick a mailbox">
    Under **Send reminders from**, choose the connected mailbox they go from. A sequence has no mailbox of its own, so this is required.
  </Step>

  <Step title="Turn on">
    The tab now shows a **Collections on** badge.
  </Step>
</Steps>

While it's on:

* **Edit** opens the Collections sequence, where you can reword the emails or change the waits.
* **Turn off** stops new reminders, after a confirmation. Customers already in the sequence finish their current step.

<Note>
  Only admins can turn collections on or off. Members see the control disabled with the reason. It also stays disabled until Settings → Payments has a Customers object.
</Note>

## On the customer record

Each customer record shows the same billing on its **Billing** panel: the subscription with its MRR, discount and way to pay, the newest invoices with their status and **Copy pay link** on open ones, upcoming instalments, and its quotes. Payments, failed charges and overdue invoices also appear on the record's timeline, for example "Payment of \$1,080.00 received (INV-0131)".

## Build your own

Collections is built from the [Invoice Overdue and Payment Succeeded triggers](/revenue/automations). Those and the other revenue triggers work in workflows of your own, for example **Payment Failed** followed by a task to call the customer.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.