QBO Bank Reconciliation Exception Log for Virtual Assistants

Turn each unexplained difference into an assigned question

A reconciliation exception log connects an observation to its source, reviewer and eventual outcome. It should let someone pick up an unresolved item without searching through a chain of messages. The assistant records and follows up on the issue; the authorized owner or accountant decides the accounting response.

Identify the account, statement period and packet version before creating an exception. Record what was observed in neutral language. Keep a possible explanation separate from a confirmed cause so a working hypothesis cannot become an instruction by accident.

Use fields that support a decision

Observed difference

Record The specific amount or record mismatch and where it appears.

Avoid Describing an unconfirmed cause as a fact.

Source evidence

Record Statement page, transaction reference and relevant supporting documents.

Avoid Replacing the original evidence with an unexplained edited export.

Decision requested

Record A clear question for the person authorized to resolve it.

Avoid A vague status such as “check this” without the information needed to act.

Ownership and timing

Record The reviewer, next action, last update and follow-up date.

Avoid Resetting the age of an unresolved issue every time the report is refreshed.

Resolution evidence

Record The authorized instruction and any resulting completion confirmation.

Avoid Marking an item closed because a request was sent.

Example: a transaction remains unexplained across two reviews

An item is still open when the next packet is prepared. Keep its original exception reference and creation date. Add the latest source comparison and explain whether the same question remains unresolved or new information has changed it.

If the reviewer confirms a timing explanation, preserve that conclusion and any instruction for later follow-up. If the reviewer instead requests a correction, record the exact affected item and authorized action. Either way, a fresh period should not erase the issue's history.

Prioritize using the owner's criteria

Group the log by the action needed: missing document, business explanation, accounting decision or completion check. Apply the owner's agreed priorities for an upcoming review or close. Keep sensitive account information in the approved location and share a concise status summary with only the people who need it.

A duplicate-transaction question may require different evidence from a missing statement. Link the relevant supporting material rather than applying the same generic instruction to every exception.

Close with a record of what changed

Before marking an exception complete, confirm that the decision is documented, any assigned task has a result and the reviewer has the evidence required by the agreed process. Leave unresolved questions open with a named owner and date. Do not create an adjustment solely to remove a difference from the log.

Use this register alongside the reconciliation support workflow. For recurring preparation help, define the account scope, escalation boundaries and review cadence with cleanup support.