A receipt and a plan confirmation can look similar in a crowded downloads folder, especially when you manage more than one mailbox or account. A small filing routine makes it easier to tell what each document relates to without relying on memory. The key is to record the date, account identifier, and document type consistently, then keep the original file intact. This approach works with records you receive or download; it does not assume that every provider supplies the same documents or that a saved confirmation proves a payment cleared.
The useful bits
- Use the same filename order: date, account, document type, then any useful detail.
- Keep payment records separate from plan confirmations, but group both under the account they concern.
- Open a few saved files to verify the names, dates, and account identifiers are readable.
Start with one account-first filing structure
Create a main folder for service records, then a subfolder for each account or workspace you manage. Name the subfolder with a recognizable account identifier, such as the mailbox address or business domain, rather than a vague label like “Work.” If you handle multiple accounts for the same organization, include enough detail to distinguish them.
Within each account folder, separate payment records from plan or subscription confirmations. For example, use “Payments” and “Plan confirmations.” This keeps related records close while making it clear that a payment receipt and a notice describing a plan are different documents. If you already use a reliable document system, keep its structure and add the same identifying details to filenames.
Use a filename that answers the basic questions
Choose one order and stick to it: date first, account identifier second, document type third, and a short detail last. Use a consistent date format such as YYYY-MM-DD so files sort chronologically. Keep names plain and readable; avoid relying on symbols or abbreviations that you may forget later.
A practical pattern is “[YYYY-MM-DD]_[account]_[document-type]_[detail]”. The date should match the date shown on the record, not the day you happened to download it. If the document does not show a clear date, use the date you saved it and mark that distinction in the detail, rather than presenting it as the transaction date.
2025-04-18_[mailbox@example.com]_payment-receipt_[reference] 2025-04-18_[mailbox@example.com]_plan-confirmation_[selected-term] 2025-04-18_[example.com]_plan-confirmation_[workspace]
Keep account names useful but discreet
For a personal mailbox, the mailbox address may be the clearest identifier. For a business workspace, the domain or an internal account label may work better. Use an identifier consistently in the folder name and filenames, so a search for that account brings up the related records.
Do not add full card numbers, passwords, one-time codes, or other sensitive credentials to filenames. A short reference already printed on the record can help distinguish documents, but do not expose more information than you need. If account details change, preserve the identifier shown on the original document and add a note or separate index explaining the change; do not rename an old record in a way that makes it appear to concern a different account.
Save the original and note what each record says
When a payment record or plan confirmation is available, save the original file or message in the matching account folder. If you download an attachment, keep its original contents unchanged. You can rename the saved copy for clarity, but retain the document’s own identifying information and avoid editing amounts, dates, or plan details.
A brief index can help when the filename alone is not enough. Record the document type, the date printed on it, the account it names, and a short status such as “saved” or “needs review.” Treat that status as your own note, not as proof that a payment settled or that a plan remains active. For BITTU Mail, check current pricing, upfront term totals, taxes, availability, and renewal terms at /pricing or authenticated checkout; do not rely on an older saved confirmation for current terms.
A quick routine when you receive a record
Before filing, check that the document belongs to the account you intended, read the date and document type, and make sure the file opens. If the record refers to a plan choice, compare its account and term details with the information you expected. If something is unclear or inconsistent, keep the record and seek clarification through the provider’s appropriate account channel instead of guessing or altering it.
For example, if one person manages a personal mailbox and a separate business workspace, save each record under its own account folder even when both arrived in the same inbox. A matching date does not mean the records belong together. The account identifier is what prevents a receipt for one from being mistaken for a confirmation for the other.
- Check the account or workspace named on the record.
- Use the date printed on the document and label other dates accurately.
- Confirm the file opens, then check that it is in the intended account folder.
Confirm the system is working
After filing, search your storage for the account identifier and a date from the filename. Confirm that the expected payment record and plan confirmation appear, and open each one to verify its contents. Then check that the folder labels make the account distinction clear without opening every file.
Review the structure when you add an account or change your naming pattern. Do not rename a whole archive hastily: first test the pattern on a small group and make sure the dates and account labels remain correct. The goal is not elaborate bookkeeping. It is a repeatable way to find the original record and understand which account and date it concerns.
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