@spaceinvoices/js-sdk 14.6.0 → 14.7.0

package/dist/generated/entity-users/entity-users.d.cts

@@ -44,7 +44,7 @@ export type getEntityUsersResponse = (getEntityUsersResponseSuccess | getEntityU
 export declare const getGetEntityUsersUrl: (params?: GetEntityUsersParams) => string;
 export declare const getEntityUsers: (params?: GetEntityUsersParams, options?: RequestInit) => Promise<getEntityUsersResponse>;
 /**
- * Add an existing white-label user for this account to the entity or send an invitation. Existing account users must accept the invitation so they receive separate entity-user access. With `silent: true` no email is sent (`send_invite` is ignored): a missing white-label user is created immediately (no password, optional `metadata`) and linked to the entity, and an existing white-label user is linked. Silent provisioning requires an account API key or an account owner/admin signed in directly (an interactive session); delegated (SSO) tokens are rejected. The new user's email counts as verified when the credential is an account API key or a user token whose email is verified; otherwise the user must verify their email before sending documents by email. Silent provisioning can be followed by `POST /entities/users/{user_id}/token` with `ttl` to embed the user.
+ * Add an existing white-label user for this account to the entity or send an invitation. The `accountant` role cannot be assigned this way (422). Existing account users must accept the invitation so they receive separate entity-user access. With `silent: true` no email is sent (`send_invite` is ignored): a missing white-label user is created immediately (no password, optional `metadata`) and linked to the entity, and an existing white-label user is linked. Silent provisioning requires an account API key or an account owner/admin signed in directly (an interactive session); delegated (SSO) tokens are rejected. The new user's email counts as verified when the credential is an account API key or a user token whose email is verified; otherwise the user must verify their email before sending documents by email. Silent provisioning can be followed by `POST /entities/users/{user_id}/token` with `ttl` to embed the user.
  * @summary Add user to entity
  */
 export type addEntityUserResponse201 = {
@@ -122,7 +122,7 @@ export type getEntityUsersAccessResponse = (getEntityUsersAccessResponseSuccess
 export declare const getGetEntityUsersAccessUrl: () => string;
 export declare const getEntityUsersAccess: (options?: RequestInit) => Promise<getEntityUsersAccessResponse>;
 /**
- * Update a user's role, metadata, or both. Send at least one of `role` and `metadata`. Roles: viewer (read-only), editor (read+write), admin (full access), staff (issues invoices and sees only their own). `metadata` replaces the stored object as a whole (string key-value data, up to 50 keys; `null` clears it) and is only available for the entity account's own white-label users (400 otherwise). Omitted fields are left unchanged.
+ * Update a user's role, metadata, or both. Send at least one of `role` and `metadata`. Roles you can assign: viewer (read-only), editor (read+write), admin (full access), staff (issues invoices and sees only their own). The `accountant` role (works like editor and also uses the accounting module) cannot be assigned here: a request naming it is refused with 422, and so is changing the role of a user who already is an accountant (remove them with `DELETE /entities/users/{user_id}` instead). `metadata` replaces the stored object as a whole (string key-value data, up to 50 keys; `null` clears it) and is only available for the entity account's own white-label users (400 otherwise). Omitted fields are left unchanged.
  * @summary Update user role or metadata
  */
 export type updateEntityUserRoleResponse200 = {

package/dist/generated/entity-users/entity-users.d.ts

@@ -44,7 +44,7 @@ export type getEntityUsersResponse = (getEntityUsersResponseSuccess | getEntityU
 export declare const getGetEntityUsersUrl: (params?: GetEntityUsersParams) => string;
 export declare const getEntityUsers: (params?: GetEntityUsersParams, options?: RequestInit) => Promise<getEntityUsersResponse>;
 /**
- * Add an existing white-label user for this account to the entity or send an invitation. Existing account users must accept the invitation so they receive separate entity-user access. With `silent: true` no email is sent (`send_invite` is ignored): a missing white-label user is created immediately (no password, optional `metadata`) and linked to the entity, and an existing white-label user is linked. Silent provisioning requires an account API key or an account owner/admin signed in directly (an interactive session); delegated (SSO) tokens are rejected. The new user's email counts as verified when the credential is an account API key or a user token whose email is verified; otherwise the user must verify their email before sending documents by email. Silent provisioning can be followed by `POST /entities/users/{user_id}/token` with `ttl` to embed the user.
+ * Add an existing white-label user for this account to the entity or send an invitation. The `accountant` role cannot be assigned this way (422). Existing account users must accept the invitation so they receive separate entity-user access. With `silent: true` no email is sent (`send_invite` is ignored): a missing white-label user is created immediately (no password, optional `metadata`) and linked to the entity, and an existing white-label user is linked. Silent provisioning requires an account API key or an account owner/admin signed in directly (an interactive session); delegated (SSO) tokens are rejected. The new user's email counts as verified when the credential is an account API key or a user token whose email is verified; otherwise the user must verify their email before sending documents by email. Silent provisioning can be followed by `POST /entities/users/{user_id}/token` with `ttl` to embed the user.
  * @summary Add user to entity
  */
 export type addEntityUserResponse201 = {
@@ -122,7 +122,7 @@ export type getEntityUsersAccessResponse = (getEntityUsersAccessResponseSuccess
 export declare const getGetEntityUsersAccessUrl: () => string;
 export declare const getEntityUsersAccess: (options?: RequestInit) => Promise<getEntityUsersAccessResponse>;
 /**
- * Update a user's role, metadata, or both. Send at least one of `role` and `metadata`. Roles: viewer (read-only), editor (read+write), admin (full access), staff (issues invoices and sees only their own). `metadata` replaces the stored object as a whole (string key-value data, up to 50 keys; `null` clears it) and is only available for the entity account's own white-label users (400 otherwise). Omitted fields are left unchanged.
+ * Update a user's role, metadata, or both. Send at least one of `role` and `metadata`. Roles you can assign: viewer (read-only), editor (read+write), admin (full access), staff (issues invoices and sees only their own). The `accountant` role (works like editor and also uses the accounting module) cannot be assigned here: a request naming it is refused with 422, and so is changing the role of a user who already is an accountant (remove them with `DELETE /entities/users/{user_id}` instead). `metadata` replaces the stored object as a whole (string key-value data, up to 50 keys; `null` clears it) and is only available for the entity account's own white-label users (400 otherwise). Omitted fields are left unchanged.
  * @summary Update user role or metadata
  */
 export type updateEntityUserRoleResponse200 = {

package/dist/generated/model/accountingSettings.d.cts

@@ -18,7 +18,7 @@ export interface AccountingSettings {
      */
     files_recapitulative_statement?: boolean | null;
     /**
-     * Email addresses notified about accounting module filing reminders. Each must belong to a user with a verified email and non-staff access to the entity: an entity user whose role is not staff, or any member of the entity's account (owner, admin or member); other addresses are rejected with 422. Reminders are sent only to recipients who are still eligible when they are sent: someone who lost access, was made a staff user or is a white-label user is skipped.
+     * Email addresses notified about accounting module filing reminders. Each must belong to a user with a verified email and non-staff access to the entity: an entity user whose role is not staff, or any member of the entity's account (owner, admin or member); other addresses are rejected with 422. Reminders are sent only to recipients who are still eligible when they are sent: someone who lost access, was made a staff user or is a white-label user who is not an accountant is skipped.
      * @maxItems 10
      * @nullable
      */

package/dist/generated/model/accountingSettings.d.ts

@@ -18,7 +18,7 @@ export interface AccountingSettings {
      */
     files_recapitulative_statement?: boolean | null;
     /**
-     * Email addresses notified about accounting module filing reminders. Each must belong to a user with a verified email and non-staff access to the entity: an entity user whose role is not staff, or any member of the entity's account (owner, admin or member); other addresses are rejected with 422. Reminders are sent only to recipients who are still eligible when they are sent: someone who lost access, was made a staff user or is a white-label user is skipped.
+     * Email addresses notified about accounting module filing reminders. Each must belong to a user with a verified email and non-staff access to the entity: an entity user whose role is not staff, or any member of the entity's account (owner, admin or member); other addresses are rejected with 422. Reminders are sent only to recipients who are still eligible when they are sent: someone who lost access, was made a staff user or is a white-label user who is not an accountant is skipped.
      * @maxItems 10
      * @nullable
      */

package/dist/generated/model/createdUser.d.cts

@@ -29,6 +29,8 @@ export interface CreatedUser {
      * @nullable
      */
     metadata?: CreatedUserMetadata;
+    /** Whether the user signed up as an accountant. Read-only. Clients must treat an absent value as false. */
+    is_accountant?: boolean;
     created_at: string;
     updated_at: string;
 }

package/dist/generated/model/createdUser.d.ts

@@ -29,6 +29,8 @@ export interface CreatedUser {
      * @nullable
      */
     metadata?: CreatedUserMetadata;
+    /** Whether the user signed up as an accountant. Read-only. Clients must treat an absent value as false. */
+    is_accountant?: boolean;
     created_at: string;
     updated_at: string;
 }

package/dist/generated/model/entityInvitation.d.cts

@@ -14,7 +14,7 @@ export interface EntityInvitation {
     entity_id: string;
     /** Invitee email */
     email: string;
-    /** User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, and `staff` issues invoices and works only with the invoices they created. */
+    /** User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, `staff` issues invoices and works only with the invoices they created, and `accountant` works like `editor` and also uses the accounting module. */
     role: EntityInvitationRole;
     /** ID of user who sent the invitation */
     invited_by_user_id: string;

package/dist/generated/model/entityInvitation.d.ts

@@ -14,7 +14,7 @@ export interface EntityInvitation {
     entity_id: string;
     /** Invitee email */
     email: string;
-    /** User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, and `staff` issues invoices and works only with the invoices they created. */
+    /** User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, `staff` issues invoices and works only with the invoices they created, and `accountant` works like `editor` and also uses the accounting module. */
     role: EntityInvitationRole;
     /** ID of user who sent the invitation */
     invited_by_user_id: string;

package/dist/generated/model/entityInvitationPreview.d.cts

@@ -11,7 +11,7 @@ export interface EntityInvitationPreview {
     email: string;
     entity_name: string;
     existing_user: boolean;
-    /** User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, and `staff` issues invoices and works only with the invoices they created. */
+    /** User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, `staff` issues invoices and works only with the invoices they created, and `accountant` works like `editor` and also uses the accounting module. */
     role: EntityInvitationPreviewRole;
     status: EntityInvitationPreviewStatus;
     expires_at: string;

package/dist/generated/model/entityInvitationPreview.d.ts

@@ -11,7 +11,7 @@ export interface EntityInvitationPreview {
     email: string;
     entity_name: string;
     existing_user: boolean;
-    /** User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, and `staff` issues invoices and works only with the invoices they created. */
+    /** User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, `staff` issues invoices and works only with the invoices they created, and `accountant` works like `editor` and also uses the accounting module. */
     role: EntityInvitationPreviewRole;
     status: EntityInvitationPreviewStatus;
     expires_at: string;

package/dist/generated/model/entityInvitationPreviewRole.d.cts

@@ -6,7 +6,7 @@
  * OpenAPI spec version: 1.0.0
  */
 /**
- * User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, and `staff` issues invoices and works only with the invoices they created.
+ * User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, `staff` issues invoices and works only with the invoices they created, and `accountant` works like `editor` and also uses the accounting module.
  */
 export type EntityInvitationPreviewRole = typeof EntityInvitationPreviewRole[keyof typeof EntityInvitationPreviewRole];
 export declare const EntityInvitationPreviewRole: {
@@ -14,4 +14,5 @@ export declare const EntityInvitationPreviewRole: {
     readonly editor: "editor";
     readonly admin: "admin";
     readonly staff: "staff";
+    readonly accountant: "accountant";
 };

package/dist/generated/model/entityInvitationPreviewRole.d.ts

@@ -6,7 +6,7 @@
  * OpenAPI spec version: 1.0.0
  */
 /**
- * User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, and `staff` issues invoices and works only with the invoices they created.
+ * User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, `staff` issues invoices and works only with the invoices they created, and `accountant` works like `editor` and also uses the accounting module.
  */
 export type EntityInvitationPreviewRole = typeof EntityInvitationPreviewRole[keyof typeof EntityInvitationPreviewRole];
 export declare const EntityInvitationPreviewRole: {
@@ -14,4 +14,5 @@ export declare const EntityInvitationPreviewRole: {
     readonly editor: "editor";
     readonly admin: "admin";
     readonly staff: "staff";
+    readonly accountant: "accountant";
 };

package/dist/generated/model/entityInvitationRole.d.cts

@@ -6,7 +6,7 @@
  * OpenAPI spec version: 1.0.0
  */
 /**
- * User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, and `staff` issues invoices and works only with the invoices they created.
+ * User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, `staff` issues invoices and works only with the invoices they created, and `accountant` works like `editor` and also uses the accounting module.
  */
 export type EntityInvitationRole = typeof EntityInvitationRole[keyof typeof EntityInvitationRole];
 export declare const EntityInvitationRole: {
@@ -14,4 +14,5 @@ export declare const EntityInvitationRole: {
     readonly editor: "editor";
     readonly admin: "admin";
     readonly staff: "staff";
+    readonly accountant: "accountant";
 };

package/dist/generated/model/entityInvitationRole.d.ts

@@ -6,7 +6,7 @@
  * OpenAPI spec version: 1.0.0
  */
 /**
- * User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, and `staff` issues invoices and works only with the invoices they created.
+ * User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, `staff` issues invoices and works only with the invoices they created, and `accountant` works like `editor` and also uses the accounting module.
  */
 export type EntityInvitationRole = typeof EntityInvitationRole[keyof typeof EntityInvitationRole];
 export declare const EntityInvitationRole: {
@@ -14,4 +14,5 @@ export declare const EntityInvitationRole: {
     readonly editor: "editor";
     readonly admin: "admin";
     readonly staff: "staff";
+    readonly accountant: "accountant";
 };

package/dist/generated/model/entityUser.d.cts

@@ -12,7 +12,7 @@ export interface EntityUser {
     user_id: string;
     /** Entity ID */
     entity_id: string;
-    /** User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, and `staff` issues invoices and works only with the invoices they created. */
+    /** User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, `staff` issues invoices and works only with the invoices they created, and `accountant` works like `editor` and also uses the accounting module. */
     role: EntityUserRole;
     /** User email */
     email: string;

package/dist/generated/model/entityUser.d.ts

@@ -12,7 +12,7 @@ export interface EntityUser {
     user_id: string;
     /** Entity ID */
     entity_id: string;
-    /** User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, and `staff` issues invoices and works only with the invoices they created. */
+    /** User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, `staff` issues invoices and works only with the invoices they created, and `accountant` works like `editor` and also uses the accounting module. */
     role: EntityUserRole;
     /** User email */
     email: string;

package/dist/generated/model/entityUserRole.d.cts

@@ -6,7 +6,7 @@
  * OpenAPI spec version: 1.0.0
  */
 /**
- * User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, and `staff` issues invoices and works only with the invoices they created.
+ * User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, `staff` issues invoices and works only with the invoices they created, and `accountant` works like `editor` and also uses the accounting module.
  */
 export type EntityUserRole = typeof EntityUserRole[keyof typeof EntityUserRole];
 export declare const EntityUserRole: {
@@ -14,4 +14,5 @@ export declare const EntityUserRole: {
     readonly editor: "editor";
     readonly admin: "admin";
     readonly staff: "staff";
+    readonly accountant: "accountant";
 };

package/dist/generated/model/entityUserRole.d.ts

@@ -6,7 +6,7 @@
  * OpenAPI spec version: 1.0.0
  */
 /**
- * User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, and `staff` issues invoices and works only with the invoices they created.
+ * User role on the entity. `viewer` reads, `editor` also writes, `admin` also manages users and settings, `staff` issues invoices and works only with the invoices they created, and `accountant` works like `editor` and also uses the accounting module.
  */
 export type EntityUserRole = typeof EntityUserRole[keyof typeof EntityUserRole];
 export declare const EntityUserRole: {
@@ -14,4 +14,5 @@ export declare const EntityUserRole: {
     readonly editor: "editor";
     readonly admin: "admin";
     readonly staff: "staff";
+    readonly accountant: "accountant";
 };

package/dist/generated/model/entityUsersAccess.d.cts

@@ -35,6 +35,8 @@ export interface EntityUsersAccess {
     can_manage_entity_settings?: boolean;
     /** Whether the actor can issue invoices and work with the ones they created. When `can_read_entity` is false, the actor sees only those invoices. */
     can_use_own_documents?: boolean;
+    /** Whether the actor can use the accounting module for this entity. Only the `accountant` role can. Clients must treat an absent value as false. */
+    can_use_accounting?: boolean;
     /** Whether final entity admin demotion/removal must be blocked for this actor */
     enforce_entity_admin_preservation: boolean;
 }

package/dist/generated/model/entityUsersAccess.d.ts

@@ -35,6 +35,8 @@ export interface EntityUsersAccess {
     can_manage_entity_settings?: boolean;
     /** Whether the actor can issue invoices and work with the ones they created. When `can_read_entity` is false, the actor sees only those invoices. */
     can_use_own_documents?: boolean;
+    /** Whether the actor can use the accounting module for this entity. Only the `accountant` role can. Clients must treat an absent value as false. */
+    can_use_accounting?: boolean;
     /** Whether final entity admin demotion/removal must be blocked for this actor */
     enforce_entity_admin_preservation: boolean;
 }

package/dist/generated/model/entityUsersAccessEntityRole.d.cts

@@ -15,4 +15,5 @@ export declare const EntityUsersAccessEntityRole: {
     readonly editor: "editor";
     readonly admin: "admin";
     readonly staff: "staff";
+    readonly accountant: "accountant";
 };

package/dist/generated/model/entityUsersAccessEntityRole.d.ts

@@ -15,4 +15,5 @@ export declare const EntityUsersAccessEntityRole: {
     readonly editor: "editor";
     readonly admin: "admin";
     readonly staff: "staff";
+    readonly accountant: "accountant";
 };

package/dist/generated/model/updateEntityUserRoleBody.d.cts

@@ -8,7 +8,7 @@
 import type { UpdateEntityUserRoleBodyMetadata } from './updateEntityUserRoleBodyMetadata.cjs';
 import type { UpdateEntityUserRoleBodyRole } from './updateEntityUserRoleBodyRole.cjs';
 export type UpdateEntityUserRoleBody = {
-    /** New role to assign to the user. Omit to leave the role unchanged. */
+    /** New role to assign to the user. Omit to leave the role unchanged. The role of an existing accountant cannot be changed (422); remove the accountant from the entity instead. */
     role?: UpdateEntityUserRoleBodyRole;
     /**
      * Replaces the white-label user's metadata. Send `null` to clear it. Omit to leave it unchanged. Only available for white-label users of the entity's account.

package/dist/generated/model/updateEntityUserRoleBody.d.ts

@@ -8,7 +8,7 @@
 import type { UpdateEntityUserRoleBodyMetadata } from './updateEntityUserRoleBodyMetadata.js';
 import type { UpdateEntityUserRoleBodyRole } from './updateEntityUserRoleBodyRole.js';
 export type UpdateEntityUserRoleBody = {
-    /** New role to assign to the user. Omit to leave the role unchanged. */
+    /** New role to assign to the user. Omit to leave the role unchanged. The role of an existing accountant cannot be changed (422); remove the accountant from the entity instead. */
     role?: UpdateEntityUserRoleBodyRole;
     /**
      * Replaces the white-label user's metadata. Send `null` to clear it. Omit to leave it unchanged. Only available for white-label users of the entity's account.

package/dist/generated/model/updateEntityUserRoleBodyRole.d.cts

@@ -6,7 +6,7 @@
  * OpenAPI spec version: 1.0.0
  */
 /**
- * New role to assign to the user. Omit to leave the role unchanged.
+ * New role to assign to the user. Omit to leave the role unchanged. The role of an existing accountant cannot be changed (422); remove the accountant from the entity instead.
  */
 export type UpdateEntityUserRoleBodyRole = typeof UpdateEntityUserRoleBodyRole[keyof typeof UpdateEntityUserRoleBodyRole];
 export declare const UpdateEntityUserRoleBodyRole: {

package/dist/generated/model/updateEntityUserRoleBodyRole.d.ts

@@ -6,7 +6,7 @@
  * OpenAPI spec version: 1.0.0
  */
 /**
- * New role to assign to the user. Omit to leave the role unchanged.
+ * New role to assign to the user. Omit to leave the role unchanged. The role of an existing accountant cannot be changed (422); remove the accountant from the entity instead.
  */
 export type UpdateEntityUserRoleBodyRole = typeof UpdateEntityUserRoleBodyRole[keyof typeof UpdateEntityUserRoleBodyRole];
 export declare const UpdateEntityUserRoleBodyRole: {

package/dist/generated/model/user.d.cts

@@ -25,6 +25,8 @@ export interface User {
     account_id?: string | null;
     settings: UserSettings;
     metadata: UserMetadata;
+    /** Whether the user signed up as an accountant. Read-only. Clients must treat an absent value as false. */
+    is_accountant?: boolean;
     created_at: string;
     updated_at: string;
 }

package/dist/generated/model/user.d.ts

@@ -25,6 +25,8 @@ export interface User {
     account_id?: string | null;
     settings: UserSettings;
     metadata: UserMetadata;
+    /** Whether the user signed up as an accountant. Read-only. Clients must treat an absent value as false. */
+    is_accountant?: boolean;
     created_at: string;
     updated_at: string;
 }

package/dist/generated/tax-reports/tax-reports.d.cts

@@ -375,7 +375,7 @@ export type getPayrollParameterHistoryResponse = (getPayrollParameterHistoryResp
 export declare const getGetPayrollParameterHistoryUrl: (params: GetPayrollParameterHistoryParams) => string;
 export declare const getPayrollParameterHistory: (params: GetPayrollParameterHistoryParams, options?: RequestInit) => Promise<getPayrollParameterHistoryResponse>;
 /**
- * Admin only. Creates an effective-dated override row for the current entity.
+ * Accountant only. Creates an effective-dated override row for the current entity.
  * @summary Set an entity-specific override for a payroll parameter
  */
 export type setPayrollParameterOverrideResponse200 = {
@@ -1240,7 +1240,7 @@ export type recomputeVatReturnResponse = (recomputeVatReturnResponseSuccess | re
 export declare const getRecomputeVatReturnUrl: (id: string) => string;
 export declare const recomputeVatReturn: (id: string, options?: RequestInit) => Promise<recomputeVatReturnResponse>;
 /**
- * @summary Approve a draft VAT return (entity admin only)
+ * @summary Approve a draft VAT return (accountant only)
  */
 export type approveVatReturnResponse200 = {
     data: VatReturn;
@@ -1284,7 +1284,7 @@ export type approveVatReturnResponse = (approveVatReturnResponseSuccess | approv
 export declare const getApproveVatReturnUrl: (id: string) => string;
 export declare const approveVatReturn: (id: string, options?: RequestInit) => Promise<approveVatReturnResponse>;
 /**
- * @summary Record a VAT return as submitted to eDavki (entity admin only)
+ * @summary Record a VAT return as submitted to eDavki (accountant only)
  */
 export type submitVatReturnResponse200 = {
     data: VatReturn;
@@ -1328,7 +1328,7 @@ export type submitVatReturnResponse = (submitVatReturnResponseSuccess | submitVa
 export declare const getSubmitVatReturnUrl: (id: string) => string;
 export declare const submitVatReturn: (id: string, submitVatReturnRequest?: SubmitVatReturnRequest, options?: RequestInit) => Promise<submitVatReturnResponse>;
 /**
- * @summary Reopen an approved VAT return back to draft (entity admin only)
+ * @summary Reopen an approved VAT return back to draft (accountant only)
  */
 export type reopenVatReturnResponse200 = {
     data: VatReturn;
@@ -1590,7 +1590,7 @@ export type dismissFilingResponse = (dismissFilingResponseSuccess | dismissFilin
 export declare const getDismissFilingUrl: (id: string) => string;
 export declare const dismissFiling: (id: string, dismissFilingRequest?: DismissFilingRequest, options?: RequestInit) => Promise<dismissFilingResponse>;
 /**
- * Account-level view for accountants managing more than one entity: returns the filing obligations of the account's entities that can use the accounting module, each tagged with its entity id and name; other entities are left out. Scoped to one environment (`environment` query param, defaults to "live"), so live and sandbox entities are not mixed in one response.
+ * Account-level view for accountants managing more than one entity: returns the filing obligations of the account's entities where the caller is the company's accountant and the accounting module is available, each tagged with its entity id and name; other entities are left out. Scoped to one environment (`environment` query param, defaults to "live"), so live and sandbox entities are not mixed in one response.
  * @summary List filing-calendar obligations across the account's entities
  */
 export type listAccountFilingsCalendarResponse200 = {

package/dist/generated/tax-reports/tax-reports.d.ts

@@ -375,7 +375,7 @@ export type getPayrollParameterHistoryResponse = (getPayrollParameterHistoryResp
 export declare const getGetPayrollParameterHistoryUrl: (params: GetPayrollParameterHistoryParams) => string;
 export declare const getPayrollParameterHistory: (params: GetPayrollParameterHistoryParams, options?: RequestInit) => Promise<getPayrollParameterHistoryResponse>;
 /**
- * Admin only. Creates an effective-dated override row for the current entity.
+ * Accountant only. Creates an effective-dated override row for the current entity.
  * @summary Set an entity-specific override for a payroll parameter
  */
 export type setPayrollParameterOverrideResponse200 = {
@@ -1240,7 +1240,7 @@ export type recomputeVatReturnResponse = (recomputeVatReturnResponseSuccess | re
 export declare const getRecomputeVatReturnUrl: (id: string) => string;
 export declare const recomputeVatReturn: (id: string, options?: RequestInit) => Promise<recomputeVatReturnResponse>;
 /**
- * @summary Approve a draft VAT return (entity admin only)
+ * @summary Approve a draft VAT return (accountant only)
  */
 export type approveVatReturnResponse200 = {
     data: VatReturn;
@@ -1284,7 +1284,7 @@ export type approveVatReturnResponse = (approveVatReturnResponseSuccess | approv
 export declare const getApproveVatReturnUrl: (id: string) => string;
 export declare const approveVatReturn: (id: string, options?: RequestInit) => Promise<approveVatReturnResponse>;
 /**
- * @summary Record a VAT return as submitted to eDavki (entity admin only)
+ * @summary Record a VAT return as submitted to eDavki (accountant only)
  */
 export type submitVatReturnResponse200 = {
     data: VatReturn;
@@ -1328,7 +1328,7 @@ export type submitVatReturnResponse = (submitVatReturnResponseSuccess | submitVa
 export declare const getSubmitVatReturnUrl: (id: string) => string;
 export declare const submitVatReturn: (id: string, submitVatReturnRequest?: SubmitVatReturnRequest, options?: RequestInit) => Promise<submitVatReturnResponse>;
 /**
- * @summary Reopen an approved VAT return back to draft (entity admin only)
+ * @summary Reopen an approved VAT return back to draft (accountant only)
  */
 export type reopenVatReturnResponse200 = {
     data: VatReturn;
@@ -1590,7 +1590,7 @@ export type dismissFilingResponse = (dismissFilingResponseSuccess | dismissFilin
 export declare const getDismissFilingUrl: (id: string) => string;
 export declare const dismissFiling: (id: string, dismissFilingRequest?: DismissFilingRequest, options?: RequestInit) => Promise<dismissFilingResponse>;
 /**
- * Account-level view for accountants managing more than one entity: returns the filing obligations of the account's entities that can use the accounting module, each tagged with its entity id and name; other entities are left out. Scoped to one environment (`environment` query param, defaults to "live"), so live and sandbox entities are not mixed in one response.
+ * Account-level view for accountants managing more than one entity: returns the filing obligations of the account's entities where the caller is the company's accountant and the accounting module is available, each tagged with its entity id and name; other entities are left out. Scoped to one environment (`environment` query param, defaults to "live"), so live and sandbox entities are not mixed in one response.
  * @summary List filing-calendar obligations across the account's entities
  */
 export type listAccountFilingsCalendarResponse200 = {

package/dist/generated-zod/entity-invitations/entity-invitations.d.cts

@@ -23,6 +23,7 @@ export declare const ListEntityInvitationsResponse: zod.ZodObject<{
             viewer: "viewer";
             editor: "editor";
             staff: "staff";
+            accountant: "accountant";
         }>;
         invited_by_user_id: zod.ZodString;
         expires_at: zod.z.ZodISODateTime;
@@ -55,6 +56,7 @@ export declare const GetEntityInvitationResponse: zod.ZodObject<{
         viewer: "viewer";
         editor: "editor";
         staff: "staff";
+        accountant: "accountant";
     }>;
     invited_by_user_id: zod.ZodString;
     expires_at: zod.z.ZodISODateTime;
@@ -111,6 +113,7 @@ export declare const PreviewEntityInvitationResponse: zod.ZodObject<{
         viewer: "viewer";
         editor: "editor";
         staff: "staff";
+        accountant: "accountant";
     }>;
     status: zod.ZodEnum<{
         pending: "pending";

package/dist/generated-zod/entity-invitations/entity-invitations.d.ts

@@ -23,6 +23,7 @@ export declare const ListEntityInvitationsResponse: zod.ZodObject<{
             viewer: "viewer";
             editor: "editor";
             staff: "staff";
+            accountant: "accountant";
         }>;
         invited_by_user_id: zod.ZodString;
         expires_at: zod.z.ZodISODateTime;
@@ -55,6 +56,7 @@ export declare const GetEntityInvitationResponse: zod.ZodObject<{
         viewer: "viewer";
         editor: "editor";
         staff: "staff";
+        accountant: "accountant";
     }>;
     invited_by_user_id: zod.ZodString;
     expires_at: zod.z.ZodISODateTime;
@@ -111,6 +113,7 @@ export declare const PreviewEntityInvitationResponse: zod.ZodObject<{
         viewer: "viewer";
         editor: "editor";
         staff: "staff";
+        accountant: "accountant";
     }>;
     status: zod.ZodEnum<{
         pending: "pending";

package/dist/generated-zod/entity-users/entity-users.d.cts

@@ -25,6 +25,7 @@ export declare const GetEntityUsersResponse: zod.ZodObject<{
             viewer: "viewer";
             editor: "editor";
             staff: "staff";
+            accountant: "accountant";
         }>;
         email: zod.ZodString;
         name: zod.ZodNullable<zod.ZodString>;
@@ -34,7 +35,7 @@ export declare const GetEntityUsersResponse: zod.ZodObject<{
     }, zod.z.core.$strip>>;
 }, zod.z.core.$strip>;
 /**
- * Add an existing white-label user for this account to the entity or send an invitation. Existing account users must accept the invitation so they receive separate entity-user access. With `silent: true` no email is sent (`send_invite` is ignored): a missing white-label user is created immediately (no password, optional `metadata`) and linked to the entity, and an existing white-label user is linked. Silent provisioning requires an account API key or an account owner/admin signed in directly (an interactive session); delegated (SSO) tokens are rejected. The new user's email counts as verified when the credential is an account API key or a user token whose email is verified; otherwise the user must verify their email before sending documents by email. Silent provisioning can be followed by `POST /entities/users/{user_id}/token` with `ttl` to embed the user.
+ * Add an existing white-label user for this account to the entity or send an invitation. The `accountant` role cannot be assigned this way (422). Existing account users must accept the invitation so they receive separate entity-user access. With `silent: true` no email is sent (`send_invite` is ignored): a missing white-label user is created immediately (no password, optional `metadata`) and linked to the entity, and an existing white-label user is linked. Silent provisioning requires an account API key or an account owner/admin signed in directly (an interactive session); delegated (SSO) tokens are rejected. The new user's email counts as verified when the credential is an account API key or a user token whose email is verified; otherwise the user must verify their email before sending documents by email. Silent provisioning can be followed by `POST /entities/users/{user_id}/token` with `ttl` to embed the user.
  * @summary Add user to entity
  */
 export declare const AddEntityUserHeader: zod.ZodObject<{
@@ -66,7 +67,7 @@ export declare const GetEntityUsersAccessResponse: zod.ZodObject<{
     account_id: zod.ZodString;
     account_role: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"owner">, zod.ZodLiteral<"admin">, zod.ZodLiteral<"member">, zod.ZodLiteral<null>]>>;
     entity_id: zod.ZodString;
-    entity_role: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"viewer">, zod.ZodLiteral<"editor">, zod.ZodLiteral<"admin">, zod.ZodLiteral<"staff">, zod.ZodLiteral<null>]>>;
+    entity_role: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"viewer">, zod.ZodLiteral<"editor">, zod.ZodLiteral<"admin">, zod.ZodLiteral<"staff">, zod.ZodLiteral<"accountant">, zod.ZodLiteral<null>]>>;
     is_account_admin: zod.ZodBoolean;
     is_entity_admin: zod.ZodBoolean;
     account_admin_override: zod.ZodBoolean;
@@ -75,10 +76,11 @@ export declare const GetEntityUsersAccessResponse: zod.ZodObject<{
     can_read_entity: zod.ZodOptional<zod.ZodBoolean>;
     can_manage_entity_settings: zod.ZodOptional<zod.ZodBoolean>;
     can_use_own_documents: zod.ZodOptional<zod.ZodBoolean>;
+    can_use_accounting: zod.ZodOptional<zod.ZodBoolean>;
     enforce_entity_admin_preservation: zod.ZodBoolean;
 }, zod.z.core.$strip>;
 /**
- * Update a user's role, metadata, or both. Send at least one of `role` and `metadata`. Roles: viewer (read-only), editor (read+write), admin (full access), staff (issues invoices and sees only their own). `metadata` replaces the stored object as a whole (string key-value data, up to 50 keys; `null` clears it) and is only available for the entity account's own white-label users (400 otherwise). Omitted fields are left unchanged.
+ * Update a user's role, metadata, or both. Send at least one of `role` and `metadata`. Roles you can assign: viewer (read-only), editor (read+write), admin (full access), staff (issues invoices and sees only their own). The `accountant` role (works like editor and also uses the accounting module) cannot be assigned here: a request naming it is refused with 422, and so is changing the role of a user who already is an accountant (remove them with `DELETE /entities/users/{user_id}` instead). `metadata` replaces the stored object as a whole (string key-value data, up to 50 keys; `null` clears it) and is only available for the entity account's own white-label users (400 otherwise). Omitted fields are left unchanged.
  * @summary Update user role or metadata
  */
 export declare const updateEntityUserRolePathUserIdRegExp: RegExp;
@@ -105,6 +107,7 @@ export declare const UpdateEntityUserRoleResponse: zod.ZodObject<{
         viewer: "viewer";
         editor: "editor";
         staff: "staff";
+        accountant: "accountant";
     }>;
     email: zod.ZodString;
     name: zod.ZodNullable<zod.ZodString>;

package/dist/generated-zod/entity-users/entity-users.d.ts

@@ -25,6 +25,7 @@ export declare const GetEntityUsersResponse: zod.ZodObject<{
             viewer: "viewer";
             editor: "editor";
             staff: "staff";
+            accountant: "accountant";
         }>;
         email: zod.ZodString;
         name: zod.ZodNullable<zod.ZodString>;
@@ -34,7 +35,7 @@ export declare const GetEntityUsersResponse: zod.ZodObject<{
     }, zod.z.core.$strip>>;
 }, zod.z.core.$strip>;
 /**
- * Add an existing white-label user for this account to the entity or send an invitation. Existing account users must accept the invitation so they receive separate entity-user access. With `silent: true` no email is sent (`send_invite` is ignored): a missing white-label user is created immediately (no password, optional `metadata`) and linked to the entity, and an existing white-label user is linked. Silent provisioning requires an account API key or an account owner/admin signed in directly (an interactive session); delegated (SSO) tokens are rejected. The new user's email counts as verified when the credential is an account API key or a user token whose email is verified; otherwise the user must verify their email before sending documents by email. Silent provisioning can be followed by `POST /entities/users/{user_id}/token` with `ttl` to embed the user.
+ * Add an existing white-label user for this account to the entity or send an invitation. The `accountant` role cannot be assigned this way (422). Existing account users must accept the invitation so they receive separate entity-user access. With `silent: true` no email is sent (`send_invite` is ignored): a missing white-label user is created immediately (no password, optional `metadata`) and linked to the entity, and an existing white-label user is linked. Silent provisioning requires an account API key or an account owner/admin signed in directly (an interactive session); delegated (SSO) tokens are rejected. The new user's email counts as verified when the credential is an account API key or a user token whose email is verified; otherwise the user must verify their email before sending documents by email. Silent provisioning can be followed by `POST /entities/users/{user_id}/token` with `ttl` to embed the user.
  * @summary Add user to entity
  */
 export declare const AddEntityUserHeader: zod.ZodObject<{
@@ -66,7 +67,7 @@ export declare const GetEntityUsersAccessResponse: zod.ZodObject<{
     account_id: zod.ZodString;
     account_role: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"owner">, zod.ZodLiteral<"admin">, zod.ZodLiteral<"member">, zod.ZodLiteral<null>]>>;
     entity_id: zod.ZodString;
-    entity_role: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"viewer">, zod.ZodLiteral<"editor">, zod.ZodLiteral<"admin">, zod.ZodLiteral<"staff">, zod.ZodLiteral<null>]>>;
+    entity_role: zod.ZodNullable<zod.ZodUnion<readonly [zod.ZodLiteral<"viewer">, zod.ZodLiteral<"editor">, zod.ZodLiteral<"admin">, zod.ZodLiteral<"staff">, zod.ZodLiteral<"accountant">, zod.ZodLiteral<null>]>>;
     is_account_admin: zod.ZodBoolean;
     is_entity_admin: zod.ZodBoolean;
     account_admin_override: zod.ZodBoolean;
@@ -75,10 +76,11 @@ export declare const GetEntityUsersAccessResponse: zod.ZodObject<{
     can_read_entity: zod.ZodOptional<zod.ZodBoolean>;
     can_manage_entity_settings: zod.ZodOptional<zod.ZodBoolean>;
     can_use_own_documents: zod.ZodOptional<zod.ZodBoolean>;
+    can_use_accounting: zod.ZodOptional<zod.ZodBoolean>;
     enforce_entity_admin_preservation: zod.ZodBoolean;
 }, zod.z.core.$strip>;
 /**
- * Update a user's role, metadata, or both. Send at least one of `role` and `metadata`. Roles: viewer (read-only), editor (read+write), admin (full access), staff (issues invoices and sees only their own). `metadata` replaces the stored object as a whole (string key-value data, up to 50 keys; `null` clears it) and is only available for the entity account's own white-label users (400 otherwise). Omitted fields are left unchanged.
+ * Update a user's role, metadata, or both. Send at least one of `role` and `metadata`. Roles you can assign: viewer (read-only), editor (read+write), admin (full access), staff (issues invoices and sees only their own). The `accountant` role (works like editor and also uses the accounting module) cannot be assigned here: a request naming it is refused with 422, and so is changing the role of a user who already is an accountant (remove them with `DELETE /entities/users/{user_id}` instead). `metadata` replaces the stored object as a whole (string key-value data, up to 50 keys; `null` clears it) and is only available for the entity account's own white-label users (400 otherwise). Omitted fields are left unchanged.
  * @summary Update user role or metadata
  */
 export declare const updateEntityUserRolePathUserIdRegExp: RegExp;
@@ -105,6 +107,7 @@ export declare const UpdateEntityUserRoleResponse: zod.ZodObject<{
         viewer: "viewer";
         editor: "editor";
         staff: "staff";
+        accountant: "accountant";
     }>;
     email: zod.ZodString;
     name: zod.ZodNullable<zod.ZodString>;