<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Playing Games With the Date Next to the Signature</title>
	<atom:link href="http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/</link>
	<description></description>
	<lastBuildDate>Tue, 31 Jan 2012 01:23:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Jorge Mafud</title>
		<link>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/comment-page-1/#comment-91728</link>
		<dc:creator>Jorge Mafud</dc:creator>
		<pubDate>Tue, 09 Jun 2009 01:34:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/#comment-91728</guid>
		<description>Hello, as a Mexican lawyer I am truly amazed of the importance you guys in the US give to the backdating issue... being franc, backdating is a common practice in Mexico, in fact, it is not customary for drafters to include a &quot;date&quot; line below the signature of each party&#039;s representative... we usually just date the contract and that&#039;s it... the date the parties agree to use will be, for legal purposes, the date when rights and obligations are born for the parties... 

I used to work in the mexican branch of an american company and most of the mexican offices and managers couldn&#039;t understand all the big fuzz about the dates in the papers... 

I can almost be sure no one has ever been imprisoned for backdating or forward-dating in Mexico... 

Best Regards.

Jorge Mafud</description>
		<content:encoded><![CDATA[<p>Hello, as a Mexican lawyer I am truly amazed of the importance you guys in the US give to the backdating issue&#8230; being franc, backdating is a common practice in Mexico, in fact, it is not customary for drafters to include a &#8220;date&#8221; line below the signature of each party&#8217;s representative&#8230; we usually just date the contract and that&#8217;s it&#8230; the date the parties agree to use will be, for legal purposes, the date when rights and obligations are born for the parties&#8230; </p>
<p>I used to work in the mexican branch of an american company and most of the mexican offices and managers couldn&#8217;t understand all the big fuzz about the dates in the papers&#8230; </p>
<p>I can almost be sure no one has ever been imprisoned for backdating or forward-dating in Mexico&#8230; </p>
<p>Best Regards.</p>
<p>Jorge Mafud</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/comment-page-1/#comment-90987</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Fri, 29 May 2009 08:05:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/#comment-90987</guid>
		<description>Rick:
Sounds like what you refer to as &quot;backdating&quot; is not the backdating of actual signatures, but rather using an &quot;effective date&quot; as the date that contractual obligations begain.  If the signatures contain the actual date that the parties signed then it is unclear where the fraud would occur in the contract (of course if one party realized the revenue as of the effective date and not of the signature date, that would be an issue).</description>
		<content:encoded><![CDATA[<p>Rick:<br />
Sounds like what you refer to as &#8220;backdating&#8221; is not the backdating of actual signatures, but rather using an &#8220;effective date&#8221; as the date that contractual obligations begain.  If the signatures contain the actual date that the parties signed then it is unclear where the fraud would occur in the contract (of course if one party realized the revenue as of the effective date and not of the signature date, that would be an issue).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Santalesa</title>
		<link>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/comment-page-1/#comment-90976</link>
		<dc:creator>Rich Santalesa</dc:creator>
		<pubDate>Fri, 29 May 2009 04:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/#comment-90976</guid>
		<description>Ken:  Good points.  Backdating, as in my example, does conduct a legal fiction that the prior contract was in force throughout.  And the new MSA or amendment could recount reasons for the dating (and on occasion does), though in such circumstances each party is often chagrined that neither caught the expiration.  

However, your point as to potential third or non-party rights (e.g. subcontractors, etc) is a serious issue that must be carefully considered in any such practice, and backdating under such circumstances where non-party rights were curtailed or imperiled - even unintentionally - would rise to level of improper conduct and potential fraud. 

But where as in a typical service agreement with the contract solely between the signing parties the backdating serves to memorialize the actual intent and ongoing conduct of the parties (who were each working up until the discovery of the expiration as if the prior contract had been still valid).  In such cases &quot;backdating&quot; with the full knowledge and ascent of the parties for no &quot;beneficial&quot; gain other than to provide continuity and permit quick continuation/resumption of services (assuming of course no other issues/regulations/statutes apply) can not be said to raise to any level of misconduct.

Indeed, rather than evidence of active &quot;dissembling&quot; it&#039;s frequently merely a case of innocuous &quot;saving face&quot; on both sides - with the proviso that the &quot;effective as of&quot; date reflects the earlier &quot;back&quot; date, while the signature dates make clear when the Amendment/new contract was executed to provide needed disclosure. 

As the Backdating article I referenced earlier notes: &quot;backdating, even in its most benign form, can potentially mislead a court or some other third party into believing a document was executed on an earlier date. To mitigate this possibility, backdating should always be disclosed. Part III examines the impact of disclosure and analyzes two disclosure methods; namely, identifying the date the document was executed and utilizing “as of” dating.&quot;</description>
		<content:encoded><![CDATA[<p>Ken:  Good points.  Backdating, as in my example, does conduct a legal fiction that the prior contract was in force throughout.  And the new MSA or amendment could recount reasons for the dating (and on occasion does), though in such circumstances each party is often chagrined that neither caught the expiration.  </p>
<p>However, your point as to potential third or non-party rights (e.g. subcontractors, etc) is a serious issue that must be carefully considered in any such practice, and backdating under such circumstances where non-party rights were curtailed or imperiled &#8211; even unintentionally &#8211; would rise to level of improper conduct and potential fraud. </p>
<p>But where as in a typical service agreement with the contract solely between the signing parties the backdating serves to memorialize the actual intent and ongoing conduct of the parties (who were each working up until the discovery of the expiration as if the prior contract had been still valid).  In such cases &#8220;backdating&#8221; with the full knowledge and ascent of the parties for no &#8220;beneficial&#8221; gain other than to provide continuity and permit quick continuation/resumption of services (assuming of course no other issues/regulations/statutes apply) can not be said to raise to any level of misconduct.</p>
<p>Indeed, rather than evidence of active &#8220;dissembling&#8221; it&#8217;s frequently merely a case of innocuous &#8220;saving face&#8221; on both sides &#8211; with the proviso that the &#8220;effective as of&#8221; date reflects the earlier &#8220;back&#8221; date, while the signature dates make clear when the Amendment/new contract was executed to provide needed disclosure. </p>
<p>As the Backdating article I referenced earlier notes: &#8220;backdating, even in its most benign form, can potentially mislead a court or some other third party into believing a document was executed on an earlier date. To mitigate this possibility, backdating should always be disclosed. Part III examines the impact of disclosure and analyzes two disclosure methods; namely, identifying the date the document was executed and utilizing “as of” dating.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/comment-page-1/#comment-90967</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Fri, 29 May 2009 02:18:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/#comment-90967</guid>
		<description>Rich: I agree that &quot;fraudulent&quot; is a bit strong, because often enough no one is in a position to claim that they&#039;ve been harmed by backdating. But backdating takes liberties with the truth. Taking your example, the fact is that if an MSA has terminated, it&#039;s dead and gone and can&#039;t be extended. Instead, you need a new contract. It might be expedient to dissemble by backdating, but why not simply say in the new MSA exactly what happened? If you&#039;re unwilling to live with the gap, perhaps because the gap would give a nonparty rights that they otherwise wouldn&#039;t have, then backdating the new MSA would in fact be fraudulent. Ken</description>
		<content:encoded><![CDATA[<p>Rich: I agree that &#8220;fraudulent&#8221; is a bit strong, because often enough no one is in a position to claim that they&#8217;ve been harmed by backdating. But backdating takes liberties with the truth. Taking your example, the fact is that if an MSA has terminated, it&#8217;s dead and gone and can&#8217;t be extended. Instead, you need a new contract. It might be expedient to dissemble by backdating, but why not simply say in the new MSA exactly what happened? If you&#8217;re unwilling to live with the gap, perhaps because the gap would give a nonparty rights that they otherwise wouldn&#8217;t have, then backdating the new MSA would in fact be fraudulent. Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Santalesa</title>
		<link>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/comment-page-1/#comment-90960</link>
		<dc:creator>Rich Santalesa</dc:creator>
		<pubDate>Fri, 29 May 2009 00:45:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/#comment-90960</guid>
		<description>Art said &quot;Backdating a signature is essentially fraudulent unless you can somehow show that the agreement simply records a pre-existing oral contract (which is unlikely to be the case).&quot;  

I disagree. &quot;[B]ackdating is essentially fraudulent&quot; is not the cut-and-dry rule that seems implied.  There are good, valid and legal reasons for backdating contracts.  For example, and I&#039;m sure any corporate lawyer has encountered this more times than we&#039;d like to recount: many times companies working under a pre-existing MSA will &quot;discover&quot; suddenly that the MSA has expired months before and did not contain an automatic renewal.  In either doing an Amendment to the prior MSA or putting a new MSA in place the effective dating is generally set as the expiration date of the prior MSA which passed months before - for good reason to provide predictability and security to both sides.  No fraud is involved.  

Indeed in cleaning up my office today I came across the Aug 2008 issue of Business Lawyer, which contains an article &quot;Backdating&quot; available here on SSRN (http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1112845) that starts: 

&quot;Backdating is a much misunderstood and largely unexplored subject. *** To the layman, backdating connotes wrongdoing.  The propriety of backdating, however, depends upon its purpose and effect.  Every lawyer should be capable of distinguishing legitimate backdating from improper backdating.  Unfortunately, the dividing line is often far from clear.&quot;</description>
		<content:encoded><![CDATA[<p>Art said &#8220;Backdating a signature is essentially fraudulent unless you can somehow show that the agreement simply records a pre-existing oral contract (which is unlikely to be the case).&#8221;  </p>
<p>I disagree. &#8220;[B]ackdating is essentially fraudulent&#8221; is not the cut-and-dry rule that seems implied.  There are good, valid and legal reasons for backdating contracts.  For example, and I&#8217;m sure any corporate lawyer has encountered this more times than we&#8217;d like to recount: many times companies working under a pre-existing MSA will &#8220;discover&#8221; suddenly that the MSA has expired months before and did not contain an automatic renewal.  In either doing an Amendment to the prior MSA or putting a new MSA in place the effective dating is generally set as the expiration date of the prior MSA which passed months before &#8211; for good reason to provide predictability and security to both sides.  No fraud is involved.  </p>
<p>Indeed in cleaning up my office today I came across the Aug 2008 issue of Business Lawyer, which contains an article &#8220;Backdating&#8221; available here on SSRN (<a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1112845" rel="nofollow">http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1112845</a>) that starts: </p>
<p>&#8220;Backdating is a much misunderstood and largely unexplored subject. *** To the layman, backdating connotes wrongdoing.  The propriety of backdating, however, depends upon its purpose and effect.  Every lawyer should be capable of distinguishing legitimate backdating from improper backdating.  Unfortunately, the dividing line is often far from clear.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cynthia Sternberg</title>
		<link>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/comment-page-1/#comment-90790</link>
		<dc:creator>Cynthia Sternberg</dc:creator>
		<pubDate>Wed, 27 May 2009 15:53:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/#comment-90790</guid>
		<description>There is a practice none have mentioned. Having the first signing party send a PDF or fax of the signature page (for long distance this beats couriers which can sometimes take 5 days - even on overnight).  The final signing party then signs the pdf or fax copy.  Then once the originals arrive it is simply a matter of re-signing with the previously recorded date (keeping both sets of signatures in the archive file just-in-case).

I&#039;ve found that India, China and Japan will not use electronic signatures in any form.</description>
		<content:encoded><![CDATA[<p>There is a practice none have mentioned. Having the first signing party send a PDF or fax of the signature page (for long distance this beats couriers which can sometimes take 5 days &#8211; even on overnight).  The final signing party then signs the pdf or fax copy.  Then once the originals arrive it is simply a matter of re-signing with the previously recorded date (keeping both sets of signatures in the archive file just-in-case).</p>
<p>I&#8217;ve found that India, China and Japan will not use electronic signatures in any form.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason M. Lemkin</title>
		<link>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/comment-page-1/#comment-90683</link>
		<dc:creator>Jason M. Lemkin</dc:creator>
		<pubDate>Tue, 26 May 2009 19:37:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/#comment-90683</guid>
		<description>This is an interesting thread.  What we&#039;ve seen at EchoSign is that these issues - which are very important ones -- mostly wither away once you have a trusted third party that dates contracts.  For our customers, it&#039;s particular relevant for sales/revenue contracts where the date is 100% tied to revenue recognition.  Once the date is simply applied by the eletronic signature vendor, these debates, questions -- and in some cases, games -- simply end.

Interestingly, we&#039;ve seen that third party dating also changes another standard practice which is &quot;who signs first&quot;.  Traditionally, the party with power in the contract or NDA would sign last.  However, if the document is immutable there is no risk it will be modified by the first party, and especially if it&#039;s tied to revenue recognition, the &quot;big co&quot; tends to sign first, so that they can recognize revenue the second the customer signs, and not have any temporal gaps until countersignature that would delay rev rec.</description>
		<content:encoded><![CDATA[<p>This is an interesting thread.  What we&#8217;ve seen at EchoSign is that these issues &#8211; which are very important ones &#8212; mostly wither away once you have a trusted third party that dates contracts.  For our customers, it&#8217;s particular relevant for sales/revenue contracts where the date is 100% tied to revenue recognition.  Once the date is simply applied by the eletronic signature vendor, these debates, questions &#8212; and in some cases, games &#8212; simply end.</p>
<p>Interestingly, we&#8217;ve seen that third party dating also changes another standard practice which is &#8220;who signs first&#8221;.  Traditionally, the party with power in the contract or NDA would sign last.  However, if the document is immutable there is no risk it will be modified by the first party, and especially if it&#8217;s tied to revenue recognition, the &#8220;big co&#8221; tends to sign first, so that they can recognize revenue the second the customer signs, and not have any temporal gaps until countersignature that would delay rev rec.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art</title>
		<link>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/comment-page-1/#comment-90284</link>
		<dc:creator>Art</dc:creator>
		<pubDate>Fri, 22 May 2009 15:23:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/#comment-90284</guid>
		<description>I was thinking more in terms of legality, and having the tax authorities knocking on your door - but you&#039;re absolutely right, there is rarely a good reason for it.</description>
		<content:encoded><![CDATA[<p>I was thinking more in terms of legality, and having the tax authorities knocking on your door &#8211; but you&#8217;re absolutely right, there is rarely a good reason for it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/comment-page-1/#comment-90276</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Fri, 22 May 2009 12:57:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/#comment-90276</guid>
		<description>Art: I think that putting a future date next to your signature is a really bad idea. You&#039;re sending mixed signals, because the fact is that you&#039;re signing, dating, and returning the signature page now, not on that future date.

So if you want certain rights and obligations to kick in on some future date, ensure that the contract says as much and date your signature the date you sign.

If you don&#039;t want the contract to become a valid contract until that later date, don&#039;t return your signature until that date.

Ken</description>
		<content:encoded><![CDATA[<p>Art: I think that putting a future date next to your signature is a really bad idea. You&#8217;re sending mixed signals, because the fact is that you&#8217;re signing, dating, and returning the signature page now, not on that future date.</p>
<p>So if you want certain rights and obligations to kick in on some future date, ensure that the contract says as much and date your signature the date you sign.</p>
<p>If you don&#8217;t want the contract to become a valid contract until that later date, don&#8217;t return your signature until that date.</p>
<p>Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art</title>
		<link>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/comment-page-1/#comment-90275</link>
		<dc:creator>Art</dc:creator>
		<pubDate>Fri, 22 May 2009 12:42:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/#comment-90275</guid>
		<description>I think backdating and forward dating can be treated quite differently. Backdating a signature is essentially fraudulent unless you can somehow show that the agreement simply records a pre-existing oral contract (which is unlikely to be the case). I think Ken&#039;s example of signing and dating, then waiting, then returning the contract, is a form of backdating (albeit one that might be done innocently) as the terms were not agreed to until the contract was returned, and it is the date of agreement that matters, not when pen was put to paper.

Forward dating is less of an issue. If a party puts a future date on a signature and passes it to the other side, that shows that he wants his agreement to be considered to be made as of the future date - there is no contract until then, and the acceptance can be withdrawn in the meantime. A similar thing can be done with written board resolutions. If a party signs and, without communicating anything to the other side, waits a day or two, then dates as of the later date, that again presents no problems. 

I think the only issue with forward dating would be if a party sent its signature back on one date (i.e. you have actually formed the contract) and subsequently tried to write in a later date. I have never seen it happen, or proposed.

As for an undated signature, if the date is important I will date it myself - but never to a date before I saw it circulated on email.</description>
		<content:encoded><![CDATA[<p>I think backdating and forward dating can be treated quite differently. Backdating a signature is essentially fraudulent unless you can somehow show that the agreement simply records a pre-existing oral contract (which is unlikely to be the case). I think Ken&#8217;s example of signing and dating, then waiting, then returning the contract, is a form of backdating (albeit one that might be done innocently) as the terms were not agreed to until the contract was returned, and it is the date of agreement that matters, not when pen was put to paper.</p>
<p>Forward dating is less of an issue. If a party puts a future date on a signature and passes it to the other side, that shows that he wants his agreement to be considered to be made as of the future date &#8211; there is no contract until then, and the acceptance can be withdrawn in the meantime. A similar thing can be done with written board resolutions. If a party signs and, without communicating anything to the other side, waits a day or two, then dates as of the later date, that again presents no problems. </p>
<p>I think the only issue with forward dating would be if a party sent its signature back on one date (i.e. you have actually formed the contract) and subsequently tried to write in a later date. I have never seen it happen, or proposed.</p>
<p>As for an undated signature, if the date is important I will date it myself &#8211; but never to a date before I saw it circulated on email.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

