Start with a worked register
The downloadable example shows a 100-USDC internal transfer between two same-network locations without counting new revenue. The editable inventory now includes six rows with token, network, location, quantity, assumed price and valuation date.
An asset register is a structured list of what the business holds and how each holding is identified. For a stablecoin treasury, the token ticker alone is not enough. Record the issuer or asset description, the network, the relevant token identifier and the account where it is held.
The register is an operating record, not a declaration that an asset is suitable or risk free. Its value is that someone reviewing a balance can tell which asset it represents and what evidence was used to identify it.
Use one row for each meaningful combination
Separate holdings when the asset, network or account differs. USDC on one network and USDC on another may serve different payment routes. A bridged representation may also differ from the issuer's native token. Circle maintains an official native-USDC network reference. Use the issuer's current materials when checking that identity.
Avoid copying token identifiers from a message or an unverified search result into the register. Record the official source and the date of the check. If the destination provider uses its own deposit instructions, keep a reference to those instructions as a separate piece of evidence. Issuer support and provider support answer different questions.
Record the purpose of the holding
Give each row an intended use, such as operating payments, a known supplier obligation or a reserve account. Identify the person responsible for the account and the approval process used to move funds. This makes it easier to see when a balance has drifted away from its original purpose.
Do not infer a target allocation from a convenient dashboard total. The right amount to hold depends on the business's obligations and approved policies. This site does not recommend a stablecoin allocation or provide an investment suitability assessment.
Keep access and exit conditions nearby
For each holding, describe the ordinary route for spending or converting it. Note whether that route depends on another service, a supported deposit network or account eligibility. Link to the relevant provider instructions and mark any unresolved condition clearly.
A useful register distinguishes what is confirmed from what is assumed. “Recipient accepts this token on this network” should have a source. “Likely works because the address looks the same” is an assumption that still needs verification. Do not erase that distinction to make a spreadsheet look complete.
Reconcile quantities before values
Begin by reconciling units: opening quantity, receipts, payments, conversions, fees and closing quantity. Then apply the valuation convention agreed with the person responsible for the books. A nominal one-dollar assumption can be useful for a planning example, but it is not a live price or an accounting policy.
Keep valuation adjustments separate from unexplained differences in token quantity. A price movement cannot explain a missing transaction, and a transfer between company accounts should not appear as new business income merely because it arrived at another address.
Maintain the register as the workflow changes
Review the record when an account is added, a payment route changes or a provider updates support. Remove obsolete routes from the approved workflow without deleting the historical evidence needed to understand past transactions. A current register should be compact enough to use before a payment and complete enough to support reconciliation afterward.
Reconcile an internal transfer without creating income
Assume a fictional opening position of 8,000 USDC in an operating wallet and zero in a reserve wallet, both on the same documented network. The business moves 1,500 USDC from operating to reserve. Ignore fees for this teaching example. A real register must record any fee in the asset actually used to pay it. The transfer changes location, not the total quantity owned.
Create two linked movement rows using a shared internal reference. The operating wallet records an outflow of 1,500. The reserve wallet records an inflow of 1,500. The closing positions are 6,500 and 1,500. Across both locations, the internal movement sums to zero. Recording the reserve inflow as a customer receipt would incorrectly add income to the operational report.
| Location | Opening USDC | Movement USDC | Closing USDC |
|---|---|---|---|
| Operating | 8,000 | −1,500 | 6,500 |
| Reserve | 0 | +1,500 | 1,500 |
| Combined | 8,000 | 0 | 8,000 |
The evidence table should retain the source position, destination position, transaction reference and business reason for the movement. If the move also changes networks or assets, this simplified same-network example no longer describes the full operation. Record each additional step and any conversion assumptions explicitly instead of forcing the result into one transfer row.
Next action: reconcile one real internal movement using approved private records outside this site. Check that both sides share a reference and that the consolidated report excludes the movement from external receipts. Leave any fee or timing difference open until supported by evidence.
Sources and context
Product facts are distinguished from original process guidance and hypothetical examples. Check the current terms for your route.
- Bancoli: pagos bancarios a stablecoins de autocustodia
- Bancoli: enviar USDC y elegir una red compatible
- Bancoli: USDT on Ethereum
- Safe: billetera de equipo, aprobaciones y registros
- Safe: opciones de comisión de gas y disponibilidad
- MetaMask: redes compatibles y cómo agregar una red
- Circle Mint: acceso institucional y flujos de trabajo
- Circle Mint: cadenas y monedas compatibles
- Circle: native USDC networks