Import Commodities from CSV file

Created by Erik Åkerlund, Modified on Wed, 07 Feb 2024 at 11:43 AM by Maria Appelquist

It is possible to import commodities from a text or CSV file. This can be useful when implementing TS and many commodities from another system needs to be entered or internal commodities. 

Open Autopilot / Integrations

1. Click new / Plugin 

2. Select Deal import - Commodity deal import

3. Give the new integration a name 

4. In Settings add all the column you have in the file you want to import

Note, The order of the COLUMN MAPPINGSs in the Settings tab is important if the imported file does not contain headings. If there are headings in the file, the order does not matter.

Import file WITH headers

Make sure the CONTAINS HEADERS checkbox is checked.

Add Column mappings and enter the header names in column File Header and map to relevant field from the drop down list in the System Field column.

Import file WITHOUT headers

Make sure the CONTAINS HEADERS checkbox is NOT checked.

Add Column mappings. Headers can be, but does not have to be, entered.


CULTURE determines how numbers are represented.

DELIMITER specifies the delimiter used in the CSV file. Most common is semicolon ;. 

Mandatory fields Commodity Swaps

Legal entity 



Commodity type

Quantity (see note below)





Deal date

Value date (Closing floating or average price will be selected from this date)

Maturity date (Closing floating or average price will be selected to this date) 

Payment date

Note: Quantity has to be in ABS number (no "-" on Sell)

Mandatory fields Commodity Future

Same as above except

Commodity type is not mandatory

Contango and backwardation is not mandatory if excluded from the file base price and Fwd price will be same. If setting 'Set base price from register' is selected, Base price is fetched from market data on deal date and contango/backwardation will be the difference between Price in the imported file and the fetched base price from market data.

Maturity date is not mandatory (will be same as payment date)

Open / close is mandatory

Price select commodity future price


Market place: is only mandatory if more than one Market place is defined in Commodity definition

Price unit: if multiple price unit for same commodity are defined in Commodity definition then this needs to be included in the import file

Closing price: is optional

External identifier are optional but if included it will check so that no deals with same external iditifier are imported twice. 

In TAB Mappings you MUST map different Legal entities and Counterparties that are included in the import file. If other TAGs are included in the file, they must also be mapped.

For example, in the view above, all Deals will have TAG VALUE "TreasurySystem" as a legal entity.

You need to map both Legal entity and Counterpart even if they have the same value in the import file.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article