Note
New Feature (Beta) – Chart of Accounts in Xentral Status 02/2026:
The new Chart of Accounts is now available as a beta version. This allows you to centrally manage your accounting accounts in Xentral and use them consistently across the entire system.
-
Status: Beta
-
Available from: 03/2026
In the beta version you can already create, edit and manage your own accounts. In the future, the Chart of Accounts will form the basis for all areas in Xentral where accounts are used (e.g. postings and DATEV export).
Note: Since this is a beta version, functions and processes may still change. Feedback is explicitly welcome.
Overview of current revisions & new features
As part of the further development of Xentral, existing modules have been revised and new features have been added. Below you will find a compact overview of the most important changes:
-
Revision of the Chart of Accounts (Chart of Accounts): Optimization and structural adjustments to better reflect accounting requirements.
-
New Feature (Beta) – Journal in Xentral: Introduction of an accounting journal for a more transparent and traceable representation of accounting processes.
-
New Tax Setup (Tax Setup): Revised setup for simplified and structured configuration of tax settings.
-
Tax Codes (Tax Codes): New or more clearly structured management of tax codes for correct tax allocation.
-
Tax Obligations (Tax Obligations): New module name (formerly “Delivery Threshold”) with extended functionality to map tax obligations.
-
-
New Revenue Account Exception: Centralized management of all revenue account exceptions in one unified overview, including search functionality, rules that can be enabled/disabled, clear rule naming, and easy deletion.
The Chart of Accounts is the central overview of all accounts that you use in Xentral. It forms the basis for postings, evaluations and exports (e.g. DATEV).
With the new feature, the Chart of Accounts has been revised to enable more functionality in the long term and to ensure consistent account logic across the entire system.
Note
Important change: Accounts must first be created in the Chart of Accounts Effective immediately: All accounts that are to be used in Xentral must first exist in the Chart of Accounts.
This means:
-
Fields where account numbers could previously be entered freely will gradually be replaced by selection fields.
-
In these selection fields, you can then only select accounts that have already been created in the Chart of Accounts.
-
This ensures that accounts are used consistently across the system and prevents incorrect or inconsistent account numbers.
Each account in the Chart of Accounts contains the following information:
-
Account number: The account number of the account you want to use in Xentral.
-
Name: The name of the account. It is displayed together with the account number in postings and in the Journal.
-
Description: An optional description that helps you better understand the purpose of the account. This field is for internal reference only.
-
Account type: The account type determines how the account is used in Xentral. The following account types are available:
-
Revenue (Revenue): Accounts for sales and revenue, e.g. product sales or services.
-
Cost (Cost): Accounts for expenses and liabilities, e.g. rent or external services.
-
Rebate (Rebate): Accounts for recording granted discounts.
-
Tax (Tax): Tax accounts for recording tax amounts. Currently, VAT accounts (input and output tax) are primarily supported.
-
To create a new account, proceed as follows:
Steps:
-
Click “Create” in the top right corner.
-
Enter the mandatory fields: account number, account type, name.
-
Optionally, you can add a description.
-
Click on "save".
Caution
Account number and account type can no longer be changed after saving. Please carefully check this information before saving.
If you want to edit an existing account:
-
Click on the "pencil icon" on the right side of the row.
-
You can then only change the following fields: name, description.
-
Click on "save".
Account number and account type remain unchanged.
Accounts can be deleted and recreated if necessary. The following applies:
-
If an account has already been used in postings, these postings remain unchanged.
-
A deleted account should not be removed if it has already been used productively.
Caution
Accounts should generally not be deleted once they have been used in postings or exports in order to ensure consistency in accounting.
With the new Journal, you now receive a central overview of all accounting-relevant transactions processed in Xentral. As soon as a transaction becomes relevant for your accounting, accounts are automatically assigned and the posting is recorded in the Journal.
Note
Status: Beta Available from: 03/2026
The Journal helps you transparently track accounting-relevant transactions and later reconcile them, for example, with DATEV. All entries are searchable and can be viewed at any time.
Each Journal entry consists of two sections:
Document information (header section): This displays the general information about the posting, e.g.:
-
Document number (triggering document)
-
Business partner number (customer or supplier; also used as the offsetting account)
-
Transaction type
-
Posting text
-
Posting date
-
Posted by (e.g. user or automated system user)
-
Amount (gross)
-
Debit/credit indicator
Line item information (detail section): Here you can see the individual posting lines, e.g.:
-
Account number
-
Account name
-
Posting text (e.g. item name for invoices/credit notes)
-
Amount
The following transaction types are collected in the Journal:
-
Debtor invoice
-
Debtor credit note
-
Creditor invoice
-
Creditor credit note
-
Incoming payment
-
Outgoing payment
Note
Initially, debtor invoices and debtor credit notes are supported. The other transaction types will be added step by step.
Caution
Important notes on how it works:
Once a transaction has been recorded in the Journal, the following applies:
-
Journal postings are immutable.
-
The associated document (e.g. invoice) is automatically set to read-only.
-
This ensures that postings cannot be changed retrospectively. This immutability is an important building block for GoBD compliance in Xentral.
The DATEV export will be based on the Journal in the future. This means:
-
Your DATEV postings can be directly reconciled with the Journal entries.
-
Accounts can no longer be changed manually in the DATEV export.
Caution
Therefore, make sure that your accounts and account settings are correctly maintained before a posting is created in the Journal.
The Journal forms the basis for further features, e.g. new evaluations or overviews for reconciliation and accounting control.
With the new version, the tax setup in Xentral has been expanded to map tax postings more precisely and consistently across the system. Instead of only using tax rate and tax type, the model is now based on tax codes (Tax Codes), which clearly define the specific tax case.
This allows Xentral to clearly distinguish between different tax cases – especially when the same tax rate such as 0 % can have different meanings depending on the context (e.g. export, reverse charge or tax-free). These cases must be reported separately and require different accounting treatment.
-
Tax Rate (Tax Rate) The tax rate describes the percentage of tax, e.g. 19 % for the German standard VAT.
-
Tax Type (Tax Type) The tax type categorizes the type of VAT. There are a total of 7 categories:
-
Standard rate (Standard)
-
Reduced rate (Reduced)
-
Tax-free (Free)
-
Reverse charge (Reverse Charge)
-
Export (Export)
-
Special case (Special)
-
Super-reduced rate (Super-Reduced)
-
Each European VAT is assigned to one of these categories.
-
Tax Code (Tax Code) A tax code is defined by the combination of tax type (Tax Type) and country (Country) and therefore describes the specific tax case. Each tax code has a fixed tax rate.
Tax rates can no longer be selected independently, but only as part of a tax code. For example, export, reverse charge and tax-free transactions all have a tax rate of 0 %, but they are considered different tax cases and must be reported separately to the authorities. Therefore, they are managed as different tax codes.
Each tax code contains four assigned accounts:
-
Revenue account (Revenue Account): Collects the net revenue.
-
Output VAT account (Debit Tax Account / Output VAT Account): Collects the outbound VAT amounts.
-
Cost account (Cost Account): Is assigned as the default cost type when receiving an invoice.
-
Input VAT account (Credit Tax Account / Input VAT Account): Collects the inbound VAT amounts.
If the tax rate is 0 %, output VAT and input VAT accounts are usually not required, as net and gross amounts are identical. In this case, postings are made only via the revenue or cost account.
In the “Tax Codes” overview, you can see all created tax codes per country. When you click on a row, the detail view of the respective tax code opens. There you can view and edit the tax parameters as well as the associated accounts.
A tax code represents a specific tax treatment (e.g. standard, export or reverse charge).
Each tax code contains the following information:
-
Country: Specifies for which country the tax code applies.
-
Name: Name of the tax code. This is initially prefilled but can be adjusted to your requirements.
-
Tax type (Tax Type): Categorization of the tax code. The following options are currently available:
-
Free (Free)
-
Reverse Charge / Transfer of tax liability (Reverse Charge)
-
Export (Export)
-
Reduced rate (Reduced)
-
Standard rate (Standard)
-
Special case / special rate (Special)
-
Super reduced rate (Super Reduced)
-
-
Tax rate (Tax Rate): Percentage tax rate, e.g. 19 %.
In addition, the associated accounts are defined:
-
Revenue account (Revenue Account): Account used to record net revenue.
-
Output VAT account (Revenue Tax Account / Output VAT Account): Account used to record output VAT.
-
Cost account (Cost Account): Standard account for incoming invoices.
-
Input VAT account (Cost Tax Account / Input VAT Account): Account used to record input VAT.
The tax setup can also be configured even if tax obligation is not yet active in Xentral, e.g. if it is foreseeable that delivery thresholds will be exceeded.
Note
By default, all common European VAT types are already available as presets. For Germany, standard accounts based on DATEV SKR03 are also stored.
-
For other countries, no accounts are prefilled, as these are not included in SKR03. These accounts must be created individually in coordination with your tax advisor.
-
If you do not want to use separate accounts per country, you can also use the German standard accounts. The DATEV export includes country and tax rate so that your tax advisor can differentiate the postings accordingly. Please clarify the desired approach with your tax advisor in advance.
-
It is important that you use consistent accounts for the same tax types (e.g. 8400 for standard revenue across multiple countries), provided this is aligned with your tax setup.
-
Please also note: Some countries have more tax types than Germany. In these cases, no direct German account equivalents can be used. Coordination with your tax advisor is recommended.
-
Note: With the planned OSS regulations from 2028, your tax advisor will likely require separate accounts for European tax filings. It may therefore make sense to create country-specific accounts already now in order to be prepared in the long term.
It is not uncommon for tax rates to change. Since tax rates in Xentral are always linked to a tax code, you need to create a new tax code when a rate changes.
To do so, click on “Create Tax Account” and proceed as follows:
-
Name: Choose a clear identifier for the new tax code.
-
Country: Select the country in which the tax rate is changing.
-
Tax type: Choose the affected type (e.g. standard rate).
-
Tax rate: Enter the new percentage rate.
-
Valid From: Select the date from which the new rate should apply.
-
Valid Until: Leave this field empty for the new tax code.
-
Select new accounts: Since new tax codes must be reported separately from old ones, you need to assign new tax, revenue and tax accounts.
Achtung
No two tax codes with the same country and tax type can be valid at the same time. Make sure to set the “Valid Until” date of the old tax code to one day before the new tax code becomes valid.
The function Tax Obligations (Tax Obligations) replaces the previous Delivery Threshold and extends the concept beyond Europe. This allows you to define in Xentral in which countries you are tax registered and must calculate local VAT.
A tax obligation may arise, for example, in the following cases:
-
Exceeding the EU delivery threshold: Once you deliver more than €10,000 worth of goods or services to other EU countries, you must charge local VAT there.
-
Permanent establishment abroad: If you operate, for example, an office or warehouse in a country, local tax registration may be required – even without exceeding the delivery threshold.
-
Deliveries outside Europe: Deliveries to non-EU countries are generally considered exports unless you are locally tax registered there (e.g. due to a permanent establishment).
As soon as you become tax obligated in a country, you should activate the tax obligation in Xentral:
-
Select the country (from the available country list)
-
Open the edit view via the pencil icon
-
Enter the VAT ID
-
Define the start date
-
Enable the active status
In the background, Xentral automatically creates a new time period. From this point on, tax calculation for transactions is carried out according to the local rules of the respective country.
Caution
If the active status is not enabled, a new time period will be created, but no tax obligation will be activated.
Tip
To ensure correct postings after activating a tax obligation, you must also store the appropriate accounts in the respective tax codes. Only if the tax codes are correctly configured can Xentral post revenues and tax amounts to the correct revenue, cost and tax accounts.
Once a tax obligation is active, local tax rates are automatically applied to new postings. The resulting postings can then be reviewed in the Journal.
If you are no longer tax obligated in a country, you can deactivate the tax obligation at any time:
-
Open the respective tax obligation
-
Define a start date from which you are no longer tax obligated
-
Leave the active status disabled
From this defined date onward, no local tax will be calculated.
Status: 03/2026: Activation via the delivery threshold (planned): A mass function is planned that will allow tax obligations for all European countries to be activated simultaneously once the delivery threshold has been exceeded. Further information will follow.
With the function “New Revenue Account Exception” you can specifically define when a different revenue account should be used instead of the account stored by default in the tax rate.
This allows you to define a different revenue account depending, for example, on:
-
Project
-
Product category
-
Product
-
Delivery country
-
Central overview: All exceptions are now managed in one place. You can no longer find them in the individual settings of projects, product categories or products.
-
Improved search function: You can search your rules specifically by: Account, Project, Product, Product category. This gives you a quick overview of existing exceptions.
-
Activate or deactivate rules: You can control each rule via its status. This allows you to deactivate rules without deleting them directly.
-
Name rules: Each rule can have its own name. This helps you immediately understand the purpose of the exception.
-
Delete rules: You can delete rules that are no longer needed at any time.
How to create a new exception:
-
Assign a name: Assign a clear and unique name that describes the purpose of the rule, e.g. “Amazon FBA Exception Germany”.
-
Define the delivery country: Select the Delivery Country Code. This determines for which country the exception should apply.
-
Define triggers: Define when the rule should apply. You can select one or more of the following criteria as triggers: Project, Product category, Product.
-
Select the booking account: Choose the revenue account that should be used instead of the standard account from the tax settings.
Example:
Name: “Amazon FBA Exception”
Delivery Country Code: “DE”
Project: “Amazon FBA”
Booking account: “8401”
Result: All revenues generated in the “Amazon FBA” project and delivered to Germany are automatically posted to revenue account 8401 instead of the standard account from the tax settings.
Practical tips:
-
Use clear and descriptive rule names.
-
Regularly review your active rules.
-
Deactivate rules first before permanently deleting them.
-
Internally document complex account logics, especially when working with multiple country-specific exceptions.