Tyler Technologies Data Validation — Row, Count, Sum, Hash — Source vs Fusion

Tyler Technologies data validation is the post-load reconciliation workstream that proves — at row, count, sum and hash level — that every Munis, Eden, iNovah, Energov, Brazos and Courts Odyssey object landed in Oracle Fusion exactly as it sat in the source. The reconciliation runs across fund accounting (trial balance by fund + control account), position control (active position count, FTE, encumbered budget), Courts case-financial-obligations (open AR by case-type), Energov permit-fee revenue, iNovah cashiering totals, payroll register (gross, net, every deduction code, every benefit deduction, every garnishment), W-2 / W-3 totals, 1099 vendor totals, fixed asset register (acquisition cost, accumulated depreciation, net book value), open encumbrances and PO commitments, and grant project-cost tie-out. Tyler Technologies data validation completes before parallel-run begins and is signed by County CFO, Clerk of Court, HR Director and external auditor.

Fund accounting reconciliation is the highest-stakes workstream in any Tyler Technologies data validation. The reconciliation engine compares the Munis trial balance by fund at period-end (General Fund 100, Special Revenue Funds, Capital Projects Funds, Enterprise Funds, Internal Service Funds, Permanent Funds, Fiduciary/Pension Funds) against the Fusion Public Sector Financials trial balance by fund at the same period-end. Every fund-level reconciliation includes: opening balance, period activity, closing balance, inter-fund transfer-in and transfer-out, control-account tie-out, GASB 34 fund-level + government-wide reconciliation, and the period-end close evidence pack. Variances at the cent level are flagged for investigation; variances at the round-dollar level trigger root-cause analysis and remediation before sign-off. The external auditor walks through the Tyler Technologies data validation pack as the first audit-walkthrough of the new Fusion environment.

Position control + payroll reconciliation is the second highest-stakes workstream in any Tyler Technologies data validation — and the most likely surface for union grievances if it lands incorrectly. The reconciliation engine compares the Munis Position Control snapshot at cutover (every active and frozen position, FTE, encumbered budget, step/grade, union code, civil service class) against the Fusion HCM Position Management snapshot at the same cutover. Every union-by-union reconciliation pack is produced for the HR Director and union business agent walkthrough. Payroll register reconciliation compares the last Munis payroll run (gross, net, every deduction code, every benefit deduction, every garnishment) against the first parallel Fusion payroll run — to the cent. W-2 / W-3 year-to-date totals are reconciled at calendar-year boundaries. 1099 vendor totals are reconciled at calendar-year boundaries. Retirement-system contribution totals (PERS, NYSLRS, local pension boards) are reconciled against state-reporting submissions.

Yes — Courts case-financial-obligation reconciliation is a dedicated workstream in any Tyler Technologies data validation where Courts Odyssey is in scope. The reconciliation engine compares the Odyssey open-AR snapshot at cutover (every active case with outstanding fines, fees, restitution, court costs, child-support orders) against the Fusion AR snapshot at the same cutover, grouped by case-type (felony, misdemeanor, civil, family, probate, juvenile, traffic, ordinance) and by court division. Case-number cross-reference is preserved end-to-end so collection workflows continue uninterrupted. Sealed and juvenile case-financial-obligations are reconciled in the CJIS-compliant partition with expungement-aware access. Clerk of Court signs the Tyler Technologies data validation pack as the first court-administration walkthrough of the new Fusion AR + Odyssey-integration environment.

Energov + Citizen Self-Service reconciliation covers the revenue-side surfaces of any Tyler footprint where Community Development is in scope. The Tyler Technologies data validation reconciles Energov permit-fee revenue, code enforcement fines, business license fees and contractor registrations against the Fusion AR landing, with parcel-ID and citizen-name cross-reference preserved end-to-end. iNovah cashiering totals (utility payments, tax payments, parking citations, permit fees, court fines) are reconciled at the daily-deposit-ticket level. Citizen Self-Service portal payment-history reconciliation compares pre-cutover Tyler portal payment history against the post-cutover archive + new portal access. DNS-level redirects from old Tyler URLs to the new portal are tested with synthetic citizen lookups before parallel-run begins.

Attached binaries reconciliation is the most under-appreciated workstream in any Tyler Technologies data validation — and the single largest source of post-cutover surprises if it is skipped. The reconciliation engine compares the source-side attachment inventory (every Munis HR W-4 / I-9 / direct-deposit form, every Energov permit site plan / inspector signature, every Odyssey case filing / court order / sealed exhibit, every recorded deed / mortgage / lien image, every iNovah signed deposit ticket) against the target-side archive partition with hash-signed evidence per file. Volume is significant: counties commonly carry 5–40 TB of attached binaries across their Tyler footprint. The Tyler Technologies data validation pack documents the full inventory, the hash-signed evidence per file, the chain-of-custody log, and the CJIS-compliant access controls on sealed/juvenile binaries.

The Tyler Technologies data validation evidence pack handed to the external auditor (typically a regional CPA firm conducting the GASB-aligned annual audit) contains: the trial balance reconciliation by fund at cutover period-end (source vs target, opening + activity + closing + control-account tie-out); the inter-fund transfer reconciliation; the GASB 34 fund-level + government-wide reconciliation; the position-control reconciliation by union and bargaining unit; the payroll register reconciliation (gross, net, every deduction code); the W-2 / W-3 and 1099 year-to-date reconciliations; the open-encumbrance and PO-commitment reconciliation; the grant project-cost tie-out for every federal grant under Uniform Guidance 2 CFR 200.334; the fixed asset register reconciliation; the Courts case-financial-obligation reconciliation; and the attached binaries inventory with hash-signed evidence. Auditors uniformly report a 40–60% reduction in audit fieldwork hours when the Tyler Technologies data validation pack replaces ad-hoc tenant queries.

Tyler Technologies data validation runs in parallel with the load workstream and completes 1–3 weeks after the final load — typical timeline 3–5 weeks total. The reconciliation engine runs automated row-count, sum and hash checks on every loaded object on the same day the load completes; cent-level variances are flagged for investigation on the same day; round-dollar variances trigger root-cause analysis and remediation cycles. The Tyler Technologies data validation pack is signed by seven accountable parties before parallel-run begins: County CFO for fund accounting; budget office for encumbrance and PO carryover; external auditor for GASB compliance; HR Director for position control + payroll; union business agents for bargaining-unit-specific payroll; Clerk of Court for Courts case-financial-obligation reconciliation; CIO for integration tie-outs. Parallel-run does not begin until every signature is in.