How we handle GDPR data-subject requests on a deadline
Legal
The accounts payable agent we run on Kortix — connected to Gmail, Google Sheets, and Slack. Every 15 minutes it pulls new invoices from the inbox, extracts vendor, amount, and line items, matches them against POs and the ledger, and routes anything clean or flagged to Slack for approval — never scheduling or marking a payment itself.

Vendor invoices arrive by email all day, on no schedule anyone controls, and each one needs the same handling: open the attachment, read off the vendor and the amount and the line items, check it against the purchase order, check it isn't a duplicate of something already in the ledger, and check the price is what was agreed. Done by hand, that's five minutes of careful reading per invoice, and the five minutes is where duplicates and overcharges slip through — not because anyone is careless, but because checking against every prior invoice and every open PO doesn't scale to a person's afternoon.
We run an accounts-payable agent on Kortix that checks the inbox every 15 minutes, extracts every new invoice, matches it against POs and the AP ledger, and posts it to Slack for approval — flagged if it's a duplicate, an overcharge, or missing a PO. It records; it never pays.
An invoice by itself is just a number. Whether it's right depends on comparing it against things that live elsewhere: the PO that authorized the purchase, the price that was agreed, and every invoice from that vendor already in the ledger. A person doing this by hand checks the easy cases — is there a PO, is the total plausible — and the checks that actually catch problems, like a vendor resending last month's invoice or padding a line item by a few percent, get skipped when the inbox is long and the afternoon is short.
The common shortcuts don't fix this. Paying on receipt catches nothing. A monthly batch review catches duplicates and overcharges after the fact, sometimes after the payment has already gone out. Neither one checks every invoice against every PO and every prior invoice at the moment it arrives.
On Kortix, a cron fires every 15 minutes. Each firing spawns a fresh agent session — a cloud sandbox with no memory of the last run, because the AP ledger in Google Sheets is the record. The agent checks a Gmail label for new invoice emails, extracts the vendor, amount, and line items from each attachment, matches it against the known POs and prior invoices tracked in the sheet, flags anything that's a duplicate, an overcharge, or missing a PO, and records every invoice in the ledger. It then posts the batch to Slack for a person to approve. It never schedules a payment or marks anything paid.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the ap-invoice-match skill and the 15-minute trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up an accounts payable invoice agent in this workspace.
Create the agent agents/ap-invoice-processing.md. Its job is to record and match new vendor invoices. It may use the Gmail, Google Sheets and Slack connectors.
Create the skill skills/ap-invoice-match/SKILL.md with these rules:
Add a cron trigger invoice-intake to kortix.yaml. It runs the ap-invoice-processing agent every 15 minutes with the prompt "Load the ap-invoice-match skill and process new vendor invoices under the Invoices label in Gmail."
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 the inbox that receives invoices, the sheet that holds your AP ledger and Slack. Credentials are brokered server-side and never enter the agent's machine.

Reads new vendor invoices filed under the invoice label.

Matches invoices against POs and records each one to the ledger.
Posts duplicates, overcharges and missing POs for a decision.
Merge the change request, then start a session with the ap-invoice-processing agent and send this prompt. Check the new ledger rows before you let the schedule take over.
Process new vendor invoices under the Invoices label in Gmail.
The change request added this trigger to kortix.yaml. From now on the agent
runs every 15 minutes, each run in a new session on its own cloud computer.
To change the interval, edit the cron line, or open Triggers in the workspace.
triggers:- slug: invoice-intake name: Invoice intake on: cron: "0 */15 * * * *" run: agent: ap-invoice-processing prompt: Load the ap-invoice-match skill and process new vendor invoices under the Invoices label in Gmail.The agent writes only ledger rows and the Slack post. It has no tool that schedules a payment or marks an invoice as paid. A person approves every invoice for payment through the normal AP process, including a clean match.
Each run that finds new invoices ends with one message in the channel. This is what a run looks like in the session:
Recorded 5 new invoices: 3 clean and 2 flagged. One is a duplicate of an invoice recorded 9 days earlier, and one bills a line item 8% over its PO price. All 5 wait in #ap-approvals for a person to approve.
Once it works, paste any of these into the same session.
For each invoice flagged missing PO, draft a reply to the vendor that asks for the PO number, and hold it for me to send.
Every Friday, post the week totals by vendor and by flag to #ap-approvals.
Each morning, list the recorded invoices that fall due in the next 5 days, so a person can schedule them in time.
Accounts payable is where a mistake costs real money, so the agent's access is scoped to match:
The five careful minutes an invoice used to wait for now happen automatically, every 15 minutes, against the full history in the ledger rather than whatever a person remembers. What used to reach the payment step unchecked now arrives flagged, with the PO and the prior invoice it conflicts with already attached — and the decision to pay stays exactly where it was: with a person.