Your finance data,
one question away.
Kipper connects to NetSuite, QuickBooks, and Xero and turns them into instant answers. Your team asks in plain English and the numbers come straight from your system — read-only, permissioned, and exact.
NetSuite · real SQL, not RAG · answered in ~5s
See it live
Try it on real finance data.
Pick an interface and open the public demo — ask about invoices, AR, bills, or purchase orders, answered live from a sample finance dataset.
Total outstanding AR is $446,490 across 38 invoices.
NetSuite, read-only, answered in 3.8s
Supported systems
Connect the system your books already live in.
Link one system or several. Every answer reads from the same live, read-only connection — set up in under an hour.
Built for finance
Accurate by architecture. Governed by design.
Kipper is built so finance teams can trust the answer — and control who gets it.
Real SQL, not RAG
Kipper writes a SQL query against a real-time copy of your data and returns the actual figure — a fact, not an approximation or a document guess.
Read-only by architecture
Kipper reads your finance data to answer questions. It can never create, edit, or delete a single record in your accounting system.
Permissioned access
Admins define exactly what each person, team, or channel can see. It's enforced on every query — no matter how the question is phrased.
Full audit trail
Every question and answer is logged in the Kipper portal — complete visibility for compliance and oversight.
What you can ask
The questions your finance team fields all day.
Answers come back in about five seconds, from Slack, Teams, SMS, or AI tools — no finance login required for your team. See where you can ask →
Data coverage
What Kipper reads — and what it doesn't.
Knowing the boundary matters more than a long feature list. Kipper reads transaction-level records, which is what makes a lookup exact. It does not touch the ledger your finance team closes and reports from.
Records Kipper reads
The same records across NetSuite, QuickBooks, and Xero:
NetSuite exposes more than the accounting platforms do, so these are available there too:
Anything you can reach by looking up, filtering, or summing these records is a question Kipper can answer — including date-range comparisons of the same.
Outside what Kipper does
Kipper is not a general-ledger, journal-entry workflow, or bank-feed tool. That puts a clear set of questions out of scope:
- Ledger-level detail and workflows — journal-entry review, revenue recognition, account reconciliation.
- Bank feed detail and planning — individual bank transactions, reconciliation status, runway, burn rate. Bank account balances are answerable on QuickBooks only.
- Reporting and analysis — budgets, budget-versus-actual variance, financial ratios, board narratives.
- Finance workflows — closing the books, reconciling, auditing. These are processes your finance team runs in the finance system, not lookups.
When the data can't answer a question, Kipper says so rather than estimating.
Breaking answers down by team, location, or cost center
Every finance system has a grouping field for splitting transactions across parts of a business. Each one calls it something different, and Kipper can group answers by whatever values your finance team has already set up in it.
Kipper groups by fields that exist in your data. It won't invent a breakdown by industry or customer sector, because those aren't real fields in any of these systems.
FAQ
Finance system questions
What Kipper reads from NetSuite, QuickBooks, and Xero, how current it is, and where the boundaries sit.
Customers, invoices, payments, line items, vendors, bills, bill payments, inventory, credit notes, vendor credits, purchase orders, reports, and report lines — in all three systems, plus bank balances on a QuickBooks connection. NetSuite additionally exposes sales orders, quotes, quantity on hand, and bills of materials.
Anything you can reach by looking up, filtering, or summing those records is answerable. Kipper reads them and never writes: it cannot create, edit, or delete a record in your accounting system.
Kipper is not a general-ledger or journal-entry workflow tool, so ledger review, revenue recognition, and account reconciliation stay in your finance system. Returning a supported financial statement is fine; running the process behind it is not.
It also isn't an analytics platform. It won't build a budget, run budget-versus-actual variance, calculate financial ratios, or write a board narrative. Kipper answers direct questions about records; it doesn't perform analysis.
Kipper does not read bank feed transactions, imported bank statements, or reconciliation status in any connected system. It can return the supported financial statements everywhere, and on a QuickBooks connection it can also return bank account balances from the Balance Sheet.
Runway, burn rate, cash planning, and reconciliation remain out of scope because they require analysis, assumptions, or the bank-feed layer behind the report.
Yes, where your finance team already records it. Each system has a grouping field — Class in QuickBooks Online, Tracking Category in Xero, Class or Department in NetSuite — and Kipper can group answers by whatever values you've set up there.
Kipper groups by fields that exist in your data. It won't invent a breakdown by industry or customer sector, because those aren't real fields.
QuickBooks Online and Xero send live change notifications and are also polled every 15 minutes, so answers reflect your system within minutes of a change. QuickBooks Desktop has no live notifications — it's polled every 15 minutes and fully re-synced weekly.
A workspace admin connects each finance system once, using their own credentials. From then on, everyone else asks through Slack, Teams, SMS, or an AI assistant without needing a login to the finance system at all.
Put your finance data to work.
Connect NetSuite, QuickBooks, or Xero, set who sees what, and give your whole team exact answers — in minutes.