Back to workflows
FinanceDraft and approveFreelancer

Freelance overdue invoice follow-up

Check payment status, prior promises, and tone before drafting the next reminder.

What this workflow does

Check payment status, prior promises, and tone before drafting the next reminder. It produces a source-linked draft, validates it against policy, and keeps publication or system updates behind an explicit approval.

What you gain

Late invoices get consistent follow-up without damaging the client relationship.

What the AI agent changes

How this worked before

Templates could merge known fields, but they could not understand source documents or adapt the draft to exceptions.

What the AI agent changes

The agent reads source material, drafts the right version for the case, cites evidence, and leaves the final send or write to a person.

Agent trigger

An invoice passes its due date without a matched payment.

Inputs

  • Process context: invoice, due date, payment feed, client history, and prior reminders
  • Approved policies, ownership, and exception rules

Agent flow

  1. 1

    Assemble the current source material, template, and policy version.

  2. 2

    Draft only claims that can be linked to allowed evidence.

  3. 3

    Prepare the next reminder, escalation level, and promised payment date and mark every unresolved exception.

  4. 4

    Publish or write back only the approved version.

Human decisions

After step 3

The accountable process owner approves the next reminder, escalation level, and promised payment date.

Outcome

  • Approved payment reminder and updated status
  • Evidence, exceptions, and audit trail

Guardrails

  • Never publish, send, or post without the named approval.
  • Keep templates, policies, and source timestamps visible to the reviewer.

Risks and mitigations

Unsupported claims can enter a customer-facing or regulated record.

Attach evidence to material claims and block approval when citations are missing.

Sources and evidence