Process & Setup Overview
Contact your Nuvo Customer Success Manager to connect your ERP and AR information to Nuvo.
Set up the files that include relevant transaction and customer information from your ERP following our format outlined in Export Format & Files below.
Send a test files to your secure Nuvo SFTP. Nuvo will provide SFTP server credentials, including: Username, Password, Host, Sandbox Port and Production Port.
Send your test files to the Sandbox Port; the Nuvo team will test to make sure that your files. Work with your Nuvo Customer Success Manager to resolve any potential errors.
Send your initial sync with 36+ months of historical data to the Production Port of your secure Nuvo SFTP.
Set up a daily recurring sync that sends records that were created or modified in the last two (2) days to the Product Port of your secure Nuvo SFTP.
You're all set! Access AR information in Nuvo.
Generating the CSV File
File Format & Frequency Details
Each file needs a header row with the column names.
The column names must match exactly (including case).
There are a few columns that require data to be mapped to a certain set of values—these typically have an asterisk, and you'll see *💡 enum, values: under the table. Incoming data must be mapped to our values, otherwise the data will not be processed.
Please use the ISO 8601 date & time format: https://www.iso.org/iso-8601-date-and-time-format.html (YYYY-MM-DD) on all
timestamptzcolumnsNuvo will request an initial sync with the information outlined below in Export Format & Files that contains 36 months of data (ideally, all complete history would be shared).
This should include all transactional record types (invoices, sales order, etc), and all records for other attributes (customers, addresses, credit terms, etc).
After the initial sync of 36+ months of data, configure the sync to push the data files daily (if you'd prefer more or less often syncs between your ERP and Nuvo please coordinate with your CSM).
To ensure completeness, we recommend sending records that were created or modified within a window that is two times the frequency. For example, a daily sync (recommended) would include records that were created or modified in the last 2 days)
File Format & Frequency FAQ
What if I leave a cell/column blank vs. leaving the column out of the export altogether?
If a column is specified but the data is null, we treat the cell as if you're nullifying the data (and clears it out). If the column doesn't exist at all, we'll leave the data as is (no action will be taken).
Columns that cannot be left blank are key to the table—eg., the
stagecolumn in the Entity Statuses table identifies if a company is an active customer or a prospect.
What if I upload multiple versions of the same file in succession?
We will process each file in the order it was uploaded.
What are the acceptable delimiter types?
Commas
Will the file names below be the same with every sync?
Yes, the the file names must be per the specification.
What character encoding is supported?
We support UTF-8.
FAQ: Viewing the Data
What will affect the customer's credit utilization calculation percentage?
Just the invoices and the amounts remaining on them (not sales orders).
How will I know if there was a problem with importing my data?
There will be an error log detailing the issues.
Export Format & Files
Data Tables
Entity (Customer)
File name: customer.csv
Name | Type | Nullable? | Notes |
| string | Y | Name of customer |
| string | Y | Customer AP email |
| string | Y | Tax ID/EIN/etc. |
| string | N | ERP’s internal ID of customer |
| string | Y | ERP’s internal ID of the parent (if this is a subsidiary) |
| decimal | Y | Credit limit of customer |
| string | Y | id on payment term table |
| string | Y | ERP internal id(s) of any subsidiaries of this entity |
| string | Y | id of entity status table |
| string | Y | Human readable customer number in the ERP |
Address
File name: address.csv
Name | Type | Nullable? | Notes |
| string | Y | Human readable address ID |
| string | Y | Name on the address |
| string | Y | First line of address |
| string | Y | Second line of address |
| string | Y | Third line of address |
| string | Y | City |
| string | Y | State |
| string | Y | Zip Code |
| country* | Y | Country (Two letter code) |
| string | Y | Phone Number |
| string | Y | Complete address as string |
| string | N | ERP internal ID of address |
Credit Notes
File name: credit_notes.csv
Name | Type | Nullable? | Notes |
| string | Y | Human readable credit note number (eg the one given to customers) |
| timestamptz | Y | Date issued |
| string | Y | Memo text |
| decimal | Y | Total Credit Note amount |
| decimal | Y | Amount remaining |
| string | N | ERP internal ID of credit note |
| string | N | ERP’s internal ID of customer |
Payment Terms
File name: payment_terms.csv
Name | Type | Nullable? | Notes |
| string | Y | Human readable payment term or number assigned |
| string | N | Name of Payment Term |
| string | N | ERP internal ID of payment term |
Entity Statuses (Customer Statuses)
File name: entity_statuses.csv
Name | Type | Nullable? | Notes |
| string | Y | Description |
| string | Y | Name of customer state (eg. CRM stage) |
| decimal | Y | Probability that deal will close (often set in CRM) |
| erpentitystatusstage * | N | Customer status, please see enum values below |
| string | N | ERP internal ID of status |
*💡 enum, values: CUSTOMER, LEAD, PROSPECT
Invoices
File name: invoices.csv
Name | Type | Nullable? | Notes |
| string | Y | invoice number |
| timestamptz | Y | Date invoice was issued |
| timestamptz | Y | Date invoice is due |
| string | Y | Memo text |
| decimal | Y | Invoice total |
| decimal | Y | Amount remaining on invoice |
| string | N | ERP internal ID of invoice |
| string | N | ERP internal ID of customer |
| string | Y | Status of invoice. |
Payments
File name: payments.csv
Name | Type | Nullable? | Notes |
| string | Y | Human readable number for a given payment. |
| timestamptz | Y | Date of payment |
| string | Y | Memo text |
| decimal | Y | Payment total |
| decimal | Y | Amount remaining |
| string | N | ERP internal ID of payment |
| string | N | ERP internal ID of customer |
| string | Y | ID of payment method |
Sales Orders
File name: sales_orders.csv
Name | Type | Nullable? | Notes |
order_number | string | Y | Human readable number for a sales order |
date | timestamptz | Y | Date of sales order |
status | salesorderstatus * | Y | Status of sales order, enum, see values below |
memo | string | Y | Memo text |
id | string | N | ERP internal ID of sales order |
entity_id | string | N | ERP internal ID of customer |
*💡 enum, values: DRAFT, BILLABLE, BILLED, CANCELED
Relationship Tables
Entity ↔ Address
File name: relationship_entity_address.csv
Name | Type | Nullable? | Notes |
| string | N | ERP internal ID of customer |
| string | N | ERP internal ID of address |
| boolean | N | If the address is the default billing address |
| boolean | N | If the address is the default shipping address |
Invoice ↔ Credit Note
File name: relationship_invoice_credit_note.csv
Name | Type | Nullable? | Notes |
| string | N | ERP internal ID of invoice |
| string | N | ERP internal ID of credit note |
| decimal | Y | Amount applied towards invoice |
Invoice ↔ Payment
File name: relationship_invoice_payment.csv
Name | Type | Nullable? | Notes |
| string | N | ERP internal ID of an invoice |
| string | N | ERP internal ID of a payment |
| decimal | Y | Amount applied towards invoice |
Sales Order ↔ Invoice
File name: relationship_sales_order_invoice.csv
Name | Type | Nullable? |
|
| string | N | ERP internal ID of sales order |
| string | N | ERP internal ID of invoice |
