Connector

Collect QuickBooks bills in Snowflake

Load QuickBooks bills, bill payments and vendors into your own Snowflake account with a custom OWOX connector. The payables side of the books lands as tables, ready to join to purchasing, inventory and ad cost.

QuickBooksConnectedA/P Aging Summar…A/R Aging Summar…AccountsBalance Sheet re…
Data MartPublishedone definition
SnowflakeRealmReportReportDaily 09:00
Refreshed on a schedule. No exports, no copy-paste.

Get started free

Endpoints

QuickBooks Endpoints

Documentation

26 QuickBooks endpoints you can import. Each lands in its own table in your data warehouse.

S00 · Why

Why join QuickBooks payables with the rest of your costs

What you owe vendors sits in QuickBooks, what you spend on ads in the ad platforms and what you buy in your own systems. Asking what a product line really costs needs all of it in one data warehouse, joined on keys.

  • See what is owed to each vendor next to what was paid
  • Compare vendor bills with the spend that triggered them
  • Close payables from the same tables that feed reporting
QuickBooksBills, vendors
PurchasingOrders to vendors
Ad platformsSpend
Your data warehouseSnowflakeQuickBooksPurchasingAd spendJoined by idGoods orderedBill paidOne query shows how long cost takes to clear.

S01 · Step 1

Step 1: Connect QuickBooks and pick the fields

Create a Data Mart, choose QuickBooks as the data source and authorize QuickBooks Online with OAuth. Add the company (realm) id, open an endpoint and tick only the fields you need.

  • Bills carries vendor, dates, amounts, balance and the line array
  • A custom connector: the credential and company id are yours
New Data MartChoose a sourceShopifyQuickBooksFacebook AdsAuthorizeConnectedEndpointBillsA/P Aging Summary…A/R Aging Summary…Accounts
Bills25 fieldsvendor_nametxn_datedue_datebalancetotal_amtcurrency_id

S02 · Step 2

Step 2: Load QuickBooks into Snowflake

Each endpoint becomes its own table, and refresh settings are set in the Data Mart. Run it and the first load lands as a table in a schema of the database you choose in Snowflake. The location is pre-filled from your data storage, and you can change it.

  • Bills and bill payments each get their own table
  • Every run is logged in Run History
DestinationSnowflakeDatabaseSchemaquickbooksTablebillRun
Run HistoryPendingRunningSuccessIncremental load
Tablequickbooks.bill

S03 · Step 3

Step 3: Get a business-friendly QuickBooks output schema

After the first run you get the output schema: every field with its type and, for key fields, a plain description. Your data quality checks can read it too.

  • Bill lines stay as JSON and unnest in SQL by their detail type
  • txn_date separates the business date from the edit date
quickbooks.billOutput schemaFieldDescriptionvendor_nameName of the vendor that…txn_dateBusiness date of the…due_dateDate the bill is due for payment.balanceOpen amount still to be paid on…total_amtTotal amount of the document…currency_idCurrency code of the document…

S04 · Step 4

Step 4: Keep the QuickBooks tables linked

Vendors, bills and bill payments stay separate tables, joined by vendor_id. Together they become the payables part of one QuickBooks data model.

  • Bills carry vendor_id; bill payments carry it and name the bills they settle
  • Add purchasing and ad tables to the same model
Vendorsiddisplay_namebalance
Billsidvendor_idbalance
Bill paymentsvendor_idtotal_amtpay_type

S05 · Step 5

Step 5: Schedule the QuickBooks refresh and backfill history

Set it once. A daily scheduled refresh keeps the payables tables current, and a manual backfill loads earlier periods.

  • Daily runs with no pipeline to maintain
  • Backfill bills and payments the first time you connect
ScheduleRun on a scheduleDaily 09:00
BackfillRun backfill
Run HistoryDaily scheduleManual backfillDaily schedule

S06 · Step 6

Step 6: Reuse the same QuickBooks table everywhere

One table feeds your data model, spreadsheets, dashboards, AI assistants and scheduled insights in Slack or email.

  • Define open payables once
  • Every report reads the same table
QuickBooksData MartPublished
Your data model
Google Sheets
Data Studio dashboards
Claude, ChatGPT
Slack, email

Recent updates

Why OWOX

Why OWOX for QuickBooks in Snowflake

Vendor bills exported by hand go stale on the day they are made. OWOX keeps payables in Snowflake current and joined to what else you spend.

  • You own the data. It lands in your own data warehouse, in tables you control.
  • Owed and paid, side by side. Bills and bill payments are separate tables you join on vendor_id.
  • Room to grow. 26 endpoints are available, so payables can grow into the full books.
  • One place to fix. When QuickBooks's API changes, you publish one new connector version.

Book a callGet started free

Trust

The Data Partner You Can Trust

users

176K Source: Internal OWOX data as of 2026-10-02

Executives and data analysts across 20+ industries

G2 rating

4.9★2

“A trusted data analytics partner” — verified review

npm installs

165K3

In Open Source We Trust

Customers