Import Financial Information

July 16, 2018

Information on how to import financial information.


This tutorial shows you how to import financial information.

It’s important to fully understand this import before you carry it out as it could involve removing or changing existing financial information.

We strongly recommend testing the upload on a test instance. Please contact us via support@ilign.com to request a temporary test instance containing your production data.

You’ll need to have the following Organisation security role to be able to carry out this upload: Configure Finance.

See Tuning i-lign: Finances for more general information on how to manage financial information in i-lign.

Import financial information from your FMIS application

Project financial information can be imported from your FMIS application into i-lign.

All import file formats need to be in comma separated format (.csv).

An individual file can only contain data for one financial year and either actual or budget data. See below for more information on import file formats for the following applications:

  • Oracle
  • Sun
  • Agresso
  • Ellipse

If your financial application isn’t on this list, please contact us to discuss. We also provide a standard format which you can use to upload financials (i-lign standard).

Once your file is in the correct format, see the screenshots below for how to import your financial information into i-lign.

Import file formats

All import file formats are in comma separated format (.csv). Note that references to the Project Finance Number may refer to either the Project Number or the Project Finance Number depending on the Interface Field selected in your Organisation Settings. See Tuning i-lign: Organisation Settings for information on this - you’ll need to scroll down to the Project settings heading.

i-lign standard

The file must have the following columns. The first four columns need to contain content. The other columns need to exist but don’t need content for the upload to work.

  • Period Number and Year - e.g. 201601 and 201602 where the last two figures refer to the month in the Financial year period.
    (If your financial year runs from June 31 to July 1, 01 is July, 02 August, 03 September etc.)
  • Project Finance Number or Project Number: Must be unique for the project.
  • Account Code: Unique code for the account.
  • Amount: +/- for the actual amount for the month.
  • Comment (Populates the Name field)
  • Journal Number
  • Employee Code
  • Supplier Code
  • Source Currency: If different from the native currency.
  • Source Currency Amount The file can contain as many rows as needed, but all should be for a single financial year. Duplicate rows for a Project and Account Code are allowed, and the Amounts in them will be shown as separate line items.
Oracle financials

The file can have as many columns as wanted, but the following data must be in the columns listed:

  • Column 2: Account Code
  • Column 4: Period Number - (1-12) Month number within the financial year.
  • Column 9: Amount - +/- for the actual amount for the month.
  • Column 20: TCode1
  • Column 23: TCode4

TCode1 and TCode4 combined make up the project finance number. The file can contain as many rows as needed, but all should be for a single financial year. Duplicate rows for a Project and Account Code are allowed, and the Amounts in them will be shown as separate line items.

Sun financials

The following data must be in the columns listed:

  • Column 2: Project Finance Number
  • Column 3: Period Number - (1-12) Month number within the financial year.
  • Column 5: Journal Number
  • Column 8: Amount
  • Column 11: Comment
  • Column 19: Account Code
  • Column 22: Employee Code
  • Column 23: Supplier Code

The file can contain as many rows as needed, but all should be for a single financial year. Duplicate rows for a Project and Account Code are allowed, and the Amounts in them will be shown as separate line items.

Agresso financials

The following data must be in the columns listed:

  • Column 3: Journal Number
  • Column 6: Period Number - (1-12) Month number within the financial year.
  • Column 7: Account Code
  • Column 19: Comment
  • Column 20: Amount
  • Column 24: Src Currency
  • Column 25: Src Amount
  • Column 29: Supplier Code

The file can contain as many rows as needed, but all should be for a single financial year. Duplicate rows for a Project and Account Code are allowed, and the Amounts in them will be shown as separate line items.

Ellipse financials

The following data must be in the columns listed:

  • Column 1: Project Finance Number
  • Column 2: Period Number - (1-12) Month number within the financial year.
  • Column 3: Journal Number
  • Column 4: Amount
  • Column 5: Comment
  • Column 6: Account Code
  • Column 7: Employee Code
  • Column 8: Supplier Code
  • Column 9: Null
  • Column 10: Null

The file can contain as many rows as needed, but all should be for a single financial year. Duplicate rows for a Project and Account Code are allowed, and the Amounts in them will be shown as separate line items.