GoCardless + Querri
Querri reads GoCardless payments, mandates, payouts and refunds, so you can see which collections failed, when cash lands and how many mandates are still active.
Querri only reads from GoCardless and never changes your records. SOC 2 Type II, HIPAA and ISO 27001:2022 certified, and your data is never used to train a model.
What you can answer
GoCardless shows each failed payment, but spotting repeat failures across months takes an export and a pivot table. Querri groups failed payments by mandate, and a saved rule for what counts as a repeat failure keeps every answer consistent.
Facts & rulesPayouts carry arrival dates and deducted fees, but summarizing them for finance means checking the dashboard by hand. Querri lists upcoming payouts with amounts, fees and arrival dates and sends the summary on a schedule.
Reports & automationGoCardless knows what it paid out and NetSuite knows what was recorded, so reconciliation usually means two exports and a lookup formula. Connect NetSuite too and Querri lines up payouts and deposits by date and amount, then lists the gaps.
NetSuiteWhat comes over
Querri copies this data into your Library on a schedule, next to every other system you connect, so one question can draw on all of it.
Each sync reloads the data you picked, daily, weekly or monthly, or whenever you run it by hand.
Querri reads from GoCardless and never creates, edits or deletes anything there. Every answer runs on Querri's own copy.
Querri's own sharing and row-level access decide who sees which rows, in chat, dashboards, Claude, ChatGPT and the API.
How to connect
Say "connect GoCardless" or pick it from the connector catalog.
The secure form takes four entries: an access token, live or sandbox to match that token, the GoCardless API version date, and a start date for how far back records go.
Pick the data you want and how often it refreshes, then approve the first load.
The data lands in your Library, ready for chat, dashboards and scheduled reports.
FAQ
With an access token plus three settings: live or sandbox, the GoCardless API version date, and a start date. The environment has to match the token, since live tokens begin with live_ and sandbox tokens with sandbox_. Pick sandbox only for test data.
Payments, refunds, mandates and payouts. Payments include amount, charge date, status and amount refunded; mandates include scheme, status and next possible charge date; payouts include amount, arrival date and deducted fees. Records before your start date are left out.
As fresh as the last sync. Each sync reloads everything you selected, on a daily, weekly or monthly schedule or when you run it by hand, so a payment that failed this morning shows up after the next sync.
Not from this connector alone. Customers aren't one of the synced objects, so payments and mandates arrive with linked GoCardless IDs and your own references rather than names. Connect the billing system or CRM that holds your customers and Querri can join the two.
No. Querri only reads from GoCardless. It never creates, edits or deletes records there, and every answer runs on Querri's own copy of the data.
Yes. Querri is SOC 2 Type II, HIPAA and ISO 27001:2022 certified, credentials are stored encrypted, and your data is never used to train a model.
Keep exploring
Customers, transactions, items and accounting periods from NetSuite.
Invoices, payments, bills and the general ledger from QuickBooks Online.
Charges, subscriptions, invoices, refunds and payouts from Stripe.
Card transactions, expenses, budgets and vendors from Brex.
Connect GoCardless, add the rest of your systems, and get answers your whole team can check.