Nance

Your BigQuery datasets, joined into your finance workflows

Orders, events and transactions live in BigQuery. The bookings live in your accounting system. Nance queries both sides and reconciles them, without anyone exporting a CSV to compare.

The pattern is familiar to anyone running finance next to a Google data stack. The answer to "did we invoice everything we shipped" lives in two places: an orders table in BigQuery and an invoice list in the accounting system. Comparing them means exporting both to CSV, matching in a spreadsheet and chasing the rows that do not line up. It works, it is slow, and it gets done less often than it should.

Nance does the comparison at the source. It queries your BigQuery datasets through a service account you control, checks event and order data against the administration, and reports the differences with the underlying records attached. Revenue completeness becomes a recurring check instead of an annual scramble, and finance reporting draws on the same governed data as everyone else. The spreadsheet step is simply gone.

What Nance automates with BigQuery

Reconciliation against the books

Nance joins BigQuery datasets into its reconciliation work, so the administration is checked against what your systems actually recorded.

Revenue completeness checks

Event and order data becomes the reference for what should have been invoiced. Orders that never made it into the books get flagged before the close does it for you.

Source detail on demand

When a booking or a question needs the underlying records, Nance queries the dataset directly instead of waiting for someone to pull an export.

Reporting from one source

Finance reporting draws on the same BigQuery data the rest of the company dashboards on, so finance and operations stop quoting different numbers.

Scheduled cross-checks

Recurring comparisons between datasets and ledger run on a schedule, so differences surface during the month rather than at month-end.

No more CSV shuttle

The export, download, paste, compare routine between BigQuery and the accounting system disappears. Nance reads both ends of it.

Connect BigQuery to Exact Online, Twinfield, Moneybird & Xero

Most BigQuery connectors are data pipes: they copy fields on a schedule and stop there. Nance is the connection and the colleague in one. It reads BigQuery, applies your rules and does the actual finance work in your accounting package, with approvals where you want them and every action logged.

Access and security

  • Scoped access that you grant per connection
  • Revocable at any time, without our help
  • Every action logged with its reasoning
  • GDPR-compliant, hosted in the EU
  • ISO 27001 certification in progress

Frequently asked questions

How does Nance connect to our BigQuery project?

Through a scoped, read-only connection by default: a dedicated service account you create and control, limited to the projects and datasets you choose. Write access only where you explicitly grant it.

Does Nance build or manage our pipelines?

No. Nance queries the datasets your team already maintains. It reads, reconciles and reports; data engineering stays where it belongs.

Our data is spread across many datasets. Is that a problem?

Nance works with whatever you expose to it. Most teams grant access to a few curated datasets or views for finance, which keeps queries fast and answers easy to verify.

Can we see what Nance queried?

Yes. Every query is logged with its context and result, and access is bounded by the service account permissions you set. Nothing happens outside what you granted.

More in Data & databases

See Nance in action.

In 30 minutes we walk through a live demo: a simple ad-hoc question, then a workflow you automate on the spot. Bring a real finance task.

GDPR-compliant · data stays in the EU
ISO 27001 in progress