How White Listing and Black Listing work

If you haven't figured it out yet, the blue coding engine, as we call it, is the secret to easy categorization.  It's far more powerful than anyone else's method because it needs a little knowledge to use, and White listing and Black listing resolve a lot of problems.  

This is an advanced discussion, before you read it you should have read these:

https://cheqbook.zendesk.com/hc/en-us/articles/360002650074-How-the-Red-Yellow-Blue-and-Green-Color-Coded-Icons-make-Cheqbook-special

https://cheqbook.zendesk.com/hc/en-us/articles/223330927-How-the-Blue-Categorization-Engine-Works-Mapping-

Here's how these features work. 

White listing

Examples are often the best way to show everything.  Let's suppose you get the following transaction descriptions each time your payroll is paid out:

  • GUSTO NET XXXXXX XX-X4-18 6semjmqo912
  • GUSTO NET XXXXXX XX-X8-18 6semjmrbje0
  • GUSTO NET XXXXXX XX-X5-18 6semjms15e2
  • GUSTO NET XXXXXX XX-X0-18 6semjmsil0s

The blue engine works by learning which descriptions go with what payees.  However if the description is always a little different like these, then you have to manually categorize these every time they clear.

With White Listing you would save the term "Gusto net", and then each time a another one of these transactions are downloaded the remainder of the description will be stripped away.  All four of these would be replaced with the term "gusto net". 

Then, once the blue engine learned which payee this term goes with, all current and future ones would be properly categorized.

Black Listing

This method works exactly the opposite: instead of seeking out terms embedded and using only them, it seeks out an removes terms that get in the way. Blacklisting solves a completely different problem than White listing.  

Take for example the term "check". Many banks will use only this term in the description, with a check number to help you identify it.  

If you had 30 checks with this description, and you manually categorized the first one, then all of the other 29 checks would get categorized to this same payee and so would all future checks!

Obviously you don't want that.  Checks need to stay uncategorized, with a red indicator, so that you know they need your attention. 

Fortunately for you we've already listed the following common terms that cause this issue:

  • debit card
  • direct withdrawal
  • ach debit
  • pos purchase
  • card purchase
  • other subtractions
  • share draft
  • purchase
  • check
  • debit
  • credit
  • adjustment

However if your bank uses a term that isn't on this list, like "cleared check", you can add this term to blacklisting and the blue engine won't use it to categorize.

Advanced Black Listing

Sometimes the term you want to match isn't in the simple or blue map description, but in the longer bank description.  Again an example might be helpful:

Bank Description: Square Inc Merchant Deposit
Blue Map Description: deposit

Suppose you see this when you click more next to a transaction.  The blue map description provided by Yodlee is rather vague "deposit".  If you categorize with this you won't be able to differenciate your merchant (credit card) deposits from your check deposits.  

However if you add the term "deposit" to your black list, which in this case is the entire blue map description, Cheqbook will look to the Bank Description and take all the words that are not "deposit".  

Thus in this example the blue map description would become "Square Inc Merchant", and you'd be able to train the blue engine to categorize that properly.

This feature was added years before white listing, so you will probably find that white listing the term "square Inc merchant deposit" will be easier to understand and implement, but they both work.  

Helpful Hint

If you're trying to fix existing transactions that these lists would help with, then after making the list changes you need, read this FAQ and you'll be able to re-categorize them all!

https://cheqbook.zendesk.com/hc/en-us/articles/223332167-How-to-revert-a-transaction

 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk