Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
typelist
printablefalse

...

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.

...

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

How does FlowAP Post unidentified items?

Use NetSuite expense items instead of expense lines

FlowAP Subsidiary Setup > USE EXPENSE ITEMS INSTEAD OF ACCOUNTS FOR EXPENSE LINES

Expense Item/Account Lookup Hierarchy

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

Inherit Purchase Order Lines with Variances

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)

Understanding the [STA] POST SINGLE BILL LINE preference

Vendor Preference: [STA] No Direct Bill

Will not allow a well-formed XML to create a stand-alone bill (Direct bill) if the PO Reference is empty.

https://staria.atlassian.net/wiki/spaces/SIS/pages/1193541651/Staria+FlowAP+Subsidiary+Setup#Flowsetup-whenbillnotfound

Vendor Preference: [STA] No Direct Credit

Will not allow a well-formed XML to create a stand-alone bill credit (Direct Credit) if the Bill Reference is empty.

https://staria.atlassian.net/wiki/spaces/SIS/pages/1193541651/Staria+FlowAP+Subsidiary+Setup#Flowsetup-whenPOnotfound

Define tax codes for each tax rate/percent parsed from the XML during conversion.

FlowAP Subsidiary Setup > TAX CODE TABLE

https://staria.atlassian.net/wiki/spaces/SIS/pages/1316683781/Hierarchy+Used+by+FlowAP+Conversion+When+Selecting+Tax+Codes+on+Vendor+Bill+Lines#Tax-Code-Hierarchy-for-Bill-Items

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.

  1. A fix is implemented for a bug affecting setup for subsidiaries setup where WHEN PO# NOT FOUND = Report Error. Subsidiaries with this setup were preventing stand-alone bills from being converted.

  1. For Post Single Bill Line - Expense Item, the rate is always set to 0 to cover discount items limitation. The amount is mapped from the XML. 'Transaction Total' added to the memo

...