CSV file structure
This table shows information that each journal line in a .csv file must contain and the order of this information:
Field | Field type | Data type | Field content description |
---|---|---|---|
Version | Required | Alphanumeric | The ID of the version, for example, V01. |
Journal ID | Optional | Alphanumeric | The journal ID from the source system is added to the description as a suffix and
a new journal ID is generated by the system. If the ID length exceeds the storage limit, the ID is shortened. Sample values are JI0001, JI0002. |
Journal Summary | Optional | String | Defined by a user. Sample values are Reclassification, Finished Goods. |
Period | Required | Date | Must be at an open status and in the format that is configured in Business Modeling. Cannot be empty or contain unnecessary characters or whitespace characters. A sample value is 01_2020. |
Journal Type | Required | String | Possible options are Entity or Group. Cannot be empty or contain unnecessary characters or whitespace characters. |
Group | Required | String | Must be in the format that is configured in Business Modeling. Group ID is valid only for group journals. For entity journals, Group ID is ignored. Cannot be empty or contain unnecessary characters or whitespace characters. Sample values are GR0001, GR0002. |
Entity | Required | String | Must be in the format that is configured in Business Modeling. Cannot be empty or contain unnecessary characters or whitespace characters. Sample values are RU0001, RU0002. |
Level | Required | String | Must be in the format that is configured in Business Modeling. Cannot be empty or contain unnecessary characters or whitespace characters. A sample value for a group journal is Cons. Capital. Sample values for an entity journal are Reclassification, Adjustment, Correction. |
Description | Optional | String | Defined by a user. The journal ID from the source system is added to the description as a suffix. |
Category | Optional | String | Defined by a user. |
Booking Sequence | Required | Numeric | One booking sequence number indicates one journal. Cannot contain negative numbers. Must start with 1 and increase incrementally for each subsequent journal. Each line within a journal must contain the same sequence number as this journal. For example, in the 1 1 2 2 2 sequence, 1 indicates a journal with two lines and 2 indicates another journal with three lines. The order in which journal lines are posted is based on an ascending order of the journal lines from a .csv file. The order in which journals are posted is based on the ascending order of the booking sequence numbers. |
Segment Stage | Optional | String | Applies only to group journals. Sample values for an entity journal are Reclassification,Possible options are Intersegment or Intrasegment. Must be left empty for entity journals. Otherwise, the import file is discarded. |
Account | Required | String | Must be a base account and in the format that is configured in Business Modeling. Cannot be empty or contain unnecessary characters or whitespace characters. Sample values are L300100, A250120. |
Intercompany | Optional | String | Must be in the format that is configured in Business Modeling. Must be specified if the Intercompany attribute is enabled for a specific account ID. Otherwise, leave it empty and the External value will be assigned by the system. Intercompany cannot contain unnecessary characters or whitespace characters. Sample values are RU0001, External. Note: Intercompany can be the same as the entity. This can be the
case for internal financial transactions within an entity, for example, between cost
centers or departments.
|
Schedule Detail | Optional | String | Must be in the format that is configured in Business Modeling. Must be specified if the corresponding account ID requires a schedule detail. Otherwise, leave it empty and the Unassigned value will be assigned by the system. Sample values are 42, 12. |
Debit | Required | Numeric | Must contain a debit amount. To post journals, the total amount of a debit and credit must balance. Otherwise, you can only save journals as drafts. |
Credit | Required | Numeric | Must contain a credit amount. To post journals, the total amount of a debit and credit must balance. Otherwise, you can only save journals as drafts. |
Segment 1 | Optional | String | Must be in the format that is configured in Business Modeling. Must be specified if the corresponding account ID requires segment information. Otherwise, leave it empty and the Unassigned value will be assigned by the system. Sample values are BU0001, BU0002. |
Intersegment 1 | Optional | String | Must be in the format that is configured in Business Modeling. Must be specified if the corresponding account ID requires intersegment information. Otherwise, leave it empty and the Unassigned value will be assigned by the system. Sample values are RE0001, RE0005. |
Segment 2 | Optional | String | Must be in the format that is configured in Business Modeling. Must be specified if the corresponding account ID requires segment information. Otherwise, leave it empty and the Unassigned value will be assigned by the system. Sample values are BU0001, BU0002. |
Intersegment 2 | Optional | String | Must be in the format that is configured in Business Modeling. Must be specified if the corresponding account ID requires intersegment information. Otherwise, leave it empty and the Unassigned value will be assigned by the system. Sample values are RE0001, RE0005. |
Segment 3 | Optional | String | Must be in the format that is configured in Business Modeling. Must be specified if the corresponding account ID requires segment information. Otherwise, leave it empty and the Unassigned value will be assigned by the system. Sample values are BU0001, BU0002. |
Intersegment 3 | Optional | String | Must be in the format that is configured in Business Modeling. Must be specified if the corresponding account ID requires intersegment information. Otherwise, leave it empty and the Unassigned value will be assigned by the system. Sample values are RE0001, RE0005. |