Bill Line Mapping Group

Use the Bill Line mapping group to export information on the product charges created automatically from purchase items and included on the invoice in SuiteProjects Pro to the corresponding billable line items listed on the Billable Items subtab on the NetSuite invoice.

This mapping group is used when the product charges are created from purchase items imported from NetSuite vendor bills into SuiteProjects Pro using the POs (Vendor Bills) import workflow and all the following condition are met.

The charge is a product charge (type P) that was created from a purchase item imported from a NetSuite vendor bill into SuiteProjects Pro using POs (Vendor Bills) import workflows. See POs (Vendor Bills) Import Workflow.
The Use Service item instead of Product item during invoices export for purchase charges box is NOT checked on the Invoices (Invoices) import workflow settings form. See Use Service item instead of Product item during invoices export for purchase charges
The Billable box is checked on the vendor bill line item in NetSuite and the NetSuite vendor bill line billable [netsuite_vb_billable] box is checked on the corresponding purchase item in SuiteProjects Pro.
The Disable vendor bill linkage on invoices in NetSuite integration box is NOT checked on the Invoices (Invoices) import workflow settings form. See Disable vendor bill linkage on invoices in NetSuite integration.

Otherwise, the Invoice Line mapping group is used to export information from product charges in SuiteProjects Pro to the corresponding line items listed on the Items subtab on the NetSuite invoice. See Invoice Line Mapping Group.

Tip:

You can use the Vendor Bill Line mapping group to include information from the original vendor bill line item in NetSuite that was imported into SuiteProjects Pro as purchase item on the invoice billable line item in NetSuite. See Vendor Bill Line Mapping Group

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 Field Mappings — Overview of default field mapping definitions including notes and best practice guidelines where relevant. Information exported by default includes
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 [`SOAP object`]	SuiteProjects Pro Record Type [`table`]	Mapping Group [`Integration point`]
Billable Line Item [`InvoiceItemCost`] Schema: InvoiceItemCost(2020.1)\|InvoiceItemCost(2023.1) XSD: tranSales (2020.1)\|tranSales (2023.1)	Charge [`slip`] Data Dictionary: slip	Bill Line [`INVOICE_BILLABLE_ITEM_LINE`]

NetSuite Record type [SOAP object]

SuiteProjects Pro Record Type [table]

Mapping Group [Integration point]

Billable Line Item [InvoiceItemCost]

Schema: InvoiceItemCost(2020.1)|InvoiceItemCost(2023.1)

XSD: tranSales (2020.1)|tranSales (2023.1)

Charge [slip]

Data Dictionary: slip

Bill Line [INVOICE_BILLABLE_ITEM_LINE]

Default Field Mappings

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

NetSuite Field	SuiteProjects Pro Field	Notes
`InvoiceItemCost.doc`	Looked up SuiteProjects Pro field value — extracted from `Purchase_item.netsuite_vendorbill_purchase_item_id` for the purchase item associated with the fulfillment record associated with the charge.	The internal ID of the vendor bill record and the vendor bill line item ID in NetSuite are stored in the NetSuite Vendor Bill ID `Purchase_item.netsuite_endorbill_purchase_item_id` custom field on the purchase item record in the format `<VendorBill.internalId> — <VendorBill.line>`. The vendor bill internal ID is extracted from this value.
`InvoiceItemCost.apply`	`="true"`	—
`InvoiceItemCost.line`	Looked up SuiteProjects Pro field value — extracted from `Purchase_item.netsuite_endorbill_purchase_item_id` for the purchase item associated with the fulfillment record associated with the charge.	The internal ID of the vendor bill record and the vendor bill line item ID in NetSuite are stored in the NetSuite Vendor Bill ID `Purchase_item.netsuite_endorbill_purchase_item_id` custom field on the purchase item record in the format `<VendorBill.internalId> — <VendorBill.line>`. The vendor bill internal ID is extracted from this value.
`InvoiceItemCost.cost`	`Slip.cost`	—

NetSuite Field

Direction

SuiteProjects Pro Field

Notes

InvoiceItemCost.doc

Looked up SuiteProjects Pro field value — extracted from Purchase_item.netsuite_vendorbill_purchase_item_id for the purchase item associated with the fulfillment record associated with the charge.

The internal ID of the vendor bill record and the vendor bill line item ID in NetSuite are stored in the NetSuite Vendor Bill ID Purchase_item.netsuite_endorbill_purchase_item_id custom field on the purchase item record in the format <VendorBill.internalId> — <VendorBill.line>. The vendor bill internal ID is extracted from this value.

InvoiceItemCost.apply

="true"

—

InvoiceItemCost.line

Looked up SuiteProjects Pro field value — extracted from Purchase_item.netsuite_endorbill_purchase_item_id for the purchase item associated with the fulfillment record associated with the charge.

InvoiceItemCost.cost

Slip.cost

—

Additional Field Mappings

Important:

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