History Data and Retrospective Trial Balances in Jobpac

Overview

Jobpac stores history data by monthly period so you can see how projects and financial results looked at specific points in time. This supports analysis, reconciliation and audit by providing a stable view of results at the end of each period.

Monthly periods and history snapshots

Jobpac operates with defined monthly periods, and each transaction is assigned to a period based on its date and configuration.

• At month end, the system moves into the next period
• The previous period is locked to prevent changes
• A snapshot of key project and financial data is captured

These snapshots form the foundation of history data across all modules.

Project history data

For projects, history data records how costs, revenue and margins looked at the end of each period.

• Review project performance at earlier points in time
• Compare trends across monthly periods
• Understand how forecasts and results have changed over the life of a job

Because periods are locked after month end, this data represents a stable and reliable view of past performance.

Retrospective trial balances

History data also supports retrospective trial balances for financial modules such as the general ledger, accounts payable and accounts receivable.

• Run trial balances as at past period ends
• Review account balances at specific dates
• Support audit and investigation by tracking changes over time

This is particularly useful when explaining differences between reporting periods or validating historical results.

Why this matters

• Allows analysis of trends across periods
• Explains changes between month end results
• Supports audit, governance and financial transparency

Without historical snapshots, it would be difficult to understand how and when results changed.

Using history data

• Run reports showing period-by-period performance
• Review prior periods during forecasting and budgeting
• Investigate movements in balances or margins

Project and finance teams can use history data together to understand both operational and financial drivers of change.

Good practices

• Run month end consistently to ensure complete history
• Avoid back-dated transactions in closed periods
• Use history reports to identify trends early
• Document significant adjustments made after period end

These practices help ensure history data remains accurate, reliable and useful for reporting and decision making.