TLDR
GrantPipe connects to QuickBooks Online through Intuit's OAuth 2.0 authorization flow and keeps donors aligned with QBO customers, grants aligned with classes or projects, and donation posting aligned with your journal. Finance staff stop re-keying gifts; development staff stop guessing whether a pledge hit the books.
Mid-sized nonprofits almost always run QuickBooks Online as their general ledger. The painful part is everything that happens between a gift landing in the CRM and a reconciled journal entry in QBO. GrantPipe’s QuickBooks Online integration closes that gap with OAuth 2.0 authentication, donor-to-customer sync, and class or project dimension mapping for restricted funds and grants.
TL;DR
- OAuth 2.0 connection through Intuit Developer; no stored passwords
- Two-way donor-to-customer sync with a reconciliation wizard on first connect
- One-way financial posting (journal entries or invoices) to keep the GL authoritative
- Restricted fund to QBO class mapping; grant to QBO project mapping on Advanced
- Nightly sync with a finance-owner reconciliation email; real-time on the Growth plan
What the integration does
The integration authenticates through Intuit’s OAuth 2.0 flow. A GrantPipe admin clicks Connect in Settings, authorizes the GrantPipe app against a QBO company, and Intuit returns a realm ID and refresh token that GrantPipe stores encrypted. From there the integration runs a reconciliation pass that matches GrantPipe donors to QBO customers on name and email, flags ambiguous matches for review, and creates missing customer records.
Financial posting goes one way, from GrantPipe to QBO. That design keeps the general ledger authoritative and prevents the double-entry problems you get with two-way financial sync. For each fund, you pick a posting mode: journal entry for operating gifts and invoice-plus-payment for pledged commitments. Classes map to restricted funds so every journal line carries the fund dimension QBO needs for a FASB ASC 958 report.
Setup at a glance
- Connect via OAuth 2.0 from Settings → Integrations → QuickBooks Online
- Select the correct QBO company (the Intuit consent screen returns every company your user administers)
- Run the donor-to-customer reconciliation wizard and review flagged matches
- Map each restricted fund to a QBO class, and optionally each grant to a QBO project
- Pick a posting mode per fund (journal entry or invoice)
- Run a sandbox sync against a QBO sandbox company and confirm the journal report
- Enable nightly production sync and subscribe the finance owner to the reconciliation email
Supported features
- Intuit OAuth 2.0 authorization with automatic refresh-token rotation
- Donor-to-customer two-way sync with reconciliation UI
- Class mapping for restricted funds (QBO Plus and Advanced)
- Project mapping for grants (QBO Advanced recommended)
- Journal-entry posting and invoice-plus-payment posting modes
- Automatic retry on Intuit rate-limit responses
- Reconciliation email with total dollars posted, customer counts, and error list
Typical use cases
- Finance closes the month without re-keying a week of donations
- Development and finance agree on restricted fund balances because both systems read the same class dimension
- Pledged grants hit QBO as invoices so finance can age pledge receivables without a second spreadsheet
- The annual auditor follows a single reconciliation trail from GrantPipe gift to QBO journal line
Limits and known gotchas
- Class tracking requires QuickBooks Online Plus or Advanced. Simple Start and Essentials do not expose classes, which means restricted fund reporting falls back to account-only posting.
- QBO allows nested classes (Parent:Child). GrantPipe’s mapping table flattens to a single level and posts to the leaf class. If you rely on deeply nested class rollups, plan your mapping before turning on nightly sync.
- Pledge invoice timing is the most common reconciliation question. A pledge recorded in GrantPipe posts an invoice dated the day the pledge was made, not the day the gift lands. Finance will see an open receivable until payment is applied.
- QuickBooks Desktop is not supported. Intuit’s Desktop API is on a sunset path and GrantPipe does not plan to integrate with it. Desktop users can use GrantPipe’s CSV journal export as a bridge.
- Rate limits from Intuit apply per QBO company (around 500 requests per minute). During first-time historical backfill the integration paces itself, so expect a multi-hour backfill for organizations with more than two years of gift history.
Start a free trial
Free resource
Get the Nonprofit CRM Cost Calculator
A companion guide explaining total cost of ownership benchmarks for nonprofit CRMs — implementation, training, data migration, hidden costs, and how to interpret your calculator results. Delivered by email.
Source: Intuit Investor Relations, Q2 FY2025 shareholder letter
Q&A
Why journal entries instead of invoices by default?
Invoice-per-gift works for pledges with stated due dates but creates noise for one-time cash gifts. Journal-entry mode keeps the GL clean while still preserving restricted-fund class detail. You can switch modes per fund.
Q&A
What about QuickBooks Desktop?
GrantPipe does not integrate with QuickBooks Desktop. Intuit is sunsetting its Desktop API, and most mid-sized nonprofits have moved or are moving to QBO. Customers on Desktop can export CSV journal entries from GrantPipe.
Q&A
How often does sync run?
Nightly by default. Admins can also trigger a manual sync from Settings after a large import or batch gift entry. Individual donations sync within five minutes in real-time mode on the Growth plan.
Q&A
What if my chart of accounts uses sub-accounts?
The mapping table supports sub-accounts and will post to the leaf account you select. Parent-account rollups happen in QBO's reporting layer, not in the GrantPipe feed.
Frequently asked