← Back to Documentation

Bring Your Own Intuit App

Step-by-step setup for white-label consultancies and enterprise SMEs who want their own Intuit OAuth app connected to TrustBill.

Who this is for: White-label consultancies that want their own brand on the Intuit consent screen, or SMEs with a security policy requiring they own the OAuth app. For 95% of SMEs the recommended path is to just click Connect QuickBooks Online in TrustBill — it uses our shared Intuit app, no setup needed. The steps below are only for the bring-your-own case.

Cost: Intuit Developer account is free. No monthly fee for the app itself. The SME’s own QBO subscription ($30–$180/mo) is paid separately to Intuit regardless of TrustBill.

The 9 steps

  1. 1

    Sign up for an Intuit Developer account

    Free, takes 2 minutes. Use the same email the consultancy uses to operate — this account owns every OAuth app you create.

    Open Intuit Developer Dashboard →
  2. 2

    Create a new app

    In the dashboard: Create an app → QuickBooks Online and Payments → pick Accounting API scope. Name the app something your SMEs will recognise on the OAuth consent screen (e.g. "Paramount Enterprise E-Invoicing").

    Create a new app →
  3. 3

    Grab your Development keys

    In your app → Keys and credentials → switch to the Development tab. Copy the Client ID + Client Secret shown there. Development keys let you test against an Intuit sandbox company first — no production approval needed to try it out.

  4. 4

    Add the Redirect URI

    On the same Keys and credentials page (Development tab), scroll to Redirect URIs and paste this exact URL — character for character, no trailing slash:

    https://trustbill.ae/api/v1/sources/oauth/qbo/callback

    This is TrustBill’s shared callback endpoint — the same URL works for every bring-your-own app, no per-tenant variant needed.

  5. 5

    Set your Launch, Disconnect, and Connect URLs

    On your app’s Settings page, fill the three URL fields. Point them at YOUR TrustBill sign-in — for white-label consultancies, that’s your custom subdomain:

    Launch URL — where SMEs land when they click your app from inside QBO
    https://app.paramountenterprise.co/en/sme/sources
    Disconnect URL — where they land after disconnecting from QBO
    https://app.paramountenterprise.co/en/sme/sources
    Connect/Reconnect URL — reconnection entry point
    https://app.paramountenterprise.co/en/sme/sources

    TrustBill users without a white-label subdomain: use https://trustbill.ae/en/sme/sources for all three.

  6. 6

    Confirm the scope + IP settings

    • API scope → only com.intuit.quickbooks.accounting is needed. TrustBill reads invoices — no payments / payroll scope required.
    • API interaction → Reads data from Intuit only. No writes, no deletes.
    • IP address → pick "Hosted on serverless or managed platform" so you don’t have to pin an IP that changes on infra cutover.
  7. 7

    Paste your keys into TrustBill

    Go to TrustBill → Sources → find the QuickBooks Online card → click the three-dot menu → Configure. Paste the Client ID + Client Secret from step 3. Save. TrustBill encrypts the secret at rest and scopes it per tenant — your creds never leak across SMEs.

    Open TrustBill Sources →
  8. 8

    Test with an Intuit sandbox company

    Back in the Intuit Developer dashboard, create a Sandbox Company (Dashboard → Sandbox) — a free test QBO account. Then click Connect QuickBooks Online in TrustBill, authorise against the sandbox company, and sync a test invoice. If the invoice appears in TrustBill, the handshake is good.

    Open Intuit Sandbox manager →
  9. 9

    Submit for Production approval

    Development keys cap at ~5 connected companies — fine for testing, not for scaling. Once your sandbox flow works end-to-end, switch to the Production tab on your app’s Keys and credentials page and fill out the Production questionnaire (security, data handling, redirect URIs, etc.). Intuit reviews in 2–4 weeks. Once approved, you get Production Client ID + Client Secret → paste back into TrustBill’s Configure modal (step 7) → done.

    Intuit Production approval guide →

Common pitfalls

  • Redirect URI mismatch: if OAuth returns the "redirect_uri invalid" error, the URL you pasted in Intuit (step 4) doesn’t match character-for-character. Case, trailing slash, and protocol all matter.
  • Development vs Production keys: dev keys only authorise against sandbox companies via sandbox-quickbooks.api.intuit.com. If a sync returns 403, your keys and TrustBill’s API base are from different environments.
  • Scope missing: if OAuth consent silently fails, verify com.intuit.quickbooks.accounting is enabled in step 6.

Need help?

Email support@trustbill.ae or open a ticket from inside TrustBill. If you’re a white-label partner, include your subdomain in the ticket for faster routing.