LendEasy/DocsLMS + Servicing·v1
Start integrating
Guides›AI Agents›The document agent

Docgest — the document agent

Docgest checks borrower documents, prepares safe working copies, and moves evidence requests forward through acceptance, review or replacement.

Docgest turns borrower documents into checked evidence that moves a case forward. It handles hardship proof, paystubs, identity documents, court filings and certificates: identifying what arrived, reading the required facts and linking the result to the step that requested it. Documents that clear the checks can advance the workflow automatically; those needing judgement reach a reviewer with the unresolved question attached.

A profile per document type

A document type is not just a label. Each one has a profile that names the facts that type must carry, where they are expected to appear, how confidently they have to be read, and the specialised checks that decide whether the document is worth anything to the case.

Document type What its profile checks beyond the basics
Doctor’s medical leave certificate The practice and the clinician who issued it, the leave and return dates against what the borrower said on the call, a signature, and how recently it was issued. Worked in full below.
Paystub Employer and pay period, net and gross consistency, that the period is recent enough to describe current income, and that the employer matches what the case was told.
Bank statement Account ownership against the borrower, the statement period, and that the closing balance and transaction lines agree.
Identity document Name and date of birth against the account, expiry, and document-number format for its issuing authority.
Court filing Court, case number and chapter, the filing date, and the debtor named against the borrower on the account.

Adding a type is adding a profile — the facts, the thresholds, the specialised checks — on top of intake, classification, sanitization, review and evidence handling that every type already shares.

Profiles are versioned. A case pins the profile version it opened under, so a certificate asked for in March is judged by the rules that were in force in March, not by the ones written since.

Check each fact against the document

Every extracted fact includes the phrase it came from. The platform locates that phrase on the page and checks that it supports the reported value. Missing support, a disagreement or an ambiguous date leaves the fact unresolved for review.

AI confidence cannot override a failed check. A name mismatch still requires attention even if the model reports a pass. A visual concern raised by the model also stays visible when the other checks pass, so the reviewer can assess possible tampering.

The result is called verified only after a person records issuer confirmation.

Worked in full: the medical leave certificate

On top of the shared intake, this profile runs its own checks:

  • Borrower name. Word order can differ: Chen, Maria Elena matches Maria Elena Chen, while Maria Chen is a partial match. The account name stays out of the model request.
  • Leave dates. Leave starts before the expected return, and both dates must be within seven days of those given on the call. A larger difference needs review.
  • Signature. A signature must be present and occupy a plausible area of the page; a scan marking most of the page as a signature does not satisfy the check.
  • Tampering. Signs of splicing, erasure or re-typing require attention regardless of confidence scores.
  • Reuse. The same file on another borrower’s case is flagged for review, without blocking on that fact alone.
  • Overshared detail. Unnecessary medical detail, such as a diagnosis, is flagged for careful handling without treating it as a borrower error.

Is this a real practice, and did they write it?

A certificate is only worth what its issuer is worth, so the practice and the clinician printed on it are checked rather than taken at face value.

The lookup answers what a directory can answer. It cannot tell you that this clinician signed this certificate on this date — for that, somebody contacts the practice, by telephone, secure portal, written correspondence or the directory itself, and records the method, the attempt and what they were told.

That confirmation is the only thing in the platform that can make an evidence result read verified. No screening outcome ever does, however confident, and no automated check does either. The lookup narrows what a person has to establish; it does not stand in for them.

The issuer directory is a commercial data source, and the agreement is between the lender and the provider. Until those credentials are in place the lookup is reported as not run rather than as passed, and the workspace shows which of the four questions went unanswered. See API availability for the connections that need an agreement first.

Protect medical details with a working copy

An authorised person can request short-lived, single-use access to the original for a permitted purpose. Each request is recorded, whether allowed or denied. Issuer verification is one such purpose: the person contacting the practice may need letterhead removed from the working copy.

A reviewer can correct a held working copy by removing more content, then have it rebuilt and checked again. If only the independent text reading remains inconclusive and the other safety checks have passed, the reviewer may approve the candidate. This can resolve a usable upload without asking the borrower to send it again.

Accept the evidence or route it for review

Automatic acceptance records the screening result as its reason. It cancels the unneeded intake review task, keeping the record clear that no person performed that review.

When judgement is needed, the reviewer receives the findings and the unresolved question. They can decide whether a partial name match or date discrepancy is acceptable; file-safety checks remain required. Four decisions determine the next step:

Decision What happens next
Confirm The reviewer records their judgement and any permitted field corrections. The certificate can satisfy the evidence request once the remaining checks and working copy are clear.
Request a replacement The borrower receives a new request explaining what the next certificate needs to address.
Escalate to a specialist The routine review ends and a specialist receives the unresolved question.
Reject The evidence request closes with the reason recorded on the case.

The screening and the person’s decision remain side by side, so a later reviewer can see what changed and who decided it.

Replace a certificate and revisit its offer

When the certificate itself needs replacing, the operator selects the reason: unreadable, incomplete, wrong document, out-of-date, or dates that do not cover the requested leave. The borrower gets a fresh upload invitation with an explanation of what is needed, and the old invitation stops working.

Replacing evidence also withdraws unsigned offers based on it. The case returns to the document step, so a borrower cannot accept terms while the certificate supporting them is being replaced. An agreement already accepted or being applied stays outside this replacement process.

Keep document work moving

Operations can see where uploads are waiting — scanning, screening, working-copy preparation or human review — and for how long. Temporary screening failures are retried within a limit; when screening cannot finish, the document becomes review work with the reason attached. A review-only mode lets the team handle certificates themselves while file-safety checks continue.

The lender’s retention policy also governs the sealed original. Once its retention period ends and a cleared working copy exists, the original can be disposed of while the working copy remains available for servicing. A retention hold pauses disposal, preserving evidence needed for an investigation or dispute.

Unified search across guides, recipes & the API referenceEsc