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:
**Message:** {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. To fix an error in the file, correct and save the file, 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. For how to change a mapping set, see [set up an import mapping set](/kb/article/set-up-an-import-mapping-set).
**Message:** 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. If the file uses the same account numbers as the budget, use **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 it is not ticked, tick it. Ticking it replaces the numbers you entered by hand.
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.
**Message:** 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 the order of the budget. A new effect appears there only if it is among these eight. KOSMA checks effect codes only if **Effects** has a column letter under **Columns**. If you leave that column letter empty, effects are optional, and KOSMA imports no effects. Do this if the effect you need is not among the first eight, because it cannot get a code.
**Message:** Line {line}: Cannot read "{column}" (column name)
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 a date only in the form day.month.year, such as 31.08.2026. A cell that Excel formats as a date gets this message too. KOSMA reads an amount in **Paid Amount** only as a number. An amount with a comma between the thousands, such as 1,250.00, gets no message: KOSMA reads it as 1.25. Correct the cell in the file and choose the file again in step **File**, or check under **Columns** in the mapping set that these fields point at the right column letters. KOSMA skips a line whose **Text** cell is empty and reports no error.
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:
**Message:** Import Unmatched Cost Items? {number} cost items have no matching account and will be added under "Unmapped". Import anyway?
If the number is high, the file probably has no account numbers in these lines, or **Account** has the wrong column letter under **Columns** in the mapping set. In that case, correct the mapping set before you import. To import the lines as they are, click **Import Anyway**. KOSMA creates an account named **Unmapped** with the number 9999, or the next free number, as the last account of an account group, and books the lines on it. That is not always the last group of the set. To find the account, type Unmapped in the search box. Each import with such lines creates another **Unmapped** account. KOSMA never adds lines to an earlier **Unmapped** account.
In the cost control grid, select the **Unmapped** account. KOSMA opens its **Cost Items** panel. Select the items there and click  **Move**. You can move items only from an account's **Cost Items** panel. 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 creates another **Unmapped** account.
Markdown