Interface IPostingProposalsApi
Represents a collection of functions to interact with the API endpoints
Inherited Members
Namespace: Simplic.Datev.Swagger.Api
Assembly: Simplic.Datev.IO.Swagger.dll
Syntax
public interface IPostingProposalsApi : IApiAccessorMethods
| Improve this Doc View SourceClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesCashRegisterGet(String, String, String)
Retrieve a list of posting proposal rules for cash register
Declaration
List<PostingProposalRuleCashRegister> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesCashRegisterGet(string clientId, string fiscalYearId, string select = null)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.String | select | Comma separated list of properties to which the results will then be limited. Example: select=id (optional) |
Returns
| Type | Description |
|---|---|
| System.Collections.Generic.List<PostingProposalRuleCashRegister> | List<PostingProposalRuleCashRegister> |
Remarks
Retrieve a list of posting proposal rules for cash register from Rechnungswesen (accounting). When posting proposals are generated from electronic documents, these are completed using the posting proposal rules. The information from the document is compared to existing entries from the posting proposal rules. If the posting proposal rule and the information from the electronic document match completely, the system completes the posting proposal with the general ledger account, contra account, posting description and cost fields.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesCashRegisterGetAsync(String, String, String)
Retrieve a list of posting proposal rules for cash register
Declaration
Task<List<PostingProposalRuleCashRegister>> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesCashRegisterGetAsync(string clientId, string fiscalYearId, string select = null)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.String | select | Comma separated list of properties to which the results will then be limited. Example: select=id (optional) |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<System.Collections.Generic.List<PostingProposalRuleCashRegister>> | Task of List<PostingProposalRuleCashRegister> |
Remarks
Retrieve a list of posting proposal rules for cash register from Rechnungswesen (accounting). When posting proposals are generated from electronic documents, these are completed using the posting proposal rules. The information from the document is compared to existing entries from the posting proposal rules. If the posting proposal rule and the information from the electronic document match completely, the system completes the posting proposal with the general ledger account, contra account, posting description and cost fields.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesCashRegisterGetAsyncWithHttpInfo(String, String, String)
Retrieve a list of posting proposal rules for cash register
Declaration
Task<ApiResponse<List<PostingProposalRuleCashRegister>>> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesCashRegisterGetAsyncWithHttpInfo(string clientId, string fiscalYearId, string select = null)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.String | select | Comma separated list of properties to which the results will then be limited. Example: select=id (optional) |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<ApiResponse<System.Collections.Generic.List<PostingProposalRuleCashRegister>>> | Task of ApiResponse (List<PostingProposalRuleCashRegister>) |
Remarks
Retrieve a list of posting proposal rules for cash register from Rechnungswesen (accounting). When posting proposals are generated from electronic documents, these are completed using the posting proposal rules. The information from the document is compared to existing entries from the posting proposal rules. If the posting proposal rule and the information from the electronic document match completely, the system completes the posting proposal with the general ledger account, contra account, posting description and cost fields.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesCashRegisterGetWithHttpInfo(String, String, String)
Retrieve a list of posting proposal rules for cash register
Declaration
ApiResponse<List<PostingProposalRuleCashRegister>> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesCashRegisterGetWithHttpInfo(string clientId, string fiscalYearId, string select = null)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.String | select | Comma separated list of properties to which the results will then be limited. Example: select=id (optional) |
Returns
| Type | Description |
|---|---|
| ApiResponse<System.Collections.Generic.List<PostingProposalRuleCashRegister>> | ApiResponse of List<PostingProposalRuleCashRegister> |
Remarks
Retrieve a list of posting proposal rules for cash register from Rechnungswesen (accounting). When posting proposals are generated from electronic documents, these are completed using the posting proposal rules. The information from the document is compared to existing entries from the posting proposal rules. If the posting proposal rule and the information from the electronic document match completely, the system completes the posting proposal with the general ledger account, contra account, posting description and cost fields.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesIncomingInvoicesGet(String, String, String)
Retrieve a list of posting proposal rules for incoming invoices
Declaration
List<PostingProposalRuleIncomingInvoices> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesIncomingInvoicesGet(string clientId, string fiscalYearId, string select = null)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.String | select | Comma separated list of properties to which the results will then be limited. Example: select=id (optional) |
Returns
| Type | Description |
|---|---|
| System.Collections.Generic.List<PostingProposalRuleIncomingInvoices> | List<PostingProposalRuleIncomingInvoices> |
Remarks
Retrieve a list of posting proposal rules for incoming invoices from Rechnungswesen (accounting). When posting proposals are generated from electronic documents, these are completed using the posting proposal rules. The information from the document is compared to existing entries from the posting proposal rules. If the posting proposal rule and the information from the electronic document match completely, the system completes the posting proposal with the general ledger account, contra account, posting description and cost fields.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesIncomingInvoicesGetAsync(String, String, String)
Retrieve a list of posting proposal rules for incoming invoices
Declaration
Task<List<PostingProposalRuleIncomingInvoices>> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesIncomingInvoicesGetAsync(string clientId, string fiscalYearId, string select = null)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.String | select | Comma separated list of properties to which the results will then be limited. Example: select=id (optional) |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<System.Collections.Generic.List<PostingProposalRuleIncomingInvoices>> | Task of List<PostingProposalRuleIncomingInvoices> |
Remarks
Retrieve a list of posting proposal rules for incoming invoices from Rechnungswesen (accounting). When posting proposals are generated from electronic documents, these are completed using the posting proposal rules. The information from the document is compared to existing entries from the posting proposal rules. If the posting proposal rule and the information from the electronic document match completely, the system completes the posting proposal with the general ledger account, contra account, posting description and cost fields.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesIncomingInvoicesGetAsyncWithHttpInfo(String, String, String)
Retrieve a list of posting proposal rules for incoming invoices
Declaration
Task<ApiResponse<List<PostingProposalRuleIncomingInvoices>>> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesIncomingInvoicesGetAsyncWithHttpInfo(string clientId, string fiscalYearId, string select = null)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.String | select | Comma separated list of properties to which the results will then be limited. Example: select=id (optional) |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<ApiResponse<System.Collections.Generic.List<PostingProposalRuleIncomingInvoices>>> | Task of ApiResponse (List<PostingProposalRuleIncomingInvoices>) |
Remarks
Retrieve a list of posting proposal rules for incoming invoices from Rechnungswesen (accounting). When posting proposals are generated from electronic documents, these are completed using the posting proposal rules. The information from the document is compared to existing entries from the posting proposal rules. If the posting proposal rule and the information from the electronic document match completely, the system completes the posting proposal with the general ledger account, contra account, posting description and cost fields.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesIncomingInvoicesGetWithHttpInfo(String, String, String)
Retrieve a list of posting proposal rules for incoming invoices
Declaration
ApiResponse<List<PostingProposalRuleIncomingInvoices>> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesIncomingInvoicesGetWithHttpInfo(string clientId, string fiscalYearId, string select = null)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.String | select | Comma separated list of properties to which the results will then be limited. Example: select=id (optional) |
Returns
| Type | Description |
|---|---|
| ApiResponse<System.Collections.Generic.List<PostingProposalRuleIncomingInvoices>> | ApiResponse of List<PostingProposalRuleIncomingInvoices> |
Remarks
Retrieve a list of posting proposal rules for incoming invoices from Rechnungswesen (accounting). When posting proposals are generated from electronic documents, these are completed using the posting proposal rules. The information from the document is compared to existing entries from the posting proposal rules. If the posting proposal rule and the information from the electronic document match completely, the system completes the posting proposal with the general ledger account, contra account, posting description and cost fields.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesOutgoingInvoicesGet(String, String, String)
Retrieve a list of posting proposal rules for outgoing invoices
Declaration
List<PostingProposalRuleOutgoingInvoices> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesOutgoingInvoicesGet(string clientId, string fiscalYearId, string select = null)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.String | select | Comma separated list of properties to which the results will then be limited. Example: select=id (optional) |
Returns
| Type | Description |
|---|---|
| System.Collections.Generic.List<PostingProposalRuleOutgoingInvoices> | List<PostingProposalRuleOutgoingInvoices> |
Remarks
Retrieve a list of posting proposal rules for outgoing invoices from Rechnungswesen (accounting). When posting proposals are generated from electronic documents, these are completed using the posting proposal rules. The information from the document is compared to existing entries from the posting proposal rules. If the posting proposal rule and the information from the electronic document match completely, the system completes the posting proposal with the general ledger account, contra account, posting description and cost fields.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesOutgoingInvoicesGetAsync(String, String, String)
Retrieve a list of posting proposal rules for outgoing invoices
Declaration
Task<List<PostingProposalRuleOutgoingInvoices>> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesOutgoingInvoicesGetAsync(string clientId, string fiscalYearId, string select = null)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.String | select | Comma separated list of properties to which the results will then be limited. Example: select=id (optional) |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<System.Collections.Generic.List<PostingProposalRuleOutgoingInvoices>> | Task of List<PostingProposalRuleOutgoingInvoices> |
Remarks
Retrieve a list of posting proposal rules for outgoing invoices from Rechnungswesen (accounting). When posting proposals are generated from electronic documents, these are completed using the posting proposal rules. The information from the document is compared to existing entries from the posting proposal rules. If the posting proposal rule and the information from the electronic document match completely, the system completes the posting proposal with the general ledger account, contra account, posting description and cost fields.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesOutgoingInvoicesGetAsyncWithHttpInfo(String, String, String)
Retrieve a list of posting proposal rules for outgoing invoices
Declaration
Task<ApiResponse<List<PostingProposalRuleOutgoingInvoices>>> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesOutgoingInvoicesGetAsyncWithHttpInfo(string clientId, string fiscalYearId, string select = null)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.String | select | Comma separated list of properties to which the results will then be limited. Example: select=id (optional) |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<ApiResponse<System.Collections.Generic.List<PostingProposalRuleOutgoingInvoices>>> | Task of ApiResponse (List<PostingProposalRuleOutgoingInvoices>) |
Remarks
Retrieve a list of posting proposal rules for outgoing invoices from Rechnungswesen (accounting). When posting proposals are generated from electronic documents, these are completed using the posting proposal rules. The information from the document is compared to existing entries from the posting proposal rules. If the posting proposal rule and the information from the electronic document match completely, the system completes the posting proposal with the general ledger account, contra account, posting description and cost fields.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesOutgoingInvoicesGetWithHttpInfo(String, String, String)
Retrieve a list of posting proposal rules for outgoing invoices
Declaration
ApiResponse<List<PostingProposalRuleOutgoingInvoices>> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesOutgoingInvoicesGetWithHttpInfo(string clientId, string fiscalYearId, string select = null)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.String | select | Comma separated list of properties to which the results will then be limited. Example: select=id (optional) |
Returns
| Type | Description |
|---|---|
| ApiResponse<System.Collections.Generic.List<PostingProposalRuleOutgoingInvoices>> | ApiResponse of List<PostingProposalRuleOutgoingInvoices> |
Remarks
Retrieve a list of posting proposal rules for outgoing invoices from Rechnungswesen (accounting). When posting proposals are generated from electronic documents, these are completed using the posting proposal rules. The information from the document is compared to existing entries from the posting proposal rules. If the posting proposal rule and the information from the electronic document match completely, the system completes the posting proposal with the general ledger account, contra account, posting description and cost fields.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsCashRegisterBatchPost(String, String, List<PostingProposalCashRegister>)
Transfer a list of cash register data
Declaration
BatchResponseMessage ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsCashRegisterBatchPost(string clientId, string fiscalYearId, List<PostingProposalCashRegister> postingProposalCashRegister)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.Collections.Generic.List<PostingProposalCashRegister> | postingProposalCashRegister | Cash register data |
Returns
| Type | Description |
|---|---|
| BatchResponseMessage | BatchResponseMessage |
Remarks
Transferring of cash register data to Rechnungswesen (accounting) which is processed to posting proposals.<br> When posting proposals are generated, the system fills the fields of the posting record using the debitor/creditor master data, the open item balance, the default settings in the program, and the entries in the posting proposal rules. When processing cash register data, the program Rechnungswesen (accounting) does not automatically perform OPOS clearing. Date specification with time zone The given time zone in the cash register data should correspond to the time zone set on the server, since otherwise dates may be deferred. As a rule, the given time zone is the Central European time zone (CET/CEST).<br><br> It is recommended that the time is set in this specific format 00:00:00.000 (hh:mm:ss.f).<br> Example: 2016-12-30T00:00:00.000+01:00<br> If 23:59.59.999 is specified as the exact date and time, depending on the database field, the next day may be displayed due to rounding differences. For example: JSON = 2016-01-01T23:59:59.999+01:00 (01.01.2016) | database = 2016-01-02T00:00.000 +01.00 (02.01.2016)<br><br> See also the official site of Microsoft:<br> English article: https://technet.microsoft.com/en-us/library/ms187819.aspx <br> German article: https://technet.microsoft.com/de-de/library/ms187819.aspx <br><br> Use multiple data paths It is necessary to know the correct data path to address the correct data stock. If the correct data path cannot be determined in DATEVconnect, the desired data path can be defined by a configuration file to resolve this data path collision. Further information is provided in Info Database, document 1071637.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsCashRegisterBatchPostAsync(String, String, List<PostingProposalCashRegister>)
Transfer a list of cash register data
Declaration
Task<BatchResponseMessage> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsCashRegisterBatchPostAsync(string clientId, string fiscalYearId, List<PostingProposalCashRegister> postingProposalCashRegister)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.Collections.Generic.List<PostingProposalCashRegister> | postingProposalCashRegister | Cash register data |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<BatchResponseMessage> | Task of BatchResponseMessage |
Remarks
Transferring of cash register data to Rechnungswesen (accounting) which is processed to posting proposals.<br> When posting proposals are generated, the system fills the fields of the posting record using the debitor/creditor master data, the open item balance, the default settings in the program, and the entries in the posting proposal rules. When processing cash register data, the program Rechnungswesen (accounting) does not automatically perform OPOS clearing. Date specification with time zone The given time zone in the cash register data should correspond to the time zone set on the server, since otherwise dates may be deferred. As a rule, the given time zone is the Central European time zone (CET/CEST).<br><br> It is recommended that the time is set in this specific format 00:00:00.000 (hh:mm:ss.f).<br> Example: 2016-12-30T00:00:00.000+01:00<br> If 23:59.59.999 is specified as the exact date and time, depending on the database field, the next day may be displayed due to rounding differences. For example: JSON = 2016-01-01T23:59:59.999+01:00 (01.01.2016) | database = 2016-01-02T00:00.000 +01.00 (02.01.2016)<br><br> See also the official site of Microsoft:<br> English article: https://technet.microsoft.com/en-us/library/ms187819.aspx <br> German article: https://technet.microsoft.com/de-de/library/ms187819.aspx <br><br> Use multiple data paths It is necessary to know the correct data path to address the correct data stock. If the correct data path cannot be determined in DATEVconnect, the desired data path can be defined by a configuration file to resolve this data path collision. Further information is provided in Info Database, document 1071637.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsCashRegisterBatchPostAsyncWithHttpInfo(String, String, List<PostingProposalCashRegister>)
Transfer a list of cash register data
Declaration
Task<ApiResponse<BatchResponseMessage>> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsCashRegisterBatchPostAsyncWithHttpInfo(string clientId, string fiscalYearId, List<PostingProposalCashRegister> postingProposalCashRegister)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.Collections.Generic.List<PostingProposalCashRegister> | postingProposalCashRegister | Cash register data |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<ApiResponse<BatchResponseMessage>> | Task of ApiResponse (BatchResponseMessage) |
Remarks
Transferring of cash register data to Rechnungswesen (accounting) which is processed to posting proposals.<br> When posting proposals are generated, the system fills the fields of the posting record using the debitor/creditor master data, the open item balance, the default settings in the program, and the entries in the posting proposal rules. When processing cash register data, the program Rechnungswesen (accounting) does not automatically perform OPOS clearing. Date specification with time zone The given time zone in the cash register data should correspond to the time zone set on the server, since otherwise dates may be deferred. As a rule, the given time zone is the Central European time zone (CET/CEST).<br><br> It is recommended that the time is set in this specific format 00:00:00.000 (hh:mm:ss.f).<br> Example: 2016-12-30T00:00:00.000+01:00<br> If 23:59.59.999 is specified as the exact date and time, depending on the database field, the next day may be displayed due to rounding differences. For example: JSON = 2016-01-01T23:59:59.999+01:00 (01.01.2016) | database = 2016-01-02T00:00.000 +01.00 (02.01.2016)<br><br> See also the official site of Microsoft:<br> English article: https://technet.microsoft.com/en-us/library/ms187819.aspx <br> German article: https://technet.microsoft.com/de-de/library/ms187819.aspx <br><br> Use multiple data paths It is necessary to know the correct data path to address the correct data stock. If the correct data path cannot be determined in DATEVconnect, the desired data path can be defined by a configuration file to resolve this data path collision. Further information is provided in Info Database, document 1071637.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsCashRegisterBatchPostWithHttpInfo(String, String, List<PostingProposalCashRegister>)
Transfer a list of cash register data
Declaration
ApiResponse<BatchResponseMessage> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsCashRegisterBatchPostWithHttpInfo(string clientId, string fiscalYearId, List<PostingProposalCashRegister> postingProposalCashRegister)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.Collections.Generic.List<PostingProposalCashRegister> | postingProposalCashRegister | Cash register data |
Returns
| Type | Description |
|---|---|
| ApiResponse<BatchResponseMessage> | ApiResponse of BatchResponseMessage |
Remarks
Transferring of cash register data to Rechnungswesen (accounting) which is processed to posting proposals.<br> When posting proposals are generated, the system fills the fields of the posting record using the debitor/creditor master data, the open item balance, the default settings in the program, and the entries in the posting proposal rules. When processing cash register data, the program Rechnungswesen (accounting) does not automatically perform OPOS clearing. Date specification with time zone The given time zone in the cash register data should correspond to the time zone set on the server, since otherwise dates may be deferred. As a rule, the given time zone is the Central European time zone (CET/CEST).<br><br> It is recommended that the time is set in this specific format 00:00:00.000 (hh:mm:ss.f).<br> Example: 2016-12-30T00:00:00.000+01:00<br> If 23:59.59.999 is specified as the exact date and time, depending on the database field, the next day may be displayed due to rounding differences. For example: JSON = 2016-01-01T23:59:59.999+01:00 (01.01.2016) | database = 2016-01-02T00:00.000 +01.00 (02.01.2016)<br><br> See also the official site of Microsoft:<br> English article: https://technet.microsoft.com/en-us/library/ms187819.aspx <br> German article: https://technet.microsoft.com/de-de/library/ms187819.aspx <br><br> Use multiple data paths It is necessary to know the correct data path to address the correct data stock. If the correct data path cannot be determined in DATEVconnect, the desired data path can be defined by a configuration file to resolve this data path collision. Further information is provided in Info Database, document 1071637.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsIncomingInvoicesBatchPost(String, String, List<PostingProposalIncomingInvoices>)
Transfer a list of incoming invoice data
Declaration
BatchResponseMessage ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsIncomingInvoicesBatchPost(string clientId, string fiscalYearId, List<PostingProposalIncomingInvoices> postingProposalIncomingInvoices)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.Collections.Generic.List<PostingProposalIncomingInvoices> | postingProposalIncomingInvoices | Incoming invoice data |
Returns
| Type | Description |
|---|---|
| BatchResponseMessage | BatchResponseMessage |
Remarks
Transferring of incoming invoice data to Rechnungswesen (accounting) which is processed to posting proposals.<br> When posting proposals are generated, the system fills the fields of the posting record using the debitor/creditor master data, the open item balance, the default settings in the program, and the entries in the posting proposal rules. Date specification with time zone The given time zone in the incoming invoice data should correspond to the time zone set on the server, since otherwise dates may be deferred. As a rule, the given time zone is the Central European time zone (CET/CEST).<br><br> It is recommended that the time is set in this specific format 00:00:00.000 (hh:mm:ss.f).<br> Example: 2016-12-30T00:00:00.000+01:00<br> If 23:59.59.999 is specified as the exact date and time, depending on the database field, the next day may be displayed due to rounding differences. For example: JSON = 2016-01-01T23:59:59.999+01:00 (01.01.2016) | database = 2016-01-02T00:00.000 +01.00 (02.01.2016)<br><br> See also the official site of Microsoft:<br> English article: https://technet.microsoft.com/en-us/library/ms187819.aspx <br> German article: https://technet.microsoft.com/de-de/library/ms187819.aspx <br><br> Use multiple data paths It is necessary to know the correct data path to address the correct data stock. If the correct data path cannot be determined in DATEVconnect, the desired data path can be defined by a configuration file to resolve this data path collision. Further information is provided in Info Database, document 1071637.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsIncomingInvoicesBatchPostAsync(String, String, List<PostingProposalIncomingInvoices>)
Transfer a list of incoming invoice data
Declaration
Task<BatchResponseMessage> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsIncomingInvoicesBatchPostAsync(string clientId, string fiscalYearId, List<PostingProposalIncomingInvoices> postingProposalIncomingInvoices)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.Collections.Generic.List<PostingProposalIncomingInvoices> | postingProposalIncomingInvoices | Incoming invoice data |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<BatchResponseMessage> | Task of BatchResponseMessage |
Remarks
Transferring of incoming invoice data to Rechnungswesen (accounting) which is processed to posting proposals.<br> When posting proposals are generated, the system fills the fields of the posting record using the debitor/creditor master data, the open item balance, the default settings in the program, and the entries in the posting proposal rules. Date specification with time zone The given time zone in the incoming invoice data should correspond to the time zone set on the server, since otherwise dates may be deferred. As a rule, the given time zone is the Central European time zone (CET/CEST).<br><br> It is recommended that the time is set in this specific format 00:00:00.000 (hh:mm:ss.f).<br> Example: 2016-12-30T00:00:00.000+01:00<br> If 23:59.59.999 is specified as the exact date and time, depending on the database field, the next day may be displayed due to rounding differences. For example: JSON = 2016-01-01T23:59:59.999+01:00 (01.01.2016) | database = 2016-01-02T00:00.000 +01.00 (02.01.2016)<br><br> See also the official site of Microsoft:<br> English article: https://technet.microsoft.com/en-us/library/ms187819.aspx <br> German article: https://technet.microsoft.com/de-de/library/ms187819.aspx <br><br> Use multiple data paths It is necessary to know the correct data path to address the correct data stock. If the correct data path cannot be determined in DATEVconnect, the desired data path can be defined by a configuration file to resolve this data path collision. Further information is provided in Info Database, document 1071637.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsIncomingInvoicesBatchPostAsyncWithHttpInfo(String, String, List<PostingProposalIncomingInvoices>)
Transfer a list of incoming invoice data
Declaration
Task<ApiResponse<BatchResponseMessage>> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsIncomingInvoicesBatchPostAsyncWithHttpInfo(string clientId, string fiscalYearId, List<PostingProposalIncomingInvoices> postingProposalIncomingInvoices)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.Collections.Generic.List<PostingProposalIncomingInvoices> | postingProposalIncomingInvoices | Incoming invoice data |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<ApiResponse<BatchResponseMessage>> | Task of ApiResponse (BatchResponseMessage) |
Remarks
Transferring of incoming invoice data to Rechnungswesen (accounting) which is processed to posting proposals.<br> When posting proposals are generated, the system fills the fields of the posting record using the debitor/creditor master data, the open item balance, the default settings in the program, and the entries in the posting proposal rules. Date specification with time zone The given time zone in the incoming invoice data should correspond to the time zone set on the server, since otherwise dates may be deferred. As a rule, the given time zone is the Central European time zone (CET/CEST).<br><br> It is recommended that the time is set in this specific format 00:00:00.000 (hh:mm:ss.f).<br> Example: 2016-12-30T00:00:00.000+01:00<br> If 23:59.59.999 is specified as the exact date and time, depending on the database field, the next day may be displayed due to rounding differences. For example: JSON = 2016-01-01T23:59:59.999+01:00 (01.01.2016) | database = 2016-01-02T00:00.000 +01.00 (02.01.2016)<br><br> See also the official site of Microsoft:<br> English article: https://technet.microsoft.com/en-us/library/ms187819.aspx <br> German article: https://technet.microsoft.com/de-de/library/ms187819.aspx <br><br> Use multiple data paths It is necessary to know the correct data path to address the correct data stock. If the correct data path cannot be determined in DATEVconnect, the desired data path can be defined by a configuration file to resolve this data path collision. Further information is provided in Info Database, document 1071637.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsIncomingInvoicesBatchPostWithHttpInfo(String, String, List<PostingProposalIncomingInvoices>)
Transfer a list of incoming invoice data
Declaration
ApiResponse<BatchResponseMessage> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsIncomingInvoicesBatchPostWithHttpInfo(string clientId, string fiscalYearId, List<PostingProposalIncomingInvoices> postingProposalIncomingInvoices)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.Collections.Generic.List<PostingProposalIncomingInvoices> | postingProposalIncomingInvoices | Incoming invoice data |
Returns
| Type | Description |
|---|---|
| ApiResponse<BatchResponseMessage> | ApiResponse of BatchResponseMessage |
Remarks
Transferring of incoming invoice data to Rechnungswesen (accounting) which is processed to posting proposals.<br> When posting proposals are generated, the system fills the fields of the posting record using the debitor/creditor master data, the open item balance, the default settings in the program, and the entries in the posting proposal rules. Date specification with time zone The given time zone in the incoming invoice data should correspond to the time zone set on the server, since otherwise dates may be deferred. As a rule, the given time zone is the Central European time zone (CET/CEST).<br><br> It is recommended that the time is set in this specific format 00:00:00.000 (hh:mm:ss.f).<br> Example: 2016-12-30T00:00:00.000+01:00<br> If 23:59.59.999 is specified as the exact date and time, depending on the database field, the next day may be displayed due to rounding differences. For example: JSON = 2016-01-01T23:59:59.999+01:00 (01.01.2016) | database = 2016-01-02T00:00.000 +01.00 (02.01.2016)<br><br> See also the official site of Microsoft:<br> English article: https://technet.microsoft.com/en-us/library/ms187819.aspx <br> German article: https://technet.microsoft.com/de-de/library/ms187819.aspx <br><br> Use multiple data paths It is necessary to know the correct data path to address the correct data stock. If the correct data path cannot be determined in DATEVconnect, the desired data path can be defined by a configuration file to resolve this data path collision. Further information is provided in Info Database, document 1071637.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsOutgoingInvoicesBatchPost(String, String, List<PostingProposalOutgoingInvoices>)
Transfer a list of outgoing invoice data
Declaration
BatchResponseMessage ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsOutgoingInvoicesBatchPost(string clientId, string fiscalYearId, List<PostingProposalOutgoingInvoices> postingProposalOutgoingInvoices)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.Collections.Generic.List<PostingProposalOutgoingInvoices> | postingProposalOutgoingInvoices | Outgoing invoice data |
Returns
| Type | Description |
|---|---|
| BatchResponseMessage | BatchResponseMessage |
Remarks
Transferring of outgoing invoice data to Rechnungswesen (accounting) which is processed to posting proposals.<br> When posting proposals are generated, the system fills the fields of the posting record using the debitor/creditor master data, the open item balance, the default settings in the program, and the entries in the posting proposal rules. Date specification with time zone The given time zone in the outgoing invoice data should correspond to the time zone set on the server, since otherwise dates may be deferred. As a rule, the given time zone is the Central European time zone (CET/CEST).<br><br> It is recommended that the time is set in this specific format 00:00:00.000 (hh:mm:ss.f).<br> Example: 2016-12-30T00:00:00.000+01:00<br> If 23:59.59.999 is specified as the exact date and time, depending on the database field, the next day may be displayed due to rounding differences. For example: JSON = 2016-01-01T23:59:59.999+01:00 (01.01.2016) | database = 2016-01-02T00:00.000 +01.00 (02.01.2016)<br><br> See also the official site of Microsoft:<br> English article: https://technet.microsoft.com/en-us/library/ms187819.aspx <br> German article: https://technet.microsoft.com/de-de/library/ms187819.aspx <br><br> Use multiple data paths It is necessary to know the correct data path to address the correct data stock. If the correct data path cannot be determined in DATEVconnect, the desired data path can be defined by a configuration file to resolve this data path collision. Further information is provided in Info Database, document 1071637.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsOutgoingInvoicesBatchPostAsync(String, String, List<PostingProposalOutgoingInvoices>)
Transfer a list of outgoing invoice data
Declaration
Task<BatchResponseMessage> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsOutgoingInvoicesBatchPostAsync(string clientId, string fiscalYearId, List<PostingProposalOutgoingInvoices> postingProposalOutgoingInvoices)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.Collections.Generic.List<PostingProposalOutgoingInvoices> | postingProposalOutgoingInvoices | Outgoing invoice data |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<BatchResponseMessage> | Task of BatchResponseMessage |
Remarks
Transferring of outgoing invoice data to Rechnungswesen (accounting) which is processed to posting proposals.<br> When posting proposals are generated, the system fills the fields of the posting record using the debitor/creditor master data, the open item balance, the default settings in the program, and the entries in the posting proposal rules. Date specification with time zone The given time zone in the outgoing invoice data should correspond to the time zone set on the server, since otherwise dates may be deferred. As a rule, the given time zone is the Central European time zone (CET/CEST).<br><br> It is recommended that the time is set in this specific format 00:00:00.000 (hh:mm:ss.f).<br> Example: 2016-12-30T00:00:00.000+01:00<br> If 23:59.59.999 is specified as the exact date and time, depending on the database field, the next day may be displayed due to rounding differences. For example: JSON = 2016-01-01T23:59:59.999+01:00 (01.01.2016) | database = 2016-01-02T00:00.000 +01.00 (02.01.2016)<br><br> See also the official site of Microsoft:<br> English article: https://technet.microsoft.com/en-us/library/ms187819.aspx <br> German article: https://technet.microsoft.com/de-de/library/ms187819.aspx <br><br> Use multiple data paths It is necessary to know the correct data path to address the correct data stock. If the correct data path cannot be determined in DATEVconnect, the desired data path can be defined by a configuration file to resolve this data path collision. Further information is provided in Info Database, document 1071637.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsOutgoingInvoicesBatchPostAsyncWithHttpInfo(String, String, List<PostingProposalOutgoingInvoices>)
Transfer a list of outgoing invoice data
Declaration
Task<ApiResponse<BatchResponseMessage>> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsOutgoingInvoicesBatchPostAsyncWithHttpInfo(string clientId, string fiscalYearId, List<PostingProposalOutgoingInvoices> postingProposalOutgoingInvoices)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.Collections.Generic.List<PostingProposalOutgoingInvoices> | postingProposalOutgoingInvoices | Outgoing invoice data |
Returns
| Type | Description |
|---|---|
| System.Threading.Tasks.Task<ApiResponse<BatchResponseMessage>> | Task of ApiResponse (BatchResponseMessage) |
Remarks
Transferring of outgoing invoice data to Rechnungswesen (accounting) which is processed to posting proposals.<br> When posting proposals are generated, the system fills the fields of the posting record using the debitor/creditor master data, the open item balance, the default settings in the program, and the entries in the posting proposal rules. Date specification with time zone The given time zone in the outgoing invoice data should correspond to the time zone set on the server, since otherwise dates may be deferred. As a rule, the given time zone is the Central European time zone (CET/CEST).<br><br> It is recommended that the time is set in this specific format 00:00:00.000 (hh:mm:ss.f).<br> Example: 2016-12-30T00:00:00.000+01:00<br> If 23:59.59.999 is specified as the exact date and time, depending on the database field, the next day may be displayed due to rounding differences. For example: JSON = 2016-01-01T23:59:59.999+01:00 (01.01.2016) | database = 2016-01-02T00:00.000 +01.00 (02.01.2016)<br><br> See also the official site of Microsoft:<br> English article: https://technet.microsoft.com/en-us/library/ms187819.aspx <br> German article: https://technet.microsoft.com/de-de/library/ms187819.aspx <br><br> Use multiple data paths It is necessary to know the correct data path to address the correct data stock. If the correct data path cannot be determined in DATEVconnect, the desired data path can be defined by a configuration file to resolve this data path collision. Further information is provided in Info Database, document 1071637.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |
ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsOutgoingInvoicesBatchPostWithHttpInfo(String, String, List<PostingProposalOutgoingInvoices>)
Transfer a list of outgoing invoice data
Declaration
ApiResponse<BatchResponseMessage> ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsOutgoingInvoicesBatchPostWithHttpInfo(string clientId, string fiscalYearId, List<PostingProposalOutgoingInvoices> postingProposalOutgoingInvoices)Parameters
| Type | Name | Description |
|---|---|---|
| System.String | clientId | ID of central client/company |
| System.String | fiscalYearId | ID of the fiscal year |
| System.Collections.Generic.List<PostingProposalOutgoingInvoices> | postingProposalOutgoingInvoices | Outgoing invoice data |
Returns
| Type | Description |
|---|---|
| ApiResponse<BatchResponseMessage> | ApiResponse of BatchResponseMessage |
Remarks
Transferring of outgoing invoice data to Rechnungswesen (accounting) which is processed to posting proposals.<br> When posting proposals are generated, the system fills the fields of the posting record using the debitor/creditor master data, the open item balance, the default settings in the program, and the entries in the posting proposal rules. Date specification with time zone The given time zone in the outgoing invoice data should correspond to the time zone set on the server, since otherwise dates may be deferred. As a rule, the given time zone is the Central European time zone (CET/CEST).<br><br> It is recommended that the time is set in this specific format 00:00:00.000 (hh:mm:ss.f).<br> Example: 2016-12-30T00:00:00.000+01:00<br> If 23:59.59.999 is specified as the exact date and time, depending on the database field, the next day may be displayed due to rounding differences. For example: JSON = 2016-01-01T23:59:59.999+01:00 (01.01.2016) | database = 2016-01-02T00:00.000 +01.00 (02.01.2016)<br><br> See also the official site of Microsoft:<br> English article: https://technet.microsoft.com/en-us/library/ms187819.aspx <br> German article: https://technet.microsoft.com/de-de/library/ms187819.aspx <br><br> Use multiple data paths It is necessary to know the correct data path to address the correct data stock. If the correct data path cannot be determined in DATEVconnect, the desired data path can be defined by a configuration file to resolve this data path collision. Further information is provided in Info Database, document 1071637.
Exceptions
| Type | Condition |
|---|---|
| ApiException | Thrown when fails to make API call |