QuickBooks and Salesforce integration.
We connect Salesforce and QuickBooks Online, so an account becomes a customer, a closed deal becomes an invoice, and the payment shows up back in Salesforce.
Sales in one system, money in the other
Salesforce knows what was sold. QuickBooks knows what was invoiced and paid.
Without a connection, someone types the same customer and the same amounts into both.
What moves each way
Three things cross between the systems. Each one moves in one direction only.
Salesforce
Accounts and opportunities.
- Accounts become customers
- Closed deals become invoices
- Payments and invoice status come back
QuickBooks Online
Customers, invoices, payments.
Built on the QuickBooks Online API and its webhooks, with Salesforce Apex or a small service in between.
Decisions to make first
We start by tracing one real deal from Salesforce to a paid invoice.Tell us how you invoice today How a project runs
QuickBooks Online or Desktop?
They connect in different ways, so we ask early.
QuickBooks Online
Has an API and webhooks. This is what we build against.
QuickBooks Desktop
Needs a different approach. We scope it case by case.
Common questions
Do you work with QuickBooks Desktop?
It needs a different approach from QuickBooks Online, so we scope it case by case after looking at your version and how it’s hosted.
Can invoices be created automatically from Salesforce?
Yes, once we agree when: at closed-won, when a contract is signed, or by another rule you choose. The rule is written down before we build.
What happens when an invoice is edited or voided in QuickBooks?
We decide that before building. Our default is to send the change back to Salesforce so both show the same status, and nothing is deleted without a record of why.
Do we need a paid connector app?
Not necessarily. We can build the connection directly on the QuickBooks Online API. If an existing connector already fits, we’ll say so.