browse
On this page, we explain how to use the clickable PDF feature
Introduction
The clickable PDF feature allows the user to simply click and point so that a value from the PDF can be captured in a certain header field from the vendor bill. The system is able to capture a single value or a section of information on the PDF. When the user does capture additional data the system will automatically learn from the click and point behavior and will try to apply it to the next incoming vendor bill.
Please note that clickable PDF currently works on the header part of the bill only. Line level is excluded from this feature.
Capturing data
Data can be captured by first clicking on a Netsuite field that is located in the header from the bill and then you can click on the PDF.
Capturing a single value
To capture a single value the user must click on a part of the information on the PDF.
Capture a section of information
The system also allows the user to capture multiple values or a section of text. To start simply click on the start of the section where you would like to capture the value and from here you can resize the selection so it includes all the values that should be captured for the Netsuite field.
Point & Click auto-learning
The clickable PDF feature will learn from the user’s selection and will apply this automatically to the next incoming vendor bill from the same vendor. The Point & Click auto-learning behavior only works on “non-standard” fields.
This means that the standard captured and populated fields won’t be included in the learning algorithm. The fields that are excluded are:
- Subsidiary
- Vendor
- Reference Number/ Invoice number (Field ID: tranid)
- Amount
- Currency
- TAX
- Date
- Due Date
Trained data
On each vendor, the Scan & Capture SuiteApp can show the user the created trained field mappings. These trained field mappings can be found under the subtab “Scan & Capture” → “Scan & Capture Trained Field Mapping”. The overview shows to the user in which subsidiary the trained field mapping is active and which field it populates and from which vendor transaction it has been created. If a trained field mapping is no longer needed or creating an incorrect capture, the user can delete it manually by pressing Edit on the line -> Delete.
If a vendor bill has been deleted by the user, the trained field mapping will still exist and work on newly incoming vendor bills. The “created from transaction” will be empty at that point.