INFOR LAWSON MIGRATION RECONCILIATION

    Infor Lawson Migration Reconciliation — Framework, Not Spot Checks

    Infor lawson migration reconciliation built into every Fusion load. Four levels: row, sum, business-rule, audit-evidence. Per AU, per process level, per period — drillable to source document. Hospital + higher-ed extensions, SOX + HIPAA + CMS + FFATA grade.

    4 levels
    Reconciliation depth
    100%
    Row-level coverage
    Per period
    CFO sign-off pack
    99.99%+
    Test-pass target

    Why infor lawson migration reconciliation has to be a framework — not a spreadsheet

    A Lawson estate carrying 15 years of GLMASTER history across 60 process levels needs reconciliation infrastructure, not spot checks. Without it, the first month-end close in Fusion exposes every variance the project missed.

    Lawson estates accumulate scale. A typical US hospital network running Lawson since 2005 holds 15+ years of GLMASTER (15–40 million journal lines), 12+ years of APINVOICE (500K–3 million invoices), 10+ years of HRPER worker history (8,000–25,000 active plus terminated workers), and 8+ years of EMDEDMASTR benefit deduction history (often multi-million rows). A higher-ed institution may add 20 years of grants and fund accounting history with attribution rules that change per funding source per fiscal year.

    Spot-checking 100 records of each entity tells you nothing about whether the other 99.99% migrated correctly. Excel-based reconciliation hits row limits within hours of trying to reconcile a single fiscal year of GLMASTER. Manual SQL queries take days to write per check and produce point-in-time outputs that don't survive the next test load. By the time variances surface in finance review, the project has already lost weeks.

    Syntra ETL ships infor lawson migration reconciliation as built-in framework. Four levels (row, sum, business-rule, audit-evidence) run on every test load and every production load automatically. Per-period, per-process-level, per-supplier, per-customer, per-worker reconciliation outputs generate browser-renderable for CFO, HR Director and Supply Chain Director review. Variances surface with drill-down to source document. The evidence pack feeds SOX, HIPAA, CMS, FFATA and state-payroll audit without reconstruction.

    The four reconciliation levels

    1
    Row-level
    Every Lawson source record produced exactly one Fusion record, hash-signed lineage preserved end-to-end, zero silent dropouts. Hash drift caught with field-level diff.
    2
    Sum-level
    Trial balance per AU per period, AP open per supplier, AR open per customer, payroll gross per pay period per process level, inventory value per warehouse — Lawson vs Fusion to the cent.
    3
    Business-rule level
    Fusion intercompany balances, HR effective-date continuity, ELC and COBRA benefits validity, AP three-way match consistency, healthcare 340B attribution preserved, fund balance integrity per higher-ed fund.
    4
    Audit-evidence level
    Signed, timestamped reconciliation packs for SOX (7-yr), HIPAA (6-yr), CMS revenue cycle, state payroll, higher-ed FFATA. Browser-renderable, drillable, exportable for auditor review.

    The reconciliation checks that surface variances spot-testing always misses

    Real variance patterns from hospital and higher-ed Lawson migrations. Each one prevents go-live until cleared.

    📊

    AU range overlap drift

    Lawson AU 1240 mapped to Fusion Cost Centre 1240 — but AU 1240A created mid-period inherited the same mapping, double-counting. Surfaces in per-AU trial balance variance. Critical for hospital networks with many process levels.

    💱

    Per-row penny rounding

    Currency conversion of 250,000 historical AP invoices loses pennies per row. Accumulated $4,200 variance against expected trial balance. Hash totals at row level catch it; aggregate reconciliation alone doesn't.

    👤

    Assignment chain gaps

    Worker A's effective-dated assignment from 2008 to 2019 in Lawson — Fusion shows a one-day gap at the 2014 process-level transfer. ELC compliance violation if missed. HR continuity check catches it.

    💊

    EMDEDMASTR carry-forward

    Benefits deductions that should have ended on termination carrying forward in Fusion. Surfaces as benefits charge variance per pay period per worker. COBRA continuation eligibility breaks if missed.

    🏥

    340B attribution gap

    340B drug flag carried as DFF in Fusion Inventory — but DFF wasn't populated for items where Lawson source value was null. HRSA audit risk if missed. Per-item population check catches.

    🎓

    Grant attribution drift

    Higher-ed grant context preserved on GLMASTER journals — but cross-fiscal-year attribution rule changes weren't applied per period. FFATA reporting variance if missed. Per-grant per-period check catches.

    How infor lawson migration reconciliation runs through the project lifecycle

    Reconciliation runs continuously — not as a single phase. Every test load, every production load, every parallel-run delta.

    1

    Test-Load Cycle 1 — Week 1 of cutover prep

    First full-volume test load runs. Reconciliation surfaces typical 25–40% variance rate (mapping bugs, data quality, configuration drift). Variances classified and assigned to owners. Project tracker established.

    2

    Test-Load Cycles 2–6 — Weeks 2–6

    Iterative test loads. Variance rate trends down each cycle. Mapping bugs fixed, data quality cleanups applied, configuration drift resolved. By cycle 4–5, test-pass rate hits 95%+. CFO + HR Director see the trend in weekly project review.

    3

    Test-Load Cycles 7–10 — Weeks 7–10

    Final test cycles target 99.99%+ pass rate. Edge cases resolved (unusual fiscal years, terminated workers with retro adjustments, suspended POs with hold history). Cutover dress rehearsal completes.

    4

    Production Cutover — Cutover weekend

    Final production load runs the same reconciliation framework on 100% of data. Variances at this stage must be zero before cutover proceeds. CFO + HR Director + Supply Chain Director sign reconciliation packs in real time.

    5

    Parallel-Run Period — Weeks 1–8 post-cutover

    Daily delta extracts from Lawson reconciled against Fusion delta loads. Period-end reconciliation per process level signed off by finance. HR reconciliation per payroll cycle signed off by HR. Parallel-run exits when all periods clear.

    6

    Steady-State Audit — Ongoing

    Signed reconciliation packs preserved for retention period. Replay capability for audit-on-demand: CMS revenue cycle review, HIPAA covered-data audit, HRSA 340B review, FFATA grant reporting — all driven from preserved evidence without reconstruction.

    What the reconciliation engine produces — per period, per productline, signed and timestamped

    Browser-renderable reconciliation packs that finance, HR, supply chain and audit teams actually use.

    📒

    Finance pack

    Lawson trial balance per AU per period vs Fusion Trial Balance. AP aging per supplier. AR aging per customer. Journal count per period. Drillable to source GLMASTER / APINVOICE / ARCUST record. CFO signs.

    👥

    HR pack

    HRPER active/terminated worker counts vs Fusion HCM. Assignment continuity per worker. Payroll gross per pay period per process level. EMDEDMASTR deductions per worker. HR Director signs.

    📦

    Supply chain pack

    INVMASTER on-hand per warehouse per item vs Fusion Inventory on-hand. PURCHORDER open count and value. Supplier balances. 340B attribution per item. Supply Chain Director signs.

    🏥

    Hospital extension pack

    340B attribution, GHX integration history, patient charge linkage, Joint Commission evidence, HIPAA Access Log. Hospital Internal Audit signs.

    🎓

    Higher-ed extension pack

    Grant attribution per period, F&A indirect cost recovery, student employment flag, fund balance integrity per fund, FFATA reporting evidence. University Controller signs.

    🔍

    SOX evidence pack

    Migration completeness (no silent dropouts), translation defensibility (S2T per period), access control (full audit log). Big 4 audit teams accept without follow-up.

    Frequently asked questions

    What is infor lawson migration reconciliation?+

    Infor lawson migration reconciliation is the structured proof — produced for every load, every period and every Lawson productline — that the data migrated from Lawson S3 into Oracle Fusion is complete, accurate and traceable. It runs at four levels: row-level (every Lawson GLMASTER / APINVOICE / ARCUST / HRPER / EMDEDMASTR / INVMASTER row produced exactly one Fusion record with hash-signed lineage), sum-level (Fusion trial balance matches Lawson per AU per period to the cent, AP aging matches per supplier, payroll gross matches per pay period per process level), business-rule level (Fusion intercompany balances, HR effective-date continuity, benefits enrollment validity per ELC and COBRA), and audit-evidence level (signed reconciliation packs for SOX, HIPAA, CMS, FFATA — drillable to source document). Syntra ETL ships infor lawson migration reconciliation built-in; it's not a separate workstream you have to scope.

    Why does infor lawson migration reconciliation need a framework, not just spot checks?+

    Spot checks fail the audit bar. A Lawson estate running since 2002 in a US hospital network typically holds 15+ years of GLMASTER (15–40 million journal lines), 12+ years of APINVOICE (500K–3M invoices), 10+ years of HRPER worker history (8,000–25,000 active plus terminated workers), and 8+ years of EMDEDMASTR benefit deduction history (multi-million row table). Spot-checking 100 records of each tells you nothing about whether the other 99.99% migrated correctly. Variances surface late, finance loses confidence, the project slips. A reconciliation framework runs continuously on 100% of data, produces structured outputs per period and per process level, surfaces variance with drill-down to source, and feeds the audit evidence pack without manual reconstruction.

    What are the four levels of infor lawson migration reconciliation?+

    Level 1 — row-level: every Lawson source record produced exactly one Fusion record, hash-signed lineage preserved end-to-end, zero silent dropouts. Level 2 — sum-level: trial balance per Lawson AU per period reconciled to Fusion to the cent, AP open per supplier reconciled, AR open per customer reconciled, payroll gross per pay period per process level reconciled, inventory value per warehouse reconciled. Level 3 — business-rule: Fusion intercompany balances, HR effective-date continuity (no gaps in assignment history), benefits enrollment validity per ELC and COBRA, AP three-way match consistency, healthcare-specific 340B drug attribution preserved. Level 4 — audit-evidence: signed, timestamped reconciliation packs for SOX (7-yr retention), HIPAA (6-yr retention), CMS revenue cycle, state payroll (varies 4–6 yr), higher-ed FFATA grant reporting. All four levels run on every load.

    How is infor lawson migration reconciliation handled for healthcare-specific data?+

    Healthcare reconciliation extends the standard four levels with hospital-specific checks. (1) 340B drug attribution: every Lawson INVMASTER item flagged for 340B preserved in Fusion Inventory DFF with attribution log intact; 340B audit teams require this for HRSA review. (2) GHX integration history: GHX-sourced supplier exchange transactions in Lawson preserved with full transaction ID lineage into Fusion Procurement; GHX reconciliation runs continuously. (3) Patient charge linkage: Lawson AR linked to patient accounting (Epic / Cerner / MEDITECH charge interface) reconciled per encounter for revenue-cycle audit. (4) Joint Commission evidence: any Lawson activity log entry relevant to JC accreditation preserved. (5) HIPAA covered-data inventory: every HRPER, dependent, EMDEDMASTR record containing PHI reconciled with HIPAA Access Log evidence. Hospital Internal Audit signs off the healthcare reconciliation pack.

    How does the infor lawson migration reconciliation framework handle higher-ed data?+

    Higher-ed reconciliation extends with grant-and-fund-accounting-specific checks. (1) Grant attribution: every Lawson GLMASTER journal carrying grant context preserved into Fusion with attribution to Fusion Grants Management; FFATA reporting reconciliation runs per grant per period. (2) F&A indirect cost recovery: indirect cost rate applications per project per period reconciled Lawson vs Fusion. (3) Student employment: HRPER worker records flagged as student employment migrated to Fusion HCM with student worker flag preserved; reconciliation per term per pay period. (4) Sponsored research compliance: time-and-effort certification evidence preserved per faculty per quarter. (5) Fund balance integrity: per-fund Lawson fund balance reconciled to Fusion ledger fund balance per period. University Controller signs off the higher-ed reconciliation pack.

    Can infor lawson migration reconciliation surface mid-project before cutover?+

    Yes — and this is one of its primary purposes. Through cutover prep (typically 6–10 test-load cycles), reconciliation runs on every test load. Variances surface immediately, get classified (mapping bug, data quality issue, system limitation, configuration drift), get owner-assigned, and get tracked to closure. The test-pass rate trends from typically 60–75% on the first test load to 99.99%+ before final cutover. CFO, HR Director and Supply Chain Director see the trend in weekly project reviews and gain confidence iteratively. By the time final cutover runs, there are no surprises — the reconciliation pattern has been proven on full-volume test data multiple cycles in advance.

    How does infor lawson migration reconciliation integrate with Fusion ESS job monitoring?+

    The reconciliation engine integrates directly with Fusion ESS via REST API to monitor every FBDI batch, HDL load, and import job. ESS job submission produces an immediate handshake record (job submitted, request ID, parameters). Job completion produces a result record (rows accepted, rows rejected, error file location). The reconciliation engine pulls these automatically, correlates with the source extract, and produces a per-job reconciliation: Lawson source rows → Fusion ESS rows accepted → variance with row-level error detail. Failed rows get routed to a fix queue with the exact reason. The next test load picks up the fixes automatically. This integration means no manual ESS monitoring, no missed errors and no surprise failures.

    What evidence does infor lawson migration reconciliation produce for SOX audit?+

    Three SOX-specific evidence artifacts. (1) Migration completeness: signed reconciliation showing every Lawson GL journal landed in Fusion or routed to retained archive with documented business reason; no silent dropouts. (2) Translation defensibility: signed source-to-target documentation showing how every Lawson account, AU, sub-account translated to Fusion COA segments; CFO sign-off per period. (3) Access control: full audit log of every read-access to financial data during the migration, every transformation applied, every signoff captured. Big 4 audit teams routinely accept these three artifacts as the migration evidence pack without follow-up requests. Customers reduce SOX audit effort post-migration by 40–60% because the evidence is structured and queryable rather than scattered across email and spreadsheets.

    Make infor lawson migration reconciliation a framework, not a spreadsheet

    Book a 30-minute walkthrough. We'll show you the four-level reconciliation framework running on a sample Lawson dataset, walk through the per-period CFO + HR Director sign-off packs, and scope it into your migration plan.