TLDR
GrantPipe's QuickBooks Online integration starts with read-only accounting ingestion. Admins connect QBO through Intuit OAuth, import accounts and accounting dimensions, review unmapped transactions, and map QBO truth into grants, funds, programs, contacts, budget lines, and accounts. GrantPipe does not write back to QuickBooks in this release.
Many nonprofits keep QuickBooks Online as the accounting system and still need grant, fund, and compliance context somewhere else. GrantPipe’s first QuickBooks release is built around that reality. It reads from QBO, brings source objects into GrantPipe, and gives staff a controlled mapping and review workflow.
It does not replace your QBO file. It does not post back to QuickBooks.
TL;DR
- OAuth 2.0 connection through Intuit
- Read-only import from QBO to GrantPipe
- Accounts, classes, customers, vendors, departments, purchases, deposits, and journal entries
- Mapping to GrantPipe grants, funds, programs, contacts, budget lines, and accounts
- Unmapped queue, conflict review, sync events, and QuickBooks source events
- No customer creation, invoice posting, payment posting, or journal write-back in this release
What the integration does
An Admin connects QuickBooks Online from Accounting -> Integrations. GrantPipe stores the QBO realm ID and encrypted tokens, then queues sync jobs in the background.
The sync imports accounting dimensions and transactions that staff can map into GrantPipe records. Imported external objects and sync events keep source-system metadata: QuickBooks, source object type, source object ID, synced timestamp, and status. That makes it easier to answer the audit question: “Where did this accounting source come from?”
GrantPipe treats QBO as the accounting source of truth. If a QBO object changes after someone has mapped or edited local context, GrantPipe flags the difference for review instead of overwriting the local value.
Setup at a glance
- Connect QuickBooks Online from Accounting -> Integrations.
- Set a sync start date and choose the QBO objects to ingest.
- Queue the first read-only sync.
- Map imported dimensions to GrantPipe grants, funds, programs, contacts, budget lines, and accounts.
- Review unmapped transactions and conflicts before using the data in reports.
Supported features
- Intuit OAuth 2.0 authorization
- Encrypted access and refresh token storage
- Read-only QBO import into GrantPipe
- Accounts, classes, customers, vendors, and departments
- Purchases, deposits, and journal entries
- Mapping workspace for GrantPipe records
- Unmapped queue and conflict resolution
- QuickBooks source events on imported external accounting objects
Limits
- GrantPipe does not write to QBO in this release.
- GrantPipe does not create QBO customers, invoices, payments, or journal entries.
- QuickBooks Desktop is not supported.
- Class and department coverage depends on the QBO plan and company settings.
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.
Looking for something else?
Q&A
Why start with read-only ingestion?
Accounting write-back has higher risk than read-only import. GrantPipe starts by ingesting QBO truth, mapping it into grant and fund context, and showing where the numbers came from. That is the safer first release for audit-facing workflows.
Q&A
What about QuickBooks Desktop?
GrantPipe does not integrate with QuickBooks Desktop. The MVP is QuickBooks Online only.
Q&A
How often does sync run?
Admins can queue a sync from Accounting -> Integrations. The sync runs as a background job so the browser request does not wait on the QBO API.
Q&A
What if my chart of accounts uses sub-accounts?
GrantPipe imports the QBO account objects it receives and keeps the source object ID with the imported record. Mapping decisions happen in GrantPipe and can be reviewed before reporting.
Frequently asked