Capturancycapture assurance
Request a demo
Vendor form validation

Prove every vendor's forms are capture-ready — before they reach production.

Capturancy is a deterministic acceptance gate for the forms your vendors produce. It reads each submitted document pixel by pixel, checks it against your exact specification, and returns a pass or fail backed by evidence — so a misread field never becomes a corrupted capture run.

Request a demo See how it works Watch the 2-minute demo
DeterministicEvidence-backedPII-masked Per-vendor isolationDedicated instance
The problem

One wrong field can corrupt an entire capture run.

Before a form goes into production data capture, the vendor that produces it has to prove it matches spec — the right layout, the right values in the right places, readable barcodes, aligned registration. Get that wrong and it doesn't fail loudly. It fails quietly, thousands of records deep, as mis-scanned data.

01 Manual review doesn't scale

Eyeballing vendor test packets against a spec sheet is slow, and no two reviewers draw the line in exactly the same place.

02 Defects surface in production

A shifted field or an unreadable barcode passes review, then shows up as garbage data after go-live — when it's expensive to unwind.

03 Acceptance isn't defensible

"It looked fine" is not an audit trail. When a capture error is questioned, there's no objective record of what was checked.

04 The vendor loop is slow

Findings get written up by hand, emailed back and forth, and re-tested — stretching onboarding across weeks.

How it works

Define the spec once. Hold every submission to it.

Capturancy turns your acceptance criteria into an automated gate. The four steps run the same way every time — that's the point.

01 / SPEC

Define the specification

Author a master form: draw the field regions, preview what the reader sees, and set the expected value, blank, or N/A for each — including values that vary per vendor. Next year, carry the whole thing forward.

draw · OCR-preview · publish · carry forward
02 / SUBMIT

Vendors submit packets

Each vendor uploads its rendition through a scoped account and sees only its own results. No shared inbox, no cross-vendor visibility.

scoped · self-service
03 / VALIDATE

Deterministic validation

Every required region is read and compared — page identity, values, marks, barcodes, registration and ink — and decided by your rules, not a model's guess.

read · compare · decide
04 / RESOLVE

Evidence, decision, resolve

You get a pass or fail with masked evidence for every check. On a failure, Capturancy drafts a vendor notice to approve and send — or an authorized reviewer can accept a known vendor limitation, on the record.

evidence · notify · accept
Author once — then carry it forward.

When next year's form arrives, clone the whole version: the capture regions, the rules, and every scenario with its expected values come across as a new draft. Drop in next year's master, adjust only what actually moved, and publish. You never rebuild a form from scratch.

What it checks

Every part of the form, held to tolerance.

Each check is an explicit rule you define, with its own pass/fail outcome and reason code — nothing is inferred or hand-waved.

Page identity

Confirms the submission is the right form, in the right order, on the right page — not a blank or a stand-in.

reason · PAGE_MISMATCH

Field values

Exact or format match against the expected value — with vendor-specific values where a test differs by vendor.

reason · VALUE_MISMATCH

Checkboxes & marks

Detects whether a mark is present in a tightly defined zone — a check, an X, a negative sign — where one belongs.

reason · MARK_MISSING

Barcodes

Decodes 1D and PDF417 symbols and verifies the encoded fields — the payload most capture pipelines actually key on.

reason · BARCODE_UNREADABLE

Registration & ink

Measures how far target marks sit from where they should, and whether a defined zone actually carries ink within tolerance.

reason · REGISTRATION_OFF

Coverage

Confirms every required rule actually ran on every required page — a submission can't pass by skipping a check.

reason · COVERAGE_INCOMPLETE
Why deterministic

A verdict you can stand behind — not a probability.

The accept/reject decision is made by rules you define and can read. The same document produces the same result every time, and every result comes with the evidence behind it. That's what makes it usable in a compliance review — and what a machine-learning "document AI" can't promise.

  • Reproducible
    Same input, same verdict — no drift, no retraining, no surprises between runs.
  • Evidence for every check
    A masked image shows exactly what was read and where — not just a score.
  • Defensible
    An objective, auditable record of what passed, what failed, and why.
  • No black box
    Your rules decide acceptance. Nothing about the outcome is hidden inside a model.
Where AI fits

AI where it helps. Never where it decides.

Rules decide pass or fail. When a submission fails, Capturancy uses AI to draft a clear, plain-language notice to the vendor — built only from masked evidence — that a person reviews and sends. The correction loop gets faster; the decision stays yours.

The engine

Deterministic. Decides acceptance from your rules.

The assistant

Drafts the vendor notice. Approved by a human before it sends.

Overrides

Objective by default. Flexible when you decide.

Not every failure is a defect. A vendor may have a genuine limitation for one field on one test. An authorized reviewer can accept that specific failed check — with a required reason — so the submission passes. The deterministic result is never rewritten, so nothing is hidden and everything stays defensible.

PRESERVED

The check still fails

The deterministic result is kept exactly as it was — never faked or overwritten. The failure stays on the record.

ACCEPTED

The submission passes

A documented waiver turns it into an accepted result, with the reason — the known vendor limitation — recorded beside it.

AUDITED

Reversible & logged

Every waiver records who accepted it, when, and why — and can be revoked at any time, dropping the submission back to failed.

GATED

Highest level only

Only approver and admin roles can waive a check — the same tier that releases a vendor notice.

Built for control

We run it for you, on an instance that is yours alone.

Capturancy is delivered as a managed service: your own application instance and your own database, provisioned for your organization and reached at your own subdomain. Nothing for your team to install, patch, or keep running — and if your program requires the software inside your own environment, on-premise deployment is available on request.

  • Hosted & managed
    We provision, run, and update your instance, served over TLS at your own subdomain. On-premise deployment available on request.
  • PII masked throughout
    Sensitive values are reduced to what a reviewer needs — in the UI, the evidence, and the notices.
  • Per-vendor isolation
    Each vendor account is scoped to its own submissions — enforced on every read and write.
  • Roles & audit trail
    Admin, approver, reviewer, and vendor roles — with a recorded action for every decision.
  • Single tenant, not pooled
    Your submissions, evidence and audit history live in a database dedicated to your organization — never co-mingled with another customer's.
Who it's for

Any program that captures data from forms it doesn't print itself.

If an outside vendor produces the documents you scan, Capturancy is the gate between their output and your capture pipeline.

Tax & revenue agenciesVendor-produced tax forms, held to spec before filing season.
Government forms programsStandardized public forms across many print and software vendors.
Healthcare & claimsClaim and enrollment forms where a misread field is a denied claim.
Insurance carriersApplications and policy forms produced by agencies and third parties.
Financial servicesAccount and application forms with strict field-level requirements.
Print & scanning bureausValidate your own output before you hand it to the client.
Outcomes

What changes when acceptance is automatic and objective.

Defects caught before production, not after
Objective, consistent acceptance criteria
Faster vendor onboarding & approval
A defensible record for every decision
Protected data-capture accuracy
Less rework and reprocessing downstream
FAQ

Straight answers.

Does Capturancy use AI to decide pass or fail?
No. A deterministic rule engine makes every acceptance decision — the same input always yields the same result. AI is used only to draft the vendor failure notice from masked evidence, and a person reviews it before it's sent.
What if a check fails for a legitimate vendor limitation?
An approver or admin can accept that specific failed check as a known limitation, with a required reason — so the submission passes for your workflow. The deterministic result is never rewritten: the failure stays on the record, and every waiver is logged (who, when, why) and reversible. Rigor with an audit trail, not a rubber stamp.
Where does our data live?
On an instance provisioned for your organization alone — your own application and your own database, not a shared multi-tenant pool. Traffic is encrypted in transit with TLS, and sensitive values are masked in the interface, the evidence images, and the vendor notices. If your program requires the software to run inside your own environment instead, on-premise deployment is available on request.
What kinds of forms can it validate?
Any PDF form with a defined layout — tax returns, claims, enrollment and application forms, government forms. You author the specification once per form, including expected values, blanks, checkboxes, barcodes, and registration.
What happens when next year's version of the form comes out?
Carry the current version forward. Capturancy clones it into a new year as a fresh draft — the capture regions, the rules, and every scenario with its expected values come across intact. Upload next year's master at the same time, adjust only the fields that actually moved, and publish. You never rebuild a form from scratch, and it flags a changed page size or page count so any shifted regions get reviewed.
How do our vendors use it?
Each vendor gets a scoped account to upload its own test packets and see only its own results. Access is enforced on every request, so no vendor can see another's submissions.
Can expected values differ by vendor?
Yes. A field's expected value can vary per vendor — for example a test identifier that ends in a vendor's own code — so one specification covers many vendors without weakening the check.
How is it delivered?
As a managed service. We provision a dedicated instance for your organization, reachable at your own subdomain over TLS, and we run and update it — there is nothing for your team to install, patch, or operate. Updates reach your instance without an upgrade project on your side. For programs that require the software inside their own environment, on-premise deployment is available on request.
Request a demo

See it run on your own forms.

Tell us a little about the forms you validate and we'll set up a walkthrough — the pass/fail, the evidence for each check, and the drafted vendor notice. We'll follow up after your first message to arrange any sample documents.

Prefer to talk? Call 614-423-5213

Prefer to watch first? See Capturancy run on video — short product demonstrations on the ModernAxis Technologies channel.