| Table of Contents |
|---|
...
| Setting | Meaning | ||
|---|---|---|---|
| ID | The ID of the interface configuration. | ||
| Name | The name of the interface configuration. | ||
| Interface type | The interface master data import is selected here. | ||
| File type | When importing master data, CSV must usually be selected. | Interface type | The interface master data import is selected here. |
| Default interface | This setting is irrelevant for the master data import. | ||
| Skip empty rows | If this box is checked, empty lines in the template are skipped. If the box is unchecked, these are reported as errors. | ||
| Do you want to archieve units, which are not included in the import file? | If this function is activated, the existing companies are archived in the period to which the master data is transferred. | ||
| Sheet name | If several worksheets are available, the name of the worksheet to be used can be entered here. | ||
| Seperator | The separator separates individual entries in the CSV file. Usually this is a semicolon or a comma. | ||
| First data row | The first row that contains data for the import. Title rows are not data rows. |
...
| Setting | Meaning | ||
|---|---|---|---|
| ID | The ID of the interface configuration. | ||
| Name | The name of the interface configuration. | ||
| Interface type | The VAT-ID Import interface is selected here. | ||
| File type | The file type can be defined (CSV or text file) | ||
| Encoding | The coding can be configured here. If the encoding does not match, special characters such as umlauts are not imported correctly. | Interface type | The VAT-ID Import interface is selected here. |
| Separator | Here you can select a separator to separate the individual entries of the CSV file. | ||
| First Data Row | Here you configure in which line of the CSV file the data to be imported starts (header lines are not to be imported). |
...
| Setting | Meaning |
|---|---|
| ID | The ID of the interface configuration. |
| Name | The name of the interface configuration. |
| Interface type | The VAT-Import interface is selected here. |
| Encoding | The coding can be configured here. If the encoding does not match, special characters such as umlauts are not imported correctly. |
| Interface type | The VAT-Import interface is selected here. |
| Default interface | If "Yes (exclusive)" is selected here, this configuration is automatically configured for all companies. Only a single VAT-import configuration can be exclusive. A configuration of the VAT-import that is defined with "No (optional)" must be assigned to the companies in the Master Data area. |
...
This interface configuration can be used to configure the import of the declaration values for the ESL. It is possible to configure several different variants of the ESL import. These can be assigned to the companies in [Master Data → Companies]. If no configuration is available, the import file is expected to be ANSI a RFASLM text file encoded inANSI by default.
| Setting | Meaning | |||||
|---|---|---|---|---|---|---|
| ID | The ID of the interface configuration. | |||||
| Name | The name of the interface configuration. | |||||
| Interface type | The ESL Import interface is selected here. | |||||
| File type | The file type can be defined (CSV or text file) | |||||
| Seperator | This field can be filled if CSV is selected as the file type. A semicolon, a comma or a pipe can be configured as separator ( ; , | ).
| |||||
| Encoding | The coding can be configured here. If the encoding does not match, special characters such as umlauts are not imported correctly |
| . | |
| Default interface | If "Yes (exclusive)" is selected here, this configuration is automatically configured for all companies. Only a single ESL import configuration can be exclusive. A configuration of the ESL import that is defined with "No (optional)" must be assigned to the companies in the Master Data area. |
| Filename pattern | A separate file name pattern can be stored for each ZM Import configuration, which differs from the standard pattern of the network drive interface. If you create an individual file name pattern here, this file name pattern is used for this ZM import configuration instead of the file name pattern stored in the network drive import configuration. The file pattern for the network drive import of an CSV file for the ESL is usually: ZM-<VATID>-<DATE:yyyy-MM>.<EXT> |
Automatic import
If the SAP reports are to be imported automatically it must be configured in the VAT@GTC.
...
| Setting | Meaning | |||||
|---|---|---|---|---|---|---|
| ID | The ID of the interface configuration. | |||||
| Name | The name of the interface configuration. | |||||
| Interface type | The interface network drive import is selected here. | |||||
| File type | The file format of the SAP reports. These are usually text files. | Interface type | The interface network drive import is selected here. | |||
| Default interface | If the network drive is the default interface, "Yes (exclusive)" must be selected. If the web service Import is also active, it can also be configured, but as "No (optional)". In this case, the companies that import via the web service must be configured accordingly in the company master data. | |||||
| Path to netdrive | The path to the folder where the SAP reports for import are stored. | |||||
| Path to archive directory | The path of the folder in which the SAP reports are archived after the import. | |||||
| Filename pattern | The pattern of SAP report names.
|
Webservice import
| Setting | Meaning |
|---|---|
| ID | The ID of the interface configuration. |
| Name | The name of the interface configuration. |
| Interface type | The interface webservice import is selected here. |
| Default interface | If the web service is the default interface, "Yes (exclusive)" must be selected. If network drive import is also active, it can also be configured, but as "No (optional)". In this case, the companies that import via the network drive must be configured accordingly in the company master data. |
| HTTP Basic Authentication | The web service can optionally be secured with HTTP Basic authentication. This is particularly interesting if the VAT@GTC cannot only be accessed from the company network. This can prevent unauthorised persons from transmitting transaction data to the VAT@GTC. |
| User name / Password | Selected combination of user name and password for HTTP Basic Authentication. These must be sent in the header of the request with the movement data if authentication is activated. Requests without this information or with incorrect information are rejected. |