Signature detection
Find candidate handwritten signatures in scanned documents.
Explore detection →BETASIGNATURE DETECTION & VERIFICATION
Add signature checks to your document workflow. Locate handwriting on the page, compare it with authorised references and give reviewers the evidence they need to make a decision. Available in beta.
Forms · contracts · mandates · delivery notes · cheques
THE FOUR QUESTIONS
Check each signature region against the required fields and expected signer roles.
ONE DOCUMENT. FOUR CONNECTED CAPABILITIES.
Find candidate handwritten signatures in scanned documents.
Explore detection →Locate each region on its source page for highlighting and review.
Explore positioning →Compare a signature with authorised samples for the intended signer.
Explore reference comparison →Apply your document rules and route results to the right reviewer.
Explore validation →BEYOND CHEQUES
Use the beta with forms, agreements, mandates, delivery notes, claims documents and cheques. Choose the signature fields and comparison requirements for each workflow.
Check the signature fields required for an applicant, account holder or authorised signatory. Evaluate single-signer and multi-signer layouts.
Locate signatures on the relevant page and field. Give reviewers the context to check customer and countersigner requirements.
Find signatures in required areas before the document moves on. Add reference comparison where your process needs it.
Evaluate drawer signatures and endorsement areas. Use signature evidence alongside your existing cheque and transaction checks.
THE CASES THAT MATTER
Keep the detected signature connected to its source page. Review the full document, inspect the signature region and compare it with the authorised reference when one is available.
Faint ink, clipped strokes and overlapping stamps can make a signature difficult to compare. Include these cases in your evaluation and decide when your team should review the page or request a clearer copy.
DOCUMENT WORKFLOW
Review an account mandate requiring one account-holder signature. Locate the signature, compare it with authorised references and handle any unresolved checks in your workflow.
Detection, comparison and validation answer different questions. Keep their outcomes distinct and assign ownership of the final document decision within your operation. Visual similarity provides comparison evidence; it does not establish that a named person signed this document.
| Situation | Question to resolve | Example next action |
|---|---|---|
| No candidate in the required field | Is the field blank, or is the scan unusable? | Inspect the page or request a clearer copy. |
| Candidate visible; no authorised reference | Does this process need presence only or comparison? | Complete the presence check or obtain the right reference. |
| Candidate and reference available | What does the comparison support under the agreed policy? | Apply the comparison review criteria. |
| Candidate partly hidden by a stamp | Is enough writing visible for a useful comparison? | Review the full page or recapture. |
PLAN THE BETA
Choose representative document layouts, identify required signature fields and describe the capture conditions your team sees. If verification is in scope, explain how authorised samples are obtained and associated with the intended signer.
Agree the signature data contract, validation responsibilities and acceptance criteria before deciding what to automate. Measure candidate detection, region placement, reference comparison and review workload separately, using evaluation documents held apart from calibration data.
QUESTIONS & ANSWERS
Yes. ChequeDB Signatures is launching in beta for scanned documents generally, including forms, agreements, mandates, delivery notes, claims documents and cheques. Evaluate the specific layouts and capture conditions in your workflow.
No. Detection and positioning identify candidate regions in the submitted document image. Verification adds comparison with authorised samples for the intended signer.
Detection asks whether a region appears to contain a handwritten signature. Verification compares that writing with supplied references. Validation then applies the agreed document checks and handling rules.
It provides image-based comparison evidence. The reference process, image quality and operational review still matter. A scan does not record the original signing dynamics or independently prove who signed.
Request a beta evaluation through the ChequeDB team. Bring representative document types, your reference-signature process if comparison is required, and the decisions your workflow needs to make.
CHEQUEDB SIGNATURES · BETA
Discuss your document types, signature references and validation workflow with the ChequeDB team.