Skip to content

Integrations

Connected to the systems your finance team already runs.

Our agents work across your ERP, banking, spend, data, CRM, communication and document systems. They query them live and take only the actions your policies allow. ERP writes require approval; other outbound actions follow the controls you set for each agent.

An illustration of the product's Integrations page: the list of systems, and the dialog that connects NetSuite.

Every integration

The finance systems, data and documents our agents work across, by category.

  • NetSuite

    ERP & ledger

    Query records and saved searches, pull the trial balance and financial statements, and post journal entries a person approves.

  • SAP S/4HANA

    ERP & ledger

    Read the universal journal, G/L accounts, open items and financial statements, and post journal entries a person approves.

  • Business Central

    ERP & ledger

    Query any entity, pull financial reports and document lines, and post what a person approves.

  • QuickBooks

    ERP & ledger

    The ledger, with QuickBooks' own trial balance, P&L and aged payables.

  • Odoo

    ERP & ledger

    The general ledger, invoices, bills and payments, with bank statement lines and AR and AP aging.

  • Plaid

    Banking

    Accounts, live balances and dated transactions from your banks: the bank side of every reconciliation.

  • Ramp

    Spend & payables

    Card transactions and vendor bills, with the GL accounts Ramp codes them to.

  • Brex

    Spend & payables

    Expenses, card and cash transactions and statements, with their vendors and coding.

  • BILL

    Spend & payables

    Bills, vendors, payments and vendor credits, with an AP aging worked out from them.

  • Snowflake

    Data & warehouse

    Explore schemas and query the warehouse where your operational and finance data meet.

  • PostgreSQL

    Data & warehouse

    Query Postgres directly or through an SSH bastion, on a read-only session.

  • Oracle Database

    Data & warehouse

    Query an Oracle database directly or through an SSH bastion, on a read-only session.

  • Salesforce

    CRM

    Search and query accounts and opportunities, and create or update records.

  • Zoho CRM

    CRM

    Query and search every module, add notes, convert leads and update records.

  • Gmail

    Email & chat

    Search the inbox, read threads and retrieve supporting invoices, statements and other finance documents.

  • Outlook

    Email & chat

    Search the mailbox, read threads and retrieve supporting invoices, statements and other finance documents.

  • Slack

    Email & chat

    Read channels and threads, and post finance updates or review requests where your team already works.

  • SharePoint

    Documents & files

    Find and read the workbooks, reconciliations, contracts and policies your team keeps in SharePoint.

  • Google Drive

    Documents & files

    Find and read the spreadsheets, models, contracts and supporting documents your team keeps in Google Drive.

Don't see a system your finance team uses?

Tell us what it is and what our agents need to read or do there.

Request an integration

One workflow, many systems

Finance work rarely lives in one system. Neither do our agents.

A single task can require the ledger, bank activity, supporting documents, operating data and a review from someone on your team. Agents work across them as one process.

Illustration: one bank reconciliation, run across five systems. The Close Agent pulls 1010 Operating account's 2,491 ledger lines from NetSuite and 2,480 bank lines from Plaid, finds AWS's invoice in Gmail, matches 2,478 lines and finds AWS's $12,480 in the bank but not the ledger. Dana Ruiz, Controller, approves journal entry JE-4471, it is posted to NetSuite, and the close update goes to Slack.

Built for finance

Purpose-built finance connectors, not generic API wrappers.

Each connector exposes the finance data and actions our agents actually need, with permissions and write controls defined explicitly.

  • Live reads, not stale copies

    Agents query the source when a task needs it, so the work reflects the system as it stands now.

  • Writes are explicitly governed

    ERP writes require approval. Other outbound actions follow the policy configured for that agent.

  • Credentials stay outside the model

    Keys and tokens are held server-side and added only when a request is made. Agents never receive them.

    How credentials are protected
  • Databases remain read-only

    PostgreSQL and Oracle connections run directly or through an SSH bastion, on read-only sessions the database enforces.

See our agents work through a finance process that matters to your team.

Tell us where the work gets stuck. We’ll walk through how the agents could help.