Discovery Module

The Discovery module compares your commission statement against your CRM database to identify coverage gaps. It answers two critical questions:

1. Which policies in your CRM are missing from this statement? These may indicate cancellations, lapses, or carrier processing delays.

2. Which statement rows are not in your CRM? These may represent new business you have not yet entered, or policies written by other agents.

When you run Discovery, the system performs a cross-reference between:

• Your CRM policies for the carrier and time period covered by the statement.

• The statement rows that were parsed and mapped.

The comparison uses policy numbers as the primary matching key. If policy numbers are not available, client name and date of birth are used as fallbacks.

Discovery results are organized into two sections:

These are policies that exist in your CRM but were not found in the uploaded statement. Possible reasons include:

• The policy was cancelled or lapsed.

• The carrier has not yet processed the commission for this period.

• The policy is with a different carrier than the one on this statement.

• A data entry discrepancy (e.g., different policy number format).

For each missing policy, you see:

• Client name and policy number

• Policy effective date and carrier

• Last known commission date

• Current policy status in the CRM

Bulk actions let you:

• Mark policies as "Confirmed Cancelled"

• Flag policies for follow-up

• Dismiss false positives

These are statement rows that could not be matched to any existing CRM record. Possible reasons include:

• A new policy that has not been entered into the CRM yet.

• A policy assigned to a different agent in the agency.

• A data mismatch preventing the match (typo in name, different policy number format).

For each unmatched row, you see the raw statement data (client name, policy number, commission amount, etc.).

Discovery is most effective when policy numbers are mapped, as it enables exact matching.

Discovery is designed to be a regular part of your commission reconciliation workflow:

1. Upload and map the statement.

2. Run Apply and Backfill to match and record commissions.

3. Run Discovery to identify what is missing.

4. Investigate gaps — contact carriers about missing commissions, update cancelled policies, or enter new business into the CRM.

5. Re-run after making corrections to verify the gaps have been resolved.

• Statement-level Discovery compares a single statement against the CRM.

• When multiple statements from the same carrier and period are uploaded, the system considers all of them together to avoid false positives.

• Commission Statements Overview

• Apply and Backfill Module

• Payments and Splits Module