---
title: "Get the accounting configuration of the authenticated company."
method: GET
path: "/core/v1/accounting/companies/current"
tags: ["Accounting"]
---

# Get the accounting configuration of the authenticated company.

`GET /core/v1/accounting/companies/current`

## Request

- Base URL: `https://api.klara.ch`
- URL: `https://api.klara.ch/core/v1/accounting/companies/current`
- Auth: one of:
  - API key in header `X-API-KEY`
  - HTTP bearer

Returns the dunning waiting periods configured for the authenticated caller's company together with the canonical compensation-side company URI. Tenant and company are derived from the bearer token — there are no path or query parameters to override them. When the company has no accounting configuration row persisted yet, the downstream service synthesises a default record (<code>id</code> = <code>null</code>, <code>waitingDunningTime</code> = <code>5</code>, <code>dunningWaitingTimeLevelOne</code> / <code>Two</code> / <code>Three</code> = <code>10</code>) so the response shape stays the same. The endpoint is a pure read — idempotent, no side effects. The caller must hold the <code>ACCOUNTING</code> permission on the company in scope.

## Response `200`

Accounting configuration of the caller's company.

- PublicApiAccountingCompany: Accounting configuration of one company — dunning waiting periods plus the canonical company URI.
  - `id` integer: Internal id of the accounting-configuration row. Null when no configuration has been persisted yet for the company.
  - `companyUri` string: Canonical compensation-side URI of the company, of the form /luz_compensation/api/{tenant}/companies/{companyId}.
  - `waitingDunningTime` integer: Number of days to wait after the invoice due date before starting the dunning cycle. Defaults to 5 when no configuration exists yet.
  - `dunningWaitingTimeLevelOne` integer: Days to wait between the level-1 dunning notice and the level-2 escalation. Defaults to 10 when no configuration exists yet.
  - `dunningWaitingTimeLevelTwo` integer: Days to wait between the level-2 dunning notice and the level-3 escalation. Defaults to 10 when no configuration exists yet.
  - `dunningWaitingTimeLevelThree` integer: Days to wait between the level-3 dunning notice and the final escalation. Defaults to 10 when no configuration exists yet.

## Other responses

- `401`: No Authorization header found or invalid token<br/><br/>Failures detected by a downstream service carry that service's own <code>code</code>, which this reference does not enumerate, so the <code>code</code> field may hold a value not documented here. Treat an unrecognised code as a generic failure of the status it arrives with, and do not branch on a code this reference does not list.
- `403`: The current user is not allowed to access this company data<br/><br/>Failures detected by a downstream service carry that service's own <code>code</code>, which this reference does not enumerate, so the <code>code</code> field may hold a value not documented here. Treat an unrecognised code as a generic failure of the status it arrives with, and do not branch on a code this reference does not list.
- `404`: The company associated with the caller's session could not be resolved by the downstream accounting service.<br/><br/>Failures detected by a downstream service carry that service's own <code>code</code>, which this reference does not enumerate, so the <code>code</code> field may hold a value not documented here. Treat an unrecognised code as a generic failure of the status it arrives with, and do not branch on a code this reference does not list.
- `429`: API rate limit exceeded<br/><br/>Failures detected by a downstream service carry that service's own <code>code</code>, which this reference does not enumerate, so the <code>code</code> field may hold a value not documented here. Treat an unrecognised code as a generic failure of the status it arrives with, and do not branch on a code this reference does not list.
- `500`: Something went wrong on our side while processing the request. Please kindly contact our support.<br/><br/>Failures detected by a downstream service carry that service's own <code>code</code>, which this reference does not enumerate, so the <code>code</code> field may hold a value not documented here. Treat an unrecognised code as a generic failure of the status it arrives with, and do not branch on a code this reference does not list.

---

[API](https://skmtc.dev/klara/apis/klara-public-api.md) · [All operations](https://skmtc.dev/klara/apis/klara-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/klara/apis/klara-public-api/revisions/490b1a879fc2?raw)