Purpose
This article explains ERP integrations that may be possible for your organization.
Audience
This article is directed toward administrators who want to set up integrations between an ERP and U.S. Bank NextView™.
Export file (self-service)
The standard expense export produces a .csv file on a predetermined schedule or on demand, depending on your preference. This process is the most common way that you can extract data from NextView. Note that an expense export only exports approved and completed transactions from the system. If you want access to an accrual view of transactions or a list of pending or open transactions, go to “Transactions” and select “Export”.
The export feature allows you to choose existing fields in NextView (such as “Posting Date,” “Transaction Amount,” “Expense Description,” “GL Account,” or “Department”) to export in whatever column order you choose. You can rename these fields for the export to match a corresponding field in your ERP system. The following Table 1 lists examples.
Table 1. NextView field names and corresponding ERP field names
NextView field name | ERP field name |
External Account ID | GL Account |
Department ID | Cost Center |
First Name | FirstName |
Custom export file (technical consultant engagement)
Custom export files are files that you cannot produce using the standard expense export method detailed in the previous section. These require custom work by U.S. Bank technical resources and will have an associated cost. U.S. Bank collaborates with you to build a custom file configuration that is delivered to you in a format that will automatically upload to your ERP/GL. These files vary in complexity, and the bank starts the process by asking you to share a copy of what you currently upload to your ERP.
A technical consultant schedules a scoping call with you to review what you need and to present the system’s capabilities to meet your needs. The entire process may involve up to four weeks for you to receive a completed custom file.
Here are common examples of when you may need a custom file:
You need credit card and out-of-pocket expenses separated into two files.
There are specific fields that do not exist in NextView that you must include for a file to upload successfully to your ERP (for example a “Date File Generated” field with the timestamp for that date).
You need to combine any existing fields in NextView to form a GL string (for example, combine your “Account ID-Department ID” and your “Custom Field ID” fields into one).
QuickBooks Online (QBO) integration
NextView has a basic API integration built with QuickBooks Online, which allows you to sync data between the two systems.
Need help?
If you need help, contact the NextView support team:
Email support@nextviewplatform.com.
From the website or mobile app: Open the left navigation menu and select Chat with us.
Publish date: January 06, 2025
Last update: NA