Import expenses and expense allocations
This article lists the columns you can use when you import expenses and expense allocations from a CSV file, and how Kompass decides whether a row updates an existing record or adds a new one. For how the Import dialog works, see Import records from a CSV file. Developers using the API can find the same columns in the API reference.
Where to import
Open Expenses, choose Actions, then Import Expenses or Import Expense Allocations.
How rows are matched
- Expenses: a row with an
idupdates that expense. A row without one adds a new expense. If an expense with the same date, amount (or currency and amount in that currency), description, notes and supplier already exists, and the same user when the row names one, the row is reported as a duplicate and nothing is saved. - Expense allocations: a row with an
idupdates that allocation; a row without one adds an allocation. Withexpense_id, the expense columns on the row update that expense; without it, Kompass uses an existing expense with the same date, amount, description, notes, supplier and user, or adds one. Unlike an expense row, a matching expense is not a duplicate here. Put 1 or yes in thedeletecolumn to remove an allocation. - Adding an expense needs
date,payment_method_idand an amount:amount, oramount_localfor an expense in another currency. - Adding an allocation without
expense_idneedsexpense_amount,expense_date,expense_description,expense_org_idandexpense_payment_method_id. A row that updates an allocation by itsidcan leave all the expense columns out, and the allocation keeps its expense.
To understand more the differences between expenses and expense allocations, please check our Expenses How-to Guides here.
Reading the column tables
Required marks a column a new record needs. A row that updates an existing record only changes the columns in your file, so you can leave the others out. Finds the record marks a column Kompass uses to find the existing record a row updates. Column names must match exactly, including underscores. Where a column only takes certain values, the description lists them. A column marked Needs an extra permission is only accepted from users who have that permission; for anyone else the import reports it as an unknown column. The Download template button in the Import dialog gives you the header row for your own permissions.
Expenses
| Column | Required | Finds the record | Description |
|---|---|---|---|
id |
No | Yes | Kompass ID of the record to update. When empty, the row adds a new record unless its other columns match an existing one. |
amount |
No | No | Amount in your organization's base currency. Required for a new expense in the base currency; an update can leave it out. For a new expense in another currency, give amount_local, or give this amount to have it converted at the exchange rate. |
amount_local |
No | No | Amount in the expense's currency, for a new expense in another currency. Wins over amount when both are given. Ignored on a new expense in the base currency; leave it empty when updating an expense. An expense in another currency cannot be updated by import. |
currency_code |
No | No | Three-letter currency code, such as EUR or USD. Leave empty for your base currency. New expenses only. |
currency_rate |
No | No | How much of your base currency one unit of the expense currency is worth. Leave empty to use your saved exchange rates. New expenses only. |
approved |
No | No | Date and time the expense was approved, such as 2026-01-31 14:30. |
approved_by_id |
No | No | Kompass ID of the user who approved the expense. |
approved_notes |
No | No | Notes added when approving the expense. |
checked |
No | No | Date and time the expense was checked, such as 2026-01-31 14:30. |
checked_by_id |
No | No | Kompass ID of the user who checked the expense. |
checked_notes |
No | No | Notes added when checking the expense. |
date |
Yes | No | Date of the expense, such as 2026-01-31. |
description |
No | No | Description of the expense. |
notes |
No | No | Internal notes about the expense. |
org_id |
No | No | Kompass ID of the organization the expense belongs to. |
payment_method_id |
No | No | Kompass ID of the payment method used. |
rejected |
No | No | Date and time the expense was rejected, such as 2026-01-31 14:30. |
rejected_by_id |
No | No | Kompass ID of the user who rejected the expense. |
rejected_notes |
No | No | Notes added when rejecting the expense. |
submitted |
No | No | Date and time the expense was submitted, such as 2026-01-31 14:30. |
submitted_by_id |
No | No | Kompass ID of the user who submitted the expense. |
submitted_notes |
No | No | Notes added when submitting the expense. |
supplier_id |
No | No | Kompass ID of the supplier. Or use supplier_name. |
supplier_name |
No | No | Name of the supplier. Or use supplier_id. |
tags |
No | No | Tag names separated by commas, or a list in square brackets such as ["Design, Build"] for a name that contains a comma. The record gets exactly these tags; an empty cell removes them all. |
user_id |
No | No | Kompass ID of the user the expense belongs to. |
Expense allocations
| Column | Required | Finds the record | Description |
|---|---|---|---|
id |
No | Yes | Kompass ID of the record to update. When empty, the row adds a new record unless its other columns match an existing one. |
amount |
Yes | No | Amount allocated to the quote item, in your organization's base currency. |
billable |
No | No | Put yes if the allocation is billable. |
expense_id |
No | No | Kompass ID of the expense this line belongs to. When filled in, the expense columns on the row update that expense instead of being used to find it. |
notes |
No | No | Notes about the allocation. |
quote_item_id |
Yes | No | Kompass ID of the quote item the amount is allocated to. |
type_id |
Yes | No | Kompass ID of the expense type. |
expense_amount |
No | No | Amount of the expense, in your organization's base currency. |
expense_approved |
No | No | Date and time the expense was approved, such as 2026-01-31 14:30. |
expense_approved_by_id |
No | No | Kompass ID of the user who approved the expense. |
expense_approved_notes |
No | No | Notes added when approving the expense. |
expense_checked |
No | No | Date and time the expense was checked, such as 2026-01-31 14:30. |
expense_checked_by_id |
No | No | Kompass ID of the user who checked the expense. |
expense_checked_notes |
No | No | Notes added when checking the expense. |
expense_date |
No | No | Date of the expense, such as 2026-01-31. |
expense_description |
No | No | Description of the expense. |
expense_notes |
No | No | Internal notes about the expense. |
expense_payment_method_id |
No | No | Kompass ID of the payment method used. |
expense_rejected |
No | No | Date and time the expense was rejected, such as 2026-01-31 14:30. |
expense_rejected_by_id |
No | No | Kompass ID of the user who rejected the expense. |
expense_rejected_notes |
No | No | Notes added when rejecting the expense. |
expense_submitted |
No | No | Date and time the expense was submitted, such as 2026-01-31 14:30. |
expense_submitted_by_id |
No | No | Kompass ID of the user who submitted the expense. |
expense_submitted_notes |
No | No | Notes added when submitting the expense. |
expense_supplier_id |
No | No | Kompass ID of the supplier. Or use expense_supplier_name. |
expense_supplier_name |
No | No | Name of the supplier. Or use expense_supplier_id. |
expense_user_id |
No | No | Kompass ID of the user the expense belongs to. |
expense_org_id |
No | No | Kompass ID of the organization the expense belongs to. |
delete |
No | No | Put 1 or yes to delete the matching record. |