> 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/work/quickstart.md).

# Your first purchase and sale, with screenshots

**Goal:** Find the fields for one complete item, then verify its purchase basis and internal margin VAT.

**Before you start:** [Check setup](/differenzbesteuerung/differenzbesteuerung_en_us/configure/setup.md) and prepare an eligible item, test vendor and test customer. Use synthetic data in a sandbox for this first walkthrough. Keep the item's regular VAT product posting group for ordinary transactions.

**Example:** One complete item, quantity 1, purchase EUR 10,000.00, sale EUR 15,000.00, VAT rate 19%. Input screenshots show unposted Dev documents. Result screenshots come from an already posted reference case with these amounts; document and item numbers differ. Screenshots show the German interface.

## 1. Enter the purchase invoice

1. Use **Alt+Q** to open **Purchase Invoices** (**Einkaufsrechnungen**) and choose **New**.
2. Select the vendor and check document date, posting date and vendor invoice number (**Kred.-Rechnungsnr.**).
3. Enter one item line per complete item. Use quantity **1** and direct unit cost **EUR 10,000.00** in the example.

![Purchase invoice in line focus mode: 1 item number, 2 quantity 1, 3 direct unit cost EUR 10,000.00](https://3330400322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FshvCzvgNovEOqwvYy9EU%2Fuploads%2FKgtOowr1jb3bbGxaxDWv%2F02-purchase-quantity.png?alt=media)

*Figure 1 · 1: item. 2: quantity (Menge). 3: direct unit cost (EK-Preis). This is an unposted sample document.*

**Cannot see the fields?** Enlarge **Lines** with the focus-mode icon at the right of the line heading. Use the bottom horizontal scrollbar to move right. Depending on your profile, additional fields may need to be shown through personalization.

## 2. Review the acquisition's tax details

![Purchase line scrolled right: 1 Margin Tax, 2 method, 3 acquisition origin, 4 classification, 5 goods assessment evidence, 6 reviewed checkbox](https://3330400322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FshvCzvgNovEOqwvYy9EU%2Fuploads%2FVQPreyyNxuUNv4oKnc1S%2F03-purchase-review.png?alt=media)

*Figure 2 · This capture is before completion of the review: “Prüfung erforderlich” (review required), no evidence reference and no review confirmation. Full field names follow below.*

1. **Margin Tax (Differenzbesteuerung):** Check that this flag is appropriate for this specific acquisition.
2. **Margin method (Besteuerungsverfahren):** Check the method; this example uses the individual margin method.
3. **Acquisition origin (Erwerbsart):** Select the origin supported by actual evidence. “Prüfung erforderlich” does not mean that review is complete.
4. **Tax classification (Steuerliche Klassifikation):** Review the actual type of goods, **Warenbeurteilung** and, where required, **Beurteilte Zolltarifnummer**.
5. **Goods assessment evidence (Nachweis Warenbeurteilung):** Enter a traceable reference to the reviewed evidence.
6. **Tax applicability reviewed (Steuerliche Anwendbarkeit geprüft):** Confirm only after the review is complete. Review again if the goods details change afterwards.

**Before posting:** Vendor, item, origin and evidence agree. An item flag or industry template alone is insufficient.

## 3. Post the purchase and check the acquisition

1. Choose **Post** (**Buchen**) on the purchase invoice. This simple workflow posts receipt and invoice together.
2. Open **Margin Tax Setup → Actions → Acquisitions**; German: **SOU Differenzbesteuerung Einrichtung → Aktionen → Warenzugänge**.
3. Find your item or purchase document. Check references, base quantity and tax purchase price.

![Posted acquisitions: 1 item number, 2 base quantity, 3 tax purchase price EUR 10,000.00](https://3330400322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FshvCzvgNovEOqwvYy9EU%2Fuploads%2FJLwUCXARjNfvZAlkaJrc%2F07-acquisitions.png?alt=media)

*Figure 3 · 1: identify the item. 2: complete base quantity 1. 3: purchase basis EUR 10,000.00. The list contains several synthetic reference cases.*

**Result:** The posted purchase has an acquisition record with its purchase basis and linked item ledger entry.

## 4. Sell that particular item

1. Use **Alt+Q** to open **Sales Invoices** (**Verkaufsrechnungen**) and choose **New**.
2. Select the customer and enter the same item, quantity **1**. The example sales price is **EUR 15,000.00**.
3. Assign the specific receipt through **Appl.-to Item Entry** (**Ausgleich mit Artikelposten**). For serial/lot tracking, also check standard **Item Tracking Lines**. Show the application field through line personalization if needed.
4. Review the sales line's tax details and confirm **Steuerliche Anwendbarkeit geprüft** only after review.

![Sales invoice in line focus mode: 1 same item, 2 quantity 1, 3 unit price EUR 15,000.00](https://3330400322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FshvCzvgNovEOqwvYy9EU%2Fuploads%2F3sUhmtIv36xOAYw43qnT%2F04-sales-quantity.png?alt=media)

*Figure 4 · Item (1), quantity (2) and sales price (3). Review the acquisition assignment separately; it is not shown in this crop.*

5. Post shipment and invoice together. If posting is blocked, read the message and correct the reported prerequisite.

## 5. Verify the margin and VAT

Open **Margin Tax Setup → Actions → Fiscal Entries**; German: **SOU Differenzbesteuerung Einrichtung → Aktionen → Steuerposten**. Find the sale and check the acquisition reference and linked standard ledger entries.

![Posted fiscal entries: 1 acquisition reference, 2 gross margin EUR 5,000.00, 3 taxable base EUR 4,201.68, 4 included VAT EUR 798.32](https://3330400322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FshvCzvgNovEOqwvYy9EU%2Fuploads%2Fu5lCGbPGnuRmabflyZMk%2F08-fiscal-entries.png?alt=media)

*Figure 5 · These four columns link the sale to the purchase and show the calculated amounts.*

| Marker | Check in this example                                  |
| ------ | ------------------------------------------------------ |
| 1      | The acquisition entry belongs to the actual item sold. |
| 2      | 15,000.00 − 10,000.00 = **EUR 5,000.00 gross margin**. |
| 3      | 5,000.00 ÷ 1.19 = **EUR 4,201.68 taxable base**.       |
| 4      | 5,000.00 − 4,201.68 = **EUR 798.32 internal VAT**.     |

For an ordinary zero or negative margin, its VAT remains zero.

## 6. Preview the customer document

Preview the approved invoice layout. Check mandatory information and the applicable margin notice. Internal purchase price, margin and margin VAT must not appear on the customer document. Compare with the internal transaction evidence if needed.

**Done:** Purchase and sale are linked; purchase basis, margin and internal VAT are traceable.

**Next:** [Returns and further workflows](/differenzbesteuerung/differenzbesteuerung_en_us/work/daily-work.md). For discrepancies, use [Troubleshooting](/differenzbesteuerung/differenzbesteuerung_en_us/help/troubleshooting.md) or the [support form](/differenzbesteuerung/differenzbesteuerung_en_us/help/support.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/work/quickstart.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.