# Design the transaction workflow FAQs

Source: https://developer.avalara.com/avatax-dm-combined-erp/sales-tax-badge/design-transaction-workflow/design-document-workflow-faqs/

# Design the transaction workflow FAQs

This section provides answers to common questions that users face when designing a transaction workflow.

How do I handle a posting process in the ERP system?

Refer to the [Document workflow with posting process](/avatax-dm-combined-erp/sales-tax-badge/design-transaction-workflow/erp-workflow-with-posting) section.

How do I handle quoting/estimates?

-   Calling the AvaTax service with a SalesOrder doc type will return a calculation/quote but will not record the transaction.
-   If you need to provide a quote, but the full address is not available, use the [DownloadTaxRatesByZipCode](https://developer.avalara.com/api-reference/avatax/rest/v2/methods/TaxContent/DownloadTaxRatesByZipCode/) endpoint and store that on the client side. After you have the full address information, you can leverage AvaTax to get the rooftop level tax calculation.

When do I call for tax?

When you call for tax depends on where you are in the workflow. As a best practice, do not call for tax every time an item is added or removed from the cart. Some implementations loop in an explict **Calculate Tax** button, or they incorporate the tax calculation in the Save function.

You can call AvaTax for tax calculation upon receiving shipping information.

[Previous](/avatax-dm-combined-erp/sales-tax-badge/design-transaction-workflow/ratio-of-determination-and-address-validation)

[Next](/avatax-dm-combined-erp/sales-tax-badge/transactions)