Understanding API vs Native Apps: QuickBooks
Choosing between an API-only app and a native app to integrate QuickBooks with Salesforce? We break down the key differences to help you decide.
Gerhard Dohne
February 18, 2021
One of the biggest questions when deciding how to integrate QuickBooks with Salesforce is choosing between an API Only App and a Native App. The correct choice will depend on your business needs.
API Only Apps
An API-only app does not include any Salesforce objects, pages, or workflow. It isn’t installed into Salesforce but instead connects to it. The app moves data between Salesforce and QuickBooks while users continue working normally in Salesforce without seeing interface changes.
Some API-only apps can only create records, while others can update them as well.
Since API-only apps lack custom Salesforce objects, they typically connect to standard objects. An opportunity or quote syncs to a QuickBooks invoice, and an account connects to a QuickBooks customer. This familiarity benefits users already comfortable with these objects.
However, limitations exist. Creating a second invoice on the same opportunity or linking multiple QuickBooks contacts to one Salesforce account becomes problematic. Some organizations work around this by creating custom objects and writing custom mappings or scripts.
API-only apps can integrate with multiple systems beyond QuickBooks. When an opportunity closes, the app might create an invoice, trigger a MailChimp email, and log a note in Evernote or Basecamp simultaneously.
A significant challenge involves data accuracy responsibility. If data inconsistencies occur, the responsibility may fall on the client and their consultant rather than the app provider, particularly when custom scripts contain errors.
Native Apps
A native app like Breadwinner for QuickBooks installs directly from the AppExchange with pre-built Salesforce components including objects, tabs, pages, and workflows. Upon installation, minimal configuration may be required since everything arrives mapped and ready.
QuickBooks’ rigid structure allows native apps to replicate data accurately. Invoices always contain the same fields, as do line items. Apps like DBSync, QB Connect, and Commercient SYNC replicate QuickBooks invoices into Salesforce, though not necessarily credit memos, sales receipts, refund receipts, bills, purchase orders, payments, or line items.
Native apps living within Salesforce offer more configuration options and tighter data mapping than API-only applications. This comes at a cost: native apps typically connect only two systems – Salesforce and QuickBooks.
Many native apps guarantee data accuracy and completeness. Completeness means all QuickBooks invoices replicate to Salesforce. Accuracy means numbers are correct, typically within the hour of the last sync.
While native apps may replicate QuickBooks invoices similarly, other aspects differ significantly. User interface, onboarding experience, support levels, and data guarantee completeness vary considerably. Some require opportunity products; others require quotes.
Why choose Breadwinner?
- Lightning-fast Integration with minimal manual setup
- Native Salesforce integration with ERP and Financial Systems.
- Unified view of financial and operational data.
- Certified by Salesforce, and featured on AppExchange