Seitenhistorie
| Auszug | ||
|---|---|---|
| ||
DATEV Nuclet – prerequisites. |
Language: Deutsch · English
3 DATEV: Prerequisites
Prerequisites – part of the DATEV Nuclet documentation (export of CSV files for further processing in DATEV (accounting)).
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
On this page
|
| Hinweis | ||
|---|---|---|
| ||
This page was machine-translated from German as a first draft and is currently under review. The authoritative source remains the German original (see the language switch above). |
3.1 Integration points
To create the following attributes you need a new integration point (Configuration > Integration points) in your main Nuclet:
3.2 Customer or debtor object for customer exports
For DATEV customer exports it makes sense to have a customer or debtor object.
A date field is required to mark exported records.
Attribute | Java data type | Nuclos data type | Mandatory field? | Unique? | Description |
|---|---|---|---|---|---|
| DATEV Export Date | Date | Date | no | no | date on which the record was transferred into a DATEV export |
| DATEV Information | org.nuclet.datev.DATEVInformation | Reference field | no | no | references the integration point "DATEV Information" |
Table 3.1: Business object for customers or debtors
3.3 Invoice objects for invoice exports
For DATEV invoice exports it makes sense to have an invoice object.
A date field is required to mark exported records.
Attribute | Java data type | Nuclos data type | Mandatory field? | Unique? | Description |
|---|---|---|---|---|---|
| DATEV Export Date | Date | Date | no | no | date on which the record was transferred into a DATEV export |
| DATEV Information | org.nuclet.datev.DATEVInformation | Reference field | no | no | references the integration point "DATEV Information" |
Table 3.2: Business object for invoices
3.4 Turnover objects for turnover exports
For DATEV turnover exports it makes sense to have a turnover object (e.g. invoice, receivable, booking item or similar).
A date field is required to mark exported records.
Attribute | Java data type | Nuclos data type | Mandatory field? | Unique? | Description |
|---|---|---|---|---|---|
| DATEV Export Date | Date | Date | no | no | date on which the record was transferred into a DATEV export |
| DATEV Information | org.nuclet.datev.DATEVInformation | Reference field | no | no | references the integration point "DATEV Information" |
Table 3.3: Business object for turnover
Related pages
Überblick
Inhalte