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.

...

  1. Fixed an issue where a duplicate number error is flagged when using the same document number between a vendor bill and a vendor credit.

  2. Fixed an issue where vendor creation fails if the XML does not contain or has an invalid payment term.

  3. The following tax code lookup options now support 0% tax rates:

    • Vendor-subsidiary sublist tax code field.

    • Item tax schedule

  4. 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.

  5. Expected errors

    1. If multiple or no vendors are found then an audit trail will be created instead of getting an unexpected error.

TO DO:

Correlate completeness of this document with Krizia’s requests for additional documents in the Jira comments.

Limitations

Warning
  • 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 supported InvoiceTypeCode values:

    1. 380 - Commercial invoice: The most common type of invoice used for general business transactions.

    2. 381 - Credit note: Used to correct or cancel a previously issued invoice.