ERP Modernization · October 27, 2026 · 6 min read
Before the first live payroll: a parallel-test checklist for Munis/EERP
Plan a municipal payroll parallel test with matched inputs, employee-level gross-to-net comparisons, reconciled postings, assigned reviewers and a recorded cutover decision.
By Altioras Civic
Key takeaways
- Use the same approved payroll inputs and identify any deliberate differences before comparing results.
- Reconcile by employee and pay component, then check deductions, leave, payment outputs and Finance postings.
- Assign every variance, retest corrections and record the agency's acceptance decision before the first live payroll.
Start with the pay run staff will have to approve
The parallel payroll finishes, and the total net pay looks close to the old system. Payroll still has unexplained differences for employees with overtime, benefit changes or unpaid leave. Finance has not checked the posting. A matching headline total cannot resolve those questions.
A payroll parallel test processes the same agreed pay-period inputs in the current system and the proposed configuration, then compares the results with approved expectations. The current system is a comparison point; staff must investigate any known errors or intentional rule changes before treating its output as correct.
Tyler describes Enterprise ERP as powered by Munis. This checklist addresses municipal payroll acceptance in that product context. Confirm the actual release, modules, interfaces and reporting available in your environment with the implementation team. The steps below do not assume particular screens or a universal test-cycle count.
Sources: Tyler Technologies — Enterprise ERP, powered by Munis
Agree the inputs and expected results before the run
Record the pay period, payment date, employee population and source cutoff. Save the approved time entries, personnel changes, pay rates, deduction elections and opening balances used for the comparison. Identify any changes entered after the extract so they can be explained or applied consistently.
Build a scenario list from the municipality's employee groups and payroll rules. Include relevant salaried and hourly employees, overtime or shift premiums, mid-period changes, new hires, terminations, leave and deduction exceptions. Select cases that exercise the rules; do not rely on one uncomplicated employee from each department.
Payroll and HR should approve the expected treatment using current agency policy, agreements and applicable requirements. Have the appropriate specialist confirm jurisdiction-specific calculations. Record each expected amount or balance and its calculation basis before reviewing the new output.
Use an employee-level comparison worksheet
Use these checks as a starting worksheet. Add the test reference, expected result, actual result, difference, owner and retest status. Review complete population and control totals alongside detailed employee comparisons. A sample that exercises a rule does not establish that every converted employee record is correct.
| What to check | Records to compare | Responsible reviewer |
|---|---|---|
| Population and time | Approved employee roster and time inputs against included employees, hours and earning codes in both runs. | Payroll with department time approvers |
| Gross earnings | Approved rates, hours, effective dates and scenario calculations against earnings by employee and pay component. | Payroll; HR confirms personnel changes |
| Deductions and contributions | Approved elections and current rules against employee deductions and employer contributions, including exceptions. | Payroll and benefits or specialist reviewer |
| Net pay | Gross-to-net calculation and employee detail against payment totals; explain differences before acceptance. | Payroll reviewer designated by the agency |
| Leave and opening balances | Approved opening balances and period activity against closing leave and year-to-date balances where in scope. | HR and Payroll |
| Payment outputs | Approved test payroll register against test payment-file counts, amounts and required identifiers. | Payroll and Treasury |
| Finance posting | Payroll summaries and liabilities against the test posting by fund, account and cost allocation. | Finance |
| Exceptions and corrections | Original failed scenario, approved correction and rerun against the expected result and affected control totals. | Issue owner and original acceptance reviewer |
Trace each difference to an assigned correction
Begin with employee inclusion, hours, rates and effective dates. If gross earnings agree, compare the deductions, contributions and other components that produce net pay. Check leave and year-to-date values separately; those balances may affect later periods even when the current payment looks right.
Illustrative example: two employees have offsetting earnings differences because one shift was assigned to the wrong earning code. The payroll total agrees, but neither employee's result is acceptable. Compare approved time, earning codes and expected premiums for each employee before changing configuration.
Record the cause and the authorized correction. It may be a source-data issue, mapping, configuration, policy interpretation or test-input mismatch. Preserve the original comparison, identify the changed setup or data, and rerun affected scenarios. Reconcile the revised control totals so a correction has not introduced another difference.
From parallel run to payroll acceptance
- Step 1Freeze the inputsRecord the period, population, cutoff and approved changes.
- Step 2Run the comparisonUse matched inputs and approved expected results.
- Step 3Explain differencesCompare employee detail, balances and postings.
- Step 4Correct and retestAssign the cause, authorize the change and rerun.
- Step 5Record acceptanceReview remaining issues before authorizing cutover.
Test the payment and posting handoffs
Payroll acceptance also needs the outputs that Treasury and Finance will use. Compare test payment totals and record counts with the approved test register. Confirm the bank or payment provider's approved validation process, including how test files are identified and kept out of live payment processing.
Have Finance inspect the test journal and liabilities using the agreed fund, account and cost-allocation mappings. Check employer costs as well as employee withholdings. Where another system receives time, benefits or retirement information, include that handoff and its rejected-record process in the test plan.
The Washington State Auditor's Payroll Guide discusses review of payroll reports, reconciliation and separation of responsibilities. Apply those control principles through your municipality's adopted review and approval arrangements; its examples are not a substitute for local requirements.
Sources: Office of the Washington State Auditor — Payroll Guide, pages 6–7, 12–14 and 16
Use AI to draft missing scenarios for staff review
A separately approved AI tool can propose additional tests from approved payroll requirements and a de-identified scenario list. Ask it to flag requirements without a corresponding scenario and suggest starting conditions and expected outputs to review.
Payroll checks the suggestions against known exceptions and approved rules, then decides which tests to add. Staff calculate and approve monetary expectations independently. Reject invented rates, deduction rules or eligibility conditions. Do not provide employee banking details, tax identifiers or unapproved personnel records.
The accepted output is a reviewed test matrix. This is a proposed use of an external tool, not a claim that Munis/EERP automatically performs the analysis or approves payroll.
Make the first live payroll a recorded agency decision
Before cutover, give the authorized decision makers the completed comparison, unresolved-issue list, retest results and payment/posting checks. State which employee groups and rules were exercised, what remains untested and how each open item could affect pay or reporting.
Set acceptance criteria before the final review. Do not introduce a percentage tolerance late in testing to clear unexplained employee-pay differences. Any accepted difference needs an explanation, the appropriate approval and a recorded disposition. If a critical condition remains unmet, use the agency's decision process to defer cutover and confirm the approved continuity plan.
GFOA recommends documenting financial procedures and assigning responsibility and authority. Carry the accepted payroll procedure, review assignments and first-run support contacts into handover so staff can execute the next cycle.