Spendesk cost center mapping (KOST1 / 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.

Related: Spendesk integration, Cost centers on invoice line items, and 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).
3. Scroll to Cost center mapping (DATEV KOST1 / KOST2).

For each dimension:

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 hub page.

Quick reference