Purpose-built dynamics gp historical reporting against a cloud archive of Great Plains data. SmartList semantic mirror, multi-company federated query, SOX trace report family, sub-second response. Finance, audit, tax and HR get their history without firing up GP.
Finance, audit, tax and HR need the same kinds of historical lookups they have always run from GP — but without the cost, the contention or the dependency on an aging on-prem environment.
Great Plains shops have decades of muscle memory built around SmartList Builder queries, Crystal/SSRS reports, FRx financial statements and Excel pivots tethered to live SQL views. When the GP system gets decommissioned (or shrinks to a minimal footprint after Fusion goes live), all of that muscle memory still needs to function. The finance team still has to compare current-year results to four-year-ago results. The auditor still asks for vendor history substantiating a 2021 expense. The tax accountant still needs vendor 1099 detail across the last seven tax years. Former employees still ask for replacement W-2s.
Dynamics gp historical reporting replaces the live-GP path with a cloud-archive path that delivers the same query semantics, the same business answers, and a far better user experience. Queries that crawled in GP run in seconds. Multi-company queries that required separate connection strings and union-all SQL run federated by default. SOX trace reports that required a Dexterity-savvy consultant run self-serve from the audit UI.
Syntra ETL ships dynamics gp historical reporting as a packaged product on top of the dynamics gp data archival foundation: cloud Parquet archive, SmartList semantic mirror, federated multi-company query layer, packaged report families for financial statement re-run, subledger aging at point-in-time, vendor/customer history, tax substantiation and SOX trace. The archive remains queryable for the full IRS Pub 583 7-year retention window — and beyond, if your retention policy requires it.
The capabilities Syntra ETL ships pre-built so finance/audit/tax can self-serve historical query day one.
Familiar SmartList query shape (column picker, filters, grouping, sorting) executed against the cloud archive. Existing SmartList exports imported and validated against GP output during onboarding.
Trial balance and financial statements per past period; subledger aging at point-in-time; vendor/customer history; tax substantiation; SOX trace chain. Each pre-modeled against the archive.
Query a single company DB or federate across every archived company. Account framework variations normalised transparently. Inter-company eliminations preserved as audit-visible adjustments.
Columnar Parquet on hot storage tier with partition pruning, predicate pushdown, result caching. Typical historical query returns in 1–2 seconds — 10–100x faster than the same query against busy GP SQL.
Dedicated report family walks GL → distribution → header → document chain. Every hop signed, every read logged. Direct delivery to internal and external audit.
Same archive queryable from Power BI, Tableau, OTBI, Excel via SQL/DAX/MDX. Power users get full SQL access; casual users get the self-serve UI.
From archive in place to finance/audit/tax self-serve — typically 3–5 weeks once the underlying dynamics gp data archival is live.
Inventory every SmartList Builder query in the source GP installation, export query definitions via SmartList metadata tables, import into the reporting layer's semantic mirror. Validate output row-for-row against GP.
Configure the five packaged report families (financial statements, point-in-time aging, vendor/customer history, tax substantiation, SOX trace) for the specific company DBs, fiscal calendars and account framework definitions in scope.
Define federated views across company DBs, normalise account framework variations, configure inter-company elimination handling, validate cross-company queries against expected results from previous consolidated reporting.
User access provisioned for finance/audit/tax/HR teams with appropriate row-level scoping (per BU, per company). Self-serve UI deployed. Power-user SQL access enabled. BI tool connections (Power BI / Tableau) tested.
Hands-on training for finance, audit and tax teams on the SmartList semantic mirror and the packaged report families. SOX trace report walked through with internal audit. Handover pack delivered.
Pre-built and validated — you do not start from a blank canvas. These are the reports auditors, tax accountants and finance leaders actually ask for.
Trial balance, income statement, balance sheet, cash flow for any past period against any past account framework. Multi-company consolidated or per-company views.
AP aging, AR aging, inventory on-hand reconstructed at any past close date. Useful for audit verification, M&A diligence and historical KPI work.
Full PM30200 / RM30201 history per vendor/customer with filterable column selection. Replaces the most-used SmartList queries.
1099 source detail per vendor per tax year; sales-tax-driving SOP30200 detail per jurisdiction per period; W-2 source detail per employee per year.
GL line → distribution → header → document, signed and hashed at every hop. Direct delivery to internal and external audit.
Year-over-year comparatives, multi-year KPI trends, board-pack support — drawing on the full archived history regardless of how many calendar years.
Dynamics gp historical reporting is the ability to query, report and reconcile Great Plains data — for years after the GP system has been decommissioned or moved into read-only mode — without requiring active GP licences or a running GP environment. The audience: small-business finance teams running year-over-year comparisons, auditors verifying SOX trace from GL back to source, tax accountants preparing IRS amendments or sales-tax returns, HR reissuing former-employee W-2s, attorneys responding to litigation discovery, and the M&A team reconciling pre-acquisition history. Syntra ETL's dynamics gp historical reporting product serves all of those queries against a cloud archive, with the same data fidelity as GP but a fraction of the cost and far faster query response.
Live GP reporting runs against SQL Server tables that are also handling live transactions. Reports are constrained by the GP application's UI patterns (SmartList window, Crystal/SSRS pixel-perfect format, FRx for financial statements), need active GP user licences, and suffer from SQL Server resource contention with the posting queue. Dynamics gp historical reporting runs against an immutable cloud archive in columnar Parquet format optimised for analytical query. Queries are 10x–100x faster for typical historical analysis. No GP licences needed for the readers. No contention with live posting. And the archive can be accessed from modern BI tools (Power BI, Tableau, OTBI, Excel) using familiar SQL or DAX semantics.
Yes — and this is one of the most important use cases. SmartList Builder reports are the lifeblood of day-to-day GP operations: finance, AP, AR and ops teams have built hundreds of custom queries over a decade. Syntra ETL's historical reporting layer ships with a SmartList semantic mirror — same query shape (column picker, filter conditions, sorting, grouping) but executed against the cloud archive instead of live GP. Existing SmartList query exports are imported during the archive setup, validated row-for-row against GP output, and surfaced through a familiar self-serve UI for finance/AP/AR users. Migration of SmartList knowledge is preserved, not lost.
Multi-company GP installations are the norm. The historical reporting layer enumerates archived company DBs from the archive metadata and exposes them as both individual scopes ('show me PM30200 history for Company FAB1') and as a federated view ('show me total AP voucher count across all six companies for fiscal year 2022'). Account framework variations across companies are normalised in the reporting metadata so cross-company queries handle segment-width and segment-count differences automatically. Inter-company eliminations (where customer-built) are preserved as audit-visible adjustments in the federated views.
Five report families, each pre-modeled against the archive. (1) Financial statement re-runs: trial balance, income statement, balance sheet for any past period, against any past account framework. (2) Subledger aging at point in time: AP aging, AR aging, inventory on-hand for a specific historical close date. (3) Vendor and customer history: full PM30200/RM30201 history per vendor/customer with sortable filters. (4) Tax substantiation: 1099 source detail per vendor per tax year, sales-tax-driving SOP30200 detail per jurisdiction. (5) Audit trace reports: GL-to-source-document chain reports satisfying SOX 7-year trace requirements.
Yes. The historical reporting layer surfaces every column that was archived — which includes Dexterity-added custom fields on native GP tables and full ISV add-on tables (Mekorma payment data, Greenshades payroll history, Integrity Data extensions, Rockton utilities, Encore add-ons). Custom fields appear as additional columns on the corresponding entity reports. ISV add-on data appears as separate dimensions or fact tables in the reporting model, joinable to native GP entities via the natural keys. This matters because much of the operational truth (payment routing, tax filing detail, custom approvals) lives in ISV or custom-field territory.
SOX requires 7-year retention with an auditable trace from GL entry back to source document. The historical reporting layer ships with a dedicated SOX trace report family that walks the chain: GL30000 journal line → PM30200 voucher distribution → PM30200 voucher header → PM10500 voucher document (and similar chains for AR, SOP, POP, FA). Every hop is hashed and signed, every read access is logged with timestamp and accessor identity, and the report output is itself signed for delivery to internal and external audit. Auditors get the trace they need without the IT team needing to spin up an old GP environment.
Dramatically faster for typical analytical workloads. A 'show me all PM30200 vouchers for vendor X in fiscal year 2022' query that takes 30–60 seconds against a busy GP SQL Server returns in 1–2 seconds against the cloud archive. A full-year vendor history report that takes 5–10 minutes against GP returns in 10–20 seconds. The performance comes from columnar Parquet storage, partition pruning, predicate pushdown and elastic cloud compute. For the rare cold-tier query (data older than the hot-tier retention window), thaw time is minutes — explicitly traded against cheap long-term storage for rarely-accessed history.
Tell us how many GP company DBs, which SmartList queries matter, and which audiences need access. We will scope a historical-reporting deployment that pays for itself the year you decommission GP.