The Accounting/Integration screen is the central place where you create and manage the accounts (called account names) used in Sapera. An account typically represents one CVR number and is linked to one or more organizational units via the financial setup. Many companies — especially chains with multiple stores — have one account per store or CVR number, so that finances and reporting are kept separate.
In addition to the naming itself, the screen is the access path for enabling and configuring integration with external accounting systems. The three available integrations are e-conomic, Inventio.IT A/S Business Central ERP and Microsoft Cloud Business Central. Which integrations are shown at all depends on what is enabled at the tenant level under Settings — integrations that are not enabled for your tenant are not shown. The Winkas integration is configured per organizational unit under Financial setup and is not described here.
Access to the screen requires the permission Access to accounting account names. If you cannot see the menu item, you most likely do not have the required permission. Contact your system administrator or support.
Go to Financial, select Setup in the left-hand menu and click Accounting/Integration. You now see the list of account names created in Sapera.
The list shows all created accounts with Display name and System name. You can double-click a row, or select the row and click the edit icon, to open the edit view.
The Show org. unit screen button opens the organizational unit linked to the selected account via the financial setup. From here you can maintain master data for the account's organizational unit.
The Export SAF-T and Import SAF-T buttons are only shown if SAF-T is enabled for the tenant and an existing account is selected. They are used to export and import SAF-T accounting data in the standard format, respectively.
Click the + button in the top right to create a new account. An edit view opens with the following fields:
System name is a unique name without spaces or special characters that is used internally in the system, for example "butik1". The system name cannot be changed after the account has been created.
Display name is the name shown to users, for example "Butik 1 ApS".
Save with the Apply button.
The Integration settings section under E-conomic is only shown if the tenant is configured to support e-conomic integration. Enable the integration for the specific account by ticking Is E-conomic integration supported — the fields below are then shown.
E-conomic token is the agreement access token (Agreement Grant Token) that identifies and authorizes the connection to your e-conomic account. The field is read-only; click the Set button next to the field to open a dialog and enter or update the token. The token is obtained from e-conomic under Settings, Access, API access. The token is required for the integration to be able to retrieve metadata and send data to e-conomic.
Transfer actor controls whether customers and vendors are transferred automatically to e-conomic when they are created in Sapera. When this is enabled, additional settings for customers and vendors are shown.
Under Create customer settings you specify default values for new customers transferred to e-conomic: Customer group determines which e-conomic customer group is linked; VAT zone specifies the default VAT zone; Payment terms specifies the default payment term.
Under Create vendor settings you specify the corresponding default values for vendors: Vendor group, VAT zone and Payment terms.
Transfer org. unit as departments controls whether Sapera's organizational units are transferred to e-conomic as departments. If this is enabled, a note is shown that e-conomic departments must be enabled and that the department names in e-conomic must match the display names in Sapera.
Journal to entry journal is a mapping grid where, for each posting journal (draft) in Sapera, you specify the corresponding entry journal number in e-conomic. Sapera uses this number when it sends entries from that journal to e-conomic. Click an empty cell in the Entry journal column to select an e-conomic journal number from the list.
Validate button (green) runs a connection validation against e-conomic and shows the result, including any configuration errors.
The Inventio.IT A/S Business Central ERP integration settings section is only shown if the tenant is configured for Inventio.IT integration. Enable the integration for the account by ticking Is Inventio.IT A/S Business Central ERP integration supported — the fields below are then shown.
SMART Alias is the alias identifier that the Inventio.IT SMART API uses to identify the specific Business Central environment. The field is required.
Voucher number prefix (optional) is an optional text prefix that is placed in front of voucher numbers when entries are sent to Business Central. Use this if Business Central requires a specific format for voucher numbers.
SMART API methods is a grid showing the API methods Sapera calls against the Inventio.IT SMART API. For each method (e.g. General Journal (POST) and General Journal Batch Name (GET)) you can specify a Reference name, which identifies the specific method, and a Token, which is used to authenticate the call.
Journal to Inventio.It journal is a mapping grid where, for each posting journal in Sapera, you specify the corresponding journal in Business Central. The Inventio.It Journal column is selected from the list of available journals retrieved from Business Central.
Org. unit to dimension setup is a mapping grid where, for each organizational unit, you can specify a Dimension code in Business Central. This is used when entries are to result in a dimension value corresponding to the sending organizational unit.
Validate button runs a connection validation against Inventio.IT and shows the result.
The Microsoft Cloud Business Central integration settings section is only shown if the tenant is configured for BC Microsoft Cloud integration. Enable the integration for the account by ticking Is Business Central Microsoft Cloud integration supported — the fields below are then shown.
Tenant ID is the Microsoft Entra tenant ID for the Azure environment that hosts your Business Central installation. The field is required and must have the format of a GUID.
Company ID is the unique ID for the specific company in Business Central that data is to be sent to. The field is required and must have the format of a GUID.
Voucher number prefix (optional) is an optional text prefix that is placed in front of voucher numbers when transferring to Business Central.
Journal to BC Microsoft Cloud journal is a mapping grid that works the same way as for Inventio.IT: for each posting journal in Sapera you specify the corresponding BC Microsoft Cloud Journal in Business Central.
Transfer organizational units as dimension values controls whether Sapera's organizational units are transferred to Business Central as dimension values. If this is enabled, additional setup fields are shown:
Dimension code for organizational units is the dimension code in Business Central under which the organizational units' values are to be recorded. Click the button next to the field to open a selection dialog.
Under Org. unit to dimension setup (which is shown when dimension transfer is enabled) you can, for each organizational unit, specify the exact dimension value to be used in Business Central.
Validate button runs a connection validation against Business Central and shows any configuration errors.
Click Apply to save all changes to the open account. Click Cancel or Close to exit without saving.
If you have any questions, you are welcome to contact support.
Want to know more?
You can adjust how this area works under the settings:
Accounting settings
Walkthrough of the general accounting settings in Sapera: posting, settlement, year-end close, department management and external accounting integrations.
