Yes. Krokul CRM integrates with QuickBooks Online. Invoices issued in Krokul become QuickBooks invoices, and payments and voids recorded in QuickBooks return to the Krokul document and deal. The link runs through the Krokul app in Zapier, Make, n8n or Albato, or through the Krokul API and webhooks.
Automation platformsZapierMaken8nAlbato
A manager presses Send to QuickBooks on a Krokul invoice, or the connector sends it on its own once the invoice is issued. The connector first creates the Customer and any missing Item, then the Invoice with the same lines, tax codes and due date. The QuickBooks Invoice ID and DocNumber stay on the Krokul document.
QuickBooks sends Krokul a signed webhook when a Payment is created or changed. One Payment can settle several invoices, so Krokul records one payment fact per invoice it covers, each on the deal that invoice belongs to. When an invoice is covered in full, invoice.paid fires and the client company debt drops.
When the bookkeeper voids an Invoice in QuickBooks, the Krokul document shows it as voided. If payments were already recorded against it, Krokul marks the document as diverged and explains the difference in the sync journal, so nobody removes a payment by accident.
QuickBooks fixes the currency of a Customer after its first transaction. Krokul keeps one QuickBooks Customer for each pair of client company and currency, so a EUR invoice and a USD invoice for the same client both go through.
If a webhook never arrives, the connector asks QuickBooks for recent changes through Change Data Capture on a schedule and applies the Invoice and Payment updates it missed.
| QuickBooks Online | Direction | Krokul | When |
|---|---|---|---|
| Customer | Krokul → QuickBooks | Client company (one per currency) | Before the first invoice to that client |
| Item | Krokul → QuickBooks | Product or service | Before the first invoice line with that product |
| Invoice | Krokul → QuickBooks | Invoice (document) | Send to QuickBooks, or automatically when issued |
| Invoice balance and status | QuickBooks → Krokul | Paid amount and status on the document | The invoice is updated in QuickBooks |
| Voided or deleted Invoice | QuickBooks → Krokul | Voided document, or a divergence in the journal | The invoice is voided or deleted |
| Payment | QuickBooks → Krokul | Payment fact per invoice on the deal | A payment is created or changed |
| Merged Customer or Item | QuickBooks → Krokul | External key moves to the surviving record | Records are merged in QuickBooks |
Yes. Krokul integrates with QuickBooks Online through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks.
QuickBooks Online. Krokul sends the invoice with its lines, and QuickBooks calculates tax under its own settings. If the totals differ, Krokul keeps its lines, shows the QuickBooks total and balance on the document and records the difference in the journal.
In a custom flow, QuickBooks sends your endpoint a signed webhook when a Payment is created or changed, and your code records it in Krokul. Through the Krokul app, the delay follows the QuickBooks trigger on your platform. Krokul sends its own webhook as soon as an event happens.
An administrator connects QuickBooks and sets the mapping. After that, any user who can edit the deal of an invoice can send it, and everyone who sees the document sees its QuickBooks status.
No. The connector uses the QuickBooks Online Accounting API. QuickBooks Desktop is a separate product with its own integration model.
QuickBooks Online stays the book of record and owns the invoice total, the open balance and the ledger. Bills, expenses, bank feeds and reconciliation stay in QuickBooks, and Krokul keeps the sales work behind each invoice.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
QuickBooks and Intuit are trademarks of Intuit Inc. Krokul is not affiliated with Intuit.
