Search 800 + Posts

May 17, 2026

Three-way count reconciliation for Employee Conversion ( from Success factor to Oracle HCM)

This post is in continuation to Original Employee Conversion Post When SuccessFactors Stays But Oracle Fusion Arrives  .The three-way count reconciliation is the core component of Stage 5 in the employee conversion process, designed to ensure absolute data consistency across all systems,. It functions by comparing record counts at three independent points, and all three must match before formal sign-off is granted for go-live.

The Three Comparison Points


The reconciliation process measures the following three points:

  • Point 1: Source File
    • Measurement: This is the total record count in the customer-provided flat file as it was originally received.
    • Role: It serves as the baseline for the entire reconciliation; all other counts must reconcile back to this total.
  • Point 2: ATP Staging "LOADED"
    • Measurement: A SQL query is run against the staging tables to count records where the status is set to 'LOADED' for the specific run ID.
    • Expected Outcome: This count must equal the source file count minus any records that were intentionally excluded by the business (which would have an 'EXCLUDED' status),.
  • Point 3: Fusion HCM REST Count
    • Measurement: A direct REST API call (GET /hcmRestApi/resources/11.13.18.05/workers) is made to Fusion HCM using a query parameter to filter by the SourceSystemOwner (e.g., 'SuccessFactors').
    • Role: This provides positive confirmation from the target system itself that the records actually exist in the Oracle environment.

Operational Impact

Any mismatch at any of these three points is considered a critical failure and must be investigated before proceeding. For example, if the ATP staging count shows 4,876 records loaded but the Fusion REST count returns a different number, the migration team cannot grant sign-off.

This count reconciliation is typically documented in a Reconciliation Report, which captures the baseline records, validation errors, and the final three-way match to prove the migration was successful. Following a successful three-way match, a spot-check of 20–30 records is performed in the Fusion UI to verify specific details like hire dates and manager relationships before the final sign-off is documented,.

 #OracleFusion #Conversion,#BizinsightConsulting,#Oracle Fusion Employee #HCM Conversion