> ## 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.

# Core Concepts: AR Agent data model and key terms

> Learn the key terms for Daylit AR Agent: signals, sequences, collection programs, AI insights and more explained.

## Platform Vocabulary

Daylit AR Agent has a specific data model that shapes how you navigate the product and how the AI generates its outputs. Understanding these terms makes it easier to interpret what you see on the dashboard, configure collection workflows, and work with the API. Each concept below maps directly to a record type or feature in the product.

<AccordionGroup>
  <Accordion title="Company">
    A **company** is the organization whose accounts receivable you are managing — in other words, your business. When you log in to Daylit, you select a company context, and all the data you see (customers, invoices, insights, sequences, and settings) belongs to that company.
  </Accordion>

  <Accordion title="Customer">
    A **customer** is a buyer who owes your company money — an entity that has one or more open invoices. Customers are synced automatically from your connected accounting system and appear on the **Customers** page.
  </Accordion>

  <Accordion title="Invoice">
    An **invoice** is a receivable — a record of money your customer owes you for goods or services delivered. Each invoice has an amount, a due date, a remaining balance, and a status (open, paid, partially paid, voided, and so on).
  </Accordion>

  <Accordion title="AR aging">
    **AR aging** is the practice of grouping open invoices by how long they have been outstanding past their due date. Daylit uses the following standard aging buckets: Current, 1–30 days, 31–60 days, 61–90 days, and 90+ days past due.
  </Accordion>

  <Accordion title="Insight">
    An **insight** is an AI-generated result attached to a customer, invoice, or your entire portfolio. Insights are produced by background AI agents that run regularly against your latest AR data.

    At the portfolio level, insights surface key receivables metrics that feed your dashboard health score and AI signals. Expand any term below to see how it is calculated.

    <AccordionGroup>
      <Accordion title="Current A/R %">
        Percentage of your total receivables that are not yet past due. Higher is better — it means more invoices are within their payment terms.
      </Accordion>

      <Accordion title="Days Beyond Terms">
        Average number of days your paid invoices were collected early or late compared to their due date (net terms), weighted by invoice amount. Positive = paid late. Negative = paid early. Only includes invoices that have been paid.
      </Accordion>

      <Accordion title="Open invoice age">
        Average age of your open invoices, weighted by balance. Severely aged invoices (365+ days past due) are excluded from the headline figure by default.
      </Accordion>

      <Accordion title="90+ Day A/R">
        Percentage of your total receivables that are more than 90 days past due. These invoices are at higher risk of non-payment.
      </Accordion>

      <Accordion title="Top Customer Exposure">
        Your largest customer's balance as a percentage of total receivables. High concentration creates risk if that customer defaults or pays late.
      </Accordion>
    </AccordionGroup>
  </Accordion>

  <Accordion title="Signal">
    A **signal** is a specific type of insight — an AI-detected pattern or risk indicator on a customer or invoice. Signals surface conditions like a history of late payments, a sudden slowdown in payment pace, or an unusually high open balance. Each signal shows as **risky**, **watch**, or **healthy** — telling you how urgently that customer or invoice needs attention.
  </Accordion>

  <Accordion title="Payment prediction">
    A **payment prediction** is an AI forecast of when a specific invoice is likely to be paid, based on the customer's historical payment behavior, the invoice's aging, and other signals.
  </Accordion>

  <Accordion title="Sequence">
    A **sequence** is a multi-step automated outreach workflow that you manually build and assign to specific customers for targeted collection outreach.
  </Accordion>

  <Accordion title="Collection program (dunning)" id="collection-program-dunning">
    A **collection program** is an always-on, rule-based program that automatically enrolls overdue customers and sends scheduled outreach based on aging rules. You configure a schedule of touchpoints — each one fires at a specific offset from an invoice's due date. Expand any term below to see how collection programs are structured.

    <AccordionGroup>
      <Accordion title="Touchpoint">
        A **touchpoint** is a single outreach action in a collection program — typically an email sent to a customer at a planned point in the schedule. Each touchpoint is a collection action with a configured **offset days** value relative to the invoice due date. For example, a touchpoint might send a service-suspension warning when an invoice is 45 days past due.
      </Accordion>

      <Accordion title="Offset days">
        **Offset days** is the number of days from an invoice's due date when a touchpoint should send. Negative values send before the due date, `0` sends on the due date, and positive values send after the due date. This is not the same as the **send date** — the send date is the actual calendar day Daylit dispatches the email, which depends on your program's run schedule.
      </Accordion>

      <Accordion title="Account / invoice level">
        **Invoice-level** and **account-level** are the two target scopes for touchpoints. They define what AR data the touchpoint is tied to and when it fires.

        <AccordionGroup>
          <Accordion title="Invoice-level touchpoint">
            A touchpoint tied to an individual invoice, triggered based on that invoice's own due date. It fires relative to the invoice's due date using an offset — for example, offset `-5` sends 5 days before due, `0` on the due date, and `+15` at 15 days past due.
          </Accordion>

          <Accordion title="Account-level touchpoint">
            A touchpoint tied to a customer's total overdue balance — not to any single invoice, but to their entire open AR picture beyond a threshold. It fires when the oldest invoice in a customer's open AR reaches a configured days-past-due threshold.
          </Accordion>
        </AccordionGroup>
      </Accordion>
    </AccordionGroup>
  </Accordion>

  <Accordion title="Inbox">
    The **Inbox** (also called the **Action Center**) is where your team reviews collection emails before they go out. Emails that need your approval land here until you approve, edit, or reject them.

    <AccordionGroup>
      <Accordion title="Action">
        An **action** is a recommended or scheduled communication (email, call, task) generated for a specific customer or invoice.
      </Accordion>

      <Accordion title="Render">
        **Render** is the act of taking an email template or snippet — which contains placeholder variables like `{{invoice_list}}`, `{{total_balance}}`, and `{{contact_first_name}}` — and substituting them with real, live data at the moment the email is prepared, producing the final readable email content. While you are drafting an email, click **Render** and each snippet in your draft is replaced with real-time data for that customer or invoice.
      </Accordion>
    </AccordionGroup>
  </Accordion>

  <Accordion title="Label">
    A **label** is a custom tag you create and apply to a customer or invoice to organize accounts, filter your tables, and focus your collection work. Labels live only in Daylit — they never sync to or from your accounting system.

    * A label is simply a name for your company (for example, `vip`, `credit_hold`, `net-90`, or `escalated`).
    * You can tag both customers and invoices, and apply multiple labels to the same account.
    * Your AR team creates and manages labels — Daylit does not generate them automatically.
  </Accordion>

  <Accordion title="Snippet" id="snippet">
    A **snippet** is a reusable content block you add to an email draft by clicking **Insert snippet**. Snippets are pre-built placeholders for things like invoice lists, balances, and payment instructions.

    When you send the email, Daylit **renders** each snippet with live data for that customer or invoice — swapping placeholders for real values to produce the final message. See **Render** under **Inbox** for how that works.

    | Snippet                | What it does                                  |
    | ---------------------- | --------------------------------------------- |
    | `invoice-list`         | Renders a table of invoices in scope          |
    | `payment-instructions` | How to pay (link and remittance details)      |
    | `aging-summary`        | Aging bucket breakdown for the customer       |
    | `total-balance`        | Full open AR balance as a one-liner           |
    | `overdue-balance`      | Balance scoped to past-due invoices only      |
    | `signature`            | Sender name, title, company, and contact info |
  </Accordion>

  <Accordion title="Communication thread">
    A **communication thread** is the full log of every email, call, and note associated with a customer or invoice.
  </Accordion>
</AccordionGroup>