How we handle GDPR data-subject requests on a deadline
Legal
An accounts-receivable agent we run on Kortix — connected to Stripe, email, and the accounting ledger. It finds overdue invoices, sends the right reminder, logs every touch, and reconciles when payment lands.
Chasing overdue invoices is steady, repetitive work that still needs judgment. Most reminders are routine: an invoice is a few days late, a polite note goes out, the customer pays. But the timing, the tone, and the escalation depend on how late the balance is and how large it is, and some accounts are sensitive enough that no automated email should go out without a person looking first.
We run an accounts-receivable agent on Kortix that does this chasing on a daily schedule. This is how we collect on our own invoices, including the connections and guardrails involved.
Receivables slip because no one has time to work the list every day. An invoice goes a week late, then two, and the reminder that should have gone out on day one never does. The ones that need a firmer note get the same generic email as the ones that are barely late, and the sensitive accounts — a large balance, a disputed line, something heading to legal — get chased the same way as everything else.
The common fixes are incomplete. Stripe's built-in reminders send on a fixed cadence regardless of balance size or account context. A spreadsheet and a calendar reminder depend on someone actually working it. A generic automation sends the same email to everyone and has no way to hold the risky ones back.
On Kortix, a daily cron triggers an agent. Each morning it spawns an isolated session (a cloud sandbox) with scoped access to Stripe, our email, and the accounting ledger. It finds every invoice that's overdue or coming due soon, decides the right reminder for each based on how late and how large the balance is, sends it, logs the touch, and reconciles the invoice when payment lands. Anything sensitive stops at a human approval gate before it sends.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the invoice-math skill and the weekday trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up an overdue-invoice chaser agent in this workspace.
Create the agent agents/ar-chaser.md. Its job is to chase overdue Stripe invoices with email reminders and post a daily summary. It may use the Stripe and Slack connectors. It only reads Stripe.
Create the skill skills/invoice-math/SKILL.md with these rules:
Add a cron trigger daily-check to kortix.yaml. It runs the ar-chaser agent every weekday at 09:00 with the prompt "Review overdue and soon-due Stripe invoices with the invoice-math skill, send the right reminder for each, and post the summary to #finance."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect Stripe, the mailbox the reminders come from and Slack. Credentials are brokered server-side and never enter the agent's machine.
Reads overdue invoices and reconciles payments, read-only.

Sends the courtesy notice, reminders and final notice.
Posts the daily summary and the invoices held for a person.
Merge the change request, then start a session with the ar-chaser agent and send this prompt. Check the reminders it sent and the invoices it held before you let the schedule take over.
Run one invoice check on Stripe.
The change request added this trigger to kortix.yaml. From now on the agent
runs every weekday at 09:00, each run in a new session on its own cloud computer. To change the time, edit the cron line, or open
Triggers in the workspace.
triggers:- slug: daily-check name: Daily invoice check on: cron: "0 0 9 * * 1-5" run: agent: ar-chaser prompt: Review overdue and soon-due Stripe invoices with the invoice-math skill, send the right reminder for each, and post the summary to #finance.Routine reminders go out on their own. A balance over the threshold, a disputed invoice, or an account marked for collections or legal gets no email. The agent lists it in the summary with the reason, and a person decides the next step. The agent never issues a refund, changes a plan or edits an invoice.
Each run ends with one message in the channel. This is what a run looks like in the session:
Sent 9 reminders: 4 first reminders, 3 second reminders and 2 final notices. 3 invoices were paid since the last run and are off the list. 2 are held for you: one disputed invoice and one balance over the approval threshold.
Once it works, paste any of these into the same session.
When a customer replies with a payment date, log it and skip reminders for that invoice until the date passes.
Every Monday, post the open balance in each aging bucket to #finance, with the change since last week.
For each invoice that reaches a final notice, send its account owner a Slack DM with the balance and the days overdue.
The agent sends email on our behalf and touches invoice state, so the access is scoped and contained:
Overdue invoices now get the right reminder on the day they should, with each touch logged and each payment reconciled when it lands. Routine chases run on their own, the sensitive accounts wait for a person, and the receivables list no longer depends on someone finding time to work it.