QuickBooks Online Transaction Attachment Coverage Check

An attachment icon beside a QuickBooks Online transaction can create false comfort. A file may be attached to the wrong transaction, unreadable, incomplete, or unrelated. Another transaction may have no file because the business stores that document in an approved external repository. Counting icons alone does not answer whether the expected source is findable.

A transaction attachment coverage check is a bounded administrative review. A virtual assistant identifies the in-scope transactions, checks attachment presence and basic usability, references approved external sources, and routes gaps. The assistant does not decide account classification, deductibility, tax treatment, approval validity, or whether a transaction should be posted.

Write the coverage rule first

The owner or accounting reviewer should define which transaction population expects support and what “covered” means. The rule might apply to selected expenses, bills, deposits, reimbursements, or high-priority exceptions. It might accept an attachment in QuickBooks or a stable reference to another approved system.

Do not apply one universal rule to every transaction. Payroll files, personal data, contracts, and other sensitive documents may have stricter storage limits. Some source material should never be duplicated into a broadly accessible location.

Record the period, transaction types, exclusions, accepted repositories, and reviewer. This scope protects both the records and the assistant.

Build a transaction checklist

Create one line per in-scope transaction with date, type, QuickBooks reference, counterparty, amount if needed for matching, expected document type, attachment status, readability status, external reference, exception reason, next owner, and review status.

Use enough context to match the source without copying private content into the checklist. A transaction ID and protected repository link are often safer than a detailed description.

If the source rule differs by transaction type, add a requirement code. For example, a vendor bill might expect the vendor document, while an expense reimbursement may require a different approved packet. The code should refer to a documented rule, not the assistant's opinion.

Check presence, identity, and readability

Use three separate questions.

Presence: Is there an attachment or approved external reference where the rule expects one?

Identity: Does the file appear to correspond to the selected transaction based on permitted matching fields such as date, vendor, document number, or amount?

Readability: Can a reviewer open the file and read the relevant ordinary details?

These checks still do not establish accounting sufficiency. A readable receipt may omit information the professional reviewer needs. Mark “present and readable” rather than “approved.”

Avoid opening more than the task requires

Attachments can contain personal, payroll, banking, health, or contractual information. Follow least-access principles. The assistant should review only the fields needed for the assigned match and should not download or copy files to personal or unapproved locations.

When a file is restricted, use a status such as “restricted, assigned reviewer required.” Do not mark it missing merely because the assistant lacks permission. Access limits are part of the evidence trail.

If a file appears to contain information that should not be stored with the transaction, stop and notify the designated privacy or record owner. Do not move or delete it without authority.

Name exception reasons precisely

A useful exception queue distinguishes:

• No attachment or external reference found.
• Attachment opens but is unreadable.
• File appears to belong to a different transaction.
• Multiple files exist and the controlling source is unclear.
• File is incomplete based on the defined document requirement.
• External link is broken or access is denied.
• Sensitive file requires a restricted reviewer.
• Transaction changed after the source was matched.

Precise reasons let the next person act. “Bad receipt” does not.

Request missing documents with context

When the business permits the assistant to request a document, provide the transaction date, vendor or source, ordinary reference, and the approved document type needed. Do not send full account details or sensitive fields merely to identify the request.

Send requests to the assigned document owner, not a broad group. Record the request date and reminder limit. If the owner supplies a file through an unapproved channel, ask them to place it in the accepted repository rather than quietly copying it yourself.

A reply that says “already sent” is a clue, not closure. Ask for the approved location or search the sources included in the workflow.

Attach only under an approved procedure

If the assistant is authorized to upload ordinary source files, match the transaction again immediately before attaching. Similar amounts and vendor names can lead to wrong-record uploads. Confirm the file name and contents, then use the permitted QuickBooks action.

After upload, reopen the transaction and confirm that the intended file appears and opens. Update the checklist with the completion date and source location. Do not delete the original from its required repository unless the retention owner directs that action.

Use clear file names if the business has a naming convention. Avoid names such as scan1.pdf that offer no context, but do not put sensitive data into file names.

Handle duplicates conservatively

Two attachments may be exact duplicates, alternate pages, corrected versions, or separate support. The assistant can compare ordinary file metadata and visible content when authorized, then record the observation. Deleting a duplicate changes the record and should require clear approval.

If a corrected document replaces an earlier one, preserve the business's version rule. The reviewer may want both retained with clear labels. Do not assume newest means controlling.

A duplicate file in two different transactions may signal a matching error. Flag both transaction references and stop further uploads until the owner resolves the relationship.

Use sampling when full review is unnecessary

The owner may define a sample rather than a full population. Record how the sample was selected, the source population, sample date, and items reviewed. Do not describe a sample result as coverage for all transactions.

If the sample reveals repeated missing or mismatched files, the owner can expand the scope. The assistant should preserve the original sample and create a new scope line for added work.

For recurring reviews, use the same selection method unless the owner changes it. Consistency makes periods easier to compare without implying an audit conclusion.

Report facts at the review meeting

A concise summary can show transactions checked, present and readable, externally referenced, missing, mismatched, restricted, and waiting for a document owner. List old exceptions by responsible person and request date.

Avoid percentages without the population definition. “Eighteen of twenty selected bills had a readable attachment under the August review rule” is more transparent than “90 percent compliant.”

The accounting reviewer decides whether any source is sufficient and what correction, if any, should be made to the transaction.

An example with an external file

A selected bill has no attachment icon in QuickBooks, but the document index points to an approved folder. The assistant opens the permitted link, confirms the vendor, date, and document number match, and marks the line “covered by approved external reference.” The assistant does not upload a duplicate because the scope accepts that repository.

Another bill links to a file for the same vendor but a different document number. The assistant marks “possible wrong attachment,” references both numbers, and routes the case. No accounting field changes.

For more on organizing sources for reconciliation work, see the QuickBooks reconciliation support packet. The QuickBooks bookkeeping VA service describes how document preparation can stay separate from professional review.

Completion has a narrow meaning

A completed coverage check means the assigned population was reviewed under a written rule, every line has a factual status, uploads were verified where authorized, and unresolved sources have named owners. It does not certify the books or bless the attached evidence.

That narrow definition makes the task useful. It lets a virtual assistant reduce document-search friction while respecting privacy, retention rules, and the judgment of the owner or accounting professional.