What to keep track of when clients pay you in stablecoins
Keep the payment agreement, invoice reference, token, network, amount, transaction reference and receiving record together. Record any transfer charge shown separately from the agreed amount. This creates a practical payment trail for reconciling work and receipts; the tax treatment, valuation method and retention period depend on the rules that apply to you.
By BullSwipe
The client says the invoice is paid. A transfer appears in your wallet. A month later, you need to remember which project it covered. A few details saved at the time can prevent a much longer search through messages and transaction histories.
Keep the agreement beside the receipt
Start with the document that explains why the payment was due. That might be an invoice, contract or written project agreement. Give it a reference you can also use in your payment notes.
Record what was agreed: a number of tokens or an amount stated in another currency, the chosen asset and network, and who would cover transfer costs. Keep later changes with the original agreement rather than relying on a memory of the conversation.
Record the transfer precisely
Use the actual details from the sending confirmation and receiving record. Do not record only “crypto payment” or treat USDT and USDC as interchangeable names.
| Detail | Why it helps |
|---|---|
| Invoice or project reference | Connects the transfer to the work. |
| Asset and network | Identifies what moved and where to look for the transfer. |
| Amount expected and amount received | Makes differences visible without guessing the cause. |
| Date, time and timezone | Helps reconcile records displayed in different timezones. |
| Transaction reference, where available | Identifies the on-chain transfer. |
| Receiving-service reference | Connects the transfer to the account's own record. |
| Separately displayed charges | Keeps a charge distinct from the payment amount. |
These are record-keeping suggestions, not a list of fields BullSwipe requires you to submit.
Distinguish receipt from later activity
If you subsequently convert funds, make a purchase or transfer crypto elsewhere, keep that record separately and link it back to the original receipt where useful. Combining everything into one note makes it harder to see which amount relates to which action.
For example, a receipt from a client and a later transfer to another wallet have different purposes. Your notes should identify both rather than describing the later movement as another client payment.
If you need to understand BullSwipe's balance model, read the wallet explanation. Its USD spending balance is a different concept from the token and network on the original payment record.
Treat payment records as private information
A blockchain transaction reference is not a password, but it can reveal transaction activity when shared. Store records securely and share only what the recipient needs for the specific task.
Do not put private keys, recovery phrases, passwords or authentication codes into an invoice folder or send them as payment evidence. If a support case requires a transaction reference, use the provider's verified support channel rather than posting your records publicly.
Leave accounting decisions to the applicable rules
A useful payment log does not determine the tax treatment of a receipt or a later transaction. Ask a qualified adviser which valuation source, currency, supporting documents and retention period apply to your situation. Do not assume the token name or its dollar reference settles those questions.
For problems with a BullSwipe transfer, the deposit and withdrawal guides explain the details that help support investigate. Keep your own records complete, then share the relevant part through the proper channel.