Search Results for

    Show / Hide Table of Contents

    Class PostingProposalsApi

    Represents a collection of functions to interact with the API endpoints

    Inheritance
    System.Object
    PostingProposalsApi
    Implements
    IPostingProposalsApi
    IApiAccessor
    Inherited Members
    System.Object.ToString()
    System.Object.Equals(System.Object)
    System.Object.Equals(System.Object, System.Object)
    System.Object.ReferenceEquals(System.Object, System.Object)
    System.Object.GetHashCode()
    System.Object.GetType()
    System.Object.MemberwiseClone()
    Namespace: Simplic.Datev.Swagger.Api
    Assembly: Simplic.Datev.IO.Swagger.dll
    Syntax
    public class PostingProposalsApi : IPostingProposalsApi, IApiAccessor

    Constructors

    | Improve this Doc View Source

    PostingProposalsApi(Configuration)

    Initializes a new instance of the PostingProposalsApi class using Configuration object

    Declaration
    public PostingProposalsApi(Configuration configuration = null)
    Parameters
    Type Name Description
    Configuration configuration

    An instance of Configuration

    | Improve this Doc View Source

    PostingProposalsApi(String)

    Initializes a new instance of the PostingProposalsApi class.

    Declaration
    public PostingProposalsApi(string basePath)
    Parameters
    Type Name Description
    System.String basePath

    Properties

    | Improve this Doc View Source

    Configuration

    Gets or sets the configuration object

    Declaration
    public Configuration Configuration { get; set; }
    Property Value
    Type Description
    Configuration

    An instance of the Configuration

    | Improve this Doc View Source

    ExceptionFactory

    Provides a factory method hook for the creation of exceptions.

    Declaration
    public ExceptionFactory ExceptionFactory { get; set; }
    Property Value
    Type Description
    ExceptionFactory

    Methods

    | Improve this Doc View Source

    AddDefaultHeader(String, String)

    Add default header.

    Declaration
    [Obsolete("AddDefaultHeader is deprecated, please use Configuration.AddDefaultHeader instead.")]
    public void AddDefaultHeader(string key, string value)
    Parameters
    Type Name Description
    System.String key

    Header field name.

    System.String value

    Header field value.

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesCashRegisterGet(String, String, String)

    Retrieve a list of posting proposal rules for cash register 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.

    Declaration
    public 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>

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesCashRegisterGetAsync(String, String, String)

    Retrieve a list of posting proposal rules for cash register 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.

    Declaration
    public async 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>

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesCashRegisterGetAsyncWithHttpInfo(String, String, String)

    Retrieve a list of posting proposal rules for cash register 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.

    Declaration
    public async 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>)

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesCashRegisterGetWithHttpInfo(String, String, String)

    Retrieve a list of posting proposal rules for cash register 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.

    Declaration
    public 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>

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesIncomingInvoicesGet(String, String, String)

    Retrieve a list of posting proposal rules for incoming invoices 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.

    Declaration
    public 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>

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesIncomingInvoicesGetAsync(String, String, String)

    Retrieve a list of posting proposal rules for incoming invoices 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.

    Declaration
    public async 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>

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesIncomingInvoicesGetAsyncWithHttpInfo(String, String, String)

    Retrieve a list of posting proposal rules for incoming invoices 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.

    Declaration
    public async 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>)

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesIncomingInvoicesGetWithHttpInfo(String, String, String)

    Retrieve a list of posting proposal rules for incoming invoices 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.

    Declaration
    public 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>

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesOutgoingInvoicesGet(String, String, String)

    Retrieve a list of posting proposal rules for outgoing invoices 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.

    Declaration
    public 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>

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesOutgoingInvoicesGetAsync(String, String, String)

    Retrieve a list of posting proposal rules for outgoing invoices 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.

    Declaration
    public async 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>

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesOutgoingInvoicesGetAsyncWithHttpInfo(String, String, String)

    Retrieve a list of posting proposal rules for outgoing invoices 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.

    Declaration
    public async 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>)

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalRulesOutgoingInvoicesGetWithHttpInfo(String, String, String)

    Retrieve a list of posting proposal rules for outgoing invoices 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.

    Declaration
    public 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>

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsCashRegisterBatchPost(String, String, List<PostingProposalCashRegister>)

    Transfer a list of cash register data 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.

    Declaration
    public 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

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsCashRegisterBatchPostAsync(String, String, List<PostingProposalCashRegister>)

    Transfer a list of cash register data 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.

    Declaration
    public async 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

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsCashRegisterBatchPostAsyncWithHttpInfo(String, String, List<PostingProposalCashRegister>)

    Transfer a list of cash register data 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.

    Declaration
    public async 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)

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsCashRegisterBatchPostWithHttpInfo(String, String, List<PostingProposalCashRegister>)

    Transfer a list of cash register data 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.

    Declaration
    public 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

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsIncomingInvoicesBatchPost(String, String, List<PostingProposalIncomingInvoices>)

    Transfer a list of incoming invoice data 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.

    Declaration
    public 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

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsIncomingInvoicesBatchPostAsync(String, String, List<PostingProposalIncomingInvoices>)

    Transfer a list of incoming invoice data 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.

    Declaration
    public async 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

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsIncomingInvoicesBatchPostAsyncWithHttpInfo(String, String, List<PostingProposalIncomingInvoices>)

    Transfer a list of incoming invoice data 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.

    Declaration
    public async 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)

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsIncomingInvoicesBatchPostWithHttpInfo(String, String, List<PostingProposalIncomingInvoices>)

    Transfer a list of incoming invoice data 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.

    Declaration
    public 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

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsOutgoingInvoicesBatchPost(String, String, List<PostingProposalOutgoingInvoices>)

    Transfer a list of outgoing invoice data 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.

    Declaration
    public 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

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsOutgoingInvoicesBatchPostAsync(String, String, List<PostingProposalOutgoingInvoices>)

    Transfer a list of outgoing invoice data 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.

    Declaration
    public async 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

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsOutgoingInvoicesBatchPostAsyncWithHttpInfo(String, String, List<PostingProposalOutgoingInvoices>)

    Transfer a list of outgoing invoice data 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.

    Declaration
    public async 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)

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    ClientsClientIdFiscalYearsFiscalYearIdPostingProposalsOutgoingInvoicesBatchPostWithHttpInfo(String, String, List<PostingProposalOutgoingInvoices>)

    Transfer a list of outgoing invoice data 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.

    Declaration
    public 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

    Exceptions
    Type Condition
    ApiException

    Thrown when fails to make API call

    | Improve this Doc View Source

    DefaultHeader()

    Gets the default header.

    Declaration
    [Obsolete("DefaultHeader is deprecated, please use Configuration.DefaultHeader instead.")]
    public IDictionary<string, string> DefaultHeader()
    Returns
    Type Description
    System.Collections.Generic.IDictionary<System.String, System.String>

    Dictionary of HTTP header

    | Improve this Doc View Source

    GetBasePath()

    Gets the base path of the API client.

    Declaration
    public string GetBasePath()
    Returns
    Type Description
    System.String

    The base path

    | Improve this Doc View Source

    SetBasePath(String)

    Sets the base path of the API client.

    Declaration
    [Obsolete("SetBasePath is deprecated, please do 'Configuration.ApiClient = new ApiClient(\"http://new-path\")' instead.")]
    public void SetBasePath(string basePath)
    Parameters
    Type Name Description
    System.String basePath

    Implements

    IPostingProposalsApi
    IApiAccessor
    • Improve this Doc
    • View Source
    In This Article
    Back to top Copyright © 2018 SIMPLIC GmbH
    Generated by DocFx