The Meridian application arrived in a password-protected file, accompanied by a letter explaining that Northbridge had retained the documents as part of its administration records.<\/p>\n
Melissa opened the file in her office while I sat beside her.<\/p>\n
The application included company financial statements, a schedule of outstanding obligations, a list of recent transfers, and a section asking whether any third-party funds had been received in connection with the debts being refinanced.<\/p>\n
The answer to that question was marked no.<\/p>\n
Melissa did not react immediately.<\/p>\n
She checked the date, then compared the application with the Harrow transfer confirmation.<\/p>\n
The advance had arrived before Nathan submitted the application.<\/p>\n
The money had been intended to help meet an obligation connected to Redfern.<\/p>\n
And Nathan had told Evan in writing that the allocation should remain pending until the Meridian terms were confirmed.<\/p>\n
\u201cCould there be a legitimate explanation for this answer?\u201d I asked.<\/p>\n
\u201cYes,\u201d Melissa said. \u201cThe question may have been interpreted narrowly, or the parties may have considered the advance separate from the listed obligations. We need the application instructions and any supporting correspondence.\u201d<\/p>\n
She emphasized that a discrepancy did not automatically establish fraud. The wording, the agreement\u2019s terms, and the parties\u2019 understanding would all matter.<\/p>\n
Still, the answer was significant.<\/p>\n
If Meridian had known about the Harrow advance, it might have assessed the company\u2019s obligations differently or required additional documentation before approving the financing.<\/p>\n
If the advance had already reduced the Redfern balance, the amount being refinanced might have needed adjustment.<\/p>\n
And if the guarantee was being used to support a balance calculated from incomplete information, the dispute over my signature could not be separated from the question of what I was allegedly guaranteeing.<\/p>\n
Melissa requested the full application instructions, any underwriting notes discussing the Redfern balance, and the correspondence between Nathan, Evan, and Meridian\u2019s representatives.<\/p>\n
She also requested confirmation of whether the application had been reviewed by a person or generated from a standard form completed by Nathan\u2019s company.<\/p>\n
The next day, Northbridge provided a second package.<\/p>\n
It contained a financial worksheet prepared before approval.<\/p>\n
The worksheet listed the Redfern obligation at a figure that appeared to include the balance before the Harrow payment had been fully reconciled.<\/p>\n
A handwritten notation in the scanned margin read, \u201cPending confirmation\u2014do not finalize.\u201d<\/p>\n
The notation had no visible initials.<\/p>\n
Melissa enlarged the image and checked its position on the page.<\/p>\n
\u201cWe need to know when this was added and by whom,\u201d she said.<\/p>\n
The final worksheet, however, contained no such notation.<\/p>\n
It carried the higher figure forward into the Meridian application.<\/p>\n
There was no separate line showing the Harrow advance as a credit.<\/p>\n
Melissa requested the original worksheet file and the document history.<\/p>\n
She also asked Northbridge to explain how the pending amount had been approved for use in the final application.<\/p>\n
Meanwhile, Nathan\u2019s attorney argued that the company had not intentionally misstated its obligations. The attorney said the Harrow payment had been subject to unresolved conditions and that the company could not know how it would ultimately be allocated when the application was prepared.<\/p>\n
That explanation was possible.<\/p>\n
But it raised another question.<\/p>\n
If Nathan genuinely believed the allocation was unresolved, why had the application answered no when asked whether third-party funds had been received in connection with the debts being refinanced?<\/p>\n
Melissa drafted a list of questions for Nathan.<\/p>\n
She asked who completed the application, who reviewed the financial worksheet, whether Nathan knew the Harrow transfer had been received, and why the transfer had not been disclosed.<\/p>\n
She also asked whether he had informed Meridian that Martin Cole was the beneficial party behind the advance.<\/p>\n
Nathan\u2019s written response arrived four days later.<\/p>\n
He said Evan had prepared most of the financing documents using information supplied by the company\u2019s accounting records. Nathan acknowledged that he knew Harrow had transferred funds, but said he believed the transaction was temporary and would be reconciled after Meridian approved the financing.<\/p>\n
He denied intending to mislead Meridian.<\/p>\n
He said he did not personally complete the third-party funds section and had assumed the answer was correct based on Evan\u2019s advice.<\/p>\n
Melissa placed the response beside the earlier emails.<\/p>\n
\u201cNotice what he admits,\u201d she said. \u201cHe knew the funds had arrived. He knew the allocation was pending. He says he relied on Evan for the final classification.\u201d<\/p>\n
\u201cAnd what does that mean for me?\u201d<\/p>\n
\u201cIt means we still have to establish whether the personal guarantee was knowingly given, what it covered, and whether the amount now being claimed is supported. His explanation about the application does not answer those questions.\u201d<\/p>\n
I read Nathan\u2019s response again.<\/p>\n
He had not said he never knew about the advance.<\/p>\n
He had not said the records were entirely outside his control.<\/p>\n
He had described a business decision that he knew was unresolved, then placed responsibility for the final wording on Evan.<\/p>\n
I wondered whether this was how he had treated every difficult decision during our marriage: not necessarily by inventing a complete lie, but by leaving out the part that would have forced me to ask harder questions.<\/p>\n
When I had asked why the company needed money, he told me business was unpredictable.<\/p>\n
When I had asked why the bank statements showed transfers I did not recognize, he said the accountant would sort them out.<\/p>\n
When he asked me to sign the paperwork, he told me it was routine.<\/p>\n
Each answer had sounded plausible in isolation.<\/p>\n
The problem was what the answers concealed when placed together.<\/p>\n
That afternoon, Melissa received a call from Meridian\u2019s outside records custodian.<\/p>\n
The custodian said an internal review had located a note from the original financing file indicating that the Redfern balance remained subject to confirmation.<\/p>\n
The note had been carried forward from an early worksheet but was not included in the final summary provided to Northbridge.<\/p>\n
Meridian had not yet determined whether the note affected its calculation of the advance or the current amount claimed.<\/p>\n
Melissa asked for a certified copy and the identity of the person who had approved the final summary.<\/p>\n
The custodian agreed to provide what the records allowed.<\/p>\n
I asked Melissa whether the discrepancy could invalidate the entire agreement.<\/p>\n
\u201cNot automatically,\u201d she said. \u201cAn accounting error does not necessarily void a contract. And even a serious error in the financing records would not, by itself, tell us whether you signed a valid guarantee.\u201d<\/p>\n
She explained that there were several distinct questions: whether the underlying company debt existed, whether the balance had been calculated correctly, whether Nathan\u2019s company had complied with its disclosure obligations, and whether I had knowingly agreed to personal liability.<\/p>\n
Those issues could overlap without having identical answers.<\/p>\n
I appreciated the precision, even though it meant we still had no single conclusion.<\/p>\n
For weeks, I had wanted someone to tell me that the guarantee was meaningless and that the house proceeds were unquestionably safe.<\/p>\n
Melissa refused to promise either outcome.<\/p>\n
Instead, she continued building the record.<\/p>\n
She requested the original signature page, the electronic execution log, the exact version of the guarantee allegedly presented to me, and evidence showing when the personal liability language had been made available to me.<\/p>\n
She also asked Northbridge to identify the person who had decided my limited authorization could support the proposed transfer.<\/p>\n
That request brought a new response from Evan.<\/p>\n
He sent a message through Northbridge\u2019s counsel saying that his role had been administrative and that he had relied on the documents provided by Nathan\u2019s company.<\/p>\n
He denied making any independent determination about whether I had knowingly accepted personal liability.<\/p>\n
Melissa read the message and looked at me.<\/p>\n
\u201cThat is important,\u201d she said. \u201cIf he says he relied on the documents, we need to know who assembled them and what he knew about the changes.\u201d<\/p>\n
The following morning, a document-history report arrived.<\/p>\n
It showed that the final guarantee package had been assembled from separate files at different times.<\/p>\n
The original signature page existed in an earlier document set.<\/p>\n
The later package included the expanded appendix and the revised authorization language.<\/p>\n
The system history showed who had uploaded and modified the files, but it could not establish who physically applied the signature or what I had been told when I signed.<\/p>\n
The records did not prove that anyone had forged my signature.<\/p>\n
They did show that the completed package was not simply a single document created and signed in one uninterrupted process.<\/p>\n
Melissa requested the underlying files and the email instructions associated with each version.<\/p>\n
Then she turned to me.<\/p>\n
\u201cWe need to find out whether you were ever shown the exact page that imposed personal liability,\u201d she said.<\/p>\n
I thought back to the afternoon Nathan had asked me to sign the paperwork.<\/p>\n
I remembered sitting at the kitchen table.<\/p>\n
I remembered him placing a stack of pages in front of me and pointing to several signature lines.<\/p>\n
I remembered asking whether the forms were connected to the company\u2019s routine financial verification.<\/p>\n
He had said yes.<\/p>\n
But I could not remember seeing a page with the words \u201cpersonal guarantee\u201d clearly presented as a separate obligation.<\/p>\n
I also could not swear that the page had not been among the documents.<\/p>\n
My memory was incomplete, and I refused to fill the gaps with certainty simply because I needed an answer.<\/p>\n
Melissa advised me to write down only what I actually remembered.<\/p>\n
I did.<\/p>\n
When I finished, she added the statement to our evidence file.<\/p>\n
The next piece of information arrived that evening.<\/p>\n
Meridian had identified an email from Nathan to Evan, sent shortly before the application was finalized.<\/p>\n
The subject line was \u201cKeep the package moving.\u201d<\/p>\n
The message said the company could not afford another delay and asked Evan to use the available records to complete the file, with any outstanding reconciliation issues addressed afterward.<\/p>\n
It did not mention my guarantee directly.<\/p>\n
It did, however, confirm that Nathan knew the financial information had unresolved issues when he wanted the financing completed.<\/p>\n
Melissa forwarded the email to Nathan\u2019s attorney and asked for an explanation.<\/p>\n
No response came that night.<\/p>\n
I sat at my kitchen table long after the house had gone quiet.<\/p>\n
I had spent years believing Nathan\u2019s confidence meant he knew what he was doing.<\/p>\n
Now I understood that confidence could also mean he was willing to move forward before anyone had answered the questions that mattered.<\/p>\n
And if he had treated the guarantee the same way, I needed to know whether my signature had been used to support a promise I never knowingly made.<\/p>\n
The Meridian application arrived in a password-protected file, accompanied by a letter explaining that Northbridge had retained the documents as part of its administration records. Melissa opened the file in … <\/p>\n","protected":false},"author":1,"featured_media":17500,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-17515","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-feel-one-story"],"_links":{"self":[{"href":"https:\/\/feelonestory.online\/index.php?rest_route=\/wp\/v2\/posts\/17515","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/feelonestory.online\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/feelonestory.online\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/feelonestory.online\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/feelonestory.online\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=17515"}],"version-history":[{"count":1,"href":"https:\/\/feelonestory.online\/index.php?rest_route=\/wp\/v2\/posts\/17515\/revisions"}],"predecessor-version":[{"id":17543,"href":"https:\/\/feelonestory.online\/index.php?rest_route=\/wp\/v2\/posts\/17515\/revisions\/17543"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/feelonestory.online\/index.php?rest_route=\/wp\/v2\/media\/17500"}],"wp:attachment":[{"href":"https:\/\/feelonestory.online\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=17515"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/feelonestory.online\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=17515"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/feelonestory.online\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=17515"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}