Following are the limitation noticed with Vertex integration:

• Use of TABLE value for company parameter XSL_TAX_INTERFACE is deprecated and replaced with INTRENAL for consistency.
• Existing data of SALES_TAX has to be revisited before and after upgrade. This table is enhanced to support multiple criteria.
• Current solution does not support Sales and Usage Tax calculation for multiple assets as part of Origination and Customer Servicing.
• OFSLL currently supports to capture only following three transactions for Sales and Usage Tax calculation - BILL/DUE, LATE FEE and PAYOFF QUOTE. This is not a finite list of transaction. Based on different implementation specification system can facilitate addition of multiple transactions. Any requirement of additional transaction should be requested to product team, based on analysis support will be provided.
• Existing use of Setup > Products > Contract > Itemizations > Taxable Indicator is depreciated and can rely on new Lease Origination Sales and Usage Tax Setup.
• As part of current release, OFSLL does not provide support for CASH basis of Sales and Usage Tax calculation.
• When uploading tax Exemptions Certificate to Vertex, OFSLL calls Vertex Create Customer service followed by Create Certificate. Due to any internal error if OFSLL is unable to complete Vertex Create Certificate request, OFSLL will enter into a dead lock mode and will try to call Create Customer followed by Create Certificate which will fail as customer already exist in Vertex. This has to be operationally handled based on messages in the error queue.
• Care should be taken to disable Calculate Tax tax button in Decision for Stream based Lease application.
• Vertex use Imposition codes to identify multiple tax rules that can be levied on application/account. OFSLL records all the tax details into single itemization/transaction amount. Split of tax details should be gathered outside the system using Vertex transactionId stored in SALES_USAGE_TAX_DETAILS [SUD_ID].
• Adjustment, Void, Charge off and Wave of tax balance based on parent transaction has to be handled manually.
• For manual transactions posted from User Interface/Web Service that are requesting for Vertex Tax update, a delay of 30 seconds is introduced to get response from Vertex. If response is received in the due time, transaction will be posted with Vertex tax data else transaction will be marked as Error and user is requested to repost the transaction based on Vertex interface availability.
• In current release, we are unable to support re-triggering of failed transaction during Vertex integration. Support will be added in future.
• Vertex Address cleansing is currently out of scope of this release. Address cleansing adapter has to be written to interact with Vertex and get source and destination address updated before using based OFSLL-Vertex integration.
• Sale and Usage Tax is not part of Bill/Due amount. Care should be taken to disable billed indicator Setup Products Contract Lease.
• Currently Vertex tax data is not getting updated in Lease Customer Service Account Details Statements [Tax Charges (+)]. This bug will be fixed in future release.
• Tax calculation support for API and Account On-boarding will be added in subsequent patch release.