Prepare your data for import to hila
As a specific use case, for an FP&A individual in a CFO’s office, hila’s Conversational Finance provides timely, accurate information with charts, tables and analysis on ERP systems. With Vianai’s specialized models and anti-hallucination features, the responses back from a system of record are 100 percent accurate and occur after asking a simple question. There is no need to send the question to a business analyst, an IT department or specialist for further analysis.
Preparing your data for Conversational Finance involves two steps:
- Prepare the data (customer task)
- Configure hila to ingest the data (Professional Services or client IT task)
Prepare the data
For the current release, you need to prepare the data for Conversational Finance in the form of CSV or parquet files that you give to your Professional Services or client IT contact for the next step.
To set up and populate Conversational Finance with pilot data for your organization, you need to prepare and provide the data in a standard format. You can do this by running a custom report in your financial system and exporting the data to a CSV file with expected columns and data. Or you can export data from your financial system in an Excel file and then transform this data to this standard format.
The core Conversational Finance flat tables contain the columns listed in the following image:
Example files
Each table below has an example CSV
file you can read to make sure your files are in the right format.
Following is a link to download example files in parquet format that you can load into hila Conversational Finance and ask questions against.
Journal table
Journal table contains transaction data from your general ledger in a flat de-normalized format. The following columns are available in the journal table:
Column Name | Data Type | Format | Required | Examples |
---|---|---|---|---|
posting_date | string | YYYYMMDD | Yes | 20230215 |
fiscal_year | string | 2023 | No | 2023 |
fiscal_quarter | string | Q# | No | Q1 |
fiscal_month | string | MM | No | 01 |
fiscal_period | string | ### | No | 001 |
fiscal_year_quarter | string | YYYY-Q# | No | 2023-Q1 |
fiscal_year_month | string | YYYY-MM | No | 2023-01 |
fiscal_year_period | string | YYYY-### | No | 2023-001 |
account_number | string | Yes | 0050301000 | |
account_name | string | No | COGS Direct Material | |
account_type | string | No | Expense | |
account_subtype | string | No | Operating Expense | |
account_category | string | No | Cost of Goods Sold | |
company_code | string | No | AUS | |
company_name | string | No | EverGreen Australia Pty Ltd | |
company_country | string | No | Australia | |
company_region | string | No | Oceania | |
company_currency | string | Yes | AUD | |
company_amount | Decimal(18,2) | No | 5936.32 | |
global_currency | string | No | USD | |
global_amount | Decimal(18,2) | No | 5936.32 | |
department_number | string | No | M001 | |
department_name | string | No | Manufacturing | |
cost_center_number | string | No | US10_ADM4 | |
cost_center_name | string | No | Purchasing | |
profit_center_number | string | No | YB800 | |
profit_center_name | string | No | Allocation | |
purchase_order_number | string | No | 0012000411 | |
invoice_number | string | No | INV-SP03278-240609 | |
supplier_number | string | No | 4500000942 | |
supplier_name | string | No | Domestic US Subcontractor A | |
material_number | string | No | RM13 | |
material_name | string | No | RAW13,PD,Subcontracting | |
material_group_number | string | No | L002 | |
material_group_name | string | No | Raw Materials | |
sales_order_number | string | No | 0000002695 | |
customer_number | string | No | EWM17-CU02 | |
customer_name | string | No | EWM Domestic Customer 02 | |
product_number | string | No | EWMS4-01 | |
product_name | string | No | Small Part, Slow-Moving Item | |
product_group_number | string | No | L001 | |
product_group_name | string | No | Trading Materials | |
transaction_id | string | No | 20230001211 | |
transaction_type | string | No | Purchase | |
transaction_document_number | string | No | BD2301000014 | |
transaction_document_item | string | No | 001 | |
transaction_description | string | No | ||
reference procedure | string | No | ||
amount | Decimal(18,2) | Yes | 5344.56 | |
income_statement_group | string | No | Operating Expense |
Template for journal data: journal_template.csv
Sample journal data: journal.csv
Comments:
- fiscal_year, fiscal_quarter, fiscal_month and fiscal_period columns are populated automatically from the fiscal_calendar table or generated using posting_date automatically if fiscal calendar is aligned with calendar year.
- account_name, account_type and account_category columns are populated from account table.
- Most of the columns have been marked as not required. However, capabilities and diversity of questions that can be asked are directly dependent on data availability in all or most of these columns.
- For each reference field like department, cost center, profit center, supplier, etc., both number and name columns are provided. You can provide either number or name or both. However, providing both will help you filter data using either number or name. You may join with your reference tables to populate these fields in flattened journal table. For simplicity, Conversational Finance does not expect master data tables for each of these fields to be populated.
Account table
Account table contains general ledger account information. The following columns must be populated in this table for each of the accounts that appear in the journal table:
Column Name | Data Type | Format | Required | Examples |
---|---|---|---|---|
account_number | string | Yes | 0050301000 | |
account_name | string | No | COGS Direct Material | |
account_type | string | No | Expense | |
account_subtype | string | No | Operating Expense | |
account_category | string | No | Cost of Goods Sold | |
income_statement_group | string | No | Revenue |
Template for account data: account_template.csv
Sample account data: account.csv
Comments:
- account_type column is used to categorize accounts into different types like Revenue and Expense.
- account_category column is used to categorize accounts into different categories like Cost of Goods Sold, Operating Expenses, etc.
Fiscal calendar table
If your organization follows a fiscal year calendar that is aligned with a calendar year, then you just need to provide the start date of the fiscal year. For example, if your fiscal year starts on 1st January, the fiscal year and calendar year are expected to be identical. If your fiscal year starts on 1st of July for example, then Q1 of the fiscal year would be 1st July to 30th September, Q2 would be 1st October to 31st December, and so on. In such cases, Professional Services will be able to generate a fiscal calendar table for queries automatically. However, if your organization follows a non-standard fiscal year calendar, you will need to provide a fiscal_calendar.parquet
file.
Column Name | Data Type | Format | Required | Examples |
---|---|---|---|---|
posting_date | string | YYYYMMDD | Yes | 20230215 |
fiscal_year | string | 2023 | No | 2023 |
fiscal_quarter | string | Q# | No | Q1 |
fiscal_month | string | MM | No | 01 |
fiscal_period | string | ### | No | 001 |
Template for fiscal calendar data: fiscal_calendar_template.csv
Sample fiscal calendar data: fiscal_calendar.csv
Comments:
- If your organization follows a fiscal year calendar that is aligned with a calendar year, then you just need to provide the start date of the fiscal year.
Company table
Company provides details about your company or companies.
Column Name | Data Type | Format | Required | Examples |
---|---|---|---|---|
company_code | string | No | AUS | |
company_name | string | No | EverGreen Australia Pty Ltd | |
company_country | string | No | Australia | |
company_region | string | No | Oceania | |
company_currency | string | Yes | AUD |
Template for company data: company_template.csv
Sample company data: company.csv
Configure hila
After you have prepared the data, convert your CSV files to parquet and send the data to your Professional Services or client IT contact. They will configure hila to ingest the data and set up Conversational Finance for your organization.