Review Billing, continue a payment and find a receipt¶

Draft guide combining the intended Tenant Admin 06 Final Screens journey with current implementation differences. Subscription, workflow/detail, checkout, history and invoice routes now load real records; that wiring does not certify every control, provider, deployment or end-to-end journey. Current renewal/removal controls have additional design follow-up. Reader and environment walkthroughs remain pending.

Use this guide to understand the intended Billing experience and the checks to make at each step. See the Billing overview for the differences between a subscription, workflow, history entry and invoice.

Before you begin¶

Confirm the workspace name in Tenant Admin. You should have responsibility for its billing and any required approval within your organization. A displayed control alone does not grant permission. Keep the workspace name, requested change and existing workflow reference available so that you can return to the same request.

The current billing rules require an organization administrator with an eligible account and membership. A product licence alone is insufficient, and an administrator may have a recovery session while product access is unavailable. See billing access and recovery. The steps below retain the inspected Final Screens journey; this prerequisite does not certify newly connected controls.

For a new purchase, first decide what capacity or access is needed. The Usage guide covers entry steps for seats, add-on access, recurring storage, storage reduction and plan changes. Those steps lead into a Billing summary; they do not themselves prove payment or activation.

Review the current subscription¶

1. Open Billing from the Tenant Admin navigation.
2. In Current Subscription, review the plan, licensed seats, recurring amount, billing contact, current period and next payment date where supplied.
3. Read Payment Posture for the latest displayed billing event and update time. Review a payment problem before requesting another unrelated change.
4. Check Plan Allowances and Storage to understand licensed capacity, extra storage and recorded usage. Follow the measurement limitations when using those figures for a decision.
5. If an Active Workflow represents the change you are investigating, choose Open Workflow. Compare its reference and requested change with your own request.
6. Use View Billing History for the event sequence, or Invoices for invoice and receipt information.

Refresh Billing is part of the intended screen. A refreshed page should be checked against the actual record and timestamp; it does not guarantee that a payment provider or background update has completed.

The current subscription page also reads the latest three workflows and history entries. Its featured workflow is the first returned record, which need not be the unresolved action you are investigating. A recent-activity load error is shown separately; missing recent items do not prove that no history exists. Open the relevant directory and original reference when investigating a particular request.

Check coverage before relying on renewal¶

Use the actual recorded expiry and current saved-payment eligibility when planning continued access. An Active label or a displayed number of days is insufficient; display days can round a partial day upward.

Read subscription access, renewal timing and saved-method consent for the full distinctions. Scheduled opportunities, reminders, old receipts and an earlier authorization choice do not prove that a new charge was sent or accepted. Use the controls currently offered to the authorized administrator, and seek support when the available journey or outcome is unclear.

Current renewal and saved-card controls¶

These controls are mounted in the current Billing implementation. The inspected final subscription screen does not show them, so their complete design companions and live walkthrough remain open. They do not replace the intended record-review journey above.

For an eligible current-plan payment:

1. Refresh Billing and review the selected workspace, current plan, recorded expiry and existing requests. If a recent request is unresolved or cannot be checked, resolve it before another payment.
2. Where offered, review Pay for this plan for a trial conversion or Renew subscription for a paid term. Trial payment starts paid coverage immediately; early renewal preserves the remaining paid time.
3. Select I authorize saving my card for automatic subscription renewals. only if you authorize it. On hosted checkout, leaving this unchecked permits a one-time payment without creating a new saved method or renewal consent. Completing a card payment with saving selected requires the verified saved-card path; method availability and native payment requirements remain separately qualified.
4. Submit once, wait for the result, then use Review saved checkout when supplied. Review its current quote, currency, payment requirement and status before paying. A saved request is not a successful charge.

If the application offers Update renewal setup, the subscription has a separate provider-managed renewal owner. The action saves a transition request; it does not itself confirm that cancellation or ownership transfer finished. Check the current result or seek support before another collection. See renewal ownership. Upgrade plan, where available, opens the plan-change journey and remains subject to its current eligibility and quote.

Change card returns to an eligible subscription payment or plan-upgrade flow. It does not directly edit card details. The existing card remains until a qualifying new payment/card is verified; keep unresolved earlier payment evidence. To remove consent, read the paid-access expiry and warning, select I understand that automatic renewal will stop, then choose Remove card once. Review the response and refresh Billing. Removal stops current automatic eligibility without shortening an already-paid term, but access that depended on grace can cease. Its acknowledgement is not a refund, provider-subscription cancellation, in-flight payment result or proof that storage cleanup has finished.

The forms lock after submission, including an unconfirmed outcome. Reopening them can create another request. Preserve the original reference and ask support to reconcile an uncertain payment/removal instead of repeatedly submitting. Current account, membership and backend authority are rechecked; a control or an earlier administrator session is insufficient permission.

Check a saved commercial summary¶

After continuing from an eligible Usage entry, the intended Checkout Summary shows the saved change and its payment state.

1. Confirm the workspace and kind of change: seats, add-on access, recurring storage, storage reduction or plan change.
2. Read the line item and quantity. Check whether the number means additional seats, the target total, add-on seats or a storage change.
3. Review the amount, currency, discount and any applicable tax information. Compare the amount due today with the recurring commitment; do not calculate the authoritative charge from a sample price.
4. Note whether payment is Required, Preparing, or Not required, and retain the workflow reference.
5. Follow the appropriate path below.

The summary is a handoff page. Billing workflows are the intended place to return for later recovery. The current checkout route loads its selected saved record, while the inspected prototype still routes through a shared ready-workflow example. This does not verify every real purchase, payment control or delivered journey. Match the original reference and current payment evidence before continuing.

For a scheduled storage reduction, check whether the remaining allowance will cover expected usage when it takes effect. For a plan change, review the target plan and seat count. “No payment today” does not mean “no future recurring charge,” nor does it mean the change is already applied.

Find and inspect a billing workflow¶

1. Open Billing Workflows from the available workflow navigation, or choose View workflows on a checkout summary.
2. Use the intended search and status controls to locate the requested change. Compare the workflow reference, type, charge, seats or storage, and update information.
3. Choose the row's View Details.
4. Review the requested change, line item, totals, Workflow Reference, Workflow Type, Payment Verified, checkout availability and Issue Details.
5. Read Workflow Timing to distinguish creation, updates, verification and completion where those times are present.
6. Follow the state-specific guidance below. Use Back to Workflows to return to the list.

The current workflow page requests ten records at a time and forwards its selected supported status to the server. Text search filters that fetched page; history and invoice text/status filters also work within their fetched page. They do not search the whole ledger. Clear filters, inspect other pages or use the original reference when a record is missing. A failed read or empty filtered page does not prove that a saved purchase is absent.

Conditional payment instructions and verification¶

Read payment methods, bank instructions and verification if a current payment needs method-specific instructions or an additional bank action. Keep the original workflow and operation references while the outcome is uncertain. Instruction expiry, payment failure, accepted coverage and workspace readiness have separate meanings. Native selection/verification actions exist in source but are not mounted in the inspected frontend; exact steps require their matching Final Screens and client implementation.

Continue or recover the right workflow¶

For a failed or expired subscription payment, read subscription checkout retry before another attempt. The newer backend requires reconciliation and current authority for a linked replacement. The state-specific screen guidance below retains the inspected design; it does not establish that every newer retry outcome has a connected control.

Checkout ready. Confirm that the reference, amount, currency and requested change are correct. Stop if required financial details are missing or uncertain. Use Resume Checkout only when the application offers a valid current payment handoff. The current workflow's Copy Link copies its internal page address so an authorized person can return to that record; it does not copy the provider payment link or grant access. Share financial records only with authorized recipients. The prototype's Resume/Copy destinations still lead to the overview and are not real payment instructions.

Checkout preparing. Keep the reference and reopen the workflow after the payment link becomes available. If it remains preparing, contact support with the recorded state and timing. Do not create several new purchases to make one preparation finish.

Manual review. Read the review or issue message, keep any payment evidence and contact support. An unresolved verification error does not establish that no money was taken. Do not pay again solely because the interface has not reached completion.

Failed payment. Check the issue details and current payment evidence. The intended failed-payment screen includes a resume action, but the implementation does not expose an old compatibility URL merely because it remains stored on a failed workflow. Modern protocol evidence and controlled retry have their own rules. Some creation failures have no link. If the provider shows a charge, reconcile it before another attempt. Once a controlled retry has closed the old attempt, do not reuse its historical link.

Expired checkout. Do not reuse the old link. The intended screen retains the expired workflow for reference and explains that a new workflow is needed. Before starting another request, confirm that there is no unresolved successful payment on the expired one. The server's expiry record alone does not prove that a provider link has been revoked.

Payment verified but change pending. Review the workflow again and check the relevant plan, seats, storage or access. If the records remain inconsistent, give support the workflow reference and payment time. Repeating payment does not resolve a delayed application step.

Scheduled change. Check the effective date and requested reduction or target plan. No immediate payment is required for the inspected scheduled paths. Track the workflow through its later application. Do not expect the change to appear immediately after opening the summary or exactly at a displayed second.

Completed. Retain the reference, check the resulting workspace state, and locate the related invoice where applicable. For add-on capacity, proceed to the member access guide if people still need assignments. A retained historical amount is not a new payment request.

Investigate an event in Billing History¶

1. From Billing, choose View Billing History.
2. In the intended ledger, locate the event by its description, status, amount, period and occurrence date. Use the displayed search, event-type and status controls where implemented.
3. Choose View Details to open Billing Activity Detail for the selected event.
4. Read its payment outcome, billing period, next payment information and recorded time.
5. When the event has a related workflow, choose View Workflow for checkout or recovery context. Otherwise, retain the event details for support.
6. Choose Back to History to continue reviewing the sequence.

The current history route loads paged backend entries. The intended activity detail explains a selected event, rather than creating a financial action; its complete composition still needs separate verification. A next-payment date or a “retry scheduled” label does not independently establish an automatic collection timetable. Match the original workflow and current coverage, especially when the visible page has been filtered.

Find an invoice and inspect its receipt status¶

1. Open Invoices in Tenant Admin.
2. In the intended Invoice Ledger, locate the entry using its amount, issued date, status and associated change. Sample invoice counts and prices are illustrative.
3. Choose View Details, including for entries without a receipt in the intended design.
4. Review Invoice Amount, Invoice Status, Receipt Status and Licensed Seats, followed by the invoice record and any linked workflow information.
5. Check Invoice Timeline and the linked workflow before concluding that payment and application are both complete.

The intended pending-review and failed-payment companions keep the invoice readable while hiding receipt actions. The current tenant invoice service returns paid invoices only, and the live frontend loader uses those results. Other invoice states remain intended behavior requiring further backend integration; sample-state components do not prove those records are selectable. If a real charge is missing, use the workflow, history and support route rather than treating absence from the list as proof that no payment occurred.

View, print or retain a receipt¶

1. On an invoice with a receipt available, choose View Receipt in Receipt Access.
2. In Receipt Preview, check the billed organization, issued date, payment amount and currency, status and workflow reference.
3. Choose Print to use the browser's print facilities, or the intended Export PDF action to retain a copy.
4. Return to the invoice detail and verify that the copy corresponds to the record you intended to retain.

The current invoice detail loads its saved invoice and, where available, a linked workflow. Both Print and Export PDF use the browser print dialog for the rendered summary; saving as PDF depends on the browser's destinations. This is distinct from Open Receipt, where supplied, which opens the saved external receipt link. The receipt service supplies invoice information and an optional link; it does not generate a new provider PDF through the print action. Check that any retained copy matches the actual record, and do not treat a local printout as independent payment verification.

If no receipt is available, keep the invoice or workflow reference and ask support to investigate. A paid status does not guarantee a receipt link has arrived. A summary line is not a detailed breakdown of all contract terms or a substitute for an agreed commercial document.

Help for other readers¶

Users and external participants: tell your workspace administrator which action is unavailable and whether a billing or access message is shown. You do not need to diagnose payment records or gain billing access to report the problem.

Managers: agree seat, storage and add-on needs with the billing owner. Check the effective date of reductions before scheduling work that depends on the old allowance.

Executives and finance owners: compare the actual recurring commitment, one-time amount due and scheduled change. Keep responsibility for approving purchases, reviewing renewal problems and retaining receipts explicit. This guide does not establish prices, contractual grace periods or financial-return estimates.

Administrators and support: capture workspace identity, workflow or invoice reference, requested change, displayed state, relevant date, amount and currency, and whether the provider reports payment. Use your approved private support channel for financial details; never request passwords, full card details or session tokens. Distinguish a failed checkout, uncertain verification, delayed application and a separate member-access restriction before choosing recovery.

Platform staff: tenant pages are not a substitute for authorized finance operations. Refunds, external reversals, reconciliation and manual interventions require their own controls and evidence. Do not instruct a tenant to alter payment data or bypass a review using a preview control.

Read how to interpret an unconfirmed hosted payment before deciding whether to pay again. A saved status read and an active check with the provider are different operations. The active check uses the original reference without creating another checkout or charge; pending verification, recorded billing completion and current workspace access remain separate results. Keep the intended task sequence above and use the controls currently available for that original request.