Name an owner and a place for the record
Choose who maintains the project’s payment record and who can access it when that person is away. The billing contact, wallet operator and application operator may be different people. Link the record to the client’s project identifier and approval record so a later reviewer can understand why the purchase was made.
Use a controlled project workspace with access appropriate to its contents. Do not store wallet seeds, spending keys, passwords or full client datasets alongside a hosting budget. A record can point to approved evidence held elsewhere rather than copying every document into one shared folder.
Capture the approved USD budget
Record the base plan and every selected recurring option before applying the period discount. Keep external purchases and your team’s work separate. This lets the client see whether a change came from more resources, a longer prepaid period or an unrelated service.
The current PrivateHostLab catalog prices in USD. Its monthly reference is useful for comparing configurations, but the amount requested is the discounted total for the selected period. Do not describe that full-period payment as a monthly debit. The budget guide contains a generated configuration example.
Scroll horizontally for all table columns.
| Field | Record | Purpose |
|---|---|---|
| Project and approver | Internal project ID; approval reference; date with timezone | Connect spending to the agreed brief |
| Configuration | Plan, resources, image, server location and selected options | Identify exactly what was reviewed |
| Monthly reference | USD amount before the period discount | Compare the resource budget |
| Prepaid period | Number of months, discount and full-period USD total | Separate commitment from monthly reference |
| External costs | Network fee; domain, licenses or other separate purchases | Avoid treating these as included VPS charges |
| Renewal decision | Owner, review date and terms still to confirm | Keep continuity planning visible |
Preserve the quote as a quote
Confirm the project contact email before payment instructions are shown. It is a contact detail, not a verified account. Correcting only the email keeps the displayed payment reference, amount, rate and original expiry unchanged; instructions stay hidden until the edit is confirmed or cancelled.
After generating payment details, record the local reference, selected asset and network, exact crypto amount, full destination address, rate retrieval time, creation time and expiry. Use the quote’s own timestamps rather than a note saying “today.” The validity period is exactly one hour; reopening the page does not create a fresh hour.
The reference is generated locally and is not a server-issued order number. Kraken’s ticker documentation identifies the last-trade price used by this checkout. That market reference is not a guaranteed execution price at your exchange. A stablecoin quote also uses a market rate.
If an effective configuration edit or expiry leads to a replacement quote, mark the earlier record as superseded and link the replacement. Do not erase the earlier quote if a transfer was already attempted against it. Its timing and details may matter when discussing an exception.
An approved budget awaiting payment details
Fictional scenario: a studio prepares hosting for an enquiry website. The client has approved the following illustrative budget. No quote, transfer or provider confirmation is fabricated for the example.
Scroll horizontally for all table columns.
| Record item | Example entry |
|---|---|
| Project / approval | Enquiry website · internal example CLIENT-BRIEF-01 · configuration budget approved in this fictional scenario |
| Configuration | Studio + 1 GB RAM + 50 GB SSD + daily backup option |
| Period and USD budget | 6 months · $18.50 monthly reference · 28% discount · $79.92 upfront |
| External costs | Domain and operator work: separate quotes still required; network fee: record from the actual transfer |
| Quote event | Not yet generated. Add the local reference, asset/network, amount, destination and exact timestamps from checkout. |
| Transfer event | No transfer recorded. Keep this field separate from the budget approval. |
| Provider confirmation | Not received. Do not mark payment verified or service delivered. |
| Next action | Billing operator reviews the final configuration and generates current payment details. |
If the client changes the resources, retain this approval as the earlier version and obtain the revised budget decision before using a new quote. The guide’s remaining steps describe how to add actual events when they occur.
Add the transfer event separately
Record the sending wallet or exchange reference permitted by your process, transaction identifier, asset, network, amount, fee and time. Keep the fee separate from the amount intended for the receiving address; an exchange withdrawal screen may present those figures differently. Compare the actual destination with the full address shown by the selected quote.
A screenshot or transaction identifier is evidence to investigate, not a declaration that PrivateHostLab has received and accepted the payment. Keep the administrative status as “transfer recorded; provider confirmation outstanding” until an authorized server-side process supplies confirmation. The current checkout remains “Payment not verified” and does not deliver a server.
Leave an explicit exception trail
If the amount, network or timing does not match the quote, document what was expected and what actually happened. Keep the relevant references together and identify the person responsible for the next decision. Avoid sending a second payment simply to make the local record look complete.
Late, partial, excess or wrong-network transfers depend on the applicable service and recovery policy. This worksheet cannot decide whether funds are recoverable or refundable. Consult the payment and refund terms and obtain a documented resolution through the provider’s agreed channel when available.
Close the administrative loop
When a provider confirmation or service record becomes available, attach its reference as a new event and compare it with the project configuration. Record discrepancies rather than silently rewriting the initial approval. Plan a separate service validation; an accepted payment does not prove the application is ready for the client.
Before the prepaid period ends, review whether the project will continue, change or close. Confirm the next price and renewal terms instead of carrying the current discount forward by assumption. An agency departure should transfer responsibility for this calendar and record together.
This is an operational record template, not an invoice, tax treatment decision or accounting advice. Any client-currency conversion and statutory records belong to your own agreed administrative and professional process.
Sources & review
Technical references were checked on September 12, 2026. Examples are planning exercises; referenced software documentation does not establish PrivateHostLab service capabilities.