Dynamo for Finance
Agents for Finance.
Your team builds agents that match invoices, reconcile accounts, explain variances, and check vendor changes. They run in your cloud, and a person signs anything above a limit you set.
Invoices matched overnight
A finance team at a global software companyCall reconciliation their biggest AI win
FloQast, 2026Runs on the systems finance already uses
Agents in Action
What Finance runs on Dynamo. Pick an agent, then click any node to see what it does.
Close the books on time. Agents match invoices to POs and bank lines in NetSuite, and flag the ones that don't add up.
What it costs today
Three jobs that still run on people and spreadsheets.
Forty to eighty accounts checked by hand every month
Bank, cards, payables, receivables, prepaids, accruals. Each one proven against outside evidence in a spreadsheet. Reconciliation is about a third of the month-end work, and half of finance teams take six or more business days to finish.
Velixo, 2025 (vendor); Ledge via CFO.com, 2025 (vendor)Every number that moved needs a written reason
The reasons are collected over Slack from budget owners and written up in the last days of the month. The same write-up goes to the CFO, the board, and the auditor. FP&A spends 45 percent of its time collecting the data before it explains anything.
Numeric, 2025; Forbes Finance Council, 2025; FP&A Trends, 2024A fifth of invoices need a person, and fraud arrives by email
22 percent of invoices fail the match and get chased by email, and one slow approver holds up the payment run. Payments are also where fraud lands: 79 percent of companies were hit in 2024, and over a third of attacks were fake bank-detail changes.
Ardent Partners, 2025; Ramp, 2025 (vendor); AFP, 2025By role
Pick a seat on the finance team.
What each person spends the month on, and the agent that takes it.
Month-end means forty to eighty reconciliations across three to five systems, about a third of the work.
Ledge, 2025; Velixo, 2025Every number that moved needs an explanation an auditor can follow, and the explanations arrive by Slack from budget owners.
Numeric, 2025; Forbes Finance Council, 2025The auditor's request list is 100 to 300 items across systems owned by four people, in the same weeks as quarter-end.
DataSnipper; Kranz Consulting, 2025
Reconciliation check
Four days after month-end, the agent checks every balance sheet account against the bank, the cards, and the subledgers. Accounts that match are filed. Accounts that don't go to the controller.
See it on the canvas →Build your finance agents on Dynamo
The platform underneath every agent on this page. Connect the systems once, describe the process in plain English, test it on last month, and run it in your cloud with a person signing where money is on the line.
Each system is connected with a scoped credential, and every finance agent inherits the connections. Security reviews the platform once instead of each vendor's agent separately.
The person who owns the process describes it. Where a step has to be exact, it is. Changes are diffs a reviewer can read, versioned like code.
Regression suites run on your own closed cases on every change, so you see matching accuracy and the over-flag rate before anything runs in production.
AWS, Azure, GCP, Kubernetes, or your own servers. Every run records what the agent read, decided, wrote, and cost. That record is what the auditor asks for.
Research · Benchmark
The monthly close, model versus model
Invoice matching, accrual drafting, and reconciliation checks, run model against model on a month of real finance data.
Questions finance teams ask.
Can an agent post to the general ledger?
Only where you say so. An agent gets the NetSuite permissions of the person who started it, and nothing more. In the reconciliation and variance agents, the agent drafts and the controller signs; no adjusting entry posts without a named approver. In invoice matching, a match inside your tolerance posts and anything outside it goes to a person. The approval points are part of the agent's definition, not a setting someone can forget.
What does the auditor see?
Every run records what the agent read, what it decided, what it wrote, and what it cost. That record is the support behind the reconciliation or the variance explanation, and it answers the PBC request for evidence that the control operated. Traces go to the observability stack IT already runs, over OpenTelemetry.
We already have AI in NetSuite and Ramp. What's different?
Those agents see one system each. Month-end runs across NetSuite, the bank, the spend platform, the checklist tool, and Slack. Dynamo connects each once, under scoped credentials, and every finance agent inherits the connections. Security reviews the platform once instead of each vendor's agent separately.
Is this a new in-scope system for SOX?
One system, reviewed once, instead of several. Changes to an agent are diffs a reviewer can read, promoted through dev, staging, and production with a check at each gate. Credentials are scoped per connection and access can be reviewed like any other system. It runs in your cloud, so your data stays where it lives.
How do we know it's accurate before it touches this month?
You test it on last month. Regression suites run on every change against your own closed cases, so you see matching accuracy and the over-flag rate before anything runs in production. Our monthly-close benchmark ranks the models on how often they guess where they should flag; each task runs on the one the evidence supports.