Purpose-built infor baan migration reconciliation across row, sum and business-rule levels. tdord/tcorda/tfgld reconciled per t_fcom per period, HGB+IFRS dual-GAAP packs per legal entity, BSE attachment hash-matched, parallel-run continuous, archived for SOX 7-year + HGB 10-year + ITAR/DFARS retention.
Consultant-led BaaN-to-Fusion programmes typically leave reconciliation to the end. The team runs the FBDI loads, declares them complete, and only at sign-off does the auditor ask for the trial-balance reconciliation per legal entity per period per HGB and IFRS ledger. By then it is too late to reconstruct.
BaaN customers carry 15–25 years of history in tfgld, tfacp, tfacr, tdsls, tdpur, tibom and the rest of the 3,500+ table catalog. A single European manufacturer with 8 legal entities and dual-GAAP HGB+IFRS reporting typically has 16 ledger streams (8 legal entities × 2 ledger streams), each carrying 25 years × 12 periods = 300 fiscal periods. The reconciliation matrix is 16 × 300 = 4,800 cells per data object. Multiply across GL, AP, AR, Fixed Assets, Inventory, Production WIP. Reconstructing this retrospectively at sign-off is impossible inside any reasonable runway against the 2030 Infor sustaining-end deadline.
Syntra ETL's infor baan migration reconciliation framework is continuous-by-design. Every record extracted from BaaN is hashed at source. Every record loaded into Fusion is re-hashed post-load. Sum-level reconciliation runs per ledger per period per legal entity automatically on each load cycle. Business-rule integrity checks (debit/credit balance, AP aging reasonableness, inventory perpetual non-negative, BOM quantity sanity) run on each load. Every variance is captured with full context and triaged in-cycle — not stockpiled for retrospective batch resolution.
When the external auditor arrives at sign-off, the reconciliation pack is already complete. BaaN trial balance per HGB ledger reconciled to Fusion HGB ledger per legal entity per period, to the cent. BaaN trial balance per IFRS ledger reconciled to Fusion IFRS ledger per legal entity per period, to the cent. AP/AR aging reconciled at customer/supplier/BU level. Fixed-asset NBV reconciled per asset category per legal entity. Inventory perpetual reconciled per warehouse per item. BSE attachment counts and hash signatures reconciled per source object. Auditor signs in days, not weeks.
Each suite runs per load cycle through the migration, daily during parallel-run, and at final cutover sign-off. Each produces a signed pack archived for the full retention period.
Debit and credit per account per period per legal entity reconciled to BaaN tfgld with HGB ledger filter. Auditor-signed pack per legal entity. §13b reverse-charge handling preserved.
Debit and credit per account per period per legal entity reconciled to BaaN tfgld with IFRS ledger filter. IFRS 16 lease right-of-use, IFRS 9 financial-instrument treatments preserved.
Open AP per supplier per BU per aging bucket reconciled to tfacp. Match-key: supplier VAT-ID + invoice number + currency. Variances grouped by root cause with disposition.
Open AR per customer per BU per aging bucket reconciled to tfacr. Disputed-status preserved. Reverse-charge tax treatment validated per intra-EU B2B flow.
Net book value per asset category per legal entity reconciled to tffam. German AfA preservation validated. IFRS componentization reconciled separately per IFRS ledger.
On-hand quantity and value per warehouse per item reconciled to whinp. Costing method consistency (FIFO/LIFO/standard/average) validated. Lot/serial preservation for FDA/ITAR environments.
WIP quantity and value per work centre per production order reconciled to tipcs. Routing operation state preserved. Material issue and labour confirmation totals validated.
Per-attachment SHA-256 hash from BaaN BSE archive vs Fusion UCM landed state. Count comparison per source-object (invoice, PO, deliverable). Missing attachments flagged for re-extract.
A repeatable workflow that runs from initial load through parallel-run through final cutover sign-off. Every cycle produces signed audit-grade evidence.
Trial balance, AP/AR aging, fixed-asset NBV, inventory perpetual, WIP, attachment hash signatures all reconciled per legal entity per period. Variances triaged and dispositioned before next load cycle.
Each variance categorized by root cause: data quality (fix in BaaN), crosswalk gap (refine mapping book), Fusion config (extend lookups), timing (re-run period). Fix applied. Partition re-loaded. Reconciliation re-runs.
Full historical reconciliation pack issued per legal entity per ledger per period (HGB + IFRS). CFO and external auditor review. Material variances resolved. Sign-off triggers move into parallel-run.
Every BaaN delta hash-matched against Fusion landed delta daily via CDC + Exchange Scheme subscription. Daily report to finance / supply chain / manufacturing leads. Anomalies investigated same-day.
Full reconciliation pack per legal entity per ledger for the month-end close. AP/AR aging, inventory, WIP, fixed-asset NBV all reconciled. Variance triage and disposition. Signed by CFO + auditor.
Final hash-signed reconciliation pack archived alongside BaaN cloud archive. Mapping book version, executable crosswalk version, auditor signatures all bundled. Retrievable for full 10-year retention period.
The hash-signed evidence pack that satisfies SOX 7-year, HGB 10-year, IFRS and ITAR/DFARS audit requirements.
Per legal entity per period per ledger (HGB and IFRS separately). Opening balance, period activity per account, closing balance. Reconciled to the cent. Auditor signature page per pack.
AP and AR aging per supplier/customer per BU per aging bucket. Match-key methodology documented. Variances grouped by root cause with disposition note. Auditor-signed.
Net book value per category per legal entity. German AfA depreciation preservation. IFRS componentization per IFRS ledger. Asset retirement and transfer history reconciled.
Inventory perpetual per warehouse per item, production WIP per work centre per order, costing method consistency, lot/serial preservation log for FDA/ITAR environments.
Per-partition hash signatures from extract + landed states. Per-attachment hash signatures from BSE archive + Fusion UCM. Hash-match percentage per object. Anomaly trace per row + field.
Mapping book version, executable crosswalk version, validation diagnostic log, export-control sign-off (ITAR/DFARS), all auditor signature pages — bundled and archived with the data per legal entity.
Infor baan migration reconciliation is the structured framework that proves — to the cent, with hash-signed evidence, for every legal entity per ledger per period — that the data landed in Oracle Fusion matches the data extracted from BaaN. It runs at three levels (row hash-match, sum reconciliation, business-rule integrity), produces signed reconciliation packs per object per legal entity per period, and provides auditor-grade evidence chains that satisfy SOX, German HGB §257, IFRS and ITAR/DFARS requirements. Syntra ETL's infor baan migration reconciliation engine is continuous-by-design — not a single post-migration spreadsheet — and it covers all 3,500+ BaaN tables across Finance (tfgld, tfacp, tfacr, tffam), Distribution (tdsls, tdpur, tcorda), Manufacturing (tisfc, tibom, tipcs), Warehousing (whinp, twhinr) and Project (tppdm).
Validation answers 'did each record load correctly?'. Reconciliation answers 'do the totals roll up to the same answer in both systems?'. They are complementary, not substitutes. The Syntra ETL infor baan migration reconciliation framework runs both: validation catches per-record issues at field and row level (range checks, lookup constraints, hash mismatches), while reconciliation rolls totals up to trial-balance, AP/AR aging, inventory perpetual, fixed-asset NBV and production WIP levels — per legal entity, per ledger (HGB and IFRS streams), per fiscal period. A clean validation pass with a failing trial-balance reconciliation usually means a crosswalk gap (e.g., a dimension value not mapped); a failing validation pass with a clean reconciliation usually means a rounding artefact that auditors accept.
European customers running BaaN with parallel HGB (German statutory) and IFRS ledger streams need each stream reconciled separately. The Syntra ETL infor baan migration reconciliation engine produces per ledger per legal entity per fiscal period: trial balance (debit/credit totals per account), opening balance carry-forward, closing balance, period activity per account. Separate packs per ledger stream. GAAP-only postings (IFRS asset componentization, HGB accelerated depreciation, IFRS lease right-of-use under IFRS 16, HGB §253 valuation adjustments) reconciled within their respective ledger. The cross-GAAP reconciliation summary identifies the explained deltas (timing, treatment, scope differences) and ties out to the consolidation worksheet. External auditor signs each ledger pack separately.
Most European BaaN customers run 5–15 t_fcom (financial companies) consolidated into 1–3 t_lcom (logical companies). The Syntra ETL infor baan migration reconciliation framework reconciles at each layer: per t_fcom trial balance to its Fusion legal entity ledger, per t_lcom roll-up to the Fusion consolidation ledger. Intercompany eliminations preserved and reconciled separately. Where multi-company harmonization collapsed overlapping vendor codes or cost-centre codes during migration, the harmonization log is part of the reconciliation pack — auditor traces from the consolidated total back through the harmonization decisions back to the original BaaN t_fcom posting. Multi-currency conversions reconciled per currency per legal entity using the loaded exchange-rate history.
BaaN's BSE archive holds binary attachments (drawings, contracts, vendor docs, customs filings) referenced from operational records. The Syntra ETL infor baan migration reconciliation framework reconciles attachment counts per source-object (every tfacp invoice with attachments, every tdpur PO with attachments, every tppdm project deliverable with attachments). Each attachment is hashed at source (SHA-256 of the binary content), re-hashed at the Fusion UCM landed state, and the hash-match percentage recorded. Missing attachments are flagged for re-extraction. The reconciliation pack includes the per-object attachment count comparison and the hash-match percentage — auditor evidence that every BaaN binary record landed in Fusion UCM with the original content intact and the BaaN reference preserved as searchable metadata.
During the parallel-run window (typically 2 month-end cycles), BaaN continues taking transactions and Fusion takes the same transactions via the data feed. The Syntra ETL infor baan migration reconciliation engine runs continuous daily reconciliation: every BaaN delta (via Oracle LogMiner / MS-SQL CDC / Informix logging plus BaaN Exchange Scheme subscriptions) is reconciled against the Fusion landed delta. Daily reconciliation reports go to finance, manufacturing and supply chain leads. Month-end produces the full reconciliation pack: trial balance per ledger per legal entity, AP/AR aging, inventory perpetual, production WIP — all reconciled to the cent. The parallel-run sign-off is the trigger to cut production transactions to Fusion and move BaaN to read-only archive mode.
Material variances block sign-off. The Syntra ETL infor baan migration reconciliation engine surfaces every variance with full context: the legal entity, the ledger, the period, the account, the source BaaN posting reference, the expected Fusion landed value, the actual Fusion landed value, the diagnostic explaining the mismatch. Variances are triaged by root cause: data-quality issue at source (fix in BaaN before next delta extract), crosswalk gap (refine the mapping book and re-version), Fusion configuration mismatch (extend Fusion lookup sets or COA values), timing artefact (period boundary issue resolved by re-running the affected window). Each fix re-runs the reconciliation on the affected partition. Immaterial variances are logged with a documented business-acceptance decision and accepted in the sign-off pack.
Migration reconciliation closure does not end the obligation. SOX requires 7 years of audit trace. German HGB §257 demands 10 years. IFRS adds harmonization requirements. ITAR/DFARS retention runs 5–7 years for defence-controlled records. Once cutover is complete and BaaN moves to read-only archive mode, the Syntra ETL infor baan migration reconciliation pack — hash-signed trial balances per ledger per legal entity, AP/AR aging, inventory, WIP, fixed-asset NBV, attachment hash matches, mapping book version, crosswalk version, auditor signatures — is archived alongside the BaaN cloud archive. Queryable for the full retention period. When the auditor returns three years later asking for the BaaN-to-Fusion bridge for fiscal 2026, the pack is retrievable in seconds with every signature intact.
Book a 30-minute discovery call. We'll walk through your in-scope BaaN modules, multi-company HGB+IFRS profile, fiscal period cadence, BSE archive scope and auditor sign-off requirements — and confirm a concrete reconciliation plan before the call ends.