FlowRunner for finance operations
Automate the invoicing, reconciliation, and close work that swallows your month, with an agent that runs the matching and the routine and a human who owns every payment, posting, and refund that touches the ledger or leaves the building.
The work that never gets easier
Your team lives in the gap between systems that should talk and do not. Orders land in the store but not in the ledger. Bills arrive as PDFs that someone keys into the ERP by hand. Bank deposits sit unmatched against invoices until a person opens two tabs and eyeballs the amounts. Month-end turns into a marathon of exports, pivots, and follow-up emails, and the close slips because one number would not tie out.
The systems are not the problem. You already run QuickBooks Online or NetSuite, a payment processor like Stripe, a store on Shopify, maybe Acumatica or Sage Intacct on the accounting side and BILL or Ramp for AP. The problem is the manual glue between them, the copy-paste, the re-keying, the second look. And the work that actually carries risk, releasing a payment, posting a journal entry, issuing a refund, is exactly the work you cannot hand to a script that does not know when to stop.
- Vendor bills arrive as PDFs that someone keys in by hand.
- Bank deposits sit unmatched against invoices for days.
- Store orders never make it cleanly into the ledger.
- Chargebacks pile up while the evidence window closes.
- Month-end close slips because one number will not tie out.
What you can automate
Each of these runs as a flow. The agent does the matching, the enrichment, and the routine data entry on its own. It stops and asks a human at the one point where money moves or a number hits the ledger. Every tool named here is a FlowRunner connector, built and verified against the vendor's official API.
- 01
Invoice validation and three-way match
Bills arrive matched and coded. The payment waits for an approver.
TriggerA vendor bill lands in BILL, or an invoice PDF hits the AP inbox.
AgentThe agent reads the invoice, pulls the matching purchase order and receipt from NetSuite or Acumatica, runs the three-way match on quantities and prices, flags variances, and codes the bill to the right GL account and cost center.
Human checkpointClean matches under your threshold it queues. When the amount is large, the variance is unresolved, or the vendor is new, it stops before scheduling payment and hands the fully-matched bill to an approver who sees the PO, the receipt, and the discrepancy.
ResultAP stops keying invoices and chasing POs by hand, and every payment that goes out has a named approver behind it in the record.
- 02
Bank and payment reconciliation
The match runs itself. The posting to the ledger waits for a human.
TriggerA payout settles in Stripe or PayPal, or a bank feed updates in Xero.
AgentThe agent pulls the settlement detail, matches each deposit against open invoices and processor fees, groups the batch, and drafts the reconciliation entries with fees split to the right account.
Human checkpointExact matches it stages. Anything that will not tie out, a short payment, an unexplained deposit, a fee that does not reconcile, stops for a controller before the journal entry posts to the ledger.
ResultReconciliation stops being a two-tab eyeball exercise, and no entry reaches the ledger without a person confirming the numbers tie.
- 03
Order-to-cash sync
Every store order lands in the ledger clean. The odd one out waits.
TriggerAn order is placed in Shopify, WooCommerce, or BigCommerce, or a subscription renews in Chargebee.
AgentThe agent creates the sales order or invoice in NetSuite or QuickBooks Online, maps SKUs to the right revenue accounts, applies tax and discounts, records the customer and payment, and reconciles the storefront payout against the deposit.
Human checkpointStandard orders flow straight through. When the tax treatment is ambiguous, the amount is unusually large, or the customer record does not resolve, it stops for accounting rather than booking revenue on a guess.
ResultStorefront revenue lands in the books the same day it is earned, mapped and taxed correctly, without a nightly export and a manual import.
- 04
Dispute and chargeback handling
The evidence assembles itself. The refund or the fight waits for a call.
TriggerA chargeback or dispute opens in Stripe, PayPal, or Paddle.
AgentThe agent gathers the order, the fulfillment and tracking from ShipBob or ShipStation, the customer history, and the original charge, assembles the evidence package, and drafts the response before the deadline.
Human checkpointSmall disputes it can resolve on policy. When the amount is above your threshold or the customer is worth keeping, it stops for a manager to decide: submit the evidence and fight, or issue the refund or credit memo and move on.
ResultDisputes stop expiring in the queue, and every refund or write-off above the line has a human decision and a timestamp attached.
- 05
Month-end close prep
The close package builds itself. The entries post on your sign-off.
TriggerThe scheduled close date arrives, or a controller kicks off the run.
AgentThe agent pulls balances and open items across NetSuite, Sage Intacct, or Acumatica, ties subledgers to the GL, reconciles the payment processors and bank feeds, flags unmatched items and accrual candidates, and compiles the close package with every variance called out.
Human checkpointIt proposes the accruals and adjusting entries and waits. A controller reviews the package, and only then does the agent post the journal entries, with every entry, its backup, and the approver written to the log.
ResultClose stops being a spreadsheet marathon, and the entries plus the sign-off come out audit-ready the first time.
The pattern that makes it safe to automate
Finance automation fails when a script moves money or posts a number that should not have gone through. FlowRunner's answer is the digital andon cord: the agent runs the line and pulls it the instant a step touches the ledger or the bank. It matches, codes, reconciles, and stages the routine work on its own. Scheduling a payment, posting a journal entry, issuing a refund or credit memo above a threshold, releasing a large purchase order, always stops and routes to the approver through the channel they already watch, with the invoice, the match, and the variance attached. And because every one of those decisions is captured with the approver and a timestamp, the record you hand an auditor already exists. That combination, a human on every consequential move and a complete trail behind it, is why finance teams trust it with the ledger and auditors accept what it produces.
The digital andon cord →What your team gets
Kill the manual re-keying
Invoices, orders, and payments move between your store, processor, and ledger without anyone copy-pasting a number or reconciling by eye.
Close faster, tie out cleaner
Subledgers, bank feeds, and processors are reconciled before close starts, so the package is ready and the entries post on a controller's sign-off.
A person behind every payment
Nothing gets scheduled, posted, or refunded on autopilot above your thresholds. The consequential move always has a named approver.
Automation that auditors accept
Every payment, posting, and refund carries the approver and the timestamp, so the audit trail is a byproduct of the work, not a scramble at year-end.
Disputes stop expiring
Chargeback evidence is assembled and filed before the deadline, and refunds above the line wait for a human call instead of a silent loss.
Runs on the stack you already have
The agent connects to your ERP, accounting system, processors, and stores, every connector verified against the vendor API, so there is no system it cannot reach.
Built for finance's requirements
The controls a controller and an auditor would demand of any automation touching the ledger are native to the platform, not add-ons.
Complete audit trail
Every payment, posting, and refund records the approver and the timestamp alongside the invoice and the match, exportable straight into an audit. The record an auditor asks for already exists.
RBAC and SSO/SAML
Role-based access to the platform itself, so approval authority maps to your segregation-of-duties policy, with SSO and SAML behind your identity provider.
Bring your own keys
Your model providers, your keys. Inference runs on credentials you control, and you pay the provider directly. Financial data never rides on someone else's account.
Self-hosted option
Deploy inside your own infrastructure so invoices, payment detail, and ledger data never leave your environment.
The complete finance and operations stack
ERP, accounting, payments, e-commerce, and logistics, from NetSuite, Acumatica, Sage Intacct, and QuickBooks Online to Stripe, BILL, Ramp, Shopify, and ShipBob. Every connector is built and verified against the vendor's official API, so an agent calls it the way the vendor's API actually allows.
Every connector verified against each vendor's official API.
Put your finance operations on autopilot, safely
$100 in credits. No card required. Every integration here is built and verified against the vendor's official API, with a human in the loop where it counts.