| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
This is the list of available FlowAP templates. 3 default templates come with FlowAP upon installation.
| Note |
|---|
You must not edit the Default FlowAP Templates. Any changes made to the default template will be overridden during new version releases of FlowAP. To use a customized version of the FlowAP template, save a copy of the Default FlowAP Template. Apply your own lookup criteria and XML mapping to the new FlowAP Template; and assign it to the relevant Staria FlowAP Subsidiary Setup. |
...
Field | Validation / Automation Details | ||
|---|---|---|---|
Expense Line : Memo field | NetSuite expense lines created when conversion is unable to identify a NetSuite item for the invoice line. The memo field of the expense line will have the value: <taxpercent> | <vendorcode> - <itemname> Related article: How to customize the memo field value of expense lines created by FlowAP conversion | ||
Currency | The XML currency is always used.
| ||
Invoice Item Line : Quantity | The quantity is defaulted to 1 if there is no indicated quantity in the XML for an item line. | ||
Vendor : VAT |
| ||
Subsidiary : VAT |
| ||
All fields | After parsing the mapped fields and no value is found in the XML, the created JSON data from the XML will set the value as “STA_EMPTY“. | ||
Location | A hierarchy is implemented for determining the location to be set. | ||
Billing Address : Country | If the XML’s billing country is empty, the vendor record’s billing country will be used. | ||
Reference Number | Unique Transaction reference numbers are validated for each transaction type (vendor bill and vendor bill credit). The conversion will fail for duplicate transaction reference numbers.
|
Related FlowAP Subsidiary Setup Options
...
Use Case | Setup Options | Related Articles | ||||
|---|---|---|---|---|---|---|
Allow transaction creation to proceed even if the conversion was unable to find a matching NetSuite item for the vendor bill lines. The conversion will post unidentified items as expense lines. | FlowAP Subsidiary Setup > CREATE UNIDENTIFIED ITEMS AS EXPENSE | |||||
Use NetSuite expense items instead of expense lines | FlowAP Subsidiary Setup > USE EXPENSE ITEMS INSTEAD OF ACCOUNTS FOR EXPENSE LINES | |||||
Ignore XML line level data and allow NetSuite to copy the line level information from the related purchase order in NetSuite. The total payable amount of the bill will always be equal to the XML. The user responsible for the bill is expected to review the line details of the bill and make the necessary data entry to correct it for the total payable amount. | FlowAP Subsidiary Setup > INHERIT PO LINES FlowAP Subsidiary Setup > INHERIT PO LINES: DEFAULT TO 0 QUANTITY AND AMOUNT | |||||
Ignore the XML line level data and save a single transaction line in NetSuite transaction. | FlowAP Subsidiary Setup > POST SINGLE BILL LINE: USE PAYABLE AMOUNT (NO TAX) | Vendor Preference: [STA] No Direct Bill | Will
| |||
Do not allow a well-formed XML to create a stand-alone bill (Direct bill) if the PO Reference is empty. | Staria FlowAP Subsidiary Setup > WHEN BILL NOT FOUND | |||||
Vendor Preference: [STA] No Direct Credit | Will Do not allow a well-formed XML to create a stand-alone bill credit (Direct Credit) if the Bill Reference is empty. | Staria FlowAP Subsidiary Setup > WHEN PO# NOT FOUND | ||||
Do not allow stand alone transactions for a specific vendor. | Configure vendor preferences in the vendor record.
Configure the Vendor-specific preferences saved search in the FlowAP Subsidiary Setup > VENDOR-SPECIFIC PREFERENCES | |||||
Define tax codes for each tax rate/percent parsed from the XML during conversion. | FlowAP Subsidiary Setup > TAX CODE TABLE | Configure the conversion to either create a stand alone transaction or report an error whenever a referenced PO number or Bill reference number in the XML is not found. |
|
|
TO DO, MOVE to other pages:
...
Fixed an issue where a duplicate number error is flagged when using the same document number between a vendor bill and a vendor credit.
...
Fixed an issue where vendor creation fails if the XML does not contain or has an invalid payment term.
...
The following tax code lookup options now support 0% tax rates:
Vendor-subsidiary sublist tax code field.
Item tax schedule
...
Fixed an issue where the final tax code lookup hierarchy entry is using a Default tax code for the vendor’s billing country instead of the transaction’s subsidiary country.
Expected errors
...
Limitations
| Warning |
|---|
|