Data Sources¶
Kipper connects to your finance systems and maintains a real-time, read-only copy of your data on AWS servers in the United States. Every answer is generated by running a SQL query against this copy — not by searching documents or approximating from training data.
Supported systems¶
| System | What Kipper can answer |
|---|---|
| NetSuite | Revenue, invoices, customers, GL transactions, subsidiary breakdowns |
| QuickBooks Online | P&L, invoices, expenses, customers, bank transactions |
| Xero | Revenue, invoices, contacts, bills, bank reconciliation |
One finance system per workspace¶
Each workspace connects to a single finance system. If you need to switch systems, disconnect the existing one from the Data Sources page and then connect the new one.
Data freshness¶
Kipper polls each connected source every 15 minutes and also receives live change notifications via webhooks, so most updates are reflected within a few minutes of a change in your finance system. Check sync status in Data Sources in the sidebar.
Read-only by architecture¶
Kipper cannot write, update, or delete anything in your finance system. Data flows one direction only: from your system into Kipper's query layer. This is enforced at the architecture level, not just by configuration.
Data after account closure¶
If you close your Kipper account, your finance data is deleted within a reasonable period. Query logs are retained as required for security and audit purposes, then deleted or anonymised.