HERE TO HELP
A clear next step.
Help with setup, account connections, donor matching, and reviewing your giving records.
Let’s look at it together.
Tell us your organization, what you were trying to do, and the exact error message. A screenshot with private details removed can help.
Please keep passwords, API secrets, access tokens, and unnecessary donor information out of your first message.
Connect the right church and company.
Open your authorized private workspace and choose Connections. Complete the relevant provider authorization and confirm the organization or company name before loading directories or scanning donations.
If an authorization expires or is interrupted, begin a fresh connection from Giving Bridge. For QuickBooks, live company access requires the matching production app settings. The app’s callback address must match the registered redirect URI exactly.
Next, choose the start date, payment methods, online-giving clearing account, fund-to-item mappings, and a dedicated Planning Center payment source for imported cash and check gifts. Review that payment source’s receipt-email settings with your church.
Open private workspaceKnow which records belong in the bridge.
| Source | Supported direction |
|---|---|
| Planning Center Giving | Eligible, successful native card and bank donations to gross QuickBooks sales receipts. |
| QuickBooks Online | Eligible cash/check donation sales receipts and supported received payments on donation invoices to Planning Center Giving. |
| Manual CSV workflow | Staged records and supported export/import workflows, with review and explicit completion steps. |
The current pilot supports U.S. organizations with USD books. It does not turn combined bank deposits into individual donor gifts, automatically post refunds or fees, reconcile processor payouts, or infer an ambiguous partial payment across several funds.
Confirm a person once, then reuse the match.
In Donor matches, review the Planning Center donor and QuickBooks customer. Compare the available details and confirm they represent the same person. Giving Bridge remembers the provider IDs, so their display names can differ.
A shared name, email, or household address alone may not establish identity. A single household customer representing multiple separately tracked donors needs a deliberate recordkeeping decision. Missing profiles remain for review; the bridge does not silently create or merge them.
Start small and verify the result.
A scan prepares records for review. It does not, by itself, post a donation. Begin with a narrow date range, confirm mappings, and check a small selection against the source before approving a transfer.
After posting, verify the destination record. If a submission is marked uncertain, reconcile it before retrying or manually entering the gift. An interrupted response can leave the app unsure whether a provider accepted the original request.
Automatic posting and scheduled scans begin paused. Activate them only after the intended workflow and its exceptions have been checked. Planning Center’s own payment-source settings may control receipt emails.
Access, disconnection, and data requests.
The current workspace is a private pilot. Signing into a provider does not, on its own, grant access to Giving Bridge’s private workspace.
Use the disconnect guide to stop an account connection. For workspace closure, exports, or deletion requests, contact support. Existing transfer history and mappings can remain after disconnection. Contact support for workspace closure or deletion, as described in the Privacy Policy.