> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/differenzbesteuerung/differenzbesteuerung_en_us/configure/setup.md).

# Set up margin tax

**Goal:** Configure the accounts, VAT groups and document layouts needed to process eligible purchases and sales.

**You need:** the installed app, setup permissions and accounts/VAT groups approved by your finance team. [Installation and permissions](/differenzbesteuerung/differenzbesteuerung_en_us/start/installation.md).

The screenshots show the German interface. The German control labels below let you match each numbered marker.

## 1. Open setup

1. Open Business Central search with **Alt+Q**.
2. Search for **Margin Tax Setup**; in the German interface, **SOU Differenzbesteuerung Einrichtung**.
3. Choose the pencil icon to edit. The following steps use the setup card directly.

## 2. Set the method, VAT groups and accounts

![Setup: 1 default method, 2 separate VAT groups, 3 reclassification and revenue accounts](https://3330400322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FshvCzvgNovEOqwvYy9EU%2Fuploads%2Fw0BCwtsXt1K6f2gpu2WO%2F05-setup-groups.png?alt=media)

*Figure 1 · Authentic Dev setup crop. The test codes are not account recommendations.*

1. **Default method (Standardverfahren):** Select the method approved for your business. The quickstart uses the individual margin method.
2. **VAT groups:** Set the domestic VAT business posting group, the margin VAT product posting group with the approved standard rate, and a separate technical zero-percent document group.
3. **Accounts:** Set the gross revenue reclassification account (**Umbuchungskonto Bruttoerlös**), taxable margin revenue account (**Erlöskonto steuerpflichtige Differenz**) and source code from your approved chart of accounts.

Check EUR, cent rounding and VAT rounding in standard setup. Do not use payment-discount VAT adjustment or unrealized VAT methods for the affected groups.

## 3. Prepare the country, number series and output

![Setup: 1 country and rate, 2 Invoice Output Reviewed, 3 item charge for purchase price corrections](https://3330400322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FshvCzvgNovEOqwvYy9EU%2Fuploads%2F73gim2QS8trAwPpLXUZz%2F06-setup-output.png?alt=media)

*Figure 2 · The item-charge field is still blank in this capture. Configure it before using vendor price credits.*

1. **Country and rate:** Check the domestic country code **DE** and the approved VAT rate. Set number series for settlements and stock operations.
2. **Invoice Output Reviewed (Rechnungsausgabe geprüft):** Leave this unconfirmed until you have tested the actual layouts in step 4.
3. **Purchase price correction item charge:** Set the standard item charge if you intend to use financial vendor price credits.

Open **Actions → Dated VAT Configuration** (**Aktionen → Datierte Steuerkonfiguration**). Enter and confirm the effective start, rate, posting groups and source evidence. Used intervals cannot be changed. For already posted legacy stock, use **Check Legacy Base Configuration** first.

## 4. Test customer layouts

1. Assign **Margin Sales Invoice SOU** and **Margin Sales Credit SOU** in standard report selection. Alternatively, your partner can integrate the extended dataset columns into your approved layout.
2. Preview a sample invoice and credit memo.
3. Check mandatory information and the applicable margin notice. Internal purchase prices, margins and margin VAT must not appear.
4. Only then confirm **Invoice Output Reviewed** in setup.

The app does not change report selection automatically. Use report names: object numbers differ between development and Marketplace profiles. Electronic output routes need their own checks; see [FAQ](/differenzbesteuerung/differenzbesteuerung_en_us/help/faq.md).

## 5. Check and enable the setup

![Setup actions: 1 Actions, 2 Check Configuration, 3 Acquisitions, 4 Fiscal Entries](https://3330400322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FshvCzvgNovEOqwvYy9EU%2Fuploads%2FWAEf2gkTc96aSmA3Ex02%2F01-actions.png?alt=media)

*Figure 3 · These four controls are used for the setup check and later posting checks.*

1. Open **Actions** (**Aktionen**, marker 1).
2. Choose **Check Configuration** (**Einrichtung prüfen**, marker 2).
3. Resolve each reported prerequisite and run the check again.
4. Enable the app only after a successful check and approval by the responsible finance team.

**Result:** Configuration has been checked. **Acquisitions** (**Warenzugänge**, 3) and **Fiscal Entries** (**Steuerposten**, 4) let you review subsequent postings.

**If this fails:** [Resolve setup errors](/differenzbesteuerung/differenzbesteuerung_en_us/help/troubleshooting.md) or [request support](/differenzbesteuerung/differenzbesteuerung_en_us/help/support.md).

**Optional:** Under **Actions → Industry Templates** (**Branchenvorlagen**), review a template and apply it to new items. Templates cover vehicles, spare parts, electronics, bicycles/e-bikes, machinery and antiques/collectibles. A template does not replace acquisition review.

Next: [Follow your first purchase and sale](/differenzbesteuerung/differenzbesteuerung_en_us/work/quickstart.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.solutioo.de/differenzbesteuerung/differenzbesteuerung_en_us/configure/setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.