Add a New Event Miscellaneous Expense/Credit

The id of the event you would like to add the miscellaneous expense/credit to.

A short description of the miscellaneous expense/credit. Longer values are truncated to 1000 characters.

The is_credit flag indicates whether or not the miscellaneous expense/credit you’re adding is a credit. For example, if you’re adding a partial credit the event organizer issued for a booth service, set the is_credit flag to true. Accepted values: true or false (also yes/no, 1/0); any other value is rejected with an error.

Use the amount field to specify the amount of the miscellaneous expense/credit. The value of this field should be a decimal with no currency symbols or commas (e.g., 11250.75). If the miscellaneous expense/credit you’re adding is a credit, pass in a positive number for the amount field, and set the is_credit flag to true. If you leave amount out, the amount is the sum of the charges in amount_cost_center_breakdown (0.00 when there is none).

The cost center allocations as a JSON array of cost_center_id and charge values. Use cost center IDs from /v1/references/cost_centers, or null for Unassigned (responses show it as cost_center "Not Specified"). Charges must be nonnegative and must not exceed the amount in total; any unallocated remainder is assigned to Unassigned. If amount is omitted, the charges determine the total. Invalid JSON, unknown cost centers, negative charges, and allocations exceeding the amount return HTTP 400 without saving changes. For example, to allocate $100, send [{"cost_center_id": 123456, "charge": 60.00}, {"cost_center_id": null, "charge": 40.00}].

The Payment Status Id for the miscellaneous expense/credit. Note: Payment status only applies to miscellaneous expenses. If you pass in a payment_status_id for a miscellaneous credit (i.e., when the is_credit flag is set to true), it will be ignored. You can use the following endpoint to retrieve a list of available payment_status_id's: /v1/references/payment_statuses. Any other value is rejected with an error.

Payment due date in YYYY-MM-DD format. Note: Payment Due Date only applies to miscellaneous expenses. If you pass in a payment_due_date for a miscellaneous credit (i.e., when the is_credit flag is set to true), it will be ignored. A value that is not a valid date is rejected with an error.

The next payment due date in YYYY-MM-DD format. This field only applies to expenses with payment_status_id 2 (Partially Paid). It is ignored for credits and other payment statuses. Responses use next_partial_payment_due_date; either name is accepted as input. If both names are supplied, their values must match. A value that is not a valid date is rejected with an error.

An input alias for next_payment_due_date. The same payment-status rules apply. If both names are supplied, their values must match. A value that is not a valid date is rejected with an error.

Notes about the payment for the expense. Note: Payment notes only apply to miscellaneous expenses. If you pass in a payment_notes for a miscellaneous credit (i.e., when the is_credit flag is set to true), it will be ignored.

Notes about the miscellaneous expense/credit. Only accepts plain text. Any html tags in the value you pass in will be stripped. New line characters will get replaced with a <br/> tag, and the text is stored HTML-encoded, so it is returned as HTML (a < b comes back as a < b).

The integration_metadata_field_1 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular miscellaneous expense/credit (e.g., the "external id" of the expense from another system you're integrating with).

The integration_metadata_field_2 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular miscellaneous expense/credit (e.g., the "external id" of the expense from another system you're integrating with).

The integration_metadata_field_3 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular miscellaneous expense/credit (e.g., the "external id" of the expense from another system you're integrating with).

The integration_metadata_field_4 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular miscellaneous expense/credit (e.g., the "external id" of the expense from another system you're integrating with).

The integration_metadata_field_5 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular miscellaneous expense/credit (e.g., the "external id" of the expense from another system you're integrating with).