Finance room · How we run Kylon
Pay $233K of vendor bills a month without hiring an AP clerk.
In October our agent paid $233K to vendors, up from $2.6K in July. Invoices come in a thread, an agent checks and dedupes them, and anything that needs a person waits for one tap in chat.
How it runs
One invoice, from thread to paid.
Five steps. Two people and two agents. Nothing leaves the bank until the right people approve it.
- 01
Submit an invoice
Drop an invoice into the Finance room to start a payment request.
Anyone on the team - 02
Check the details
The Accounting Agent checks the invoice and payee details, flags possible duplicates, and prepares the approval request.
Accounting Agent
- 03
Get approval
Below your threshold, one person approves. At or above it, two people approve.

Approvers - 04
Pay through your bank
The Payment Agent submits the approved payment through your connected bank. Changes to the payee or amount require new approval.
Payment Agent - 05
Track and record
Payment status and bank receipts update in the thread and payment tracker. Your spending dashboard updates automatically.
Automation
PersonAgentAutomation
Who decides
Your rules, held at every step.
One approver taps once
Below your limit, one of the approvers you name approves each payment.
Two people sign
Both approve in the thread. The bank can ask for its own approval before money moves.
No payment without a person
Every payment needs a human approval, with no exceptions and no automatic payments. The Payment Agent never sends anything without a recorded approval, and the Accounting Agent has no bank access. Approvals are also enforced in your bank, not only in chat.
Our own books
Vendor payments our agent made, by month.
Connections
Bring the bank you already use.
Pick your bank to start. The rest you choose during setup, and each agent only gets the access its job needs.
AirwallexAirwallex is added during setup as an API service, with your client ID and an API key.
Mercury
Ramp
Brex
02 · Company cards
Checked for duplicates
Before every payment goes out.
03 · Inbox
Where invoices arrive
Forwarded into the finance thread.
04 · Files
Where receipts are kept
Every invoice filed by month.
What you get
The template, ready in your workspace.
One click sets up the same room we run, with your tools and your approval limit.
Room
Finance
A private room for requesters and approvers. The approval limit and who signs are written into its rules.
Agent
Accounting Agent
Collects invoices in threads, checks the invoice and payee details, flags possible duplicates and prepares the approval request. No bank access.
Agent
Payment Agent
Submits approved payments through your connected bank. Changes to the payee or amount require new approval.
App
Vendor Payments
The ledger: every request with amount, approvers, status and the bank's receipt.
Automation
Receipts and reminders
Bank receipts update the ledger and the thread. Every Monday, a list of what is waiting.
Rules
Your approval limit
One approver under the limit, two at or above it. An agent can never approve its own request.
App
Finance Dashboard
Reads from the ledger: paid by month as a chart, what is waiting for approval, top payees and duplicates caught.
Set it up
Set up your finance room.
Set up our vendor payments in this Room. Take it one step at a time and wait for my OK before you move on. 1. Ask which bank we pay vendors from (Airwallex, Mercury, Ramp, Brex or another bank with an API) and connect it first. Airwallex isn't in the connection list yet: if we use it, help me add it as an API service with our client ID and an API key from Airwallex's developer settings, and suggest a key that can only create beneficiaries and transfers. Then ask which company cards we use (Ramp, Brex or Airwallex cards), where invoices arrive (Gmail, Outlook or Slack) and where we keep receipts (Google Drive, Dropbox or OneDrive), and connect those. Tell me which ones still need connecting. Whenever the bank offers one, use a scoped key that can only do what this job needs, never a full-access admin key. 2. Required before any payment: help me turn on approval in the bank itself for payments made through the API, with an amount limit, then wait until I confirm it to you, for example with a screenshot. For the bank we use: In Airwallex, set a transfer approval policy that also covers transfers created through the API. In Mercury, use a request-only API key so the agent can only request payments and a person approves them in Mercury. In Ramp, create bills through the draft path so your approval rules apply to them. In Brex, set payment approval policies. For another bank, find its approval setting for API payments. Don't run any payment, not even the $1 test, until I have confirmed this. 3. Every payment also needs a human approval in this Room, with no exceptions and no automatic payments. Ask me for our approval limit and who approves: below the limit one approver, at or above it two approvers. Copy these rules into this Room's guideline. 4. Set up two agents. An Accounting Agent collects invoices in threads, checks the invoice and payee details, flags possible duplicates in the bank and on company cards, and prepares the approval request. It has no access to the bank. A Payment Agent holds the bank connection and never sends anything without a recorded approval; if the payee or amount changed, it needs a new approval. 5. A question or complaint, such as "why didn't you pay?", is never an approval. After a payment is declined or held, pay it only after a new explicit approval card, and first check the bank for a payment already made by hand to the same payee for the same period, so nothing is paid twice. Copy this rule into the guideline too. 6. Build a Vendor Payments App with one record per request: payee, amount, currency, invoice, approvers, status and the bank's receipt. 7. Build a Finance Dashboard App that reads from the Vendor Payments ledger: paid by month as a chart, what is waiting for approval, top payees, and duplicates caught before payment. 8. Once the bank approval in step 2 is confirmed, run a $1 test that does not move money: draft a request to a test payee, post the approval card, and show me what the Payment Agent would submit. Nothing goes to the bank. 9. After the test, offer an Automation that writes each bank receipt back to the ledger and the request's thread, and every Monday lists what is waiting for approval. Start with step 1.
Questions
Which banks does it work with?
Mercury, Ramp and Brex connect from Kylon's connection list. Airwallex is added as an API service with your client ID and an API key. Any bank with a payments API can be added the same way.
Can a payment go out without a person approving it?
No. Every payment needs a human approval, with no exceptions and no automatic payments. Below your limit one person approves; at or above it, two people approve. The Payment Agent never sends anything without a recorded approval. Approvals are also enforced in your bank, not only in chat: setup turns on the bank's own approval for API payments before any payment runs.
What if it pays twice?
Before each payment the agent looks for the same payee and amount in the bank and on company cards, and each transfer is sent with a key that makes a retry safe.
Do I have to move money to try it?
No. Setup ends with a $1 test that drafts a request, posts the approval card and shows what would be sent, without contacting the bank.
Your vendors paid. Your rules kept.
Every payment waits for a person. Everything else, the agents do.