Master trial balance

Compare, consolidate, and publish trial balance data to create a master trial balance.
Compare, consolidate, and publish trial balance data to create a master trial balance. This process involves combining data from multiple sources, rolling up data based on account and entity roll-ups, and managing multiple versions for tracking changes over time.

Create master trial balances

  1. Go to the Master Trial Balance section.
  2. Select
    Add
    to create a new master trial balance.
  3. Enter a name, year, and period for the master trial balance.
  4. Select the data format.
  5. Choose which processed data sets to include.
  6. Select a chart of accounts for roll-up.
  7. Select an entity roll-up.
  8. Save the master trial balance.
  9. Review the created master trial balance:
    • Check included data sets.
    • Verify record counts.
    • Use filters to analyze specific subsets of data.
  10. Publish the master trial balance to make it read-only.

Managing trial balances

  1. Remove any trial balances that are incorrect or no longer needed,
  2. Rename trial balances for easier identification
  3. Review specific subsets of data using the filter function.

Consolidate and analyze data

Combine data from multiple sources into a master trial balance. You can choose to roll up data based on account and entity roll-ups. Utilize the trial balance feature to review and consolidate your financial data.
  1. View consolidated data aligned to master account codes and entity codes.
  2. Group data by various fields (for example, account code, Flex fields).
  3. Download data in CSV or Excel format for detailed analysis.
  4. Analyze differences between master trial balances or versions.

Versions for master trial balances

Create and manage multiple versions of the master trial balance for tracking changes over time.
  1. Create new versions of master trial balances for edits or updates
  2. Use versions to track balances at different times (e.g., day 1, day 2, day 3)
  3. Delete unpublished versions if needed.
  4. Link versions to specific applications as required.