How the connection works
When you authorize, QuickBooks returns your company identifier (realmId) and OAuth 2.0 tokens, which Nectar stores as encrypted credentials. Nectar then creates each bill through the Accounting API Bill endpoint (/v3/company/{realmId}/bill). Each bill references the vendor (VendorRef) and posts one or more account-based expense lines (AccountBasedExpenseLineDetail) mapped to the correct expense account (AccountRef) from your GL coding rules, against your Accounts Payable account (APAccountRef).
Set up in Nectar
Open the ERP wizard
Go to Bill Pay > Destinations, click AP/ERP Integrations, and select QuickBooks Online.
Authorize QuickBooks
Sign in to your QuickBooks Online account and authorize Nectar to create bills on your behalf. Nectar captures your company
realmId and stores the OAuth 2.0 access and refresh tokens securely as encrypted destination credentials.Add a routing rule
Create a routing rule with Route to AP integration targeting your QuickBooks destination.
If QuickBooks Online is not yet available in your environment, contact [email protected] to request access or share requirements for your QuickBooks setup.
What gets delivered
When a bill is routed to QuickBooks Online, Nectar posts aBill object with the vendor reference, transaction and due dates, currency, and account-based expense lines coded to the expense accounts from your rules. Delivery status appears in the bill audit trail.
FAQ
Can I connect multiple QuickBooks companies?
Can I connect multiple QuickBooks companies?
Yes. Each QuickBooks company has its own
realmId, so create a separate destination for each company you authorize and point routing rules at the destination that matches the bills you want in that company.