One count, reconciled across two systems.
The old SQL database and the new-system masterlist are matched by registration ID, deduplicated, and evaluated with the new system taking precedence for current status.
Category comparison
Old and new counts shown side by side; true count is deduplicated
| Category | Old | New | True reconciled | Difference |
|---|
Registration crosswalk
Search every verified registration identity and compare its old and new status
| Registration ID | Category | Comparison | Old status | New status | Current approved | Historical approved | Old label transactions | New label evidence |
|---|
Label control-number audit
Product control numbers are counted once; distinct later label control numbers are renewals
| Product control number | Label control number | System | Category | Issue date | Classification | Sequence | Reason |
|---|
Product application export
One workbook containing the complete old-system and new-system application lists.
Separate Old Applications and New Applications sheets preserve product control numbers, statuses, dates, source rows, and duplicate/invalid-ID flags.
Data-quality exceptions
Kept outside the verified totals until corrected
Counting rules
The definitions used for the reconciled totals
Count one record per valid product registration control number across both systems.
Use the new status for overlapping controls, then include approved old-only controls.
Include Approved and Registered, *Approved and Registered, and Phased-Out Product.
Count each product control number once. A later distinct label control number under the same product is a renewal, not another product.
The same label control number repeated in multiple rows is a true duplicate row and is excluded.