When several domains have paid plans, it is easy to treat them as one subscription—until an invoice, account login, or term date does not match. A useful review starts by separating records by both domain and the account that manages them. Then distinguish dates you can confirm from details you still need to check. This approach helps you spot gaps without assuming that domains share a billing account, renewal date, or renewal setting. Keep the review as an organized record, not as a substitute for the current terms shown in pricing or authenticated checkout.
The useful bits
- Give each domain and managing account its own plan record.
- Label a term date confirmed only when you can verify its source.
- Check renewal terms for each plan instead of assuming they are shared.
Make one record for each domain-account pair
Start with a table or spreadsheet you control. Create a separate row for every domain and the account associated with its plan. If one account manages plans for several domains, keep separate rows and repeat the account identifier. If a domain has plans managed through more than one account, make a row for each relevant pairing.
Use an account label that helps you recognize the correct sign-in without exposing credentials. For example, record an administrative email address or an internal label, but never write down a password or one-time code. A mailbox alias should not be treated as a separate login unless you have confirmed it is an independent account.
Domain: [example.com] Managing account: [admin@example.com] Plan: [plan name shown in the account] Term date: [date, or not confirmed]
Separate known facts from open questions
For each row, record the plan name as displayed, the date or term wording you can see, where you found it, and when you checked. Keep the source specific: for example, “authenticated checkout” or “current account record,” rather than simply “confirmed.” If you have a dated receipt or other record, note its date separately from the plan’s term date.
Use clear labels such as “confirmed,” “needs verification,” and “not found.” Do not turn an estimate, an old note, or a date remembered from another domain into a confirmed date. If the account shows a term but not the next renewal date, record that distinction rather than filling the gap with a guess.
- Confirmed: the date and its source are visible in a current record.
- Needs verification: a date or setting is missing, unclear, or from an older record.
- Not applicable: use only when the available information establishes that it does not apply.
Verify term dates in the right place
Check the record for the specific domain and account, not a neighboring row. BITTU Mail’s live prices, upfront term totals, taxes, availability, and renewal terms need to be checked at /pricing or in authenticated checkout. Sign-in and account actions go through mail.bittuicloud.com. If you need to confirm a detail tied to an account, use the appropriate authenticated account flow and record what it actually shows.
Keep different dates separate. A purchase or payment date is not automatically the end of a plan term, and a displayed term is not automatically evidence of a particular renewal arrangement. If the information does not identify a date unambiguously, mark it for verification and avoid using it as a deadline.
Check renewal details domain by domain
Do not assume that plans renew together because they belong to the same organization, use the same account, or were arranged around the same time. Renewal terms must be checked for each relevant plan. Record the exact wording you can verify and the source, or mark the setting as unknown. One-time checkout does not, by itself, imply an automatic charge or mandate.
If several rows show different terms, preserve those differences. If they appear to match, verify each row before treating them as shared. For a detail you cannot see or interpret confidently, consult the current pricing information or authenticated checkout rather than inferring a setting from another domain.
Flag uncertainty so it leads to an action
Give every unresolved item a short next step and an owner. Examples include “check the term in authenticated checkout,” “confirm which account manages this domain,” or “compare the current pricing details.” Avoid vague notes such as “look into billing”; they do not identify what is missing.
If a domain or account is inaccessible, leave its date and renewal status unconfirmed. Do not attempt account recovery through an unverified route: BITTU Mail account recovery and account actions go through mail.bittuicloud.com. Keep sensitive sign-in details out of the review sheet and out of messages to anyone helping with the review.
Domain: [example.org] Managing account: [account not confirmed] Term date: [needs verification] Renewal detail: [not confirmed] Next step: [identify the managing account, then check its current record]
Close the review with a row-by-row check
Before relying on the summary, compare every row with its source. Confirm that the domain, managing account, plan name, term date, and renewal note belong together. Check that each date has a source and that uncertain details remain visibly uncertain. Update the review date when you revisit a record, while retaining enough context to tell which information was checked.
The review is complete when every plan you know about has a distinct record, every confirmed date can be traced to a source, and each open question has a next step. This confirms the quality of your inventory; it does not establish that separate plans have identical settings or guarantee that an unverified term is correct.
- Match each domain to the account that actually manages its plan.
- Mark dates confirmed only when their source supports them.
- Verify renewal terms separately; leave unclear settings flagged.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction