kkozak
Occasional Member - Level 1

Concur / NetSuite Connector Field Mapping

While working on building the Concur/ NetSuite connector for both expense and invoice I am now finding out that required fields are not mapable which is very disappointing and frustrating after spending all this time on a project.  The purpose of a connector is the eliminate manual work which is not the case with this connector. 

 

The following fields below do not currently map leaving no use for this integratation.   I highly reccomend any looking into this connector to do all your research first.  It sound like Concur is working on setting up more mappable fields, however, I will not recommend this to anyone until the basic fields that are in the system such as the ones listed below can be mapped.

  • Payment Terms, Invoice Approver, Invoice Owner, Default Expense Account, Amortization Schedule, Amortization Start Date

 

2 REPLIES 2
KevinD
Community Manager
Community Manager

@kkozak I passed your question on to a couple of colleagues that work with our connectors. I'm hoping they can shed some light. 


Thank you,
Kevin
SAP Concur Community Manager
Did this response answer your question? Be sure to select “Accept as Solution” so your fellow community members can be helped by it as well.
martinatoebe
SAP Concur Employee
SAP Concur Employee

Hello @kkozak,

Thank you for sharing your experience. This is genuinely useful feedback for the community, and I wanted to add some context that may help clarify what is available through the Concur Invoice APIs and where additional integration logic may be required.

 

Based on the API documentation, I would group the fields you mentioned into three categories:

  1. Available natively through the API
  2. Not exposed natively, but can potentially be handled through custom fields
  3. NetSuite-specific concepts that need to be derived or maintained outside Concur


Here is how I understand each field:

Payment Terms


Available natively, with mapping required.

PaymentTermsDays is a writable field on the Invoice v3 header, and payment terms information is also available on the Vendor record.

The main consideration is the difference in data models: Concur represents payment terms as a number of days, while NetSuite may expect a terms record or code such as "Net 30." In that case, the integration layer would need to translate between the two values, for example:

30 days → Net 30



References:


Invoice Owner


Available natively.

On invoice creation, the owner can be set using EmployeeLoginId. When retrieving invoices, ownership information is returned as OwnerLoginID / OwnerName through the Payment Request Digest API.

Because the field names differ between write and read operations, this can be easy to overlook when designing the mapping.

 


Reference:

Payment Request Digest v3


Invoice Approver


No Concur APIs expose this data.

The approval workflow is managed within Concur, but the approver identity is not exposed as a standard invoice field in the APIs referenced here. Approval status is available, but not necessarily the identity of the individual approver.

If the approver identity is required downstream in NetSuite, one possible workaround is to capture it in a custom invoice field and include that value in the integration.

 


Reference:

Payment Request v3


Amortization Schedule and Amortization Start Date


These are better treated as NetSuite-specific accounting attributes rather than native Concur invoice fields.


Because the accounting recognition schedule is ultimately managed in NetSuite, one approach would be to derive the amortization schedule there based on criteria such as expense type, vendor, or another accounting dimension, with the start date derived from an agreed business rule.

If these values need to originate upstream, another option would be to capture the required schedule and start-date information through custom fields in Concur and pass them through the integration.


Default Expense Account



This requires mapping at the appropriate accounting level.

Concur identifies the expense type at the invoice line level through fields such as ExpenseTypeCode. Vendor information can also provide defaults that may be useful when determining the appropriate downstream accounting treatment.

The integration can therefore translate the Concur expense type or vendor default into the corresponding NetSuite GL account rather than expecting a single invoice-header "Default Expense Account" field.



Reference:

Vendor v3.1


Custom fields

For NetSuite-required attributes that do not have a direct Concur equivalent, custom fields are likely the most practical extension mechanism.

The Payment Request API supports custom fields that can be used to carry integration-specific values. Where appropriate, those fields can also be associated with controlled lists, which helps keep the values consistent and makes downstream mapping more reliable. 

Reference:

Payment Request v3

 

Note: Custom fields need to be set up by an SAP Concur Administrator to be added to specific Forms & Fields. For more information on how to add custom fields to your SAP Concur forms and fields, please contact SAP Concur via the Support Portal. 

For completeness, the relevant Concur Invoice API references are:


I hope this provides some additional context and a clearer path forward. From an integration perspective, the key distinction is between data that Concur already exposes, data that requires translation, and NetSuite-specific data that needs to be derived or carried through custom fields.

Please advise if you have additional questions. 

Kind regards,

@kkozak

Martina T.
Customer Innovation Advisor
SAP Concur | Managed Integration & Automation Services