Northbridge’s supplemental report arrived three days after Melissa received the letter acknowledging the discrepancy.
It was accompanied by a cover note from the company’s counsel explaining that the review had identified differences between the authorization originally supplied by Nathan’s company and the version included in the completed Meridian package.
Melissa printed both versions and placed them side by side.
The original authorization allowed Northbridge to verify financial information connected to Nathan’s company and communicate with designated representatives about the financing.
The later version contained additional language concerning the administration of related obligations and the use of financial information in connection with repayment arrangements.
The wording was more expansive.
Neither document, however, expressly stated that Northbridge could take money from my share of the house proceeds without separate approval.
I read both versions carefully.
The original language looked familiar.
It was consistent with what I remembered Nathan telling me when he asked me to sign the paperwork.
The later version was different enough that I would have wanted an explanation before agreeing to it.
“Does this prove they changed it after I signed?” I asked.
Melissa shook her head.
“It proves the versions differ. We still need to establish when the change occurred, who authorized it, and whether you ever agreed to the revised wording.”
The report identified an account associated with Nathan’s company as the source of the original authorization file.
A later account associated with Evan Price’s administrative work had uploaded the expanded version into the financing package.
The system recorded the upload date, but it did not establish who drafted the additional language or whether anyone had received instructions to change it.
Northbridge said the expanded wording was intended to clarify the scope of the existing authorization rather than create a new financial obligation.
Melissa pointed to the sentence describing the company’s interpretation.
“That is their explanation,” she said. “It is not proof that you agreed to the broader language.”
She drafted a response asking Northbridge to identify the author of the revision, provide the source file, and disclose any communication discussing the change.
She also asked whether the expanded authorization had been shown to me before the guarantee package was finalized.
The request went to Northbridge’s counsel and to Nathan’s attorney.
Nathan responded through his lawyer that he had not personally drafted the revised wording.
He said he believed Evan had prepared the administrative documents using standard language and that he had assumed the final package accurately reflected the original authorization.
He did not deny reviewing the completed package.
He did not claim that he had compared every line.
He said he had trusted the administrator to prepare the documents correctly.
I read the response without feeling the relief I might once have expected.
Nathan’s explanation could be true in part.
He might not have written the changed language himself.
But he had known that the financing records were incomplete, had wanted the package completed quickly, and had reviewed the finished documents afterward.
He had been close enough to the process to know that questions remained.
Melissa reminded me that responsibility and intent were separate issues.
Even if Nathan had not created the expanded language, the records could still show that he had allowed a package containing it to move forward without verifying what it meant.
And even if Northbridge believed the revision merely clarified the original authorization, that belief did not establish that I had knowingly accepted it.
The following afternoon, Evan’s attorney supplied a short statement.
Evan said he had uploaded the revised authorization after receiving a request to complete the financing file.
He described the language as an administrative clarification based on the documents already available.
He denied intending to create additional personal liability for me.
The statement did not identify who had requested the revision.
It also did not explain why the revised language appeared in the final package after the original signature page had been uploaded.
Melissa sent another request.
This time, she asked for the email or internal instruction that led to the revision.
The answer came two days later.
Northbridge had located an email from Nathan to Evan sent shortly before the completed package was finalized.
Nathan wrote that the existing authorization might not be sufficient for the administrator’s proposed reconciliation process and asked Evan to make sure the file contained whatever wording Northbridge needed to finish the account.
He did not specify the exact language to use.
He did not explicitly instruct Evan to create a personal guarantee.
But the email made it harder to maintain that Nathan had no knowledge of a potential problem with the authorization.
Melissa read it twice.
“He knew the existing document might not be sufficient,” she said. “That is different from knowing exactly what Evan would add, but it is important.”
I felt the familiar anger rise.
Nathan had repeatedly told me that the documents were routine.
Now the records showed that he had questioned whether the authorization was sufficient before asking Evan to complete the file.
Why had he not told me?
Why had he not asked me to review the revised language?
Why had he allowed a broader version to become part of a package that Northbridge now relied on to support its claim?
Those were questions Nathan could no longer answer by saying that paperwork was complicated.
I asked Melissa whether the email meant Northbridge had no basis for pursuing me.
“Not by itself,” she said. “The enforceability question depends on the applicable law, the complete documents, the circumstances of signing, and the evidence of what you agreed to. But it strengthens our argument that the final package cannot simply be treated as proof of informed consent.”
She explained that a genuine signature did not resolve every issue.
A signature could be authentic while the scope of the agreement remained disputed.
A document could be assembled from legitimate pages while its final wording differed from what a person had originally been shown.
And a company could possess a signed authorization without being entitled to interpret it as permission to redirect unrelated personal funds.
Our next request focused on the exact version of the guarantee that had existed when I supposedly signed.
Northbridge had already acknowledged that the signature page existed separately from the completed package.
Now we wanted the original file containing the signature page, its creation date, and any version of the guarantee that had been attached to it before the later appendix was added.
We also requested a comparison identifying when the personal liability language first appeared in the document set.
The company agreed to provide a further technical export.
While we waited, Melissa sent Northbridge a formal notice that I disputed the guarantee, the scope of the authorization, and the claimed balance.
She instructed them not to treat my silence or participation in the accounting review as acceptance of liability.
Northbridge acknowledged the notice.
It confirmed that the house proceeds would remain in the closing attorney’s trust account and that no further transfer would be attempted while the dispute was unresolved.
That assurance was important.
I had begun to understand that protecting the money and proving the guarantee invalid were separate tasks.
The proceeds were protected for now because the transfer had been challenged and the closing attorney had not released them.
The guarantee still needed to be evaluated.
And the accounting still needed to be reconciled.
Three days later, the technical export arrived.
It showed that the original authorization file had been created before the financing package was finalized.
The expanded version had been uploaded afterward.
The file history also showed that the completed guarantee package had been assembled from separate documents rather than signed as one complete electronic agreement.
The export did not establish whether I had been shown the original guarantee page during the earlier meeting.
It did not establish whether I had knowingly accepted personal liability.
But it showed that Northbridge’s current claim depended on a package assembled through a sequence of separate actions, some of which occurred after the printed execution date.
Melissa placed the export beside the email from Nathan.
“We now have a documented reason to question the sequence,” she said. “The next issue is whether anyone can establish what you actually saw and agreed to.”
I thought of the kitchen table, the stack of pages, and Nathan’s assurance that I was helping with routine financial verification.
I could not make my memory more precise by wishing for certainty.
But I could refuse to let someone else’s assumption become the final answer.
For the first time, I felt that I was no longer simply defending myself against a demand.
I was reconstructing how that demand had been created.
And the more carefully we reconstructed it, the less reasonable it seemed to treat the final package as an unquestionable record of what I had agreed to.
Click here to continue reading: PART 18: A Forgotten Message From Nathan Revealed He Had Promised Someone the House Proceeds Before Our Divorce Was Final
The Warning My Father Gave Me Before I Could Even Remove My Wedding Ring
Part 17 of 28
