Pre-Nuptial Agreements and Post-Nuptial Agreements are contracts between people who intend to marry or have already married, dealing with what should happen to assets in the event of a divorce.
They are often used if either person wishes to protect assets that they have built up before the marriage.
They are more commonly used now and involve couples from all ends of the financial spectrum as many may have children from previous relationships and would wish to ensure they can make a Will providing a degree of certainty for their beneficiaries.
Traditionally, Courts in England and Wales did not see Pre or Post-Nuptial Agreements as binding. Their existence was considered by the Courts but in circumstances where the Court felt it appropriate, they may not have effected the outcome of a financial settlement on divorce.
+ Read More
The case of Radmacher -v- Granatino changed this in 2010. The Supreme Court, in that case, upheld a Pre-Nuptial Agreement. The general principle to be taken from the case was that where there has been full and frank financial disclosure and both spouses have taken independent legal advice, it is likely that a Pre-Nuptial Agreement will be upheld.
This case does not mean that Pre or Post-Nuptial Agreements are all to be held as legally binding. In that particular case the assets were worth many millions. In circumstances where there are fewer assets, the needs of the spouses and any children may take precedence over the agreement if proper provision has not been made for them.
If however consideration is given to potential issues which might foreseeably arise and the agreement is reviewed at agreed intervals, a Post-Nuptial Agreement could update the original agreement to reflect changed circumstances and give the couple the certainty they sought at the outset.
To regulate your affairs on marriage or on remarriage. This can include agreeing how assets are to be dealt with during the marriage, on separation and divorce. One example is where a couple are engaged to be married. They had each been married previously and have children from those marriages and also assets such as property and savings. They may both agree that during their marriage they will keep their assets separate and in the event of separation they would retain their own assets for the benefit of themselves and their children in the future.
It is very important to consider a Pre-Nuptial Agreement well in advance of the intended date of marriage. Ideally, such an Agreement should be finalised and signed no less than 21 days before the wedding. We would suggest that advice should be taken on this issue at least 6 months before the date of the wedding which gives you both sufficient time to consider the terms of the Agreement and to take advice from solicitors.
If you have already married and want to provide for what should happen to your assets you can enter into a Post-Nuptial Agreement at any point.
There is no doubt that discussing what should happen in the event of separation can be difficult but it is important to consider whether it would be sensible to enter into a Pre-Nuptial Agreement. The outcome would be that, in the unfortunate occurrence of divorce, both spouses will have protected the assets that they had built up or acquired prior to the marriage, providing certainty for the couple and their wider family.
Provided you have both given full information about your finances and have taken advice from solicitors, it is likely that a Pre-Nuptial Agreement will be upheld by the Court. In some circumstances courts can vary the contents of such an Agreement if the marriage has been a long one and circumstances have changed significantly since marriage. Even in such circumstances the Agreement can be influential on the outcome. Provision can be built in for the Agreement to be reviewed.
There was no doubt the 2010 Supreme Court decision of Radmacher significantly changed the status of pre-marital agreements although it stopped short of making them automatically binding on parties. However, it did establish that under the right set of circumstances the court should give effect “to a nuptial agreement that is freely entered into by each party with a full appreciation of its implications unless in the circumstances prevailing it would not be fair to hold the parties to their agreement…” The upshot was that unless it was deemed wholly unfair to hold a party to the agreement, then the agreement should stand. In Radmacher, they applied this test and found that a properly executed pre-marital agreement was a decisive factor in reaching their decision.
Following on from Radmacher, a set of criteria developed to make clear what could be held as “freely entered into” and with “full appreciation of its implications”. The latter was achieved by ensuring both parties had the opportunity of taking legal advice, that each had provided full and frank disclosure. What was slightly less straightforward was establishing that the agreement was “freely entered into”. As a starting point, there should be no evidence of duress or misrepresentation. Equally that there is a requirement that any pre-nuptial agreement should be entered into at least 21 days before the marriage ceremony in order for it to be regarded valid. It remains good practice to ensure a longer period of time between signing and the ceremony but that it is not too long before as to potentially warrant the agreement being considered out of date.
This brings us to the case of S v H  which serves as a clear reminder that there remains very strict parameters in which a court will be willing to accept the validity of a pre-nuptial agreement and therefore its capability of being upheld or its terms recognised within a financial settlement imposed by a court.
S v H involved a couple who were both entering a second marriage. 5 days prior to their marriage they had an agreement drawn up by a foreign notary. Neither took independent legal advice. After their marriage broke down the wife (S) sought to rely on the Agreement. The husband (H) having gone bankrupt, sought to avoid the agreement being upheld as it would have severely restricted the financial support he could receive from S. The parties’ evidence was totally at odds as to their level of understanding of the agreement they signed. H said he was taken by surprise by the visit to the Notary and at being asked to evidence his assets. HHJ Booth considering the case, found the Agreement, not unsurprisingly to be invalid. Judge Booth highlighted that there was no formal process of disclosure, no legal advice taken or given and it was only signed 5 days before the wedding took place.
However, the Judge went on to make it clear that regardless, the agreement would not have met the husband’s needs in any event. As such, the agreement failed on all three fronts that the Supreme Court felt was required to uphold a valid agreement.
The parties were married just over 10 years which considering the length of marriage, they had time to re-evaluate the agreement and correct the defective original agreement by entering into a post nuptial agreement but for whatever reason never had referred to the document again until their divorce. It is always sensible to include a review provision and to ensure the parties keep their pre-nuptial arrangements under scrutiny so that, if necessary, any redrafting can take place to record specific changes or upon significant events such as a birth of a child, loss of work or disability. What S v H highlights very clearly is the need to not only ensure the formalities are followed when an agreement is executed in order for it to be held up as being valid, but that throughout the lifetime of the agreement, it is continually reviewed to ensure it remains useful in the event of divorce.
If you would like more advice on how to protect your assets either in the contemplation of marriage or possibly post marriage, please contact us on Ipswich 01473 213311 or Colchester 01206 584584 or email us [email protected], alternatively if you would prefer us to call you please visit our web site and click “Call Me Back”.
If you would like to know more about this process or feel this could be something you would benefit from, please contact us at [email protected] or telephone Ipswich 01473 213311 or Colchester 01206 584584, where we will be happy to speak with you.
Subscribe Now for Newsletter and Updates
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
|_zcsr_tmp||Zoho - This cookie is necessary for the login function on the website.|
|bcookie||2 years||This cookie is set by linkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page.|
|collect_chat_launcher_load||1 month||This cookie is set by the provider Collect.chat. This cookie is used for enabling the chat function on the website.|
|collect_chat_page_load||1 month||This cookie is set by the provider Collect.chat. This cookie is used for optimizing the chat-box functionality by recognising the user.|
|kerseys-_zldp||1 year||This cookie identifies the unique visitors for the website, www.kerseys.co.uk for Zoho Live Chat functionality.|
|kerseys-_zldt||1 day||This cookie identifies unique visits for a visitor in the website, www.kerseys.co.uk for Zoho Live Chat functionality.|
|lang||This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website.|
|lidc||1 day||This cookie is set by LinkedIn and used for routing.|
|ypsession||1 day||For Yumpu PDF viewer.|
|yumpu_slc||7 days||PDF viewer|
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
|_ga||2 years||This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.|
|_gat_UA-46814924-1||1 minute||This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites.|
|_gid||1 day||This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.|
|_hjAbsoluteSessionInProgress||30 minutes||This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.|
|_hjFirstSeen||30 minutes||This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.|
|_hjIncludedInPageviewSample||30 minutes||This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.|
|_hjTLDTest||session||When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.|
|vuid||2 years||This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website.|
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
|_fbp||3 months||This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.|
|AVPUID||1 year||imagazine.advertserve.com Used to identify the visitor across visits and devices. This allows the website to present the visitor with relevant advertisement - The service is provided by third party advertisement hubs, which facilitate real-time bidding for advertisers.|
|b3e783bb62||This cookie is set by the provider Zoho. This cookie is used for collecting information on user interaction with the web-campaign content. This cookie helps the website owners to promote products and events on the CRM-campaign-platform.|
|bscookie||2 years||This cookie is a browser ID cookie set by Linked share Buttons and ad tags.|
|fr||3 months||The cookie is set by Facebook to show relevant advertisments to the users and measure and improve the advertisements. The cookie also tracks the behavior of the user across the web on sites that have Facebook pixel or Facebook social plugin.|
|MUID||1 year 24 days||Used by Microsoft as a unique identifier. The cookie is set by embedded Microsoft scripts. The purpose of this cookie is to synchronize the ID across many different Microsoft domains to enable user tracking.|
|NID||6 months||This cookie is used to a profile based on user's interest and display personalized ads to the users.|
|test_cookie||15 minutes||This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies.|
|UserMatchHistory||1 month||Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences.|
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
|_hjid||1 year||This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.|
|AnalyticsSyncHistory||1 month||No description|
|cookielawinfo-checkbox-functional||1 year||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checkbox-others||1 year||No description|
|S||1 hour||No description|