If you’re a Brainware user and you want to learn more about the verification stage, you’re in the right place! This blog and the demo video below will teach you the basics of Brainware Verifier.

Keep reading to get a step-by-step view of how we navigated Brainware verifier.

The Basics of Brainware Verifier

The Basics of Brainware Verifier

1. First, we went into Brainware Verifier. At the bottom of our screen among our various icons, we were able to see a key-shaped orange icon – and we clicked on that and signed in.
2. Know that once you’re in, if there’s a need for a human to take a look at anything, you’ll see items listed in 550s. In our example demo, the first one we saw listed needed us to check that the vendor ID within it was correct. When we entered it, we discovered that it was a “NO PO”. Usually, we can get the vendor’s name and address and go from there, but for this particular case, we didn’t have this one in our system. We ended up doing a vendor search, and found that the vendor in question did not show up in our vendor master, so we decided we’d need to update that a little later. In the meantime, we entered “Vendor Not Found” into the field “Invalid Reason.”
3. Next, we pressed enter, which took us to the next one. One nice feature of Brainware is it will highlight everything that you’re looking at – in this case, the invoice date was highlighted, so we knew we needed to check that the invoice date had been read by Brainware correctly. When we did that, the date looked good to me, but the issue was that there were two dates. To determine which date was valid, we made a note to double-check with the AP team, but in the meantime, we just chose a date knowing we could just update it later if this guess turned out to be wrong.
4. Next, we hit enter again, and the previous batch was good to go. Then, we clicked “yes” in the pop-up window, which took us to the next item, which showed that our PO number was highlighted, indicating that it doesn’t exist. So, we needed to go update the information in our ERP side of things. Aside from that, though, everything else looked good, so we selected our invalid reason as “Missing or Invalid PO” and we were good to go. Now, this batch is good to go too.
5. If you want to hop around from one item to another without going in order, you can do that by going back to your batch list. As far as the “State” column next to “Batch ID” goes, know that 800 means the item is already exported, 700 means that it’s in the process of exporting, and 550s like we mentioned in the beginning means that it requires human verification.

And that’s the basics of Brainware verifier.

Want to Expand your OnBase Knowledge?

Bookmark our Question Corner playlist on YouTube. Every other week, we add a new OnBase demo led by experts from the Naviant Customer Success Team. Each demo is 3-10 minutes long and answers questions frequently asked by OnBase users like you.

View Playlist

Want More Content Like This?

Subscribe to the Naviant Blog. Each Thursday, we’ll send you a recap of our latest info-packed blog so you can be among the first to access the latest trends and expert tips on workflow, intelligent automation, the cloud, and more.