Overdue invoice chase
Vendor-agnostic action workflow over an accounting capability pack (QuickBooks or Xero) and the mail outbox. Binds the accounting connection through canonical core.acct.* op-steps (invoice / customer search), so the same recipe runs against whichever accounting vendor you connected: the resolver dispatches each op to the bound vendor and projects its raw records to the canonical accounting fields (balance / due_date / customer_id / email). It finds invoices that are open and past due, resolves which customers are overdue and have an email on file, drafts one concise reminder per customer, and sends the approved batch through the mail-send kernel ingredient. The chase emails the customer about their outstanding balance; it never creates, voids, or pays anything (canonical accounting op-steps are read-only — money writes ride the explicit gated ingredient binding). Because mail-send is the irreversible send-class boundary, attended runs hold the send step at the preflight approval gate.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
acct
setting
=
tone
setting
=
concise_professional
send limit
setting
=
10
business context
setting
=
sender mail instance
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.