Cost Control
You can fix the three errors that the Preview step of an import reports, and you know where KOSMA books lines that have no account number.
In the **Preview** step of an import, KOSMA checks every line of the file against the import mapping set. As long as any line has an error, **Continue** stays greyed out, while **Back** and **Cancel** stay active. Above the preview, KOSMA shows how many lines it cannot map:
{number} lines cannot be mapped.
Below this message, KOSMA lists each error with its line number. KOSMA counts the lines of the file, the header row included, so with a header row, Line 3 is the second line of data.
- To fix an error in the mapping set, click **Back**, correct the mapping set and click **Continue** again. KOSMA then reads the file again. For how to change a mapping set, see [set up an import mapping set](/kb/article/set-up-an-import-mapping-set). - To fix an error in the file, correct and save the file, then click **Back** and choose the file again in step **File**: drop it on **Drop file here**, or click **Select file**. Then click **Continue**. Clicking **Continue** alone does not pick up the corrected file.
Line {line}: No such account
The account number in this line is not in the mapping set. In the mapping set, under **Accounts**, enter the number from the file next to the account it belongs to. One account can take several numbers, separated by commas or semicolons.
Ticking **Budget and import file use identical account numbers.** replaces the account numbers you entered by hand in the mapping set.
If the file uses the same account numbers as the budget, tick **Budget and import file use identical account numbers.** instead. If the box is already ticked, untick it and tick it again, so KOSMA copies the current account numbers.
If the account is not in the cost control set yet, add it to the set first and then enter its number in the mapping set. See [add an account to a set](/kb/article/add-an-account-to-a-set). Adding the account to the budget does not add it to the set.
Line {line}: No such effect
An effect code in this line is not in the mapping set. In the mapping set, under **Effects**, enter the code next to the effect it belongs to. If the budget does not have this effect yet, add it to the budget first.
Under **Effects**, the mapping set lists only the first eight visible effects of the budget, in budget order. If the effect you need is not among them, you cannot give it a code. The only way out is to leave the column letter of **Effects** under **Columns** empty. KOSMA then stops checking effect codes, but it also imports no effects for any line.
Line {line}: Cannot read column "{column}"
The message names the column: **Date**, **Payment Date** or **Paid Amount**. A cell in that column is filled, but KOSMA cannot read it.
KOSMA reads dates as day.month.year (31.08.2026) or year-month-day (2026-08-31). A cell that Excel formats as a date gets this message too. Format it as text in Excel and enter the date again in one of these forms.
All amounts in a file must use the same notation: German (1.250,00) or English (1,250.00); see [import accounting data](/kb/article/import-accounting-data). In an English-notation file, KOSMA therefore reads 1,250.00 as 1250. If a file mixes both, KOSMA won't get past step **File**.
Correct the cell in the file and choose the file again in step **File**. If the cell looks right, check the column letters of these three fields under **Columns** in the mapping set.
KOSMA skips a line without text and reports no error. This means an empty cell in the **Text** column. That booking is then missing from the import.
You choose one company for the whole file in the mapping set. KOSMA does not check a company per line, so no line can report a company error.
A line whose account cell is empty causes no error and does not block **Continue**. In the **Matching** step, KOSMA shows these lines in the group  **Unmapped**, each with the status **New**.
When you click **Import**, KOSMA asks:
Import Unmatched Cost Items? {number} cost items have no matching account and will be added under "Unmapped". Import anyway?
If many lines are affected, the file probably has no account numbers in them, or **Account** has the wrong column letter under **Columns** in the mapping set. Correct the mapping set first. To import the lines as they are, click **Import Anyway**. KOSMA posts them to the **Unmapped** account. If there is none yet, KOSMA creates it with the number 9999, or the next free number. It sits near the end of the set, but not always at the very end. To find it, type Unmapped in the search box.
In the cost control grid, select the **Unmapped** account. KOSMA opens its **Cost Items** panel. Select the items there and click  **Move**. For the steps, see [move cost items to another account](/kb/article/move-cost-items-to-another-account).
Then correct the account column in the file, or its column letter in the mapping set. Otherwise the next import puts lines on **Unmapped** again.
Markdown