History Data and Retrospective Trial Balances in Jobpac

Jobpac stores history data by monthly period so you can see how projects and financial results looked at specific points in time. This article explains how history data works and how retrospective trial balances support analysis and audit.

Monthly periods and history snapshots

Jobpac operates with defined monthly periods. Every transaction is assigned to a period based on the date and your configuration.

At the end of each month, when you complete period end processing, Jobpac:

• moves modules into the next active period
• locks the previous period to prevent further changes
• captures a snapshot of key project data as at the end of the month

These monthly snapshots form the basis of history data for both projects and financial modules.

Project history data

For projects, history data records how costs, revenue and margins looked at the end of each period. This allows you to:

• review project performance at earlier points in time
• compare month by month trends in cost, revenue and margin
• understand how forecasts and results have changed over the life of the job

Because the previous period is locked after month end, the history reflects a stable view of the project at that date.

Retrospective trial balances for financial modules

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

This means you can:

• run a trial balance as at the end of a past period, even after later periods have been processed
• review how account balances looked at specific dates
• support audit and investigation by tracing changes over time

Retrospective trial balances are particularly valuable when you need to explain differences between periods or confirm what the ledger looked like at the time of a particular report.

Why history data and retrospective trial balances matter

History data and retrospective trial balances give you more than just a current view of results. They allow you to:

• analyse trends in project and financial performance across multiple periods
• answer questions about what changed between one month end and the next
• demonstrate control and transparency for audit and governance purposes

Without this history, it would be harder to understand how and when results changed, especially in complex multi project or multi company environments.

Using history data in day to day work

In day to day use, you may work with history data when you:

• run project reports that show period by period performance
• review prior period financial reports during budgeting or forecasting
• investigate unusual movements in balances or margins between months

Finance and project teams can use history data together to understand both the operational and financial reasons behind changes in results.

Good practices for managing history data

To make the most of history data and retrospective trial balances in Jobpac, consider the following practices:

• run period end processing consistently at the close of each month so that history snapshots are complete.
• avoid posting back dated transactions into closed periods unless strictly controlled and documented.
• use history reports to review trends and identify issues early.
• retain documentation that explains significant adjustments made at or after month end.

These practices help ensure that your history data remains reliable and useful for both operational review and external reporting.