Importing rate cards – procedure and template

Guidelines

Before reading this article, we recommend that you find out about standard, “manual" way to create rate cards for users. If so, see the following article: How to create a rate card for a linguist.

Before reading this article, we recommend that you find out about standard, “manual" way to create rate cards for users. If so, see the following article: How to create a rate card for a linguist.

The whole process of importing and implementation takes place on the XTM International Support team side. When requesting such an action, you should create a .csv file and provide it to them.

Find attached the template file.

A provided file can contain the IDs of multiple user/LSPs for whom rate cards need to be added.

IMPORTANT!

When creating a file with multiple user/LSP IDs, separate them with a comma!

Also, you might sometimes incorporate rate cards that have the same language combination, same workflow steps and same subject matter. Keep in mind that this will not work because the rate cards are duplicated and either need different subject matters or workflow steps.

A specific version of this kind of file needs to be created.

DATA FROM THE TEMPLATE:

1

lsp id;client;user id;;;;;;;;;;;;;;;;;;

2

mpera2;488169,385306;;;;;;;;;;;;;;;;;;

3

ratecard name;description;activity;language combinations;subject matter;calculate using;charging type;Base Rate;Words Per day;Minimum Charge;Fixed price per project;Fixed price per language;Fixed price per file;Management fee;MinManagementFee;MinChargePerLang;HalvedManagementFee;Currency

4

;;;;;;;;;;;;;;;;;;;

5

rate1;1rate;active;en_GB-pl_PL,en_GB-ar_AA,en_GB-zh_CN;other;Actual price;per word;;2;2;;;;;eur;;;;;

6

workflow step name;fixed price per project;fixed price per language;Fixed price per file;management fee;rush job premium;minimum charge;price per hour;no matching;ice;leveraged;95-99% Fuzzy match;85-94% Fuzzy match;75-84% Fuzzy match;95-99% Fuzzy repeat match;85-94% Fuzzy repeat match;75-84% Fuzzy repeat match;machine translation;Non-translatable;repeat;Fixed price per word

7

translate;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2

8

correct;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2

EXPLANATION:

  • First line → This is a primary header: do not change it.

IMPORTANT!

There should only be one header at the top! Copying this header for each rate card is incorrect.

1

lsp id;client;user id;;;;;;;;;;;;;;;;;;

1

lsp id;client;user id;;;;;;;;;;;;;;;;;;

  • Second line → Either enter LSP IDs or USER IDs , but not both! Note that the Client field is required, as it is referenced as the company name to which the rate card is being imported.

Example (user):

2

;mpera2;488169,385306;;;;;;;;;;;;;;;;;

2

;mpera2;488169,385306;;;;;;;;;;;;;;;;;

Example (LSP):

2

123123;mpera2;;;;;;;;;;;;;;;;;;

2

123123;mpera2;;;;;;;;;;;;;;;;;;

IMPORTANT!

The LSP/user ID needs to be provided by the LSP account ID and ID, and not from the LSP connection field.

  • Third line → This is a general header: do not change it.

3

ratecard name;description;activity;language combinations;subject matter;calculate using;charging type;Base Rate;Words Per day;Minimum Charge;Fixed price per project;Fixed price per language;Fixed price per file;Management fee;MinManagementFee;MinChargePerLang;HalvedManagementFee;Currency

3

ratecard name;description;activity;language combinations;subject matter;calculate using;charging type;Base Rate;Words Per day;Minimum Charge;Fixed price per project;Fixed price per language;Fixed price per file;Management fee;MinManagementFee;MinChargePerLang;HalvedManagementFee;Currency

The headers above point to this part of the rate card:

  • Fourth line → Breaking line that should not be changed. It might seem empty, but when you edit the file in Excel/OpenOffice Calc/Notepad++, it really is.

For example, if you want to add a Minimum Charge, you need to add it to the line below, which is row 5, not row 4. This is what it looks like in the CSV file:

4

;;;;;;;;;;;;;;;;;;;;

4

;;;;;;;;;;;;;;;;;;;;

  •  Fifth line → Identifies the rate card data that is being created as it matches the headers from line 3.

To specify the language combination, use this format: target_languageCode-source_languageCode, e.g. en_GB-pl_PL. Language codes can be found in the XTM Cloud manual.

The format should be en_US-de_DE

When adding more than one language combination, separate them with separated by commas without spaces, e.g. en_GB-pl_PL,en_GB-ar_AA.

5

rate1;1rate;active;en_GB-pl_PL,en_GB-ar_AA,en_GB-zh_CN;other;Actual price;per word;;2;2;;;;;eur;;;;;

5

rate1;1rate;active;en_GB-pl_PL,en_GB-ar_AA,en_GB-zh_CN;other;Actual price;per word;;2;2;;;;;eur;;;;;

  • Sixth line → Headers for the next part of the rate card.

6

workflow step name;fixed price per project;fixed price per language;Fixed price per file;management fee;rush job premium;minimum charge;price per hour;no matching;ice;leveraged;95-99% Fuzzy match;85-94% Fuzzy match;75-84% Fuzzy match;95-99% Fuzzy repeat match;85-94% Fuzzy repeat match;75-84% Fuzzy repeat match;machine translation;Non-translatable;repeat;Fixed price per word

6

workflow step name;fixed price per project;fixed price per language;Fixed price per file;management fee;rush job premium;minimum charge;price per hour;no matching;ice;leveraged;95-99% Fuzzy match;85-94% Fuzzy match;75-84% Fuzzy match;95-99% Fuzzy repeat match;85-94% Fuzzy repeat match;75-84% Fuzzy repeat match;machine translation;Non-translatable;repeat;Fixed price per word

  • 7th, 8th line, and so on → Indicate the data per workflow step ("Translate" and "Correct" ).

IMPORTANT!

Any workflow step name you add to this import file must exist on your XTM Cloud instance beforehand in Configuration → Settings → WorkflowWorkflow steps (only an administrator can add this).

Furthermore, you cannot include a particular workflow step without setting any rates for that step is incorrect (see the 9th line below for an example). Remove this step.

7

translate;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2

8

correct;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2

9

review;;;;;;;;;;;;;;;;;;;;

IMPORTANT!

The rate card import tool uses commas, not full stops, as decimal separators. If you notice that you have used full stops, replace them with commas. There should not be a single full stop in the file.