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

# Daily AR workflow: review, prioritize, and follow up

> A practical daily workflow for using Daylit to review receivables, prioritize risky accounts, send follow-ups, and manage exception cases.

<Callout icon="route" color="#2F6F9F">
  **Next** in [Run your daily AR workflow](/): [AR Manager journey](/journeys/ar-manager) — go deeper on the daily and weekly operating model for AR teams.
</Callout>

## Purpose

Use this page as your daily operating loop in Daylit. It shows what to open first, how to decide what needs attention, and where to take action.

Follow the steps in order on a normal AR day: review portfolio health, prioritize customers, clear work queues, handle cases, and confirm automation coverage.

**Example:** On Monday morning, **Jobin (AR manager)** at **Acme Corporation** opens Daylit, checks whether overdue balance moved, reviews risky accounts, clears the Inbox, accepts case suggestions, and confirms that collection programs are running for the long tail.

## Daily workflow at a glance

```mermaid theme={null}
%%{init: {"theme":"base","themeVariables":{
  "fontFamily":"Plus Jakarta Sans, -apple-system, sans-serif",
  "background":"#fefdf8",
  "primaryColor":"#ffffff",
  "primaryTextColor":"#3d0c11",
  "primaryBorderColor":"#e8e5df",
  "lineColor":"#3d0c11",
  "secondaryColor":"#fef9c3",
  "tertiaryColor":"#fefdf8"
}}}%%
flowchart LR
    S([Start]) --> A[Review dashboard]
    A --> B[Prioritize risky accounts]
    B --> C{Routine or exception?}
    C -- Routine --> D[Clear Inbox]
    C -- Exception --> E[Review cases]
    D --> F[Check programs]
    E --> F
    F --> G([Done])

    classDef current fill:#3d0c11,color:#fefdf8,stroke:#3d0c11,stroke-width:1px;
    classDef active  fill:#fef9c3,color:#3d0c11,stroke:#3d0c11,stroke-width:1px;
    classDef alert   fill:#f5b878,color:#3d0c11,stroke:#3d0c11,stroke-width:1px;
    class A current;
    class D active;
    class E alert;
```

## Before you start

This workflow assumes your workspace is already set up:

* Accounting data is connected in [Integrations](/settings/integrations).
* Customer and invoice data appears in the [Dashboard](/dashboard/overview).
* Email is connected for the teammates who send collection messages.
* At least one collection program or sequence exists for repeatable outreach.

If you still need to connect data, email, or programs, start with [Quickstart](/quickstart).

## Step 1 — Review portfolio health

<Steps>
  <Step title="Open Dashboard">
    Go to **Dashboard** and review total AR, DSO, aging buckets, top customer exposure, and portfolio health.
  </Step>

  <Step title="Check what changed">
    Look for aging buckets that moved, especially **61–90 days** and **90+ days**. These buckets show where collection risk is concentrating.
  </Step>

  <Step title="Drill into aging">
    Open [AR Aging](/dashboard/ar-aging) to see which customers are driving overdue balances by bucket.
  </Step>
</Steps>

After this step, you should know whether the day is routine or whether a specific segment, customer, or aging bucket needs attention.

## Step 2 — Prioritize customers

<Steps>
  <Step title="Open Customers">
    Go to **Customers** and sort or filter by AR balance, days past due, owner, label, or signal severity.
  </Step>

  <Step title="Open the riskiest accounts">
    Start with customers that are **Risky**, have high overdue balances, or appear in the aging bucket that moved most.
  </Step>

  <Step title="Read the account context">
    On each customer profile, review open invoices, AI signals, conversation summary, contacts, labels, and notes.
  </Step>
</Steps>

Use [AI Signals](/customers/signals-insights) to understand why an account is flagged before deciding the next action.

## Step 3 — Decide routine follow-up or exception handling

Use this decision table before sending outreach:

| Situation                            | Use this path                                                                                                                                        |
| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Customer is simply overdue           | Use [Inbox](/collections/action-center), [Collection programs](/collections/collection-programs), or [Collection sequences](/collections/sequences). |
| Customer promised to pay             | Review or open a [Collection case](/collections/collection-cases) so the promise is tracked.                                                         |
| Customer disputes the invoice        | Review or open a [Collection case](/collections/collection-cases) so the dispute is tracked and conflicting routine dunning is paused.               |
| Contact is wrong or unresponsive     | Review or open a [Collection case](/collections/collection-cases) so the contact issue is tracked before sending more reminders.                     |
| Strategic account needs careful tone | Review the AI draft manually before sending.                                                                                                         |

This keeps routine dunning separate from exception workflows that need a case or owner.

## Step 4 — Clear the Inbox

<Steps>
  <Step title="Open Inbox → Review">
    Review AI-recommended emails and calls. Approve routine actions in bulk when the content and recipients look right.
  </Step>

  <Step title="Edit sensitive messages">
    Open high-value, escalated, or relationship-sensitive actions individually. Edit the draft before clicking **Review & Send**.
  </Step>

  <Step title="Check Inbox → Sequences">
    Review sequence steps that are ready today. Send, complete, or edit them based on the customer context.
  </Step>
</Steps>

Use [Email drafting](/collections/email-drafting) if you need to understand how drafts are generated, rewritten, and sent.

## Step 5 — Work case suggestions

<Steps>
  <Step title="Open Cases → Suggestions">
    Review AI-recommended case actions, such as opening a promise-to-pay case, dispute case, inquiry, or wrong-contact case.
  </Step>

  <Step title="Accept or reject suggestions">
    Accept suggestions that match the customer context. Reject suggestions that do not apply.
  </Step>

  <Step title="Open active cases">
    From **Cases → All cases**, review open cases that need your team, the customer, or an internal partner.
  </Step>
</Steps>

Cases help prevent routine dunning from colliding with disputes, promises to pay, and other exception workflows.

## Step 6 — Check automation coverage

At the end of the workflow, make sure repeatable work is covered by automation.

<Steps>
  <Step title="Review collection programs">
    Check that your main customer segments are enrolled in the right [collection programs](/collections/collection-programs).
  </Step>

  <Step title="Review sequences">
    Confirm custom or case-specific workflows use the right [collection sequences](/collections/sequences).
  </Step>

  <Step title="Assign owners">
    Make sure high-priority accounts have the right AR owner in [Customers](/customers/managing-customers) or [Team settings](/settings/team).
  </Step>
</Steps>

After this step, routine accounts should be covered by programs or sequences. Exception accounts should have cases or owners.

## What good looks like

| Outcome                              | Signal                                                                             |
| ------------------------------------ | ---------------------------------------------------------------------------------- |
| You know what changed                | Dashboard and AR Aging show the accounts or buckets that need attention.           |
| Routine work is cleared              | Inbox review items are approved, edited, sent, or dismissed.                       |
| Exceptions are tracked               | Promises to pay, disputes, wrong contacts, and inquiries live in Collection Cases. |
| Automation is covering the long tail | Collection programs and sequences handle repeatable follow-up.                     |
| Ownership is clear                   | High-risk customers have an AR owner and next action.                              |

## Related pages

* [AR Manager journey](/journeys/ar-manager) — Go deeper on the AR manager operating model.
* [Dashboard overview](/dashboard/overview) — Understand the main portfolio metrics.
* [Manage customers](/customers/managing-customers) — Search, filter, assign owners, and open customer profiles.
* [Inbox](/collections/action-center) — Review and send collection actions.
* [Collection cases](/collections/collection-cases) — Track disputes, promises to pay, inquiries, and wrong contacts.
* [Collection programs](/collections/collection-programs) — Automate repeatable dunning.
* [Collection sequences](/collections/sequences) — Build customer-level or case-specific playbooks.

<Callout icon="circle-check" color="#2F6F9F">
  Finished this page? Continue [Run your daily AR workflow](/) with [AR Manager journey](/journeys/ar-manager).
</Callout>