How we handle GDPR data-subject requests on a deadline
Legal
The finance agent we run on Kortix — connected to Stripe, the close checklist and revenue ledger in Google Sheets, and Slack. Each month it walks the checklist, reconciles revenue against the ledger, flags anomalies and missing docs, and posts the open items — never touching a journal entry or closing the books itself.
Month-end close runs the same way every month and takes days anyway: walk a checklist of a few dozen items, reconcile revenue against the ledger, chase down whatever documentation is missing, and sanity-check the numbers against the trend before anyone signs off. None of it is hard. All of it is slow, and most of the time goes to confirming that the easy 90% is actually fine so the close team can focus on the 10% that isn't.
We run a close agent on Kortix that does that first pass every month. It reconciles our Stripe revenue against the ledger, works the rest of the checklist for missing docs, flags anything that looks off against prior months, and posts the open items to our finance Slack channel. It never writes a journal entry and it never marks a period closed — a human owns the close.
The close checklist itself isn't the bottleneck — it's re-confirming the same categories of thing every month: does recognized revenue tie out to what Stripe actually processed, does every line have the supporting document it's supposed to, and does anything look different enough from the last few months to need an explanation before the numbers go out. Each check is quick in isolation. Doing all of them, consistently, on top of everything else close week involves, is where the days go.
A reconciliation formula in the sheet catches the exact ties but not the near ones, and doesn't know what "looks anomalous" means without a person supplying that judgment fresh each time. So the checklist gets worked start to finish by hand, at the same cost, every single month, and it only happens as carefully as there's time for.
On Kortix, a monthly cron triggers a close agent after the period closes. Each run spawns its own isolated session — a cloud sandbox — with read access to Stripe revenue and to the close checklist and ledger tabs in a Google Sheet. It reconciles Stripe revenue against what the ledger recorded, works the rest of the checklist for missing supporting docs, compares this month's figures against the trailing months for anomalies, and posts a close-status summary with every open item to Slack. It assembles and flags; it never enters a journal line and never marks the close done.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the close checklist skill and the monthly trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a month-end close agent in this workspace.
Create the agent agents/month-end-close.md. Its job is to walk the close checklist, reconcile Stripe revenue against the ledger and post the open items. It may use the Stripe and Google Sheets connectors and post to Slack.
Create the skill skills/close-checklist/SKILL.md with these rules:
Add a cron trigger monthly-close to kortix.yaml. It runs the month-end-close agent on the 2nd of each month at 07:00 with the prompt "Load the close-checklist skill and run one complete month-end close pass."
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 your billing system, the sheet that holds your checklist and ledger, and Slack. Credentials are brokered server-side and never enter the agent's machine.
Reads the month's revenue to reconcile against the ledger.

Walks the close checklist and reads the ledger.
Posts the close summary and the open items.
Merge the change request, then start a session with the month-end-close agent and send this prompt. Compare its flags with your own close notes before you let the schedule take over.
Run one month-end close pass for last month.
The change request added this trigger to kortix.yaml. From now on the agent
runs on the 2nd of each month at 07: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: monthly-close name: Monthly close checklist run on: cron: "0 0 7 2 * *" run: agent: month-end-close prompt: Load the close-checklist skill and run one complete month-end close pass.The agent reads Stripe and the ledger, and writes only the checklist status and flag columns. It never writes a journal entry, never edits a ledger amount and never marks the period closed, even when every line ties out. The finance team works the open items and closes the books.
Each run ends with one close-status message in the channel. This is what a run looks like in the session:
Worked 23 checklist items and 19 are clean. 2 revenue lines are unreconciled, $1,240 in total, and 1 item is missing its bank statement. Marketing spend is up 22% against the trailing average with no note on the sheet.
Once it works, paste any of these into the same session.
For each checklist item that is missing a document, add its owner from the checklist tab to the Slack summary.
On the 15th of each month, run only the revenue reconciliation for the month to date and post any unreconciled lines to #finance-close.
For each anomaly, list the three ledger lines that contribute most to the swing in the Slack summary.
Touching a company's close process is a trust question first, so the access is scoped tightly and one direction only:
The days that used to go to confirming the easy 90% of the checklist now go to the handful of items the agent actually flagged. The close still runs on the same schedule whether or not anyone has gotten to it yet, and the open-items list is waiting in Slack when the finance team sits down to close the books.