Shift Log: Invoice Checks and Prepaid Balance Rules

The billing handover is complete when the next person can explain every payment, every credit, and every unresolved refund without searching a chat history. That is the standard worth keeping this year. For teams buying API access, the useful improvements are practical: preserve the evidence, distinguish cash from credit, and assign an owner to anything still pending.

Start by separating three records that often get treated as interchangeable. An invoice documents a charge and may show an amount due or a paid status. A payment receipt records a payment. A prepaid balance shows credit available under the service’s billing rules. Depending on the provider and jurisdiction, those records may arrive separately. Keep them connected through transaction identifiers rather than assuming one document answers every accounting question.

Before a payment leaves the company, check the billing name, address, currency, and any required tax details. Confirm which document the service issues and how to retrieve it. Correcting those details after payment can require support involvement, so make the first check part of the purchasing routine.

A useful transaction record contains enough detail for another person to reconcile it:

• Record the payment date, amount, currency, payment reference, and internal owner.
• Save the invoice or receipt alongside the corresponding balance credit.
• Record any payment fees or currency conversion differences separately from service usage.
• Keep refund requests and their final outcomes attached to the original transaction.

Prepaid credit needs its own operational discipline. A successful top-up gives the team spending capacity, but it does not show how much work has already run. Track additions, usage deductions, adjustments, and the closing balance as separate movements. When the numbers disagree, that structure helps identify whether the issue is a missing credit, an unexpected charge, or a timing difference between reports.

Size top-ups around observed demand and the time your team needs to approve another payment. Avoid choosing an amount simply because it covers an optimistic growth forecast. A team testing Claude Haiku 4.5 alongside Gemini 2.5 Flash should first measure representative workloads, then set a replenishment threshold with enough room for normal variation. Review that threshold when traffic, model selection, or request size changes.

Refunds deserve a distinction between requested, approved, and received. Those are separate events. A support acknowledgment does not establish approval, and approval does not establish that funds have reached the original payment account. Keep the case open until the destination and received amount have been checked, including any difference caused by fees or exchange rates.

Before adding substantial credit, read the current refund terms. Check whether unused purchased credit is eligible, whether a request window applies, which payment methods are supported, and how promotional credit is treated. Ask support to clarify unclear wording before relying on it. Preserve the answer with the purchase record so the next shift has the same information.

Referral earnings need a separate record too. Relay365 members can earn a referral bounty when people they invite pay. Track those earnings separately from purchased credit and customer refunds, and verify the current eligibility, availability, and withdrawal or spending terms. Keeping those categories distinct makes it easier to explain both the balance and the source of each credit.

Relay365 is worth considering when your team wants pay-as-you-go access to multiple model families through one relay desk. It works with Claude Code, Codex, Gemini CLI, and OpenAI SDK clients. That can simplify access management, while your own transaction records remain essential for understanding spending. If that setup fits your workflow, create a Relay365 account and review the billing and refund terms before your first top-up.

Leave the next shift a short exception list: unmatched payments, disputed usage, refunds awaiting receipt, and balances approaching the replenishment threshold. Give each item an owner and a next action. That turns a collection of billing documents into a process someone can reliably continue tomorrow.