This worked case belongs to the loan document exception closure guide, which covers what to inventory before a document system consolidation. Here the job is to tell one hard case decision by decision.
What went wrong: a valid signature on a superseded amount (Illustrative)
Invented for this page. A fictional 410-person equipment finance lender is closing a loan to a fictional paving contractor. The package goes out on Monday morning: a promissory note, a security agreement and a personal guaranty, all at $2.4M.
On Monday afternoon credit approves a second paver. The loan system regenerates the note at $2.6M and sends it in a new envelope. The guaranty is not regenerated. On Tuesday morning the guarantor, working from the first envelope, signs the guaranty at $2.4M.
Nobody forged anything and the signature is genuine. The problem is sequence: the guaranty no longer matches the note it secures. That is why version history and signature timestamps matter more here than the final PDF.
Seven events, three systems, and the record each one left
| Step | When | Event or decision | Who | Record that captured it |
|---|---|---|---|---|
| 1 | Mon 9:10 | Closing package sent: note, security agreement, guaranty at $2.4M | Closing coordinator | Envelope 1 and document versions in the loan system |
| 2 | Mon 15:40 | Second paver approved; note regenerated at $2.6M in a new envelope; guaranty not regenerated | Credit officer | Credit approval and envelope 2 |
| 3 | Tue 8:05 | Guarantor signs the original guaranty at $2.4M | Guarantor | Recipient events on envelope 1 |
| 4 | Tue 10:30 | Pre-funding review flags the mismatch; exception opened; funding held | Closing team lead | Checklist item and exception log entry |
| 5 | Tue 11:00 | Guaranty regenerated at $2.6M and sent | Closing coordinator | Envelope 3, linked to the exception |
| 6 | Wed 14:20 | Guarantor signs the corrected guaranty | Guarantor | Recipient events on envelope 3 |
| 7 | Wed 16:00 | Exception closed with the envelope 3 reference; signed set filed | Closing team lead | Closed exception and imaging record |
Steps 3 and 4 are the heart of the case. A signature arrived after another document changed, and a reviewer decided to hold funding rather than accept it.
Why the superseded envelope is the most important record
Because it is the evidence of the problem. A consolidated file that keeps only the final signed set would show a guaranty at $2.6M signed on Wednesday, and nothing would explain why funding slipped a day.
The event history pins the sequence. According to Docusign, every completed transaction gets a certificate listing who did what and when, split into envelope details, recipient events and summary events. In this case the first certificate would place the guarantor's signature at 8:05 on Tuesday, hours after the regenerated note went out.
The completed document cannot be quietly edited. Docusign says completion produces a final PDF that is tamper-evident. So the lender could not alter the signed guaranty to $2.6M; it had to issue a fresh one, and the first signing stays on file beside the second.
The exception is tracked, not just fixed. Bank examiners expect this: the OCC handbook on loan portfolio risk treats identifying, approving and tracking exceptions, including documentation exceptions, as part of sound practice. Step 4 is identification and the hold decision; step 7 closes the tracked item with a reference to the cure.
Judgment is visible. The closing team lead could have treated the signed guaranty as good enough. The record shows they did not. That kind of decision is what exception handling data for AI agents describes, and how the keys join across systems is mapped in the records across systems page.
How to recognise a similar case at a client
Ask the lending operations head five questions. None requires opening a file.
- Do documents ever change after the package goes out? Amount changes, collateral additions and corrected borrower names are the usual triggers.
- Does the loan system keep every generated version, or only the latest? Only-latest systems lose the "before" side of the case.
- Does a pre-funding review compare documents against each other? Cases like this one are caught there, and that is where the exception is opened.
- Does each exception entry cite the loan number and the cure envelope? Without that link, the cure looks like an ordinary signature.
- Are completed envelopes and certificates kept, or only signed PDFs? For Docusign accounts, the bulk download guide explains what an account holds and what survives a cancellation.
Strong signals: a lender with several hundred closings a year, an exception log kept for years, more than one e-sign account after an acquisition, and a consolidation project under way. Periodic file reviews, covered in the commercial loan annual review checklist, often surface older exceptions too. Advisors who already work with SBA lenders will find related context on the SBA lender referral partner page.
What a partner notes, and what stays unknown
Write the pattern in plain words: "About 1,100 documentation exceptions a year; loan system keeps all generated versions since 2018; two e-sign accounts with certificates; lending operations head owns the exception log." Never ask for loan files, envelopes, certificates or borrower names. The referral brief template gives the fields, and the who can license decision tree identifies who to introduce.
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions.
Unknown until SourceX reviews it: what rights review concludes about borrower and guarantor information, what must be removed or de-identified, buyer interest and any price.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a client's lending team can describe a signature that arrived after another document changed, the hold it placed and the cure it recorded, register as a partner, check the lender against who qualifies and read the program terms before you introduce its lending operations head.