> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor/ln/example-export-ln/configuring-the-default-tax-country-for-export-ln.md).

# Configuring the Default Tax Country for Export LN

### Overview

The default Tax Country for export is set to **DE (Germany)** to prevent export errors. This can be changed in the mapping file by either:

* Defining a different static value.
* Mapping it dynamically to a field in DocBits.

<mark style="color:red;">**Note:**</mark> If the specified field does not exist or is empty, the export will default back to **DE**.

### Steps to Modify the Tax Country

#### 1. Obtain the Mapping File

* Navigate to **DocBits → Settings → Document Processing → Export**.
* Open the export configuration you want to modify.
* Click on **Download** to obtain the mapping file.\\

  <figure><img src="/files/dAunj1nitKyU4bSFWKSI" alt=""><figcaption></figcaption></figure>
* Open the file in a text editor.

#### 2. Modify the Mapping File

Choose one of the two options below and apply the necessary changes.

**Option 1: Static Value**

To set a static Tax Country value, follow these steps:

1. Define a new static field by adding `,TaxCountry` to the `StaticFields` line.

   ```properties
   StaticFields=FinancialCompany...,TaxCountry
   ```
2. Set the country code by adding the following line:

   ```properties
   SF_TaxCountry=CountryCode
   ```

   Replace `CountryCode` with the actual country code, e.g., `ES` for Spain or `DE` for Germany:

   ```properties
   SF_TaxCountry=ES
   ```

**Example:**

```properties
StaticFields=FinancialCompany,TaxCountry
SF_TaxCountry=FR
```

<figure><img src="/files/ozVnJLJGtO5UHT9pHfrT" alt=""><figcaption></figcaption></figure>

**Option 2: Dynamic Mapping from DocBits Field**

To dynamically map the Tax Country from a field in DocBits:

1. Add `,TaxCountry` to the `HeaderFields` line:

   ```properties
   HeaderFields=SupplierCode,...,TaxCountry
   ```
2. Define the corresponding field mapping:

   ```properties
   HF_TaxCountry=DocBits_Field_name
   ```

   Replace `DocBits_Field_Name` with the actual field name in DocBits:

   ```properties
   HF_TaxCountry=tax_country_1
   ```

**Example:**

```properties
HeaderFields=SupplierCode,TaxCountry
HF_TaxCountry=tax_country_1
```

<figure><img src="/files/oeIBKycpvJt38clBVTMu" alt=""><figcaption></figcaption></figure>

### Summary

* If the Tax Country is **not defined or the field is empty**, it defaults to **DE**.
* **Use a static value** if the Tax Country remains constant for all exports.
* **Use a dynamic field mapping** if the Tax Country varies per document.

By following these steps, you can successfully modify the Tax Country mapping to fit your needs.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor/ln/example-export-ln/configuring-the-default-tax-country-for-export-ln.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
