Skip to main content
Finance requests are mostly approvals wearing a costume. Someone wants to spend money, and the work is establishing who says yes, in what order, and with what evidence attached. That is the part Ravenna is unusually good at.

What Finance owns in Ravenna

Purchase approvals

A request form with thresholds that pick the approval path for you.

Expenses and invoices

Vendor invoices and expense questions in one tracked place instead of an inbox.

Suggested shape

One workspace called Finance. Whether it should be private depends on your culture: purchase requests are usually fine in the open, and payroll or compensation questions are not. If you handle both, keep the workspace open and use private tickets for the sensitive ones, or split payroll questions into the People desk. Categories that pay off later in reporting: Purchase request, Expense, Invoice, Payroll, Vendor, Policy question. The two entry points that matter most are the Slack channel for spend requests and the channel’s inbound email address for vendors, who will never be in your Slack workspace.

Custom fields are what make Finance work

Every other department can get by with a description field. Finance cannot. Add these as workspace custom fields so they are usable in workflow conditions and analytics, not just as form text: A workflow can only branch on a field that exists. Adding Amount as a number field is what lets a request under 1,000 skip a round that a request over 50,000 does not.
Learn more about custom fields

The agent’s job here

Finance questions are heavily policy-shaped: what can I expense, what is the approval limit, when do we pay invoices, which card do I use. Those are answerable from documents, which means the agent can take them if the documents exist as text. What the agent should not do is give a spend decision. Put that in the custom prompt as a hard boundary and let the approval flow make the call.
Learn more in writing agent rules

Connecting your ERP

Ravenna has no native ERP integration. If you need to create a purchase order in NetSuite or check a budget in your accounting system, build it with Foundry, which generates a typed action against any REST API and exposes it to workflows and agents. Do this second. Get the approval flow correct with a human filing the PO first, then automate the filing.

Next

Purchase approvals

Thresholds, rounds, and budget owners.

Expenses and invoices

Get the AP inbox under control.
Last modified on September 17, 2026