> This page is for Documentation, version Integration guides (default).
> For other versions, use one of these documentation indexes:
> - Integration guides (default): https://avalara.ferndocs.com/docs/integration-guides/llms.txt
> - Refactor guides: https://avalara.ferndocs.com/docs/refactor-guides/llms.txt
> - Get certified: https://avalara.ferndocs.com/docs/get-certified/llms.txt
> - Agent to Agent (A2A): https://avalara.ferndocs.com/docs/agent-to-agent-a2a/llms.txt
> - AI use cases: https://avalara.ferndocs.com/docs/ai-use-cases/llms.txt
> - API versioning: https://avalara.ferndocs.com/docs/api-versioning/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://avalara.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://avalara.ferndocs.com/_mcp/server.

# Design the transaction workflow

A typical beverage alcohol transaction involves creating a transaction and then verifying the shipment. This verification checks whether the shipment is compliant and adjusts volumetrics as necessary. The verification APIs must be called after a sales or return invoice transaction is created.

The image below summarizes the entire process, from transaction to compliance verification to shipping.

![](https://www.avalara.com/content/dam/assets/illustrations/diagrams/shipping_compliance_workflow_recommended.png)

[Previous](https://developer.avalara.com/avatax-for-bevalc/configure-your-account/test-your-setup)

[Next](https://developer.avalara.com/avatax-for-bevalc/typical-transaction-workflow/pos-workflow)

> **Note**
>
> Part of the **Beverage Alcohol** integration guide. [Open the full "Design the transaction workflow" milestone on Avalara](https://developer.avalara.com/avatax-for-bevalc/typical-transaction-workflow/) to see every page in this section.