FINANCE

Daily Past-Due Invoice Aging Digest

Each morning, pulls all open and uncollectible Stripe invoices, buckets them by days-overdue, and emails finance a prioritized recovery worklist via Outlook.

CategoryFinance
Enginesim
Difficultybeginner
Triggerschedule
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekday-morning schedule
  • ActionFetch open and past-due invoices from StripeStripeStripe
  • LogicBucket invoices by aging band
  • ActionEnrich accounts from PostgresPostgreSQLPostgres
  • ActionPersist daily totals to PostgresPostgreSQLPostgres
  • OutputEmail aging digest via OutlookOutlook

What it does

This workflow gives the finance team a single daily snapshot of every dollar stuck in dunning. It aggregates open and past-due Stripe invoices, ages them into buckets, and delivers a ranked worklist so the team knows exactly which accounts to chase first.

When to use it

Use it when failed-payment recovery is ad hoc and nobody has a reliable view of total at-risk revenue. Ideal for a controller or AR analyst who wants one digest instead of living inside the Stripe dashboard.

How it works

  1. 1A scheduled trigger fires every weekday morning.
  2. 2The workflow queries Stripe for all invoices in `open`, `past_due`, and `uncollectible` states.
  3. 3A logic step buckets each invoice by age (1-7, 8-30, 31-60, 60+ days) and sorts by amount within each bucket.
  4. 4It enriches the top accounts with owner and plan data from Postgres.
  5. 5It writes the rolled-up totals back to a Postgres reporting table for trend tracking.
  6. 6It emails the formatted aging digest to the finance distribution list through Outlook.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect OutlookMail, calendar, contacts.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.