How Entry Verification Supports a Post-Entry Process
For current users, decisions as to which data is compared and which errors are displayed within ONESOURCE Entry 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 entry data and source data stored within ONESOURCE.
After the data sources (Global Classification, Purchase Order, Commercial Invoice, Receipt and Accounts Payable files, etc.) and data elements to be compared are configured in the validation engine, the screens within ONESOURCE Entry Verification will display the required information.
After entries are received from the Customs Brokers (usually nightly), the entries are run through the validation rules engine. Any discrepancies found during the validation process are then flagged in the system and shown on the entry line level. 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, entries can be corrected either internally by the Customs Broker after the discrepancies are communicated and/or externally with Customs.
This manual starts with an introduction to ONESOURCE Entry Verification followed by instructions for using the application to support the company’s post-entry review process.
Related Content
-
Entry Verification Overview
Format:
Article