Connector

Collect QuickBooks credit memos in AWS Redshift

Load QuickBooks credit memos, invoices and customers into your own AWS Redshift cluster with a custom OWOX connector. Credits land next to the same customer's invoices, so net revenue per customer is computed, not argued about.

QuickBooksConnectedA/P Aging Summar…A/R Aging Summar…AccountsBalance Sheet re…
Data MartPublishedone definition
AWS RedshiftRealmReportReportDaily 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 look at credit memos beside the invoices they reverse

Revenue in QuickBooks is invoiced minus credited, and the two live on different records. Seeing which customers get the most credit needs invoices and credit memos in one data warehouse, joined on the customer.

  • Net revenue is invoices minus credit memos, per customer
  • Credits can be set against refunds from the store
  • A rising credit rate is visible before the close
QuickBooksCredits, reversals
RefundsShopify refunds
SupportTickets
Your data warehouseAWS RedshiftQuickBooksRefundsSupportJoined by idInvoice issuedCredit memo raisedOne query nets credits against invoices per customer.

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.

  • Credit memos mirrors Invoices: customer, dates, amounts and lines
  • A custom connector: the credential and company id are yours
New Data MartChoose a sourceShopifyQuickBooksFacebook AdsAuthorizeConnectedEndpointCredit memosA/P Aging Summary…A/R Aging Summary…Accounts
Credit memos23 fieldstxn_datetotal_amtcustomer_namedoc_numbercurrency_id

S02 · Step 2

Step 2: Load QuickBooks into AWS Redshift

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 your own AWS Redshift cluster or workgroup. The location is pre-filled from your data storage, and you can change it.

  • Credit memos land in their own table in the Redshift schema
  • Every run is logged in Run History
DestinationAWS RedshiftSchemaquickbooksTablecredit_memoRun
Run HistoryPendingRunningSuccessIncremental load
Tablequickbooks.credit_memo

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. Key fields carry a plain description, and your data quality checks can read it.

  • Amounts stay in the transaction currency, with the exchange rate beside them
  • id and realm_id identify a credit memo
quickbooks.credit_memoOutput schemaFieldDescriptiontxn_dateBusiness date of the…total_amtTotal amount of the document…customer_nameName of the customer that…doc_numberDocument number shown on the…currency_idCurrency code of the document…

S04 · Step 4

Step 4: Keep the QuickBooks tables linked

Customers, invoices and credit memos stay separate tables, joined by customer_id. Together they give the net-revenue part of one QuickBooks data model.

  • Credit memos carry customer_id, as invoices do
  • Add store refunds to the same model
Customersiddisplay_name
Invoicescustomer_idtotal_amtbalance
Credit memoscustomer_idtotal_amt

S05 · Step 5

Step 5: Schedule the QuickBooks refresh and backfill history

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

  • Daily runs with no pipeline to maintain
  • Backfill credits for the periods under review
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 net revenue 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 AWS Redshift

A credit memo list from QuickBooks is a list. OWOX makes credits a table you can join, in your own AWS Redshift.

  • You own the data. It lands in your own data warehouse, in tables you control.
  • Credits tied to the customer. Credit memos and invoices share customer_id, so net revenue per customer is one query.
  • Built to extend. As a custom connector it can gain fields without a vendor roadmap.
  • 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