Payments (Invoice Payments) Import Field Mapping Definition
The Payments (Invoice Payments) import workflow includes one mapping group:
-
Invoice Payment [Integration point:
PAYMENT_TO_PAYMENT
] — See Invoice Payment Mapping Group.
Invoice Payment Mapping Group
Use the Invoice Payment mapping group to map information about payment records in SuiteProjects Pro with information about payments applied to invoice transaction records in NetSuite. The mapping group supports filters.
For reference information and best practice guidelines, review the following topics:
-
References — Overview of record types in SuiteProjects Pro and NetSuite with links to the relevant reference material for information about fields available for mapping.
-
Default and Custom Filters — Overview of default filters and how to modify the default behavior, and custom filters. Custom filters are supported for this mapping group.
-
Default Field Mappings — Overview of default field mapping definitions including notes and best practice guidelines where relevant. Information imported by default includes project name, associated customer, and start date. Filters are supported.
-
Additional Field Mappings — There are no specific guidelines for custom field mapping definitions in this mapping group.
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 [ |
SuiteProjects Pro Record Type [ |
Mapping Group [ |
---|---|---|
Customer Payment [ Schema: TransactionSearchRowBasic (2020.1)|TransactionSearchRowBasic (2023.1) XSD: |
Payment [ Data Dictionary: payment |
Invoice payment [ |
Default and Custom Filters
By default, applied customer payment records are imported from NetSuite into SuiteProjects Pro if there is an invoice record in SuiteProjects Pro matching the invoice record to which the customer payment was applied in NetSuite.
Custom filters are supported for this mapping group. For more information about adding filter conditions, see Using Filters and Filter Definition.
Default Field Mappings
The following table describes the default field mapping definitions for the Invoice Payment mapping group tab.
NetSuite Field |
D |
SuiteProjects Pro Field |
Notes |
---|---|---|---|
|
![]() |
|
When you import a new applied payment from NetSuite into SuiteProjects Pro, SuiteProjects Pro stores the internal ID of the NetSuite payment in the NetSuite Invoice Payment ID [ |
Looked up SuiteProjects Pro field value — |
![]() |
|
A customer payment can be applied to multiple invoices on the Apply subtab in NetSuite. Make sure you check only the box for the invoice corresponding to the SuiteProjects Pro invoice to which you want to apply the payment. |
|
![]() |
|
The date the customer payment was applied to the invoice in NetSuite. |
|
![]() |
|
The customer payment amount. |
|
![]() |
|
[Initial Only] By default, the following content is added to the Notes field on the payment record in SuiteProjects Pro: |
|
![]() |
|
Active and visible only if the Multicurrency feature is enabled for your SuiteProjects Pro account. Multiple currency — The Currency on the payment record in SuiteProjects Pro is set to the Currency on the customer payment transaction record in NetSuite. |
The integration updates automatically the SuiteProjects Pro invoice record corresponding to the NetSuite invoice transaction to which the customer payment is applied. The following information is updated:
-
Invoice.balance
— outstanding balance on the invoice.
Additional Field Mappings
Review the following guidelines
-
You should contact your SuiteProjects Pro 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 SuiteProjects Pro technical documentation before attempting to set field mapping definitions using the advanced notation — See Schema Reference Documentation.
No specific guidelines