Receivables follow-up

Before you start

Discuss setup and account eligibility with the founding team. This manifest is not an executable or purchasable template.

• Invoice ID, customer, due date, amount and currency
• Current payment and dispute status
• Approved reminder policy and a named finance reviewer

How the workflow should run

• Read the latest invoice and payment records from authorized sources.
• Exclude paid, disputed and incomplete records; show the reason for each exception.
• Draft a reminder for each eligible overdue invoice with its invoice ID and source.
• Wait for approval before sending. Recheck payment status immediately before the approved action.

Human review and limits

A finance owner reviews recipients, balance and wording before a reminder is sent. Posting entries or making payments needs its own authority.

• No debt collection, legal escalation or money movement is implied. Source access and account eligibility must be confirmed.

Synthetic example input

This is a small illustration of the expected contract. It is not a customer record, live execution result or performance benchmark.

{
  "synthetic": true,
  "asOf": "2026-10-26",
  "invoices": [
    {
      "id": "INV-DEMO-01",
      "due": "2026-10-20",
      "amount": 500,
      "currency": "USD",
      "status": "unpaid"
    },
    {
      "id": "INV-DEMO-02",
      "due": "2026-10-20",
      "amount": 250,
      "currency": "USD",
      "status": "paid"
    }
  ]
}

Expected review output

{
  "synthetic": true,
  "draftFor": "INV-DEMO-01",
  "excluded": [
    {
      "id": "INV-DEMO-02",
      "reason": "paid"
    }
  ],
  "state": "awaiting_human_review",
  "sent": false
}

What to verify before deployment

• Paid and disputed invoices never enter the send queue.
• Every amount and invoice reference matches its source.
• The same invoice and reminder window cannot produce a duplicate send.
• Revoked source access stops future reads and actions.