What is and isn't covered by Rutter's Intuit Bank Feeds integration?

Rutter's Intuit (QuickBooks Online) Bank Feeds integration handles the bank feed itself — but it does not power every QuickBooks flow that touches a bank account. Knowing the boundary helps you route issues to the right place during onboarding.

What Rutter's bank feeds integration covers

• Listing you as a bank feeds provider in QuickBooks.
• Pushing your bank feed accounts and transactions/statements into your end user's QuickBooks.
• Connection lifecycle for the bank feed (connect, status, disconnect).

What it does not cover

• Intuit's payroll and invoicing flows. Rutter does not power QuickBooks Payroll or invoicing. If your end user hits an error in those flows (for example, a bank-verification error while setting up payroll), that originates with Intuit.
• Bank-account eligibility/verification. Whether a bank account can be verified or used for a given QuickBooks flow is decided by Intuit. For example, Intuit may require a routing number to be RTP-enabled — Rutter does not control that check.

Where to take those issues

For payroll, invoicing, or bank-verification errors that originate on Intuit's side, open the "View error details (for Developers)" message in the Intuit UI and escalate to Intuit (via the Intuit Partner Technical Support form). Rutter can help escalate through our Intuit contacts where possible.

One more onboarding note

Rutter does not currently publish a language-specific SDK — you integrate directly against the REST API. This applies to all Rutter products, not just bank feeds.

If you are unsure whether an issue is on Rutter's side or Intuit's, reach out with the connection ID and request ID. 📄 How do I contact Rutter Support and what are your SLAs?