Create Invoice
Create a new invoice
Request
- Base URLhttps://app.moderntreasury.com/api
- URLhttps://app.moderntreasury.com/api/invoices
- AuthHTTP basic
Request body
When true, the invoice will progress to unpaid automatically and cannot be edited after entering that state. If the invoice fails to progress to unpaid, the errors will be returned and the invoice will not be created.
Defaults to USD if not provided.
A date
When payment_method is automatic: fallback payment method to use when an automatic payment fails.
Name of the issuer for the invoice. Defaults to the Organization name in Modern Treasury.
The internal account the invoice should be paid to.
When opening an invoice, whether to show the embedded payment UI, automatically create a payment or rely on manual payment from the recipient.
When payment_method is automatic: the date that the transaction resulting from the automatically created payment order is to be posted to the participants’ account.
When payment_method is automatic: payment_type on the automatically created payment order
When payment_method is automatic: receiving_account_id on the automatically created payment order
If true, the invoice will send email notifications to the invoice recipients about invoice status changes.
Emails in addition to the counterparty email to send invoice status notifications to. At least one email is required if notifications are enabled and the counterparty doesn't have an email.
The virtual account associated with an invoice. The virtual account routing and accounts numbers will be shown on the invoice in place of the internal account information.
The name of the recipient of the invoice. Leaving this value as null will fallback to using the counterparty's name.
The email of the recipient of the invoice. Leaving this value as null will fallback to using the counterparty's email.
A list of days after the due date on which overdue reminder emails should be sent. Maximum length of 3, and maximum value of 365, email notifications must be enabled
Additional data represented as key-value pairs. Both the key and value must be strings. See Metadata.
Changes
No recorded changes to this operation across all 2 revisions of this API.