Import invoices
This article lists the columns you can use when you import invoices 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 Invoices, choose Actions, then Import.
How rows are matched
- Each row is one line of an invoice, for one proposal item. Rows with the same date and name, for proposal items in the same project, belong to one invoice; Kompass creates the invoice with the first of them.
- A row for a proposal item and nominal account the invoice already has updates that line's amounts. Otherwise the row adds a line.
- A row with an
idupdates that invoice.
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.
Invoices
| 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_net |
No | No | Net amount before tax. Required for new invoices. |
amount_tax |
No | No | Tax amount. Required for new invoices. |
approved |
No | No | Date and time the invoice was approved, such as 2026-01-31 14:30. |
approved_by_email |
No | No | Email address of the user who approved the invoice. Or use approved_by_id. |
approved_by_id |
No | No | Kompass ID of the user who approved the invoice. Or use approved_by_email. |
approved_notes |
No | No | Notes added when approving the invoice. |
client_id |
No | No | Kompass ID of the client billed. Leave empty to use the project's billing client. |
date |
No | Yes | Invoice date, such as 2026-01-31. |
details |
No | No | Detailed description shown on the invoice. |
due |
No | No | Payment due date, such as 2026-01-31. |
end |
No | No | Last day of the invoiced period, such as 2026-01-31. |
name |
No | Yes | Invoice name or number. |
nominal_account_id |
No | Yes | Kompass ID of the nominal account. Leave empty for the organization's default. |
notes |
No | No | Internal notes about the invoice. |
posted |
No | No | Date and time the invoice was posted, such as 2026-01-31 14:30. |
posted_by_email |
No | No | Email address of the user who posted the invoice. Or use posted_by_id. |
posted_by_id |
No | No | Kompass ID of the user who posted the invoice. Or use posted_by_email. |
posted_notes |
No | No | Notes added when posting the invoice. |
price_type |
No | Yes | L for a lump sum, R for a rate. With project_id and service_id, finds the quote item. Accepted values: L, R. |
project_id |
No | Yes | Kompass ID of the project. With service_id and price_type, finds the quote item. Or use project_reference. |
project_reference |
No | Yes | Project reference. Can be used instead of project_id. |
quote_item_id |
No | Yes | Kompass ID of the quote item. The simplest way to say which quote item is invoiced. Or use quote_item_name. |
quote_item_name |
No | Yes | Quote item name. Needs project_id or project_reference too. |
rejected |
No | No | Date and time the invoice was rejected, such as 2026-01-31 14:30. |
rejected_by_email |
No | No | Email address of the user who rejected the invoice. Or use rejected_by_id. |
rejected_by_id |
No | No | Kompass ID of the user who rejected the invoice. Or use rejected_by_email. |
rejected_notes |
No | No | Notes added when rejecting the invoice. |
sent |
No | No | Date and time the invoice was sent, such as 2026-01-31 14:30. |
sent_by_email |
No | No | Email address of the user who sent the invoice. Or use sent_by_id. |
sent_by_id |
No | No | Kompass ID of the user who sent the invoice. Or use sent_by_email. |
sent_notes |
No | No | Notes added when sending the invoice. |
service_id |
No | Yes | Kompass ID of the service. With project_id and price_type, finds the quote item. |
start |
No | No | First day of the invoiced period, such as 2026-01-31. |
submitted |
No | No | Date and time the invoice was submitted, such as 2026-01-31 14:30. |
submitted_by_email |
No | No | Email address of the user who submitted the invoice. Or use submitted_by_id. |
submitted_by_id |
No | No | Kompass ID of the user who submitted the invoice. Or use submitted_by_email. |
submitted_notes |
No | No | Notes added when submitting the invoice. |
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. |
udf |
No | No | Custom field values. Copy the format from an export of this list. Leave the column out to keep the current values. |
udf_schema_id |
No | No | ID of the custom field set to use. Leave empty for the default invoice set. |
voided |
No | No | Date and time the invoice was voided, such as 2026-01-31 14:30. |
voided_by_email |
No | No | Email address of the user who voided the invoice. Or use voided_by_id. |
voided_by_id |
No | No | Kompass ID of the user who voided the invoice. Or use voided_by_email. |
voided_notes |
No | No | Notes added when voiding the invoice. |