> Source: [/docs/resources/guides/corporate-treasury](https://tempo.xyz/developers/docs/resources/guides/corporate-treasury.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) / [Liquidity and issuance](https://tempo.xyz/developers/docs/resources/guides#liquidity-and-issuance) / Corporate treasury operations # Corporate treasury operations Stablecoin treasury operations connect intercompany funding and supplier payments to onchain settlement and finance records. Start with one flow, then define the entity that owns each account, who can authorize payments, and the evidence your finance system needs. ## Define the treasury operating model Stablecoin balances add another asset and account type to cash positioning. Keep them distinct from bank cash, provider balances, and investment positions. A consolidated view needs records from each system. | Decision | Record before the pilot | | --- | --- | | Account ownership | Legal entity, network, token contract, account address, and wallet or custodian. | | Payment authority | Who proposes, approves, and submits a payment; amount and destination limits. | | Asset selection | Issuer, token contract, redemption access, and provider support. | | Liquidity | Operating balance, fee funding, replenishment, withdrawal access, and payout dependencies. | | Reconciliation | Business reference, delivered transfer, internal ledger entry, and exception status. | | Recovery | How to stop new submissions and investigate unknown or failed payments. | Tempo's [account model](https://tempo.xyz/developers/docs/accounts/how-it-works) explains signers and delegated access keys; the [custodian and treasury setups](https://tempo.xyz/developers/docs/accounts/custodians) help you choose who holds them. Record legal entity ownership in your own records. ## Pilot an intercompany funding flow For example, a parent company can fund a subsidiary's approved account with a supported stablecoin. The receiving entity verifies the asset and amount before posting the intercompany movement. If it needs bank funds, conversion and bank delivery are additional stages. :::steps ### Establish the source and destination Record both entities, accounts, network, token contract, business purpose, and amount. Choose the token from the [stablecoin registry](https://tempo.xyz/developers/docs/partners/stablecoins) and check that the receiver and any conversion provider accept it. ### Apply approvals and signing bounds Keep the business approval record separate from submission. Use the selected account and custody model's controls. Where appropriate, give a backend its own [access key](https://tempo.xyz/developers/docs/accounts/access-keys) with amount limits, permitted calls, and expiry. ### Fund and submit the payment Check payment and fee balances, then follow [sending payments](https://tempo.xyz/developers/docs/guide/payments/send-a-payment). Save the transaction identifier against the treasury instruction before processing retries. ### Verify receipt and any bank delivery Use [receiving payments](https://tempo.xyz/developers/docs/guide/payments/accept-a-payment) to confirm the delivered token and amount. If a provider converts the funds or pays a bank account, require its completion evidence before marking that stage complete. ### Reconcile both entities' records Match the treasury instruction, approval, delivered transfer, and any provider record. Post each movement once in the appropriate entity ledger and investigate differences explicitly. ::: ## Connect transfers to the ERP or TMS Use an opaque [payment reference](https://tempo.xyz/developers/docs/guide/payments/transfer-memos) to connect a transfer to an instruction, invoice, or intercompany record. Store detailed accounting, entity, and counterparty data offchain. Preserve the network, transaction hash, and transfer log index as a unique event key. One transaction can contain several transfers. Your integration or a provider connector maps transfers to the general ledger and posts the entries. Reconcile onchain transfer records, wallet or custody statements, provider conversion records, and bank delivery where applicable. Read historical activity after reconnecting so a missed callback does not leave a payment unrecorded. See [payment reconciliation](https://tempo.xyz/developers/docs/resources/guides/payment-reconciliation). ## Keep usable liquidity visible Monitor the balances needed for payments and network fees, pending instructions, provider holds, conversion capacity, and the time needed to reach bank accounts. Tempo provides near-instant onchain settlement. Funding, redemption, conversion, and bank processing determine when funds are usable elsewhere. Test replenishment and out-of-hours operation on your provider route. Keep payment liquidity separate from investment allocation. If the organization uses earning products, track the position, withdrawal terms, and available withdrawal amount separately. ## Measure the treasury pilot Compare the same source and recipient outcome against the existing route. Record the full cost, delivery time for each stage, liquidity required, reconciliation completion, and unresolved exceptions. The network fee is only one part of that cost. Test insufficient funds, rejected destinations, receive-policy holds, expired or revoked keys, unknown submissions, and failed provider delivery. Verify that an interrupted job can resume without sending the instruction twice. ## Treasury operation questions ### Must the company custody stablecoins directly? Not for every model. A provider can supply agreed custody and settlement services. Document who holds the assets, who can authorize transfers, and which balances your entity can redeem or withdraw. ### Will an existing bank account support the flow? It depends on the bank and provider terms for the entity, currency, payment direction, and funding or payout method. ### Does an intercompany transfer need separate controls? Yes. Preserve the entity purpose, authority, accounting treatment, destination validation, and applicable requirements for the selected flow.