> ## Documentation Index > Fetch the complete documentation index at: https://docs.withacclaim.com/llms.txt > Use this file to discover all available pages before exploring further. # Implementation guide > Plan, configure, and launch Acclaim. Set up your account structure, workflows, and team before moving money in production. This guide walks through how to implement Acclaim in a production environment. It focuses on **planning, configuration, integration, and operational setup**, followed by validating the payment flows your team will use. *** ## Overview A successful implementation involves more than enabling payments. You will need to: * Define how funds should be structured and controlled * Configure your account and workflows * Integrate with your systems * Align internal teams and processes * Then test and go live Most teams follow a sequence of **plan → configure → integrate → test → go live**. *** ## Step 1: Define requirements Start by defining how you intend to use Acclaim. Consider: * What types of payments you will support (claims, vendor payments, collections) * Which countries and currencies are required * Whether funds are prefunded or collected before payout * How funds should be separated (by program, entity, or workflow) * What reporting and reconciliation requirements exist This step ensures your implementation matches your operational and financial model. *** ## Step 2: Design your account structure Define how funds will be organized in Treasury. * Create accounts based on your operating model * Separate funds by program, entity, or use case * Plan for multi-currency needs For example: * Loss funds for claims * Subscriber or participant funds * Operational or clearing accounts A well-designed account structure makes reconciliation and reporting significantly easier. **See also** * [Accounts](/guides/treasury/accounts) * [Balances](/guides/treasury/balances) *** ## Step 3: Configure access and internal workflows Set up your team and operational controls. * Add users and assign appropriate roles * Define approval workflows (if applicable) * Establish processes for reviewing and executing payments * Align responsibilities across operations, finance, and engineering This ensures your team can operate the system effectively. *** ## Step 4: Configure system settings Configure platform-level settings before enabling payment flows. * Add and verify [settlement accounts](/guides/treasury/withdraw-funds#settlement-accounts) * Configure [webhooks](/developers/webhooks) for event tracking * Configure [email sending settings](/guides/platform/email-sending) if you want to send from your own domain * Set up notification preferences * Review any limits or controls required for your workflows These settings support reliable and automated operations. *** ## Step 5: Configure payment flows Define how money will move through the platform. ### Collect (if receiving funds) * [Payment requests](/guides/collect/payment-requests) (hosted or embedded) * [Virtual accounts](/guides/collect/virtual-accounts) for bank transfers * [Setup requests](/guides/collect/setup-requests) for stored payment methods **See also** * [Payment methods](/guides/collect/payment-methods/index) * [Payment failures](/guides/collect/payment-failures) *** ### Disburse (if sending payouts) * Create and manage [payees](/guides/disburse/payees) * Configure [payout methods](/guides/disburse/payout-methods) * Define payout workflows (manual, [batch payouts](/guides/disburse/batch-payouts), or [payout links](/guides/disburse/payout-links)) *** ### Treasury * [Add funds](/guides/treasury/add-funds) or configure incoming funding flows * Set up [FX](/guides/treasury/fx) if operating across currencies * Validate balances and availability (see [Balances](/guides/treasury/balances)) *** ## Step 6: Integrate with your systems Connect Acclaim to your internal systems and workflows. You can choose the integration approach that fits your needs: * **API integration** — automate payment flows, data sync, and event handling * **File uploads** — support bulk operations using structured files ([File uploads](/guides/disburse/file-uploads/overview)) * **Console** — manage payments and operations manually in the [Acclaim Console](https://app.withacclaim.com) Many implementations use a combination of these approaches. Common integration patterns include: * Creating payment requests or payouts from internal systems * Syncing payment and payout status updates via webhooks * Exporting data for accounting and reconciliation * Automating batch workflows **See also** * [Developer guides](/developers/getting-started) * [Concepts](/developers/concepts) *** ## Step 7: Train your team Before going live, ensure your team understands how to operate the platform. * Train operations on payment workflows * Train finance on reconciliation and reporting * Align on how to handle [payment failures](/guides/collect/payment-failures), payout failures, refunds, and disputes Clear ownership and training reduce operational risk. *** ## Step 8: Test end-to-end workflows Validate your implementation in a controlled environment. * Test full payment flows (collect → treasury → disburse) * Verify balances and transactions * Confirm reconciliation and reporting outputs * Validate webhook delivery and automation **See also** * [Testing and going live](/guides/getting-started/testing-and-going-live) *** ## Step 9: Go live Move to production once testing is complete. * Switch to live API keys * Run initial transactions with small amounts * Monitor balances, transactions, and outcomes * Validate reconciliation against external systems Gradually increase volume as confidence builds. *** ## Key considerations * Design your account structure early. It impacts everything downstream. * Choose the right integration approach for your workflows. * Align internal teams before enabling payment flows. * Ensure settlement accounts and funding flows are configured correctly. * Plan for multi-currency and FX if applicable. * Use webhooks to automate workflows and reduce manual effort. *** ## Summary * Start with requirements and account design * Configure users, settings, and workflows * Integrate with your systems using API, files, or Console * Train your team and validate with testing * Go live in a controlled and monitored way A structured implementation ensures your payment operations are **reliable, scalable, and easy to manage**. *** ## Related resources * [Testing and going live](/guides/getting-started/testing-and-going-live) * [Key concepts](/guides/getting-started/key-concepts) * [Treasury](/guides/treasury/overview)