Investigate a bank-feed gap when the complete statement is available

Compare source coverage with imported coverage

Identify the missing coverage before proposing entries so the team fixes the source problem without introducing duplicate transactions.

When an exception needs a supplier invoice schedule, ParseMill can extract the invoice PDFs into Excel and keep source references available for checking. That gives the reviewer a concrete starting point. Bank reconciliation, accounting judgments and posting stay in your accounting system.

A complete document and a complete import are different controls. The statement can cover every day while the application view omits a subset. Conversely, a filtered view can look incomplete even when the records exist. Establish the actual gap before repeating an import or changing financial records.

Define a comparison population

Record statement artifact, account reference, period, source entry count and the application view or export being checked. Include date filters and relevant states. Use transaction identifiers where available, with dates, amounts, currencies and descriptions as supporting comparison fields. Do not rely on a daily total alone when several transactions can offset.

Intuit: Find missing transactions describes checking other transaction states and accounts. Intuit: Reconcile an account describes comparison with the account statement. The proposed coverage worksheet uses these checks to distinguish missing imported records from records that are simply outside the current view. Follow the current vendor process for any authorized remediation.

Locate a fictional gap

In this synthetic example, the statement has twelve entries for the selected period. The initial review view shows nine, but further inspection changes the explanation.

The correct next action concerns one unresolved entry, not reimporting all twelve. Preserve the source reference for that entry and check the account, date range and relevant history. If remediation is needed, have the authorized owner choose the method and verify that it does not create duplicates.

Keep technical repair separate from reconciliation judgment

An administrator may restore a connection or import missing records, while the reviewer decides how those records should be matched or categorized. Record both steps and their owners. A successful import message is not proof that every expected entry arrived correctly or that the reconciliation is complete.

• Confirm the statement and application account agree.
• Record filters and states included in the comparison.
• Search for existing records before reimporting.
• Preserve the exact missing-entry list.
• Reconcile the repaired result back to the source.

Do not disconnect and reconnect accounts reflexively or manually add transactions simply because the current screen looks empty. Use the approved product procedure and consider existing records. The worksheet should supply a narrow, evidence-backed repair request rather than a vague report that the feed is broken.

Verify coverage after the repair

Repeat the same defined comparison and record which formerly missing entries are now present. Check boundary dates and duplicates as well as total counts. If the counts agree but identities differ, the coverage issue remains unresolved. Retain the before-and-after evidence with the exception case.

Use the related workflow guide for the broader exception workflow and the workflow audit checklist to distinguish collection gaps from import gaps. Test a filtered-view case and a genuinely absent record so the process does not solve both by requesting another statement.