> Source: [/docs/resources/guides/stablecoin-payroll-for-global-teams](https://tempo.xyz/developers/docs/resources/guides/stablecoin-payroll-for-global-teams.md) > Section: [Get Started](https://tempo.xyz/developers/get-started.md). Choose a starting point, send a test payment, get testnet funds, connect a coding agent, find the SDKs and CLI, and use the resource guides to plan payment workflows, liquidity, provider selection, and partner integrations. > [Documentation index](https://tempo.xyz/developers/llms.txt) · [Docs skill](https://tempo.xyz/developers/SKILL.md) > Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation. > If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.xyz/developers/llms.txt) and Markdown pages directly. [Guides](https://tempo.xyz/developers/docs/resources/guides) / [Payment workflows](https://tempo.xyz/developers/docs/resources/guides#payment-workflows) / Plan stablecoin payroll # Plan stablecoin payroll Stablecoin payroll connects approved compensation to a token transfer or provider-mediated local payout. Keep calculation, deductions, and approval in your payroll system, and enable the payment method only where the worker and compensation are eligible. Start with [Send payments](https://tempo.xyz/developers/docs/guide/payments/send-a-payment) and use [batch payouts](https://tempo.xyz/developers/docs/resources/guides/batch-payments) for an approved run. A production workflow needs worker onboarding, payment preferences, treasury funding, destination validation, error handling, reconciliation, and support. The network does not supply those business processes automatically. ## Separate payroll approval from payment execution The payroll system determines the worker, amount, pay period, classification, and approval status. Your application or provider funds and executes the approved payment. A worker can receive a supported stablecoin directly, or a payout provider can convert it to a supported local payment method. Define which route is available for each worker before offering it. Check permitted payment forms and currencies, any required consent, worker classification, supported assets, and local delivery requirements. An employee's preference for stablecoins does not by itself establish that the method meets applicable wage-payment rules. Keep withholding, reporting, and payroll records in the applicable process. For example, the [IRS digital-asset guidance](https://www.irs.gov/individuals/international-taxpayers/frequently-asked-questions-on-digital-asset-transactions) treats digital assets paid as employee remuneration as wages for U.S. federal employment tax purposes. Contractor payments have a separate treatment. Tax treatment does not establish whether the wage-payment method is permitted. ## Capture worker payment preferences | Record | What to store | | --- | --- | | Approved compensation | Payroll or invoice ID, pay period, entity, amount, and approval. | | Recipient preference | Stablecoin balance or local-currency payout and the agreed asset or currency. | | Destination | Verified network and token contract, wallet address, or provider beneficiary details. | | Delivery expectation | Required delivery date, provider estimate, and evidence of usable funds. | | Support | Exception owner, communication process, and verified procedure for changing payment instructions. | A dollar-denominated balance may fit a worker's preference, but it still involves issuer, custody, and conversion risks. Explain the actual withdrawal or spending options supplied by the product. Do not imply that a supported wallet guarantees local-currency access. ## Fund and schedule an authorized payroll run Set the balances needed for principal, network fees, provider charges, and any conversion. Funding too late can delay a run; funding early ties up liquidity. Measure both before selecting a funding cadence. Choose an atomic batch when the calls must succeed together. Choose [independent transactions](https://tempo.xyz/developers/docs/guide/payments/send-parallel-transactions) when a failure in one worker's transaction must not revert another worker's payment. A reverting call reverts an atomic batch. Each approach still requires verifying the delivered transfers; a receive-policy hold can occur without reverting the call. Your application or provider schedules and submits recurring runs. [Transaction validity windows](https://tempo.xyz/developers/docs/protocol/transactions#scheduled-transactions) constrain when a transaction can be included; they do not create a recurring job or guarantee execution. If you sponsor fees, monitor the sponsor's eligible fee-token balance and the applicable liquidity requirements. [Fee sponsorship](https://tempo.xyz/developers/docs/guide/payments/sponsor-user-fees) changes who pays network fees and does not remove the need to fund them. ## Reconcile each worker payment Attach an opaque [32-byte payment reference](https://tempo.xyz/developers/docs/guide/payments/transfer-memos) and map it to the offchain payroll record. Keep names, pay details, cost centers, and other sensitive information offchain. The memo is public transaction data on the public network. A batch shares a transaction hash, so use each transfer's log index to distinguish outcomes. Store the network, transaction hash, and transfer log index as a unique event key. Verify the recipient, token, amount, and successful delivered transfer before marking the obligation paid. For local-currency delivery, retain the provider payout ID and delivery evidence as well. Near-instant onchain settlement does not prove that a worker received a bank deposit. See [global payouts](https://tempo.xyz/developers/docs/resources/guides/global-payouts) for route evaluation and [payment reconciliation](https://tempo.xyz/developers/docs/resources/guides/payment-reconciliation) for finance records. ## Handle unresolved and incorrect payouts Keep an unresolved submission pending while inspecting its existing identifiers. Retrying a complete payroll run can pay workers twice. Test duplicate notifications, a blocked receipt, a wrong token, an outdated destination, a failed conversion, and a delayed provider payout before expanding. Record support ownership and the evidence needed to resolve each exception. Verify a refund or corrected destination independently. A direct onchain correction is a new payment, not an edit to the confirmed transfer. ## Evaluate the worker experience Compare the complete source amount, usable recipient amount, delivery time, prefunded balances, and support burden with the existing process. Stablecoin payroll succeeds when the worker can receive and use the promised funds and finance can reconcile the obligation once. If you need private balances, review the [Zones privacy model](https://tempo.xyz/developers/docs/zones/privacy) and current [preview capabilities](https://tempo.xyz/developers/docs/zones) separately. The current permissioned runtime disables general TIP-20 transfers; do not assume public-network payroll transfers are available inside a Zone. ## Stablecoin payroll questions ### Do workers have to receive stablecoins directly? No. A provider can convert the stablecoin leg into a supported local payment method. Verify the route, eligibility, price, and delivery evidence for each worker. ### Does the payment rail determine compensation treatment? No. Keep worker classification, wage rules, tax reporting, and recordkeeping in the applicable payroll process. Confirm the operating requirements for the jurisdictions involved before enabling the option. ### What infrastructure is required? Worker onboarding, preferences, approved obligations, funding, signing controls, destination validation, monitoring, reconciliation, and support. Decide which parts your application operates and which the provider supplies. ### How do references support payroll reconciliation? An opaque memo maps the transfer to an offchain payroll record. Combine it with verified delivery and a unique event key; a matching reference alone does not prove payment.