Knowledge BaseGL History LoaderGL History Loader Overview
Updated 2026-04-12

GL History Loader Overview

An introduction to the GL History Loader -- what it does, when to use it, and how it differs from regular sync pipelines.

What the GL History Loader Does

The GL History Loader is a purpose-built pipeline for bulk-loading historical general ledger data from NetSuite into your EPM planning tool (Adaptive Planning or Pigment). Where a regular sync moves incremental changes -- last week's new hires, this month's invoice updates -- the GL History Loader moves months or years of actuals in a single, orchestrated run.

You typically use it during:

  • Initial implementation -- Populating your planning tool with 12-36 months of historical actuals so that variance analysis and trend models work from day one.
  • Historical migration -- Backfilling data when you switch planning platforms or consolidate business units.
  • Restatement loads -- Reloading corrected historical periods after an audit adjustment.

How It Differs from Regular Syncs

A standard VersionForge sync extracts the current state, diffs against the last snapshot, and loads the delta. The GL History Loader works differently in three important ways:

  • Period-by-period processing -- Instead of pulling one giant date range (which times out on most NetSuite instances), the loader breaks the extraction into fiscal period chunks. Each period is extracted, validated, and staged independently.
  • Trial balance validation -- After each period is extracted, VersionForge compares the sum of debits and credits against NetSuite's native trial balance for that period. If the numbers do not tie, the period is flagged before any data reaches your target.
  • Batch-oriented load -- Approved periods are loaded to the target system in sequence, preserving period boundaries so that your planning tool's period-level aggregations remain consistent throughout the load.

Dashboard Walkthrough

The GL History Loader has its own dashboard, accessible from Pipelines > GL History Loader in the sidebar.

Configuration Panel

At the top, you configure the load parameters:

  • Source connection -- Your NetSuite connection (must have GL read permissions).
  • Target connection -- Your Adaptive Planning or Pigment connection.
  • Date range -- The start and end periods for the historical load.
  • Account mapping -- Maps NetSuite chart-of-accounts segments to your target's dimension hierarchy.

Period Progress Grid

The center of the dashboard shows a grid of every fiscal period in your selected range. Each period displays a status badge:

| Status | Meaning | |--------|---------| | Queued | Period is waiting to be extracted | | Extracting | NetSuite query in progress | | Validating | Trial balance check running | | Staged | Extracted and validated, ready for review | | Loaded | Successfully pushed to target | | Failed | Validation or load error -- click to see details |

Summary Bar

The bottom bar shows aggregate progress: total periods, periods completed, rows extracted, and overall validation status. When all periods are loaded and verified, the run is marked complete.

You can pause a GL History Loader run mid-way and resume it later. Completed periods are not re-processed -- the loader picks up from the next queued period.

Next Steps

Built by Vantage Advisory

VersionForge is built by the team at Vantage Advisory Group — consultants who have spent years implementing Workday, NetSuite, Stripe, Salesforce, Adaptive, and Pigment integrations for finance, RevOps, and workforce-planning teams. We built the product we kept wishing existed.

See It Running on Your Own Data in 30 Minutes

Book a walkthrough with the founding team. Bring your messiest data pipeline — GL close, MRR reconciliation, or headcount plan. We'll show you how VersionForge handles it.