Dry Run Mode

What Dry Run Mode Does

Dry run mode executes the complete GL History Loader pipeline -- extraction, period chunking, account mapping, trial balance validation -- but stops before writing anything to your target system. You see exactly what would be loaded without any risk to production data.

Think of it as a full dress rehearsal. Every step runs for real against live source data, but the final load step is skipped.

When to Use Dry Run

• Before initial go-live -- Validate your complete configuration (account mappings, period formats, subsidiary scope) against real data before committing to a production load.
• After mapping changes -- When you update account mappings or add new dimension translations, run a dry run to confirm the changes produce the expected output.
• Auditor review -- Generate a dry run report showing exactly what data would flow into the planning tool. Auditors can review row counts, totals, and validation results without any data actually moving.
• Troubleshooting -- If a previous load had issues, run a dry run to see whether your fixes resolve the problem before re-loading.

How to Enable Dry Run

From the UI

1. Open the GL History Loader dashboard

   Navigate to Pipelines > GL History Loader and select an existing configuration or create a new one.

2. Toggle dry run mode

   In the top-right corner of the configuration panel, toggle the Dry Run switch to On. The switch turns amber to indicate dry run mode is active.

3. Start the run

   Click Run. The pipeline executes normally through extraction and validation, but the load step displays Skipped (Dry Run) instead of executing.

From the API

Include dryRun: true in your GL History Loader trigger request:

curl -X POST https://your-instance.versionforge.com/api/v1/gl-loader/run \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "configId": "gl-config-abc123",
    "dryRun": true
  }'

The API response includes a runId that you can use to poll for status or retrieve the dry run report.

Dry Run Report

When the dry run completes, VersionForge generates a detailed report available on the run detail page. The report includes:

Summary Section

• Total periods processed and their pass/fail status
• Total rows extracted across all periods
• Total rows that would be loaded (after mapping and deduplication)

Period Breakdown

For each fiscal period:

• Row count (adds, updates, deletes)
• Trial balance validation result (passed/failed with variance)
• Account-level distribution -- how many rows map to each target account

Cross-Check Preview

The report includes a simulated cross-check showing what the source-vs-target reconciliation would look like after the load. Since no data was written to the target, the cross-check compares extracted totals against the current target state (if any data exists there already) or shows the expected target totals for a fresh load.

Export

Download the dry run report as CSV or PDF from the Reports tab on the run detail page. The CSV export includes row-level detail for every record that would have been loaded.

Dry Run vs. Regular Run Comparison

| Aspect | Dry Run | Regular Run | |--------|---------|-------------| | Reads from source (NetSuite) | Yes | Yes | | Validates trial balance | Yes | Yes | | Applies account mappings | Yes | Yes | | Writes to target system | No | Yes | | Generates reconciliation report | Yes (simulated) | Yes (actual) | | Appears in run history | Yes (tagged as dry run) | Yes |