On this page, you can setup how XML elements are mapped to NetSuite fields.
Note: Create a file cabinet folder for saving the PDF files.
Warning: Do not edit and save any of the following default templates that are included in the FlowAP SuiteApp.
Default FlowAP Template
Default FlowAP Template - Tax ID Lookup Only
Legacy FlowAP Template
If customizing the mapping for a specific use case, create a copy of the template and save it with a new name.
Navigate to FlowAP > FlowAP Configuration > Staria FlowAP Template.
View the default Staria FlowAP Template.
Hover over actions and click Make Copy.
Field name | Description |
Primary Information | |
Name | Enter a name for your FlowAP Template. |
Lookup Criteria | |
Vendor Lookup Criteria | This field should contain an array of JSON objects that would be used as criteria for searching the Vendor for the FlowAP Document. You can enter a maximum of 15 criteria and a minimum of 1. |
Item Lookup Criteria | This field should contain an array of JSON objects that would be used as criteria for searching the Item for the FlowAP Document. You can enter a maximum of 5 criteria and a minimum of 1. |
Mapping Templates | |
Transaction Mapping | Enter the mapping for the Transaction Header and Lines in a well-formed JSON object. |
Vendor Mapping | Enter the mapping for the Vendor in a well-formed JSON object |
Limitations
The FlowAP conversion only supports UBL 2.1 Invoice XML schema. The UBL 2.1 (Universal Business Language) standard provides a set of predefined codes for the
InvoiceTypeCode
element, which specifies the type of invoice being issued. The following are supportedInvoiceTypeCode
values:380 - Commercial invoice: The most common type of invoice used for general business transactions.
381 - Credit note: Used to correct or cancel a previously issued invoice.