Vendor Bill Mapping Group

Use the Vendor Bill mapping group to map expense report header information on the OpenAir expense report record with vendor bill header information on the NetSuite vendor bill transaction record. The mapping group supports filters.

For reference information and best practice guidelines, review the following topics:

References

The following table gives reference information about the records and fields available for custom field mapping definition with links to the relevant reference material. See also Schema Reference Documentation.

NetSuite Record type [SOAP object]

OpenAir Record Type [table]

Mapping Group [Integration point]

Vendor Bill [VendorBill, TransactionSearch]

Schema: VendorBill (2020.1)|VendorBill (2023.1)

XSD: tranPurch (2020.1)|tranPurch (2023.1)

XSD (pullback): TransactionSearchRowBasicplatformCommon (2020.1)|platformCommon (2023.1)

Expense Report [envelope]

Data Dictionary: envelope

Vendor Bill

  • [EXPENSE_REP_TO_VENDORBILL]

  • Pullback row [NS_EXPENSE_REP_TO_OA_EXPENSE_REP]

Default and Custom Filters

By default, expense report records are exported from OpenAir to NetSuite if the following conditions are met:

  • The expense report is approved in OpenAir.

  • The expense report was not already exported — Envelope.exported is empty.

  • The NetSuite ID [netsuite_envelope_id] custom field is empty OR the Allow objects with a NetSuite ID to be exported during integration run box is checked on the OpenAir NetSuite Connector administration form. See Allow objects with a NetSuite ID to be exported during integration run.

  • The expense report must contain at least one receipt.

  • The Enable OpenAir expense reports to NetSuite vendor bill integration box is checked on the OpenAir NetSuite Connector administration form and the Export folders from this employee as NetSuite vendor bills [User.netsuite_export_envelope_to_vendorbill__c] box is checked on the employee record associated with the expense report in OpenAir. Otherwise, the Expense Report mapping group is used instead. See Expense Report Mapping Group.

Custom filters are supported for this mapping group. For more information about adding filter conditions, see Using Filters and Filter Definition.

Note:

Custom filters for the Expense Report and Vendor bill mapping group are the same. Use the Expense Report mapping group tab to set custom filters for both mapping groups.

Default Field Mappings

The following table describes the default field mapping definitions for the Vendor Bill mapping group tab.

NetSuite Field

Direction

OpenAir Field

Notes

VendorBill.custbody_oa_exp_report_internal_id

Arrow pointing right

Envelope.id

Visible and always active if the Verify expense report export box is checked on the OpenAir NetSuite Connector administration form. See Verify expense report export.

VendorBill.entity

Arrow pointing right

Looked up OpenAir field value

  • User.netsuite_vendor2_id__c for the employee with User.id equal to Envelope.user_id if the Employees (Vendors) import workflow is used in conjunction with the Vendors (Vendors) import workflow.

  • User.netsuite_vendor_id__c for the employee with User.id equal to Envelope.user_id if only the Employees (Vendors) import workflow to import vendors from NetSuite into OpenAir.

  • User.netsuite_vendor_parent_id__c for the employee with User.id equal to Envelope.user_id

The internal ID for the NetSuite vendor record corresponding to the employee who submitted the expense report in OpenAir, or the parent vendor record (if the Export folders from this employee to the NetSuite parent vendor [User.netsuite_expense_map_parent_vendor__c] box is checked on the employee record associated with the expense report in OpenAir).

VendorBill.tranDate

Arrow pointing right

Envelope.date

VendorBill.tranId

Arrow pointing right

Envelope.number

VendorBill.custbody_oa_expense_report_number

Arrow pointing right

Envelope.number

Not visible on mapping definition table

The Tracking # of the OpenAir expense report is stored in both the Exp. Rept. # [ExpenseReport.tranId] standard field and the OpenAir: Expense Report Number [ExpenseReport.custbody_oa_expense_report_number] custom field on the vendor bill in NetSuite.

VendorBill.custbody_oa_exp_approver_supervisor

Arrow pointing right

Looked up OpenAir field values

List of User.netsuite_user_id__c for the employees who approved the expense report (Approval.user_id) if the approval records are not associated with a project.

Information about expense report approvers (except for project approvals) is stored in the OpenAir Expense Report Approver — Supervisor [ ExpenseReport.custbody_oa_exp_approver_supervisor] custom field on the expense report in NetSuite (OpenAir subtab).

VendorBill.custbody_oa_exp_approver_project

Arrow pointing right

Looked up OpenAir field values

List of User.netsuite_user_id__c for the employees who approved the expense report (Approval.user_id) if the approval records are associated with a project.

Information about expense report approvers for project approvals is stored in the OpenAir Expense Report Approver — Project [ ExpenseReport.custbody_oa_exp_approver_project] custom field on the expense report in NetSuite (OpenAir subtab).

VendorBill.custbody_oa_expense_report_user

Arrow pointing right
  • User.netsuite_vendor2_id__c, if the Employees (Vendors) import workflow is used in conjunction with the Vendors (Vendors) import workflow.

  • User.netsuite_vendor_id__c, if only the Employees (Vendors) import workflow to import vendors from NetSuite into OpenAir.

The internal ID for the NetSuite vendor record corresponding to the employee who submitted the expense report in OpenAir.

VendorBill.memo

Arrow pointing right

Envelope.notes

VendorBill.currency

Arrow pointing right

Envelope.Currency

Visible only if the Multicurrency feature is enabled for your OpenAir account.

Multiple currency — By default, the currency of the expense report is set automatically to the currency on the employee or vendor record.

VendorBill.custbody_oa_gst_override

Arrow pointing right

Calculated sum of GST or HST amounts across all receipts in the expense report

Not visible on mapping definition table

When the Allow manual override of Canadian taxes on expense report export box is checked on the Expense Reports (Expense Reports) export workflow settings form, calculated sum of Goods and Services Tax (GST) or Harmonized Sales Tax (HST) across all expense lines is stored in the OpenAir: GST/HST Amount [custbody_oa_gst_override] custom field on the vendor bill in NetSuite. See Allow manual override of Canadian taxes on Expense report export.

VendorBill.custbody_oa_pst_override

Arrow pointing right

Calculated sum of PST amounts across all receipts in the expense report

Not visible on mapping definition table

When the Allow manual override of Canadian taxes on expense report export box is checked on the Expense Reports (Expense Reports) export workflow settings form, calculated sum of Provincial Sales Tax (PST) across all expense lines is stored in the OpenAir: PST Amount [custbody_oa_pst_override] custom field on the vendor bill in NetSuite. See Allow manual override of Canadian taxes on Expense report export.

Transaction.internalId

Arrow pointing right

Envelope.netsuite_envelope_id__c

Not visible on mapping definition table

[Pullback] When you export a new expense report record from OpenAir to NetSuite, OpenAir stores the internal ID of the NetSuite expense report or vendor bill in the NetSuite ID [netsuite_envelope_id] custom field.

Arrow pointing right

Envelope.exported

Not visible on mapping definition table

OpenAir adds a timestamp for the date and time the record was exported.

Additional Field Mappings

Important:

Review the following guidelines

  • You should contact your OpenAir Professional Services representative if you need to make changes to your integration configuration and field mapping definitions.

  • For advanced mapping usage and best practice guidelines, see Advanced Field Mapping Definition.

  • Familiarize yourself with the NetSuite and OpenAir technical documentation before attempting to set field mapping definitions using the advanced notation — See Schema Reference Documentation.

No specific guidelines