AI backup capture for ABBYY FlexiCapture
Keep the FlexiCapture project you already run. Add one event handler that sends only the incomplete reads to WiseCHECK IQ and writes back only what the primary read left empty.
Last updated
WiseCHECK IQ connects to an existing ABBYY FlexiCapture 12 check project through one document event handler that runs after the document rules are checked. Complete, consistent reads never leave FlexiCapture. Incomplete ones are posted to WiseCHECK IQ over HTTPS, and the handler writes returned values only into empty fields, with a Status line the verifier can read.
Why add an AI backup to a working FlexiCapture project?
A tuned FlexiCapture check project is fast, cheap, deterministic and auditable on the checks it was built for. Nothing here proposes replacing it. The cost sits in the items it reads only partly: handwritten fields, stock with no FlexiLayout, degraded MICR bands. Each of those lands in the verification queue, where a person keys it by hand. WiseCHECK IQ reads exactly those items.
What changes in the project, and what doesn't?
| Before | With WiseCHECK IQ | |
|---|---|---|
| Machine-text capture | The primary and only path | Still primary. Unchanged, runs first, wins every tie |
| Handwritten fields | Empty, keyed by an operator | Filled by WiseCHECK IQ and flagged for the operator to confirm |
| Unread MICR characters | A verification task | Re-read, re-parsed by structure, and the routing number tested with its check digit |
| Unfamiliar stock | No FlexiLayout, no data | Read without a template |
| Validation | Your project rules | Your rules, plus WiseCHECK IQ's findings, added alongside |
| Who approves | A person | Still a person. Nothing is auto-approved because a model produced it |
Your document definitions, FlexiLayouts, stations, batch types and export stay as they are. You add one document event handler and one read-only Status field.
How does the event handler work?
The handler is a JScript document event handler for ABBYY FlexiCapture 12 on the event After document rules are checked, so it sees exactly what the primary read produced after your own rules have run.
- It tests the primary read. Does the routing number pass the ABA check digit? Are the account number, serial, date and amount present, and is the amount well formed? If yes, it writes MACHINE to the Status field and stops. No call is made.
- It sends the page. Otherwise it posts the page image to WiseCHECK IQ over HTTPS, authenticated with an API key, with a note of which fields came up short.
- It merges the reply. A returned value is written only into a field that is still empty. If FlexiCapture already holds a different value, nothing is overwritten and the field is named in an AI-CONFLICT status.
- It explains itself. The Status field records what was filled, the verdict and the findings behind it, so the verifier doesn't have to guess.
The reply comes back as plain text in FlexiCapture field names, one field per line, so the handler needs no JSON parser.
How does sending only exceptions control cost?
A complete machine read never leaves FlexiCapture, so it adds no model cost and no latency. The AI is called only for the items that would otherwise go to a person to key by hand. You pay for the tail of the run, not the run.
You also choose where the line sits. The default trigger is the set of checks above: an invalid routing number, or a missing account number, serial, date or amount. It can be tuned to your stock and volumes during a pilot.
What keeps the integration safe?
- Fail-open, never fail-dirty. If the service can't be reached, the handler writes AI-BACKUP ERROR and the primary read stands. A check run never stops because the AI backup is down.
- Additive only. A value is written only into an empty field.
- No silent disagreement. A conflict is named in the Status field and routed to a person.
- No auto-approval. Rule findings from the primary pass stay on the document, so an item the AI filled always reaches a verifier.
Where does the WiseCHECK IQ service run?
| Option | What it looks like |
|---|---|
| Hosted by WiseTREND | An HTTPS endpoint WiseTREND runs. Nothing to host; the handler calls it with an API key. |
| Your cloud tenancy | The service runs in your cloud subscription or data center, against your own AI service agreements. Check images stay inside your boundary. |
| On the FlexiCapture server | For on-premises projects the service sits on the FlexiCapture application server and is called over loopback. Only the outbound AI calls leave the machine. |
What does a pilot involve?
- Stand up the service in the place your documents are allowed to go.
- Add the handler and the Status field to one document definition, then publish the project.
- Run a batch of your own checks, ideally the ones that reach your verification queue today. We report on them item by item.
- Tune the trigger so the AI is called for the shortfalls that are worth a call on your stock.
We use ABBYY Vantage as well as FlexiCapture in client projects. If your check capture runs on Vantage, talk to us about connecting WiseCHECK IQ there.
Questions about WiseCHECK IQ
Answers written for buyers, operations teams, search engines and AI assistants.
Do I need to change my FlexiCapture document definitions?
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.
Why send only the exceptions to the AI?
Cost and control. A complete machine read is fast, cheap and deterministic, so it never leaves FlexiCapture and adds no model cost. The model is called only for the items that would otherwise be keyed by hand, which is where the verification cost of a check run sits.
Which FlexiCapture version does the integration support?
The handler is written for ABBYY FlexiCapture 12, as a JScript document event handler on the event After document rules are checked. Talk to us about other versions or about ABBYY Vantage.
Send us the checks that reach your verification queue
The handwritten ones, the bad scans, the stock you have no layout for. We'll run them through WiseCHECK IQ and show you, item by item, what it read, what it checked and why it decided what it did.