BETASCANNED DOCUMENTS
Detect handwritten signatures, return their positions, compare them with authorised references and run agreed validations across scanned forms, agreements, mandates, delivery notes, claims documents and cheques.
Forms · contracts · mandates · delivery notes · cheques
THE FOUR QUESTIONS
Two drawn signature candidates appear on this fictional agreement. Their positions do not identify the signers.
Synthetic drawings and example workflow. No upload, model inference or live validation is performed here.
START WITH THE DOCUMENT
A document can contain several signature candidates without satisfying its requirements. Start with the pages and fields that should be signed, the expected roles and the action your team takes when evidence is missing or unclear.
Detection and positioning can support a presence check without reference samples. Verification adds a comparison against authorised samples for the intended signer. Two detected regions do not establish that two different people signed. Your document context supplies the relationship between a field, a role and a reference set.
SYNTHETIC WORKED EXAMPLE
Consider a fictional two-page application: an applicant field on page one and an authorisation field on page two. The sequence below illustrates an agreed workflow; it is not a beta inference result.
For a consent form, add the guardian or witness field only where your process requires it. For a standing-order or payroll mandate, establish which account or person supplies the authorised references. Agree these mappings during the beta evaluation.
| Stage | Evidence to consider | Operational next step |
|---|---|---|
| Find | A candidate appears in the applicant field; no candidate appears in the mandate field. | Keep the two page results separate. |
| Position | Each region is associated with its source page and expected field. | Check the mandate area in the original image. |
| Compare | An authorised applicant reference set is available. | Evaluate the visible applicant signature against those samples. |
| Validate | The application requires both fields to be signed. | Route the incomplete packet according to the team's policy; an applicant comparison does not resolve the missing mandate. |
DIFFERENT DOCUMENTS, DISTINCT CHECKS
A fictional agreement has customer and countersigner blocks on its final page. Locate each candidate, retain the relevant page context and use the references assigned to each expected role. If only one block contains a candidate, record that unresolved requirement separately from any comparison. The checks do not determine whether the agreement is legally enforceable.
A synthetic receipt contains a recipient field, a printed name and a warehouse stamp. Start by distinguishing a signature candidate from neighbouring marks. Presence may be the required check; comparison needs an authorised recipient reference source. Preserve uncertainty when the stamp covers the writing and follow the agreed review process.
A fictional claims packet includes separate claimant and assessor fields. Specify which pages are required, associate regions with those fields and compare only where eligible references exist. An unavailable assessor reference is a different condition from an absent signature or an unclear scan, with its own next step.
CHEQUES ARE ONE DOCUMENT FAMILY
For a synthetic cheque, check the drawer's expected signature area and compare with the authorised references associated with the account. If endorsements are part of your process, evaluate those regions separately. A useful front-side comparison does not resolve a missing back-side requirement.
Cheque amounts, dates, MICR and reconciliation remain separate processing tasks. Signature evidence contributes to the wider review; it does not independently authorise a payment.
PLAN YOUR BETA EVALUATION
Bring a list of document types, required fields, capture channels and available references to the evaluation discussion. Include layout changes, multiple pages, faint writing, overlapping stamps and incomplete packets. Use permissioned samples and agree how each case is labelled.
Measure each workflow separately. A strong result on one clean form should not become an assumption about delivery photos or a different agreement layout. Define who reviews unresolved cases and what evidence they need before deciding.
QUESTIONS & ANSWERS
Yes. Detection and positioning do not require a reference set. Verification compares a candidate with authorised reference samples, so that additional task needs an appropriate reference source.
No. A position locates a candidate on the page. Your document layout and supplied context associate a field with an expected role; comparison then uses the references for the intended signer. Ambiguous assignments need an agreed review path.
Start with the forms, agreements, mandates, delivery notes, claims documents or cheques you actually process. Agree specific layouts, capture conditions, input formats and required checks during the evaluation rather than assuming every variation is supported.
It supplies image-comparison evidence against authorised references. It does not independently prove identity, personal signing of that document or legal validity. Your operational review uses that evidence alongside the document's other requirements.
CHEQUEDB SIGNATURES · BETA
Discuss your document types, signature references and validation workflow with the ChequeDB team.