--- title: "Accounting settings" description: "A walkthrough of the general accounting settings in Sapera: posting, settlement, year-end closing, department management and external accounting integrations." url: https://support.sapera.io/en/articles/419-accounting-settings collection: "Accounting" updated: 2026-06-11 language: en alternates: [da] --- # Accounting settings A walkthrough of the general accounting settings in Sapera: posting, settlement, year-end closing, department management and external accounting integrations. ## Accounting – general settings This page describes the general accounting settings that sit directly at the "Accounting" level — that is, settings that apply broadly to posting, settlement, year-end closing, department management and external accounting integrations. Under "Accounting" there are also three underlying areas with their own settings and their own help articles: **MobilePay**, **Interest calculation** and **Bank import**. They are described here: [MobilePay](https://support.sapera.io/en/articles/179-mobilepay.md), [Interest calculation](https://support.sapera.io/en/articles/177-interest-calculation-renteberegning.md) and [Bank import](https://support.sapera.io/en/articles/420-bank-import.md). ### How to find the settings Open the hamburger menu in the top left corner of Sapera and select **Financial**. Then go to **Setup** → **Settings** → **Accounting**. If you cannot see the menu item, you probably lack permissions — contact support. ### Override per department Most settings on this page can be overridden per department (organizational unit, OU), so a specific department can have a different value than the general default. The exception is the three integration settings (e-conomic, Inventio.IT Business Central and Microsoft Cloud Business Central) — they always apply globally, can only be changed by an administrator, and cannot be overridden per department. ## Posting and drafts ### Automatically print draft report Determines whether the draft's report is automatically printed when a posting draft is posted. **Yes:** The report is printed automatically after posting. **No (default):** Nothing is printed automatically. ### Allow define appendix number Determines which appendix number is used when invoices and purchase invoices are posted. **Yes:** The invoice's own identifier/appendix number is used as the appendix number when posting. **No (default):** The system's number series assigns the appendix number. ### Skip copying of organizational unit on row creation in stock drafts Determines whether the department (OU) is copied from the previous row when a new row is created in a draft. **Yes:** The department is not copied to new rows. **No (default):** The department is copied from the previous row. ## Department (organizational unit) and year-end closing ### Filter financial accounts data by current OU by default Determines whether account and posting lists are by default pre-filtered to the department (organizational unit) the user is currently working in. **Yes:** The lists by default show only the current department's data (can be changed manually). **No (default):** The lists are not pre-filtered by department. The filter can always be adjusted directly in the individual list — see [How to search in lists](https://support.sapera.io/en/articles/545-sadan-soger-du-i-lister.md). ### Choose OU on end of year booking Determines whether year-end closing runs per department, so the department can be chosen at the year-end closing posting. **Yes:** Year-end closing runs in per-department mode. **No (default):** Year-end closing runs combined. ## Settlement ### Settle automatically (open post) when booked Determines whether entries are automatically settled as open post per actor when they are posted. **Yes:** Entries are settled automatically when posted. **No (default):** Settlement is done manually. ### Should settle by OU Determines whether settlement is done per department (OU) instead of combined across departments. **Yes:** Settlement is done per department. **No (default):** Settlement is done combined across departments. ### Supported settlement modes Determines which settlement modes are available in the settlement dialog. The setting is a multi-choice, so you can enable one or both modes. **Options:** Open post, Full, or both. **Default:** Both modes are enabled. ### Open Post settlement mode Determines how the automatic open post settlement is grouped. **One-to-one (default):** Settlement is done 1-to-1 between entries. **Aggregated:** Entries are settled together (aggregated). ## External accounting integrations The three integration settings below can only be changed by an administrator and cannot be overridden per department. In addition to enabling the setting, the integration itself must also be activated on the individual accounting record before export works. ### Is Economic Integration Supported Enables integration with e-conomic so that entries can be exported there. ### Is Inventio.IT A/S Business Central ERP Integration Supported Enables integration with Inventio.IT's Business Central solution so that entries can be exported there. ### Is Microsoft Cloud Business Central Integration Supported Enables integration with Microsoft Cloud Business Central so that entries can be exported there. * * * **Want to know more?** Read more in these related articles: [ Finance setup The finance setup determines which financial accounts and posting drafts Sapera uses when the system automatically generates entries for sales, purchases, cash register closing, stock adjustment and year-end closing. Here you configure default accounts, drafts and integration settings per organizational unit. ](https://support.sapera.io/en/articles/68.md)[ Accounting/Integration Under Accounting/Integration you create and name the company's accounting records and link them to organizational units. Here you also enable integration with external accounting systems such as e-conomic, Inventio.IT A/S Business Central and Microsoft Cloud Business Central, and configure the necessary connection settings per accounting record. ](https://support.sapera.io/en/articles/111.md)