How Export Verification Supports a Post-Declaration Process
For current users, decisions as to which data is compared and which errors are displayed within ONESOURCE Export Verification were determined during the requirements-gathering phase of the software implementation. By the time the module goes “live,” rules engines are configured to identify pre-defined discrepancies between declaration data and source data stored within ONESOURCE or other external systems.
After the data sources (Global Classification, Purchase Order, Commercial Invoice, and Accounts Receivable files, etc.) and data elements to be compared are configured in the validation engine; the screens within ONESOURCE Export Verification will display the required information.
After declarations are received from the Filers, the declarations are run through the validation rules engine. Any discrepancies found during the validation process are then flagged in the system and shown on a variety of declaration levels (Header, Detail/Line, Parties and Fees). From there, error(s) can be assessed to determine whether any corrective action is required or recommended.
If corrective action is required or recommended to resolve known issues, declarations can be corrected either internally by the User or after the discrepancies are communicated externally with the Filer.
This help starts with an introduction to ONESOURCE Export Verification followed by instructions for using the application to support the company’s post-declaration review process.
Related Content
-
Export Verification
Format:
Article