How to Perform an End-to-End Test
Purpose:
End-to-end testing confirms that time data can successfully move from your source system into HCM TradeSeal, pass through the key validation steps, and reach your payroll system in the correct format.
This test does not require detailed payroll audits, overtime tuning, or reconciliation. Instead, it focuses on confirming that the data flows correctly from start to finish.
✅ Step 1: Import or Enter Hours
Use one of the following methods:
- Upload time data via the Source Upload screen
- Manually enter hours directly into the Cost Entry screen
💡 Tip: Choose a simple test file or a limited set of employees to start.
✅ Step 2: Review Hours in Rate Validation
- Go to the Rate Validation screen
- Confirm that all imported or entered hours appear correctly
- Make sure positions and classifications are mapped correctly
This step verifies that HCM TradeSeal successfully received and understood the time data.
✅ Step 3: Export the Payroll File
- From the Rate Validation screen, use the Export Payroll File function
- Note: if you are on a staging instance of HCM TradeSeal, you will need to ask your TradeSeal implementation team for a copy of the payroll export file rather than downloading.
- Select the appropriate payroll format for your system
- Save the file locally
This file represents your gross payroll as calculated by HCM TradeSeal.
✅ Step 4: Import to Your Payroll System
- Log into your payroll system
- Import the file using the standard import function
- Confirm that the import completes without errors
💡 You’re not reviewing every number here—just verifying the full file successfully makes it from HCM TradeSeal into payroll.
What End-to-End Testing Is Not
This process does not include:
- Verifying net pay or tax calculations
- Reviewing overtime details line-by-line
- Comparing pay stubs or GL results
- Any formal “parallel testing”
Those steps come later, once you’ve confirmed that the data pipeline is working.
Need Help?
If the data doesn’t appear as expected in any step, reach out to our support team. Please include:
- A copy of the original test file
- A screenshot of the issue
- A brief description of where the process failed
We’ll help you troubleshoot and get back on track.