How can I skip Human Validation if a field is sometimes not present?

[Craig_Bannerman1 (Craig Bannerman)]

Hi folks,

Bit of a strange one, we are automating an invoicing process.
Alot of the invoice suppliers are smaller companies so their invoices are not the greatest quality.

Main issue I am having, is that sometimes the same supplier will supply a Template that has VAT, then some that don’t have VAT.

The templates look very similar but the identifier for VAT will be gone, it will only display net & total; not a £0.00 with a VAT empty field.

Any ideas on how I could configure that if the rest of the fields have been picked up with high confidence, and no confidence with the VAT field; that it looks at a different taxonomy setup?

The taxonomy will be setup to have the VAT Field as it sometimes can appear.

Example of what it may look like:

Invoice Number: 1234
Net Amount: £100
VAT Amount: £20
Total Amount: £120

Invoice Number 5678
Net Amount: £100
Total Amount: £100

Hopefully that makes sense

[Anil_G (Anil Gorthi)]

@Craig_Bannerman1

two ways

1. Use a classifier and classify based on VAT present and not
2. Or else check the individual confidence levels and see if vat is zero ignore

cheers

[supermanPunch (Arpan)]

Hi @Craig_Bannerman1 ,

Maybe you could check the below post as well on identifying Missing or Empty field values extracted :

How to get give an error if any fields are missing in Pdf data extraction?

Hi @raju_alakuntla , We can use the Extraction Results from the Data Extraction Scope to Check if there are any Data Missing. First, Since you need to Check only some fields are Required, we can use a String Array variable, and assign all the field name values to it like below : requiredFields = {"Name","Address","ID"} requiredFields variable is an Array of String Type. Next, we assume extractionResults variable is the Output of Data Extraction Scope. Then Check if the Required Fields are m…

[Lekshmi_R]

Hi Craig,

Once extraction results are available(After data extraction scope activity), you can check if the field is missing or not using the below expression:
extractionResultvariable.ResultsDocument.Fields(IndexinTaxonomy).IsMissing
Make sure you replace the variables extractionResultvariable and IndexinTaxonomy accordingly.
Thanks!

[Ioana_Gligan]

Why is it not okay to just leave the field as Missing?

From the feedback we’ve gotten, for high volume use cases, it’s easier for human reviewers to view all fields all the time than to have some disappear every now and then…

So I would guess it depends - if you don’t want the user to see the field at all (you have other means to check that there should not be a VAT amount there), then you can delete it from the Taxonomy and from the Extraction Results for that document before you create the task. (make sure you are editing a COPY of the taxonomy object )

[Rodrigo_Silva]

Just use a try catch

Try
when field exists do this steps

catch
when field doesn’t exists do this steps

Also you can add a counter and logs to check if there is happening a lot or not.

Or before doing something in the fields just check what do you have after extraction and act based on that?