Edit

Share via

Import format for consolidation

This article provides detailed information about the import format that is used when you consolidate financial data from multiple legal entities. The import format must be saved as a text (.txt) file.

Import format

The following table lists the import format that you should use when you do a consolidation during an import.

Record table Format Notes
1 170150, Goodwill, 4
  • The record table
  • The source main account ID
  • The main account line
  • The main account type
2 110130, 2015/01/01, 1, USD, 0,0,80699.39,0,1
  • The main account ID
  • The transaction date
  • The fiscal period type (0 = Opening, 1 = Operating, and 2 = Closing)
  • The transaction currency
  • Debit or credit (0 = Debit and 1 = Credit)
  • The posting layer
  • Transaction amounts
  • Quantity
  • The local RecID (ambiguous, unique int64 value for the transaction)
3 USMF0000009, 2017/01/01, FY2017, 1, 2017,01,01, 602200, USD, 6053.6.0
  • The entry number (budget header transaction number)
  • The default date of the budget header
  • The budget model ID
  • Budget type (1 - Original Budget, 2 - Transfer, 3 - Revision, 4 - Encumbrance, 5 - Pre-encumberance, 6 - Carry-forward budget, 7 - Project, 8 - Fixed Assets, 9 - Demand forecast, 10 - Supply forecast, 11 - Apportionments, 12 - Preliminary budget.)
  • The date of the line
  • The main account ID for the line
  • The currency code for the line
  • The amount for the line, in the transaction currency
  • The enumeration integer value for the budget type for the line (expense or revenue)
4 DEMF RecordCompany is the Source legal entity.
5 110130, 2015/01/01, 1, USD, 0,0,80699.39,0,1
  • Main account ID
  • Transaction date
  • Fiscal period type (0 Opening, 1 Operating, 2 Closing)
  • Transaction currency
  • Debit or Credit (0 for Debit, 1 for Credit)
  • Posting layer
  • Transaction amount
  • Quantity
  • Local recid (ambiguous unique int64 value for the transaction)
6 BusinessUnit, 1 Department, 2 The financial dimension attributes that are defined in the segment order.

You can use the Export page to verify how the attributes are defined.
7 002,1,658
  • The financial dimension value
  • The financial dimension, as the index that is provided in RecordDimensions
  • An ambiguous, unique record ID that is associated with the unique record ID from RecordTrans or RecordTrans2
8 002,1,1
  • Dimension values that are associated with the transaction from RecordBudget
  • The financial dimension, as the index that is provided in RecordDimensions
  • An ambiguous line record ID that is aligned with the order of the transaction lines in the file