Yes. Krokul CRM integrates with Avalara AvaTax. Quotes and invoices get their sales tax from AvaTax, issued invoices are committed as AvaTax transactions, cancelled invoices are voided there, and exemption certificates of tax-exempt buyers are stored with the customer in AvaTax. The calls run through the Krokul app in Make, or through the Krokul API and webhooks.
Automation platformsMake
When a manager prepares a quote, Krokul sends its lines and the ship-to address to CreateTransaction as a SalesOrder, which AvaTax calculates without recording. The tax per line appears on the quote, so the client sees the full amount up front.
Issuing the invoice sends a SalesInvoice transaction with the same document code, and the connector commits it with CommitTransaction once it is final. The AvaTax transaction code stays on the Krokul invoice as its external key.
Cancelling an invoice in Krokul calls VoidTransaction for its AvaTax transaction. A change after commit goes through AdjustTransaction and a refund through RefundTransaction, so the AvaTax record matches the Krokul document.
When a client company is created or its address changes, the connector runs ResolveAddress. A normalised address is offered to the manager, and an address that AvaTax cannot resolve becomes a task before the first invoice.
For a tax-exempt buyer, the connector creates the AvaTax customer with CreateCustomers and attaches the exemption certificate with CreateCertificates. Later transactions for that client carry the stored customer code, and AvaTax applies the exemption.
| Avalara AvaTax | Direction | Krokul | When |
|---|---|---|---|
| Transaction (SalesOrder) | Krokul → AvaTax → Krokul | Quote (document) with tax per line | A quote is saved |
| Transaction (SalesInvoice, CommitTransaction) | Krokul → AvaTax → Krokul | Invoice (document) | An invoice is issued |
| VoidTransaction, AdjustTransaction, RefundTransaction | Krokul → AvaTax | Cancelled, changed or refunded invoice | The invoice changes after commit |
| Address (ResolveAddress) | Krokul → AvaTax → Krokul | Client company address | A client company is created or its address changes |
| Customer and certificate (CreateCustomers, CreateCertificates) | Krokul → AvaTax | Tax-exempt client company | An exemption certificate is added |
Yes. Krokul integrates with Avalara through the Krokul app in Make and through its API and webhooks. In Make, the Krokul app runs next to the Avalara AvaTax app.
No. Krokul asks AvaTax and stores the result on the document lines. Where you charge VAT at a fixed rate instead, Krokul uses the rate set on each line.
No. AvaTax answers requests, and the Avalara AvaTax app on Make has actions and searches only. Flows start from Krokul events or a schedule.
The flow calls VoidTransaction for the AvaTax transaction of that invoice, found through the external key that Krokul keeps on the invoice.
Tax returns, filing and remittance stay with Avalara. AvaTax answers calls and sends no events back, so every result reaches Krokul as the answer to a request the connector makes.
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.
Avalara and AvaTax are trademarks of Avalara, Inc. Krokul is not affiliated with Avalara.
