Use the The table below to understand explains how the FlowAP conversion process determines and assigns the payment term to the converted bill.
XML File Payment Term Use Cases | NetSuite Vendor Record : Paymenter Term | Expected Result |
|---|---|---|
Payment term is not mapped in the FlowAP Template / Payment Term XML element is excluded from the XML | Empty | Empty |
Not Empty (e.g.: Net 30) | Payment term is sourced from the vendor record. (e.g.: Net 30) | |
Payment term XML element is included but Empty | Empty | Empty |
Not Empty (e.g.: Net 30) | Payment term is sourced from the vendor record. (e.g.: Net 30) | |
Payment term XML element is included and not Empty (e.g.: Net 30) | Empty | Payment term is sourced from the XML data. (e.g.: Net 30) |
Not Empty (e.g.: Net 30) | Payment term is sourced from the XML data. (e.g.: Net 30) | |
Payment term XML element is included and not Empty (e.g.: Net 15) | Empty | Payment term is sourced from the XML data. (e.g.: Net 30) |
Not Empty (e.g.: Net 30) | Payment term is sourced from the XML data. (e.g.: Net 30) | |
Payment term XML element is included and not Empty but invalid in NetSuite (e.g.: 1 month) | Empty | Empty |
Not Empty (e.g.: Net 30) | Payment term is sourced from the vendor record. (e.g.: Net 30) |
Related Setup Pages
Staria FlowAP Subsidiary Setup
...
Send an email to support@staria.com for questions or concerns regarding this topic.