Not detected
Inspect the required area before treating it as unsigned. A missed or unusable image can also produce no detected candidate.
BETASIGNATURE VALIDATIONS
Run the checks your document requires.
ChequeDB’s signature beta brings detection, positioning and verification into agreed document validations. Define what needs to be signed, which references apply and how your team handles a missing, unclear or uncertain result.
Forms · contracts · mandates · delivery notes · cheques
Document → signature evidenceILLUSTRATION
THE FOUR QUESTIONS
The two expected fields contain drawings. Reference comparison and your operational decision remain separate steps.
Synthetic drawings and example workflow. No upload, model inference or live validation is performed here.
DOCUMENT REQUIREMENTS
Begin with what a completed document means.
An agreement may require a customer signature and a countersignature. A mandate may require a signature in a specified field. Another form may need presence checking without reference comparison. State the requirements for each document workflow before interpreting the signature evidence.
During the beta evaluation, agree which validations apply and where each check runs. Define the expected pages and fields, the reference process, the conditions that require review and the person who owns the exception.
ILLUSTRATIVE WORKFLOW
An agreement with two required signature fields.
This synthetic worksheet shows checks and handling decisions to agree during evaluation. It does not specify production rule names or automatic actions.
Two detected regions do not, by themselves, confirm that the two required people signed. Field association and the correct references remain part of the workflow.
| Check to agree | Illustrative observation | Handling to agree |
|---|---|---|
| Required presence | No candidate found in the countersignature field | Inspect the field and resolve whether a signature or a clearer capture is needed |
| Expected position | A candidate is found outside the customer field | Review its relationship to the required field |
| Usable image | A stamp obscures part of the candidate | Follow the recapture or exception process |
| Reference availability | The customer’s authorised samples are unavailable | Resolve the reference gap before interpreting a comparison |
| Comparison review | Comparison evidence needs inspection | Assign the case to the agreed reviewer |
Keep the reason alongside the outcome.
A useful validation explains what was checked and what prevented the document from proceeding. A reference gap needs a different action from an unclear image or a comparison discrepancy.
Agree how your integration retains the source document, located region, reference association, applicable requirement and handling reason. When a person resolves the exception, your workflow should record the decision and its explanation. These are integration requirements to settle in the beta, not a promise of a particular record format.
Separate an unresolved case from a failed requirement.
Not usable for comparison
Resolve clipping, blur or obstruction through the agreed process. Image quality should not be disguised as a clear signature mismatch.
Reference unavailable
Make the missing reference explicit. Presence and positioning may still be useful while verification remains unresolved.
Comparison needs review
Keep the candidate and references available to the reviewer, with a clear reason for the handoff.
Give every exception an owner.
Choose who can request a replacement document, resolve a reference association and decide whether a case can proceed. Agree how decisions return to the system that manages the application, agreement or transaction.
Test those handoffs alongside the model results. A validation is useful when the team knows what to do next and can explain why the document took that path.
QUESTIONS & ANSWERS
Validation: practical questions.
Which validation checks are included in the beta?
Agree the supported checks and their ownership for your document workflow during evaluation. The beta covers signature detection, positioning, verification and running validations; exact rule inventory and integration details need to be confirmed for your use case.
Does a missing detection mean the document is unsigned?
Not automatically. A genuinely blank field, an unclear image and a missed detection need to be distinguished through the agreed checks and review process.
Does validation automatically approve the document?
The validation evidence feeds your operational process. Agree the decision rules, exception handling and review ownership for your application or transaction.
Is this PDF digital-signature validation?
This beta concerns handwritten signatures visible in scanned documents. Certificate-based PDF signatures involve separate certificate and document-integrity checks.
CHEQUEDB SIGNATURES · BETA
Start with your documents.
Define the checks that matter.
Discuss your document types, signature references and validation workflow with the ChequeDB team.