Saved custom reports in QuickBooks Online tend to accumulate quietly. One was built for a past meeting, another for a manager who left, and three have nearly identical names but different filters. People keep opening the familiar one without knowing whether its settings still match the intended question.
A custom report library catalog gives the list some order. It records what each saved report is for, who owns its definition, which settings matter, who receives it, and when it was last reviewed. A virtual assistant can prepare and maintain that catalog. The assistant does not interpret financial results, decide accounting presentation, or certify that a report is correct.
Treat the catalog as a map, not a second report system
The catalog should help a user find and understand saved reports. It does not need to reproduce every output value. Include the saved report name, stable reference if available, report type, stated purpose, key date setting, major filters, columns or grouping that define it, intended audience, owner, distribution method, review date, and status.
Use short descriptions. “Weekly open invoice review by assigned customer owner” is more useful than copying a page of settings into one cell. Link to controlled documentation when the configuration is complex.
Never store report exports containing sensitive financial or personal data in a broadly shared catalog merely for convenience.
Inventory without changing anything
The first pass is observation only. List the saved reports visible within the assistant's authorized access. Record names exactly, including punctuation and dates. Do not rename, schedule, share, or delete reports while building inventory.
If the assistant cannot see a report another user references, note an access gap. Do not request broader access automatically. The owner can decide whether the report belongs in the shared library and who should inspect it.
Take the inventory on a recorded date. Saved report lists can change during review, and the timestamp provides a clean baseline.
Ask each report to justify its place
For every report, ask the owner or designated user:
- What recurring question does this report support?
- Which settings are essential to that purpose?
- Who owns changes to the definition?
- Who should have access or receive an export?
- What event should trigger review?
- Is the report current, temporary, restricted, or a retirement candidate?
A report without an immediate answer is not automatically useless. Mark it “purpose unconfirmed” and preserve it until the owner decides.
Record configuration that changes meaning
Two reports can share a title while using different dates, methods, filters, classes, locations, customers, vendors, or display columns. Capture the settings that materially distinguish the saved view. The accounting reviewer should identify which settings matter for interpretation.
The assistant can transcribe visible settings and compare them with the approved definition. If they differ, use a factual status such as “saved settings differ from owner description.” Do not decide which version is correct.
Be careful with relative date ranges such as “this month” or “last quarter.” Note that the range moves. A reviewer looking later should know whether a setting is relative or fixed.
Adopt a naming convention slowly
A good saved-report name usually communicates purpose, scope, and perhaps cadence. It should not contain confidential details that appear broadly in menus. Before proposing names, document the team's current language and abbreviations.
Prepare a rename sheet with current name, proposed name, reason, owner, and approval. Similar reports may need distinct audience or filter labels. Avoid appending random numbers just to make names unique.
Renaming can disrupt user habits and written procedures. Provide an effective date and a cross-reference from old to new. For widely used reports, notify users before the change.
Identify near-duplicates with evidence
Start by grouping similar names, then compare their visible configurations. Record differences field by field. One report may include inactive customers, another may filter a location, and another may use a different date basis. Those are not duplicates simply because the output looked similar on one day.
Use statuses such as exact configuration appears matched, configuration differs, purpose differs, owner review needed, and restricted comparison. The owner decides whether to retain, rename, consolidate, or retire.
Never delete a saved report merely to clean the list. Retirement can affect schedules, shared access, bookmarks, or recurring processes.
Map distribution separately
A useful report can still have an outdated audience. Record whether it is viewed on demand, exported manually, sent through a schedule, or used in a meeting packet. Note the authorized recipients by role or controlled group where possible, rather than copying personal addresses unnecessarily.
If a former employee or obsolete list appears, flag the distribution for immediate owner review. Do not add new recipients or forward a report as a test. Report content may be sensitive even when the saved definition seems ordinary.
Document the last confirmed recipient review. Access and distribution questions should be routed to the designated owner, not solved by granting broad permissions.
Assign lifecycle statuses
A compact lifecycle helps:
- Current: purpose, owner, configuration, and audience are confirmed.
- Review due: the report remains in use but one element needs confirmation.
- Temporary: created for a defined event with a planned review or end date.
- Restricted: cataloged, but details or access are limited.
- Purpose unconfirmed: owner or use has not been established.
- Retirement candidate: the owner is evaluating whether to remove it.
- Retired: the approved action is complete and the retirement date is recorded.
Keep retirement candidates visible until the action is authorized and verified.
Perform a controlled review
A quarterly or semiannual session can focus on review-due, unconfirmed, and retirement-candidate reports. The assistant prepares the catalog changes and exact questions beforehand. Owners spend meeting time making decisions rather than searching menus.
For each approved configuration or name change, record who authorized it and when. The permitted user makes the edit, reopens the saved report settings, and compares them with the approved definition. If the platform behavior differs, leave the line open.
Report output review is a separate step performed by the appropriate financial reviewer. The catalog check only verifies that saved settings match the documented instruction.
Example: three “monthly” reports
The inventory contains “Monthly Review,” “Monthly Review 2,” and “Monthly P&L Review.” The assistant compares visible settings and finds that the first is a customer balance report, the second is a profit and loss filtered to one location, and the third is a companywide profit and loss with comparative columns. None is an exact duplicate.
The owners provide purposes and audiences. They approve descriptive names and identify the second report as temporary until a project ends. The assistant records the cross-reference and review date. No output is interpreted and no report is removed.
Keep the catalog useful between reviews
When someone requests a new saved report, add a draft catalog line before or when it is created: purpose, owner, essential settings, audience, and review date. This small intake step prevents future mystery reports.
When a report changes, update both the saved configuration and catalog through the approved change process. Preserve the prior review date and note what changed. Do not silently overwrite the history.
A simple monthly check can identify new uncataloged names and overdue temporary reports. It should not rerun every report or expand the assistant's access.
The reporting and tax prep support VA service describes preparation boundaries for report organization. For recurring scheduling context, read the QuickBooks reporting calendar for a VA.
What the catalog can honestly claim
A mature catalog can show that saved reports have named purposes, visible configuration notes, accountable owners, controlled audiences, and planned reviews. It cannot claim that every number is correct or that every report suits every decision.
That honest boundary is a strength. The assistant maintains the map, users can find the right saved view, and accounting interpretation stays with qualified reviewers who understand what the report is meant to show.
QuickBooks VA workflow table
| Workflow area | What the VA prepares |
|---|---|
| Daily queue | Invoices, receipts, bank feeds, and open QuickBooks questions |
| Weekly review | Owner approvals, exception list, and unresolved transaction notes |
| Monthly packet | Reports, missing documents, and accountant-ready source material |
Related resources
Compare the service fit on the QuickBooks VA services page, then use the free consultation form to map the first handoff. For platform context, review QuickBooks Online.
