WiseCHECK IQ questions, answered

WiseCHECK IQ is WiseTREND's AI backup reader for check capture. ABBYY FlexiCapture stays the primary reader. When its read of a check is incomplete, WiseCHECK IQ reads the page, tests the MICR line, amounts, date, signature and fraud signals with deterministic rules, and returns the values with a verdict and the reasons for it. Nothing is auto-approved.

No. FlexiCapture stays the primary reader, with your document definitions, layouts, rules and export unchanged. WiseCHECK IQ is the backup reader for the checks FlexiCapture reads only partly.

No. WiseCHECK IQ returns field values, findings and a verdict to FlexiCapture or to the system that called it. It does not create X9.37 or X9.100-187 image cash letter files. That stays with your remote deposit or banking platform. An optional Check 21 integration is available: WiseTREND connects WiseCHECK IQ's verified data to the platform that builds those files, scoped per project.

Yes. Handwritten dates, payees and amounts are the main reason a check reaches the AI backup. The written amount is parsed from the words and compared with the numerals, and a disagreement between them is never auto-posted: it goes to a person.

Personal and business checks, payroll checks, cashier's and teller's checks, money orders, bill-payment drafts and rebate checks. They are not treated alike: on a payroll check the maker is the payroll service, a money order is signed by its purchaser, and the six-month staleness rule does not apply to a cashier's check.

Only the ones FlexiCapture reads incompletely: a routing number that fails the ABA check digit, an empty account number, serial, date or amount, or an amount that isn't a well-formed number. A complete read is marked MACHINE and never leaves FlexiCapture.

No. The FlexiCapture handler writes a returned value only into a field the primary read left empty. If both hold a value and they differ, nothing is overwritten. The Status field says AI-CONFLICT and names the field, so a verifier looks at it.

The primary read stands. The handler writes AI-BACKUP ERROR and the reason into the Status field, and the batch carries on. A check run never stops because the AI backup is down.

Not through FlexiCapture. The engine returns a verdict (AUTO, REVIEW or EXCEPTION) with its findings, but the handler leaves the rule findings from the primary pass on the document, so an item the AI filled always reaches a verifier.

PNG, JPG and TIFF images, and PDF files, of which the first page is read. The default limit is 25 MB per image.

Very little. You add one document event handler and one read-only Status field to the check document definition. Field names, FlexiLayouts, stations, batch types, rules and export stay as they are.

No. No rule consults a confidence score, the model's or anyone else's. Every rule is computed from the values read off the check and the routing directory, so the same record always gets the same findings, and each finding names the rule that raised it.

Under UCC 3-114 the words govern, so WiseCHECK IQ records the legal amount as the payable amount. It still never auto-posts that item. A disagreement between the courtesy and legal amounts is a classic sign of an altered check, so the item goes to a person.

The duplicate rules compare items processed together in a batch. The same routing, account and serial with the same amount is a duplicate; with a different amount it is flagged as a possible alteration. Matching against your deposit history is not built yet.

We haven't measured it yet. Accuracy needs a client's own keyed values to compare against, and we don't have that ground truth. What we have measured is a straight-through rate and how often two independent readers agreed. We'll publish an accuracy figure, with its denominator, once it exists.

The directory holds 19,010 routing numbers and is frozen at 2018-12-04, because the public mirror it is built from stopped updating then. So the check that a routing number belongs to the bank printed on the face is informational only for present-day items. Keeping it current needs a licensed feed.

Partly. Canadian CPA-006 transit numbers are parsed and the institution number is checked against a list of known institutions. CPA-006 has no check digit, so that is a membership test, weaker than the US ABA check, and the branch number is not validated. The finding says which test the item got.

The WiseCHECK IQ service log masks account numbers to the last four digits. Full values are returned only to the system that called the service, because that system needs them to post the payment.

The hosted WiseCHECK IQ engine runs on WiseTREND's servers and reads checks with Azure AI services (Document Intelligence and Azure OpenAI) under WiseTREND's account. It can also run in your own cloud tenancy or on the FlexiCapture server.

Not generally. The engine running behind FlexiCapture today reads each check once. The Council second reading is in development and is the direction the product is going. Talk to us if you want it for your checks.

At WiseTREND One Portal (my.wisetrend.com) with your organization's WiseTREND One Portal account. Access to WiseCHECK IQ is turned on per organization; if you don't see it after signing in, talk to us.

Pricing depends on volume and on how it is deployed. Because only the checks FlexiCapture reads incompletely reach the AI, most of a check run adds no model cost. Talk to us and we'll size it on your own checks.