PrivateHostLab editorial ·
At a glance
| Axis | An agency-paid crypto expense | A client-paid crypto expense |
|---|---|---|
| Approval record | The agency needs authority to incur and later recharge the expense. | The client needs a clear configuration and transfer record. |
| Network fee | The agency records the fee and its accounting treatment. | The client records the fee alongside its transfer evidence. |
| Payment evidence | Keep the local quote reference separate from reconciliation evidence. | Keep the same separation; the quote is not a receipt. |
| Handover | The agency must state what is transferred at contract end. | The client can retain the primary expense record while delegating operation. |
What changes the decision
- Who approves the period and receives the local payment record?
- Who bears network fees and reconciliation work?
- Who keeps evidence of the configuration and transfer?
Decision example
A client approves a six-month Studio configuration but asks its agency to make the transfer. The written record names the payer, client approver, selected asset/network and who receives payment-association updates.
The honest verdict
Choose the payer who can keep the approval and payment record connected; a local quote is not a receipt.
This page does not send invoices, detect transfers or decide any payment exception.
Neither column is a PrivateHostLab product claim beyond the VPS catalog shown on service facts.