| Tip |
|---|
Available from CRM.COM R9.1.0 |
...
Name | Type | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
token | String | The token retrieved from the login method | ||||||||
| invoice_identifier (mandatory) | Invoice identifier | The identifier of the invoice that should be updated. Only invoices in draft state can be specified.The allowed invoice identifier fields are the following:
| ||||||||
accounts_receivable_identifier (optional) | Accounts receivable identifier | The identifier of the invoice's updated accounts receivable. The allowed accounts receivable identifier fields are the following:
| ||||||||
type_identifier (optional) | Financial Transaction Type identifier | The identifier of the invoice's updated type. Only Financial transaction Types with classification Invoice are allowed to be specified. The allowed financial transaction type identifier fields are the following:
| ||||||||
category_identifier (optional) | Financial Transaction Category identifier | The identifier of the invoice's updated category. The allowed financial transaction category identifier fields are the following:
| ||||||||
member_accounts_receivable_identifier (optional) | Accounts receivable identifier | The member accounts receivable. Applicable only if the invoice is issues against a parent accounts receivable which fund its member accounts. The allowed accounts receivable identifier fields are the following:
| ||||||||
intended_currency_identifier (optional) | Currency Identifier | The currency that the user was intended to use for the invoice. If specified then it is validated against the currency of the specified accounts receivable and if they don't match then an error is throw. Note that the intended currency is not saved within CRM.COM; it is just used for validation purposes. The allowed currency identifier fields are the following:
| ||||||||
due_on (optional) | Date | The Date on which the Invoice will be due on. | ||||||||
issuedposted_on (optional) | Date | The Issue posting date of the Invoicethe financial transaction which is before or equal to the current date and not included in already closed accounting periods. If not specified then the current date is applied.
| ||||||||
notes (optional) | String | Shared notes for the invoice | ||||||||
back_office_code (optional) | String | The back office code of the invoice | ||||||||
udf_string_1 (optional) | String | User Defined Field of type String | ||||||||
udf_string_2 (optional) | String | User Defined Field of type String | ||||||||
udf_string_3 (optional) | String | User Defined Field of type String | ||||||||
udf_string_4 (optional) | String | User Defined Field of type String | ||||||||
udf_string_5 (optional) | String | User Defined Field of type String | ||||||||
udf_string_6 (optional) | String | User Defined Field of type String | ||||||||
udf_string_7 (optional) | String | User Defined Field of type String | ||||||||
udf_string_8 (optional) | String | User Defined Field of type String | ||||||||
udf_float_1 (optional) | Float | User Defined Field of type Float | ||||||||
udf_float_2 (optional) | Float | User Defined Field of type Float | ||||||||
udf_float_3 (optional) | Float | User Defined Field of type Float | ||||||||
udf_float_4 (optional) | Float | User Defined Field of type Float | ||||||||
udf_date_1 (optional) | Date | User Defined Field of type Date | ||||||||
udf_date_2 (optional) | Date | User Defined Field of type Date | ||||||||
udf_date_3 (optional) | Date | User Defined Field of type Date | ||||||||
udf_date_4 (optional) | Date | User Defined Field of type Date | ||||||||
| invoice_item_set | Set of Invoice Item objects | The information related to the items of the invoice to be updated
| ||||||||
fields_set (optional) | List of Strings, comma separated | A list of fields that should be included in the results. If not specified then all the available fields will be returned |
...