# Spendesk cost center mapping (KOST1 / KOST2)

Map Spendesk cost centers to KOST1 and KOST2.

Map Spendesk dimensions to Cortena **cost centers** before payables sync · so DATEV export receives the correct **KOST1** (primary) and optional **KOST2** values on imported Spendesk invoices.

**Who this is for:** Admins connecting **Spendesk** for a German DATEV workspace who use Kostenstellen on bookings and need Spendesk analytical fields to land in the right Cortena cost center slots.

Related: [Spendesk integration](https://help.cortena.ai/guides/integrations/spendesk), [Cost centers on invoice line items](https://help.cortena.ai/guides/invoices/cost-centers-line-items), and [Expense workflow](https://help.cortena.ai/guides/workflows/expense-workflow).

## 1. Open mapping in Settings

1. Open **Settings → Integrations → Expense management**.
2. Connect **Spendesk** (API client with read access; optional bookkeeping write if you use Spendesk export ownership · see [Spendesk integration](https://help.cortena.ai/guides/integrations/spendesk)).
3. Scroll to **Cost center mapping (DATEV KOST1 / KOST2)**.

For each dimension:

| Field | Meaning |
| --- | --- |
| **KOST1 (primary)** | Required mapping · which Spendesk dimension feeds Cortena’s primary cost center used on DATEV export |
| **KOST2** | Optional second dimension when your chart uses two KOST slots |

Choose the Spendesk dimension source for each slot from the dropdowns (values come from your Spendesk account).

4. Click **Save** on the Spendesk integration card.

## 2. Sync gate (save before sync)

Spendesk **Sync now** for payables stays disabled until a valid **KOST1** mapping is saved:

- Banner: *Save a cost center mapping below before Spendesk payables can sync.*
- **Sync now** shows hint: *Save cost center mapping first*.

This prevents importing expenses without export-ready KOST data.

## 3. After sync · on invoices

Imported Spendesk payables receive cost centers according to your mapping. On payable detail:

- Header **KOST1** / **KOST2** (or line-item KOST when line-level cost centers are enabled for the tenant) reflect mapped values.
- DATEV **Buchungsstapel** export uses the same stored cost centers as the invoice detail view.

Adjust mapping in Settings, save, then run **Sync now** for new imports; already-imported invoices keep values from the sync that created them unless reprocessed or edited.

## Tips and limitations

- Mapping is **per workspace** · configure each Spendesk-connected tenant separately.
- **KOST1** is mandatory for payables sync; **KOST2** is optional.
- If Spendesk changes dimension names, refresh mapping and save before the next sync.
- Full connect steps, DATEV vs Spendesk export ownership, and list workspace by payable type remain on the [Spendesk integration](https://help.cortena.ai/guides/integrations/spendesk) hub page.

## Quick reference

| Task | Where |
| --- | --- |
| Map dimensions | **Settings → Integrations → Expense management → Spendesk** |
| Primary KOST | **KOST1 (primary)** dropdown |
| Optional second | **KOST2** dropdown |
| Enable sync | **Save** mapping, then **Sync now** |
| Verify on invoice | Payable detail cost center fields |
| Connect Spendesk | [Spendesk integration](https://help.cortena.ai/guides/integrations/spendesk) |