Contact SLRIS
For questions that are not about a demo, such as commercial terms or an existing engagement, use the contact page on the SLRIS website.
Contact SLRISRequest a demo
See a payroll comparison demo on your own extracts
A SmartCompaire demo walks through a payroll comparison from first import to graded results. Bring a source and a target extract and a few pay codes, and the demo can use data that looks like yours instead of a generic sample.
Request a demo
SmartCompaire is built by SLRIS Solutions, LLC and is currently in a private beta for SLRIS users. Leave your details below and the SLRIS team will get in touch to arrange a demo. Details such as your source and target systems, and whether it is a payroll or time comparison, help SLRIS plan the session.
Your details go to the SLRIS team, who use them to reply to you.
Other ways to reach SLRIS
Both links below open the SLRIS website in a new tab.
Privacy and your details
What you send with the form above is stored by SmartCompaire for the SLRIS team. A SmartCompaire privacy notice is still being prepared; until it is published, see the SLRIS privacy policy.
SLRIS privacy policyWhat the payroll comparison demo covers
The demo follows the same order as a real project, so you see each step a payroll or implementation team would take.
- Project setup. Creating a payroll or time project and working through its four setup steps: employee mapping, paycode mapping, source pay data and target pay data. Each step takes a file upload, typed rows or rows pasted from a spreadsheet.Learn more
- Imports and error reports. Loading an .xlsx, .xls or .csv export, and seeing how rejected rows are reported with their spreadsheet row number and a plain reason while the good rows are saved.Learn more
- The readiness check. Before a run, how many source and target pay rows will match a mapping, which pay codes are still unmatched and why, and which employees have no mapping yet.
- A comparison run and its results. How each Amount difference is graded against an absolute threshold per Bucket and Bucket code type, how status rules label rows, and how a pay code found on only one side still appears as a result row.Learn more
- Review and follow-up. Setting a status override or comment on a row, raising a defect, recording a known or acceptable difference (KD/AD), and generating a PDF or Excel report.
- Hirra, the in-app assistant. Asking Hirra to summarize a project or explain a run. Hirra is in beta and can make mistakes, so the demo shows where to check the figures it quotes. The data it reads goes to outside AI services.Learn more
What to bring to a SmartCompaire demo
None of this is required; SLRIS can prepare sample data for the session instead. A small slice of your own data makes the session more useful, because the questions it raises are the ones your project will face.
- A source extract and a target extract. Pay results from the old and new system for the same group of employees, as .xlsx, .xls or .csv. Each upload reads the first worksheet only.
- One pay period. A project adds up all the pay data it holds per employee and pay code, rather than comparing period by period, so extracts covering one period are easiest to read.
- A few pay codes on each side. A handful of earnings, deductions and taxes, with the code each one maps to in the other system. A paycode mapping needs a Bucket, a Bucket code type, a source pay code and a target pay code; tax authority codes are optional.
- Employee number pairs. Every employee needs a source-to-target pair, in a two-column list; if the numbers are the same in both systems, the list simply repeats them. A run will not start without employee mappings.
- The tolerances you work to. The difference you would accept per Bucket and Bucket code type, such as a cent on Net Pay. Thresholds are absolute amounts, not percentages.
Preparing demo data safely
Keep demo extracts small and limited to the columns SmartCompaire uses. The pay data template has 15 columns, including Employee #, Tax Auth. Code, PayCode, Number, Rate and Amount, and only PayCode is required on each row.
The template has no columns for employee names, national ID numbers, dates of birth, addresses or bank details, so leave those out of the extracts.
An uploaded file is stored as it was sent, including any extra columns the import ignores. Uploaded files are kept until SLRIS removes them; deleting the demo project removes its database records but not the file itself.
To limit what is kept, use sample data, or remove extra columns and replace real employee numbers with test values used consistently across both extracts.
If Hirra is used in the demo, the data it reads (pay rows, employee numbers, amounts) goes unredacted to OpenRouter and the model provider it picks, with no zero-retention or no-training option set. The demo can skip Hirra or use it on sample data only.
For a time comparison, put hours or units in the Number column. Time projects use the same file layout and comparison logic as payroll; Number differences are recorded but only Amount differences are graded against thresholds.
What happens after you request a demo
You send your details.
The form at the top of this page sends your name, email and anything else you add to the SLRIS team.
SLRIS gets in touch.
SLRIS replies to agree a time and to confirm whether you want to use sample data or extracts of your own.
We run the demo together.
SLRIS loads the data, runs a comparison and goes through the results with you, stopping at whatever matters most to your project.
You decide on next steps.
After the session you have seen how your pay codes, or the sample data, behave in SmartCompaire, which makes the next decision a concrete one.
Frequently asked questions
Can the demo connect directly to our payroll system?
No. SmartCompaire has no live connections to SAP, Workday, Oracle, ADP or any other payroll or time system. All data comes in as exported spreadsheets or CSV files, typed rows or pasted rows, so the demo uses files exported from your systems.
Do we have to share real employee data?
No. SLRIS can prepare sample data for the session. If you bring your own, keep to the template columns and use test employee numbers: uploaded files stay in storage until SLRIS removes them, and data Hirra reads goes to outside AI services.
Does SmartCompaire fix the differences it finds?
No. SmartCompaire finds, grades and records differences, and helps your team track them as defects or known differences. It does not change data in, or write corrections back to, any payroll system.