Field support per integration
DATEV Unternehmen Online
DATEV Unternehmen Online
If you’re not using the Interactive Authentication Flow, make sure the query parameter
companyId
is accurately populated with the appropriate company ID. You can obtain this value by using the GET Companies
endpoint available under the Authentication section.The name of the uploaded file must include the file extension, for example
invoice.pdf
.The
documentId
field can be used to uniquely identify a document. If provided, it must be a valid GUID.The
documentType
field must match one of the document types returned by the GET Document Types
endpoint.DATEV Rechnungswesen
DATEV Rechnungswesen
If you’re not using the Interactive Authentication Flow, make sure the query parameter
companyId
is accurately populated with the appropriate company ID. You can obtain this value by using the GET Companies
endpoint available under the Authentication section.The name of the uploaded file must include the file extension, for example
invoice.pdf
.The
documentId
field can be used to uniquely identify a document. If provided, it must be a valid GUID.The
documentType
field must match one of the document types returned by the GET Document Types
endpoint.The
integrationSource
field should be set to the name of your application integrating with DATEV.Exact
Exact
If you’re not using the Interactive Authentication Flow, make sure the query parameter
companyId
is correctly populated.
You can obtain this value by using the GET Companies
endpoint available under the Authentication section.The
contactId
field is required for the INVOICE
document type.Available options:
BILL
, INVOICE
Query Parameters
Body
multipart/form-data
Example:
"Ausgangsrechnung"
Example:
"287a382-s35e624e5-fb9e-483"
Example:
"2021-01-01T00:00:00Z"
Example:
"b5e624e5-fb9e-4836-a443-87a3820f5b48"
Example:
"Third party app"
Example:
"Invoice 02-03-2023"