> 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.

# Onboarding

Guide: Avalara Managed Returns API (EMEA)

Understand the end-to-end process to onboard VAT clients with the Avalara Managed Returns API, from creating client accounts to generating and retrieving return drafts.

A partner (Firm or marketplace) uses the Avalara Managed Returns API to onboard VAT clients, configure registrations and obligations, upload and validate data, generate drafts, and prepare filings.

![Onboarding workflow](https://knowledge-be.avalara.com/bundle/aot2888389596944_aot2888389596944/page/juc5076493051924.image?_LANG=enus)

The onboarding process includes the following steps:

1. Create client account and Company:
   * The partner operates as a Firm and creates a Client Account for each merchant.
   * A default Company is created under the Client Account to represent the legal entity for VAT filings.

2. Configure VAT registrations and filing setup:
   * For each Company, VAT registrations are established for relevant jurisdictions (for example, GB).
   * Filing configuration includes selecting regions and forms, and submitting a filing calendar that defines obligation types, frequencies, and effective dates.

3. Import transaction data:

   During onboarding and ongoing operations, transaction data is imported (for example, using `VatUploadData`) to support VAT return preparation across the configured Return periods.

4. Validate and review data:
   * Data ingestion runs validations and aggregations.
   * Invoice-level results are available using data preparation APIs (for example, `VatDataPrepResults`) so partners can surface detailed issues in their own UI before draft generation.

5. Generate and monitor return drafts:

   For each Return period, partners initiate draft generation (for example, `VatStartDraftGeneration`) and monitor progress (for example, `VatDraftGenerationStatus`) until all artifacts are ready.

6. Retrieve drafts and proceed to filing:

   Generated draft files (JSON e-filing payloads, PDF summaries, CSV reconciliation files) are retrieved (for example, `VatReturnDrafts`) and used for review, approval, and downstream filing and reconciliation workflows.

> **Note**
>
> Part of the **Managed Returns — EMEA** integration guide. [Open the full "Onboarding" milestone on Avalara](https://developer.avalara.com/products/returns/integration-guides/managed-returns-emea/hnw9333317521708/) to see every page in this section.