Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2023-11-03
Reference: Consolidation Data - Inbound Integration CSV File Format

Reference: Consolidation Data - Inbound Integration CSV File Format

You can't generate A CSV file from a delivered template. Your organization will have to create one using the Workday defined guidelines as specified below:
The CSV import file format has 2 types of rows:
  • Header
     row. The first row in the CSV file is a fixed header row. The header row describes the columns that the consolidation data rows populate. There can be only 1 header row in a file, and it must be the first row of the file. You can skip the optional columns in the input file by removing the column or leaving it empty.
  • Consolidation Data
     are rows that display the summarized trial balance lines. The integration separates the CSV file by grouping all lines with the same
    Grouping Dimension
     that consists of:
    • Company
    • Book Code
    • Accounting Date
For each set of lines with the same Grouping Dimension, Workday will:
  • Create a single Consolidation Data file.
  • Process the single Consolidation Data file into a single journal entry in Workday.
The CSV import file format has 2 types of fields that you can use to upload consolidation data from the
Consolidation Data Hub
 report or using a Document Retrieval Service connection (Example: SFTP):
  • Standard Fields
    You can include these standard fields:
    Field Name
    Supported Data Type
    Grouping Dimension
    Required
    Description
    ACCOUNTING_DATE
    YYYY-MM-DD
    MM/DD/YYYY
    MM-DD-YYYY
    MM/DD/YY
    MM-DD-YY
    Yes
    Yes
    Determines ledger period based on Company fiscal schedule.
    BOOK_CODE
    Integration ID-for the Book Code
    Access
    Integration IDs
    View IDs
     as a related action on the book code.
    Yes
    No
    If left blank, Workday records the journal to blank/common book code.
    Segregates transactions for financial reporting.
    HEADER_MEMO
    Free Text
    No
    No
    Header message
    TRANSACTION_CURRENCY
    Alpha‑3 code
    No
    No
    Currency in which a transaction takes place.
    TRANSACTION_AMOUNT
    Amount with no commas.
    No
    No
    Amount in transaction currency.
    LEDGER_CURRENCY
    Alpha‑3 code
    No
    Yes
    Ledger currency of specified Company.
    LEDGER_AMOUNT
    Amount with no commas.
    No
    Yes
    Amount in ledger currency of specified Company.
    LINE_MEMO
    Free Text
    No
    No
    Line level message
    EXTERNAL _REFERENCE ID
    Free Text
    No
    No
    Enables you to associate a journal with a record in a third party system.
    DOCUMENT_ LINK
    Free Text
    No
    No
    Enables you to create a link to additional information for the journal.
    Before you enter the Document Link, ensure you enter
    Consolidation Data Capture Document Link
     as a Valid URI Pattern on the
    Maintain External Link Validation
     task.
    Enter the field name as shown in the
    Field Name
     column above. Example: Enter ACCOUNTING_DATE not ACCOUNTING.DATE.
    Column names are case-sensitive.
  • Mapping Fields
    You can use these fields in your mapping tables:
    Mappable Field
    Data Type
    Singular
    Grouping Dimension
    Required
    Description
    Company
    Mapping Value
    Yes
    Yes
    Yes
    Company in Workday
    Ledger Account
    Mapping Value
    Yes
    No
    No
    Ledger accounts from the account set of the company.
    Worktags
    Mapping Value
    One per type.
    No
    No
    Attributes for each consolidation data line.
    As you enter mapping values, keep these guidelines in consideration:
    Mapping Value
    Valid Values
    Alphabet
    aA-zZ
    Numbers
    0 to 9
    Expressions aren’t case-sensitive.
    Use this format for a field or column header on your CSV file for mapping values:
    EC.TableName.ColumnName
    , where:
    • EC indicates that the column contains mapped values. Every mapping field must start with 'EC.'
    • TableName is the external value of the mapping table name. This name should correspond to the external value in the
      Map: Apply Mapping Tables
       located on the integration system.
    • ColumnName is the exact name of the Column in the Referenced Mapping Table in Workday.
      For more information about the configuration, see Integration Maps Configuration, on Community.
      Example:
EC.Map1.Ledger Acct
EC.Map2.Company
ACCOUNTING _DATE
LEDGER_CURRENCY
LEDGER_AMOUNT
Cash
Company A
2023-01-31
USD
1000
Accounts Receivable
Company A
2023-01-31
USD
250
Fixed Assets
Company A
2023-01-31
USD
3000

Additional Guidelines

Consider these additional guidelines when you format a CSV file:
  • Workday records positive ledger amounts or transaction amounts as Debits and negative ledger amounts or transaction amounts as Credits.
  • When you open CSV files with certain editors (Example: Excel) Workday might convert certain field display formats. Remove non-English values such as accents, symbols, and characters and so on. After using such an editor, view the CSV file with a program such as TextEdit to ensure file wasn’t altered.
  • Field or column order doesn’t matter.
  • Commas in Ledger Amount or Transaction Amount fields aren’t supported (Example: input 1000 vs 1,000).
  • Workday considers a field required unless otherwise stated.
  • Boolean values are
    1
     (true) and
    0
     (false).
  • Date value formats accepted are:
    • YYYY-MM-DD
    • MM/DD/YYYY
    • MM-DD-YYYY
    • MM/DD/YY
    • MM-DD-YY
  • Field or Column header names must display in the file exactly as this document specifies.
  • Column header names
    are
     case-sensitive.
  • For HEADER_MEMO, Workday will use a memo per unique grouping, based on Company, Accounting Date, and Book Code.