JournalRelease NotesSupport
Guides
Log inSign up

Create Invoices in Bulk

A guide to bulk Invoice creation using CSV uploads.

Within Modern Treasury, you have the option to create individual Invoices or create Invoices in bulk with CSV uploads.

🚧

Case-sensitive values

Some values are case-sensitive and should match the guidance shown below.

🚧

Record limit

You can upload a maximum of 1,000 Invoices with one CSV. Each Invoice (grouped by invoice identifier) can have a maximum of 50 line items.

Create Invoices in bulk

  1. Login to Modern Treasury.

  2. Navigate to the Invoices Overview page.

  3. From the Create New dropdown menu, select Bulk Invoice to go to the Invoice bulk import page.

    • From here, you can click the Download Template CSV button to obtain a template CSV that includes all possible header fields. See the "Bulk Counterparty CSV Guidance" section in this guide for more information about each column.

  4. If you have a file ready, click Import Invoices to open the import modal.

  5. Click Upload file in the modal and select the CSV you wish to upload.

  6. Once uploaded, the tool maps your columns to the accepted fields needed to create the Invoices. Verify the mapped columns and click Continue.

  7. The tool will identify any cells that need to be reviewed by highlighting them in red. Make your edits as necessary.

  8. Once you are ready to submit, click on the Submit uploaded data button in the top right.

    1. If there are no errors, you will see a success modal. Click on View Bulk Import to open a new tab to the resulting bulk import.

    2. If there are data errors, you will see a submission failure message:

      The tool will highlight any cells with remaining errors in red along with an error message. Make your corrections and re-attempt the upload as necessary.

Bulk Invoices CSV Guidance

Each row in the upload CSV represents one invoice line item. Rows with the same invoice identifier (see below) will be created on the same invoice.

Invoice Attributes

General

AttributeRequiredData TypeDescription
invoice_identifierYesstringIdentifier to indicate which invoice the line item is being created for. Can be used to verify correct creation of invoice.
originating_account_idYesstringThe internal account the invoice should be paid to.
invoicer_emailNostringThe email in the invoicer's contact details displayed at the top of the invoice.
invoicer_phone_numberNostringThe phone number in the invoicer's contact details displayed at the top of the invoice.
invoicer_websiteNostringThe website in the invoicer's contact details displayed at the top of the invoice.
due_dateNodate

Format: YYYY-MM-DD		A date in the future when the invoice is due.
currencyNostringCurrency that the invoice is denominated in.
descriptionNostringAn optional free-form description of the invoice.
counterparty_idYesstringThe ID of the counterparty receiving the invoice.
recipient_nameNostringThe name of the recipient of the invoice. Leaving this value blank will fallback to using the counterparty's name.
recipient_emailNostringThe email of the recipient of the invoice. Leaving this value blank will fallback to using the counterparty's email.
auto_advanceNostringIf true, the invoice will progress to unpaid automatically upon creation and cannot be edited after entering that state.
payment_methodNostringWhen opening an invoice, whether to show the embedded payment UI, automatically create a payment, or rely on manual payment from the recipient.
Case sensitive - one of ui, automatic, or manual.
Default: manual
notifications_enabledNostringIf true, the invoice will send email notifications to the invoice recipients about invoice status changes.
notification_email_addressesNostringEmails (comma separated) 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.
metadataNostringAdditional data represented as key-value pairs separated by a | (pipe character).
Note: do not include special characters outside of ":" and "|"

Invoice Address Attributes

AttributeRequiredData TypeDescription
invoicer_address_line_1NostringStreet address of the invoice issuer.
invoicer_address_line_2NostringApartment, suite, or unit number of the invoice issuer.
invoicer_address_localityNostringCity of the invoice issuer.
invoicer_address_regionNostringState of the invoice issuer.
invoicer_address_postal_codeNostringPostal/region code of the invoice issuer.
invoicer_address_countryNostringCountry of the invoice issuer.
counterparty_billing_address_line_1NostringStreet address of the counterparty's billing address.
counterparty_billing_address_line_2NostringApartment, suite, or unit number of the counterparty's billing address.
counterparty_billing_address_localityNostringCity of the counterparty's billing address.
counterparty_billing_address_regionNostringState of the counterparty's billing address.
counterparty_billing_address_postal_codeNostringPostal/region code of the counterparty's billing address.
counterparty_billing_address_countryNostringCountry of the counterparty's billing address.
counterparty_shipping_address_line_1NostringStreet address of the counterparty's shipping address, where physical goods should be delivered.
counterparty_shipping_address_line_2NostringApartment, suite, or unit number of the counterparty's shipping address.
counterparty_shipping_address_localityNostringCity of the counterparty's shipping address.
counterparty_shipping_address_regionNostringState of the counterparty's shipping address.
counterparty_shipping_address_postal_codeNostringPostal/region code of the counterparty's shipping address.
counterparty_shipping_address_countryNostringCountry of the counterparty's shipping address.

Invoice Auto Payment Attributes

These attributes are only required if you want the invoice to automatically create a payment order upon issue.

AttributeRequiredData TypeDescription
fallback_payment_methodYes if payment_methodis automaticstringThe fallback payment method to use when an automatic payment fails. Case sensitive - one of ui, automatic, or manual.
payment_typeYes if payment_methodis automaticstringThe automatically created payment order's payment type. Case sensitive.
payment_effective_dateYes if payment_method is automaticdate

Format: YYYY-MM-DD		The date that the transaction resulting from the automatically created payment order is to be posted to the participants’ account.
receiving_account_idYes if payment_methodis automaticstringOne of the counterparty's bank account IDs.

Invoice Line Item Attributes

These attributes are used to create the line items for the invoice. Line items are grouped into invoices using the invoice_identifier (see general attributes above).

AttributeRequiredData TypeDescription
line_item_nameYesstringName of the line item, typically a product or SKU name.
line_item_descriptionNostringAn optional free-form description of the line item.
line_item_quantityYesintegerThe number of units of a product or service that this line item is for. Must be a whole number. Defaults to 1 if not provided.
line_item_unit_amountYes or line_item_decimal _unit_amountintegerThe cost per unit of the product or service that this line item is for specified in the invoice currency's smallest unit.
line_item_decimal_unit_amountYes or line_item _unit_amountstringThe cost per unit of the product or service that this line item is for specified invoice currency's smallest unit. Allows a decimal scale of up to 12.
line_item_directionYesstringEither debit or credit.
debit indicates that a client owes the business money and increases the invoice's total_amount due. credit has the opposite intention and effect. Case sensitive.
line_item_metadataNostringAdditional data represented as key-value pairs separated by a | (pipe character).
Note: do not include special characters outside of ":" and "|"

Updated 8 months ago