Avoiding Arbitrary Edits

Avoid negative impacts to your AI

Ryan Goetz avatar
Written by Ryan Goetz
Updated over a week ago

What decreases efficiency and impairs the learning of my AI?

The #1 reason that the AI learns slowly - or even incorrectly(!) - is that predictions are changed by arbitrary edits.

Arbitrary edits are changing values to those not found on an invoice. By making these changes, you are confusing the AI as you're telling it the predictions are wrong, negatively affecting your automation efforts.

Common arbitrary edits include:

  • Adding text to predictions: Commonly happens to invoice numbers, by appending the invoice date or vendor acronym to the invoice number.

    E.g. "123456" to "Inv. 123456"

  • Changing the invoice date/ due date to a different value not found on the invoice. This may happen when clients wish invoices to be paid on a cash accrual basis.

  • Removing predicted fields: Commonly happens to Payment Terms, removing a predicted field tells the AI it was wrong.

  • Deleting predicted line items: If the amounts are correct, and creating new ones, instead of updating GL account/dimension coding to correct coding.

What do I do about Utility/Recurring Bills without an invoice number?

For invoices that do not have an invoice date listed, you should instead use the invoice date as the invoice number, specifically in the format of "mmddyyyy".
The "mmddyyyy" format that Vic.ai will predict when the AI doesn't detect an invoice number with high confidence.

E.g. "July 4, 2021" would be "07042021"

If there are several invoices for the same date and vendor, add an increment to the end of the invoice number like "07042021-1" , "07042021-2" and so on.

Did this answer your question?