Skip to main content



Coupa Success Portal

Using Loaders with Non-English Character Sets

When loading csv files into Coupa that have non-English character sets, you must convert the file into the proper format to load successfully.  Failing to do so will corrupt data.  Please follow the instructions below:

  1. Using Excel make sure you have filled in all the required columns and you have verified the data you want to load

  2. Save the file as a .csv file (CSV MS DOS for Windows or Windows CSV file for Mac)

  3. The file that you just saved, open in a Text Editor program - recommended text editor for Mac is Text Wrangler and Kalytta Character Set Converter for Windows (can be downloaded at   You can use other text editor programs as long as they support your language.

    Important: When you open the file in text editor program, please make sure you pick the source character set for your file.  For Text Wrangler, you will pick this in Read As box when you open the file.  For Kalytta Character Set Converter, you can pick this in 'Source character set' box when you pick your file to convert.

  4. Now you are ready to save your converted file.  In Text Wrangler, click Save As, select Options box, pick Unicode (UTF-8, No BOM), and save the file.  In Kalytta converter for Windows select 'UTF-8' in Destination Character Set box and check the box 'Do not write a Byte Order Marker (BOM). Then click Convert.

  5. Upload the newly created CSV file into Coupa

After the data is successfully loaded into Coupa you can follow the same process to make updates using the .csv loader.   Please note that if you open the CSV file in Excel, the special characters do not look as they are supposed to. But once you make any edits and upload the file using the above process the characters will look as they are supposed to in your Coupa environment.

You can use other text editors to deal with Non-english characters in addtion to the ones mentioned above.  The steps above should also be carried out for other text editor programs.  Similar options should be available to you to pick the encoding of your source file and UTF-8, no BOM as your destination character format.

  • Was this article helpful?