What are custom deal fields in ActiveCampaign. How can they improve your sales workflow. How do custom deal fields differ from custom contact fields. What are practical use cases for implementing custom deal fields.
Understanding Custom Deal Fields in ActiveCampaign
Custom deal fields in ActiveCampaign are powerful tools that allow you to capture and display additional information associated with specific deals directly on the deal card. These fields provide a centralized location for all deal-related data, making it easily accessible to team members for review, decision-making, and action-taking.
Custom deal fields can be used to collect various types of information, such as:
- Geographic region of the deal
- Sales enablement information (e.g., potential competitors)
- Revenue projection data (e.g., forecasted close date, expected revenue over time)
- Internal invoice or inventory numbers
- Deal source
- Reasons for winning or losing a deal
Custom Deal Fields vs. Custom Contact Fields: Key Differences
While both custom deal fields and custom contact fields allow for the collection of additional information, they serve different purposes within ActiveCampaign:
Custom Contact Fields:
- Associated with individual contacts
- Appear in the Personal Info tab of a contact’s profile page
- Used to store personal information (e.g., birthdate, travel preferences, fitness goals)
Custom Deal Fields:
- Associated with specific deals
- Visible on the deal card and in the Deal tab of a contact’s profile page
- Used to store deal-related information
Both types of custom fields share some common features:
- Can be used to create segments for targeted messaging
- Can be updated via automation
- Allow for building automations and sending campaigns based on specific field data
Implementing Custom Deal Fields: A Step-by-Step Guide
To implement custom deal fields effectively, follow these steps:
- Identify the additional information you need to capture for each deal
- Create custom deal fields in ActiveCampaign to store this information
- Set up corresponding custom contact fields if necessary
- Create forms to collect the required data from leads or customers
- Build automations to populate custom deal fields based on form submissions or other triggers
- Train your team on how to use and update custom deal fields
Use Case: Proactive Follow-up with Leads Using Geographic Data
One practical application of custom deal fields is optimizing sales outreach based on geographic location. Here’s how you can set this up:
1. Create Custom Fields
Start by creating a “Geography” custom deal field and a corresponding custom contact field to collect and store geographic region data.
2. Design a Lead Capture Form
Create a form on your website that includes the custom contact field for geographic region. This form will be used to collect information from new leads.
3. Build an Automation
Set up an automation that triggers when the form is submitted. This automation should:
- Create a new deal in your sales pipeline
- Copy the geographic region data from the contact field to the custom deal field
4. Utilize Advanced Search
With this setup in place, sales representatives can use ActiveCampaign’s Advanced Search feature to find contacts associated with deals in specific geographic regions, allowing for time-zone appropriate outreach.
Maximizing the Potential of Custom Deal Fields
To get the most out of custom deal fields in ActiveCampaign, consider the following strategies:
- Regularly review and update your custom deal fields to ensure they remain relevant to your sales process
- Use custom deal fields to create detailed reports and analytics on your sales pipeline
- Integrate custom deal field data into your lead scoring model to prioritize high-potential deals
- Leverage custom deal fields in automations to trigger specific actions based on deal characteristics
- Use custom deal fields to segment your deals for targeted follow-up campaigns
Overcoming Common Challenges with Custom Deal Fields
While custom deal fields offer numerous benefits, users may encounter some challenges. Here are some common issues and how to address them:
Data Consistency
Ensuring consistent data entry across your team can be challenging. To maintain data integrity:
- Provide clear guidelines on how to use each custom deal field
- Use dropdown menus or predefined options where possible to limit inconsistencies
- Regularly audit your data and clean up any inconsistencies
Field Overload
Too many custom deal fields can overwhelm users and lead to poor adoption. To avoid this:
- Only create fields that provide actionable insights or necessary information
- Regularly review your custom deal fields and remove any that are no longer useful
- Group related fields together to improve organization and usability
Integration with Other Systems
Ensuring custom deal field data syncs properly with other tools in your tech stack can be challenging. To address this:
- Use ActiveCampaign’s native integrations where possible
- For custom integrations, work with your development team to ensure proper data mapping
- Regularly test your integrations to catch and resolve any sync issues
Advanced Strategies for Custom Deal Fields
Once you’ve mastered the basics of custom deal fields, consider these advanced strategies to further enhance your sales process:
Dynamic Deal Scoring
Use custom deal fields to create a dynamic scoring system for your deals. This can help prioritize high-potential opportunities and allocate resources more effectively.
Automated Deal Updates
Set up automations that update custom deal fields based on specific triggers or actions. This can help keep your deal information current without manual intervention.
Custom Deal Stages
Use custom deal fields to create more nuanced deal stages that align with your specific sales process. This can provide a more accurate representation of your pipeline.
Predictive Analytics
Leverage the data in your custom deal fields to develop predictive models for deal outcomes, helping you forecast more accurately and identify potential roadblocks early.
Measuring the Impact of Custom Deal Fields
To ensure that your implementation of custom deal fields is delivering value, it’s important to measure their impact on your sales process. Here are some key metrics to consider:
- Deal velocity: Are deals moving through your pipeline faster with the additional information provided by custom fields?
- Win rate: Has your win rate improved since implementing custom deal fields?
- Data completeness: What percentage of your deals have all custom fields filled out?
- User adoption: How often are your sales team members updating and using custom deal fields?
- Forecasting accuracy: Has the additional data improved the accuracy of your sales forecasts?
Regularly reviewing these metrics can help you refine your use of custom deal fields and demonstrate their value to stakeholders.
Best Practices for Custom Deal Field Management
To maintain the effectiveness of your custom deal fields over time, consider the following best practices:
Regular Audits
Conduct periodic reviews of your custom deal fields to ensure they remain relevant and valuable. Remove or modify fields that are no longer serving their purpose.
User Training
Provide ongoing training to your sales team on the importance of custom deal fields and how to use them effectively. This can improve adoption and data quality.
Documentation
Maintain clear documentation on the purpose and usage of each custom deal field. This can serve as a reference for your team and help onboard new members.
Feedback Loop
Establish a process for collecting feedback from your sales team on the custom deal fields. They may have insights into new fields that could be valuable or existing fields that are no longer useful.
Data Validation
Implement data validation rules where possible to ensure the quality of data entered into custom deal fields. This can help prevent errors and maintain consistency.
By following these best practices, you can ensure that your custom deal fields continue to provide value and support your sales process effectively over time.
What are Custom Deal Fields? How to Add Custom Fields to Deals in ActiveCampaign
If you use—or are considering using—our CRM to manage your sales process or as a workflow management tool, you may find it valuable to start using custom deal fields.
This guide will help you understand custom deal fields and how they can positively impact your sales processes and workflows. Learn from three use cases, and get some strategic guidance around what you need to consider as you transition to custom deal fields.
What are custom deal fields?
Custom deal fields allow you to capture and view additional pieces of information associated with a particular deal, right there on the deal card. Like custom contact fields, you can define the fields and field types.
Custom deal fields help you keep all the information relevant to a deal in one place so it’s easily accessible, enabling you and other team members to easily review all the info, make decisions, and take action.
Use them to collect the information that’s most helpful to you, like a deal’s geographic region, sales enablement information such as which competitor a deal may be at risk of being lost to, or revenue projection data such as a forecasted close date, or the deal’s expected revenue over time.
What’s the difference between custom contact fields and custom deal fields?
Custom contact fields are associated with contacts and appear in the Personal Info tab of a contact’s profile page. Use custom contact fields to collect and store information you need about a contact, such as their birthdate, travel preferences, or fitness goals.
Custom deal fields are associated with deals. To view all custom deal field information for a deal, click on the deal card. You’ll be directed to the Deal tab of a contact’s profile page:
Use custom deal fields to collect and store information related to a deal, such as the source of the deal, internal invoice or inventory numbers, or the reason why the deal was won/lost.
Like custom contact fields, custom deal field data:
- Can be used to create segments so you can target the right contacts with the right message
- Can be updated via automation
- Allows you to build automations and send campaigns based on specific custom deal field data
Ready to see custom deal fields in action? Here are some use cases to help you get started.
Use Case #1: Proactive Follow-up with Leads
A custom field for a deal’s geographic region can help a proactive salesperson optimize their time. For example, if a salesperson located in Australia is up at the crack of dawn and wants to begin outreach to new deals, they can use custom deal field data to find deals located only within geographic regions where the time is currently within regular business hours.
Let’s back up a bit. Before the salesperson can conduct a search to find those deals, there is some setup work that needs to have been completed previously:
1) Create a Geography custom deal field to collect a deal’s geographic region.
An example of a custom deal field created to collect a deal’s geographic region.
(Click here to learn how to create a custom deal field.)
2) Create a Geography custom contact field to collect a deal’s geographic region in the form (see next step).
A custom contact field identical to the custom deal field above. In this example, we’ll use a form containing this custom contact field to collect geographic region data. Then, we’ll use an automation to update the custom deal field with this data.
(Click here to learn how to create a custom contact field.)
3) Create a form to collect deal information, including geographic data. The salesperson’s company has a form on their website that contacts can fill out to learn more about product offerings. The form includes the custom contact field that collects a contact’s geographic region.
Example of a form integrated with a sales company’s website to source and collect information from new leads.
4) Build an automation that creates a new deal whenever the form is submitted, and copies data from the Geography custom contact field on the form into the Geography custom deal field.
An “Update custom field” action configured to copy data from the “Geographic Region” contact field on the form to the “Geographic Region” deal field.
An automation triggered when a contact submits the form on the sales company’s website. Each time the form is submitted by a new contact, the automation creates a new deal in the company’s sales pipeline, then copies the geographic region data from the contact field on the form to the deal field within that deal.
(Click here for help adding and configuring an “Update custom field” action in an automation.)
Now, let’s return to our salesperson. With this setup in place, the salesperson can simply perform an Advanced Search to find all the contacts associated with deals located within a geographic region where the time is currently within regular business hours.
These will be the deals that they can call up right now.
To conduct an Advanced Search, the salesperson navigates to Contacts, clicks into the search bar on the Contacts page and selects “Advanced Search.” The salesperson can now use custom deal field data to search for contacts associated with a deal located within an appropriate geographic region.
Selecting “Custom Deal Fields” from the Advanced Search menu.
An example of an Advanced Search the salesperson can use to find contacts associated with deals in specific geographic regions.
Use Case #2: Identify Opportunities to Upsell
Custom deal fields can be used to pinpoint easy upsell opportunities. For example, take a marketing consulting company with a sales process that includes a push to upsell clients who are interested in a particular service.
After a team member has a conversation with a potential client to learn more about their needs, that team member manually inputs which service(s) that deal is for into a Service custom field.
An example of a custom deal field created to track which service(s) a deal is for.
A potential client interested in newsletter engagement strategy may also be interested in hiring the consulting company to write a subscriber opt-in page, or might be interested in the newsletter opt-in email course they offer. With that information readily available in the deal, a team member can easily send a follow-up email highlighting those additional services.
Open a deal to view its custom deal field data, such as which product or service a deal is for.
Take quick action based on custom deal field info. In this example, a team member can open a deal to see which service it’s for, and send an email highlighting related services that may also be of interest to that contact.
Use Case #3: Target Specific Deals with a Sales Promotion
Do you like to know where your deals come from? A Source field can keep that information handy for every deal.
When you know how your deal was sourced, you can use that information to send specially targeted communications to your leads.
For example, a life coach may have deals in their pipeline that are generated through referrals, in-person meetings and networking events, and whenever the form on their website is submitted. The deals that come through the form often don’t have that special in-person element, so the life coach likes to offer a discount code in a personalized message to those leads to sweeten the deal and establish trust upfront.
As in our proactive salesperson example above, there is some setup work that needs to have been completed previously:
1) Create a Prospects list.
2) Create a Source custom deal field.
An example of a “Source” custom deal field.
3) Create a form and add it to the life coach’s website. In this example, the form must have an action that adds a contact to the Prospects list whenever it is submitted. This ensures that prospective clients end up on the right list, which is key—the life coach needs to be able to email their prospective clients for this process to work.
They can then build an automation that 1) creates a deal whenever the form is submitted, and 2) updates the Deal Source field to “Form Submitted.”
An “Update custom field” action configured to update a “Source” custom deal field with “Form Submission,” to indicate that a new lead came into the pipeline by submitting a form.
An automation triggered when a contact submits the form on the life coach’s website. Each time the form is submitted by a new contact, the automation creates a new deal in the life coach’s pipeline, and updates the “Source” field to “Form Submission.”
Now, the life coach can prepare a campaign email containing the discount code. When prompted to select a list or lists to send to, the life coach will select the Prospects list, and add a segment condition: Deal Source = Form Submission.
Selecting the “Prospects” list when sending a campaign email.
Using custom deal field data to further segment a list before sending a campaign email.
This will ensure the discount code is sent only to prospective clients who submitted the life coach’s form.
How to Get Started with Custom Deal Fields
Whether you’ve been capturing your deal information elsewhere or you’re just starting to think about the information you want to collect to better inform your sales process, make sure you give some thought to how you transition to custom deal fields.
Here are some questions to consider as you prepare to transition:
- What information would you like to capture for each deal?
- Where are you currently capturing deal information? In Notes? In custom contact fields? In other pipelines?
- How are your pipelines organized currently—by initiative, geography, product, or team?
- How would you like your pipelines to be organized? By product or service? By geographic region? Forecasted close date Reason a deal was won or lost? Or by competitor?
- How do deals make it into your pipeline? Are they added by a form or automation? Via API? UI?
- How far back do you want to populate custom deal field data?
- How will custom deal fields impact your current workflow/processes, pipelines, and automations?
- How will custom deal fields impact the different roles that use your ActiveCampaign account? For instance, how is your Sales team impacted? How is your Marketing team impacted?
- Who do you want to add/edit/delete your custom deal fields?
- How do you want to be able to view your custom deal fields?
Once you have a clear understanding of how you’ll integrate custom deal fields into your current sales process, it’s time to implement them.
Remember, be thoughtful not only about the information you want to capture, but how you’ll use it, so you can work with more information as you sell, target specific groups of contacts based on custom deal field data, and close more deals with more power and precision.
Set up and customize your deal pipelines and deal stages
Deal pipelines help visualize your sales process to predict revenue and identify selling roadblocks. Deal stages are the steps in your pipeline that signal to your sales team that an opportunity is moving toward the point of closing.
If you have Edit property settings access, you can create and edit deal pipelines and stages to best suit your team’s needs.
Create a new deal pipeline
Please note: only Sales Hub Starter, Professional or Enterprise accounts can create additional pipelines. Learn more about the maximum number of pipelines you can create in your HubSpot account depending on your subscription.
- In your HubSpot account, click the settings settings icon in the main navigation bar.
- In the left sidebar menu, navigate to Objects > Deals.
- Click the Pipelines tab.
- Click the Select a pipeline dropdown menu, then select Create pipeline.
- In the dialog box, enter a Pipeline name and click Create.
Once you’ve added deals to your pipeline, learn how to edit the deals in a pipeline.
Edit or delete deal pipelines
You can also rename, reorder, manage access to, or delete deal pipelines.
Please note: if you connect an ecommerce integration to HubSpot, another pipeline will be automatically added to your account that you cannot modify.
- In your HubSpot account, click the settings settings icon in the main navigation bar.
- In the left sidebar menu, navigate to Objects > Deals.
- Click the Pipelines tab.
- Click the Select a pipeline dropdown menu and select a pipeline.
- Click the code code icon to view the pipeline’s internal name. The internal name is used by integrations and the API.
- On the right, click the Actions dropdown menu and select one of the following:
- Rename this pipeline: change the pipeline’s name. In the dialog box, enter the new name, then click Rename.
- Reorder pipelines: change the order of your pipelines. In the pop-up box, drag the pipelines to move them to a new position, then click Save.
- Manage access: manage which users can view and edit the pipeline.
- Delete this pipeline: delete the pipeline. In the dialog box, click Delete pipeline to confirm. You can’t delete a pipeline if it contains deals. You’ll need to delete or move deals to another pipeline before deleting the pipeline.
- Click Customize board and card view to select the properties that are displayed on the board and board cards for the pipeline.
- Click Customize deal tags to create and manage color-coded labels that categorize deals (Sales Hub Starter, Professional, and Enterprise only).
In the dialog box, click Delete pipeline to confirm. You can’t delete a pipeline if it contains deals. You’ll need to delete or move deals to another pipeline before deleting the pipeline.Add, edit, or delete deal stages in a pipeline
You can use deal stages to categorize and track the progress of your ongoing deals in HubSpot. Each deal stage has an associated probability that indicates the likelihood of closing deals marked with that deal stage. Stage probability is used to determine the weighted amount shown in board view, which is calculated by multiplying the total amount in each stage by the stage probability.
By default, HubSpot includes a sales pipeline with seven deal stages: Appointment scheduled (20%), Qualified to buy (40%), Presentation scheduled (60%), Decision maker bought-in (80%), Contract sent (90%), Closed won (100% Won), and Closed lost (0% Lost).
If you have an Asset Marketplace provider account, your account will also have a Marketplace Transactions deal pipeline with a Transactions and Refunded deal stage.
You can also add your own stages or edit and delete existing stages. To customize the stages in a pipeline:
Please note: to ensure all sales reports, custom deal or revenue reports, and sales analytics tools process your deals correctly, ensure you at least have deal stages for both Won and Lost under Deal probability.
To reorder stages, click the stage and drag it to a new position.
- To view the internal name for a deal stage, hover over the stage and click the code code icon. The internal name is used by integrations and the API.
To delete a stage, hover over a stage and click Delete. If there are deals in the stage you’re deleting, you’ll need to move these existing deals to another stage.
To do this in bulk, navigate to the deals index page, and in list view, bulk edit the Deal Stage property.
To do this in bulk, navigate to the deals index page, and in list view, bulk edit the Deal Stage property.- To set who can edit deals in a specific stage, in the Editing access column, click the dropdown menu, then select whether to give edit permissions to all users with deal access, or only to super admins (Professional and Enterprise only).
- To edit the properties shown when a deal moves to a certain stage, hover over the Update stage properties column and click Edit properties.
- Once you’re done editing, click Save in the bottom left.
You can also automate tasks on deal stages when editing or creating a sales pipeline.
Customize properties shown in each deal stage
You can also customize which deal properties are presented to users when a deal moves to a specific stage. Users must have Edit property settings permissions to customize deal stage properties.
- Navigate to the pipeline you want to edit.
In the row of a stage, hover over the Update stage properties column and click Edit properties.
In the dialog box, select the checkboxes next to any new properties you want to appear.
Please note: properties with read-only values (i.e. that aren’t set by users, such as score or calculation properties) cannot be used as deal stage properties, and will not appear as options to select. Learn how to include these properties in the About this deal section on a record instead.
To require a value for a property, select the checkbox in the Required column (Starter, Professional or Enterprise only). When a property is required, users won’t be able to create a deal in that stage unless they enter a value for that property.
To reorder the properties, click and drag them to a new position.
- To remove a selected property, click the X next to that property in the Selected Properties column.
Once you’ve selected your properties, click Next. The properties you’ve selected will automatically appear when manually creating a new deal in that stage.
- Once you’re done editing, click Save in the bottom left.
Manage editing access for deal stages (
Professional and Enterprise only)
Super admins can set whether deals in specific stages are editable by all users with access to deals, or only by other users with super admin permissions. If a stage is limited to super admins, once a deal enters that stage, only super admins will be able to edit the deal or move it to a different stage. Users with deal access can still view deal records in that stage, but can’t make changes until an admin moves it to an editable stage.
Please note: even if a stage is limited to admins, the following behavior is expected:
- Deals in the stage can still be edited via workflows, API, or the forecast tool.
- Associations can still be edited on deals in the stage if a user has access to other objects (e.g., a user adds the deal as an association on a contact record, which adds the associated contact to the deal).
To avoid certain users editing deals via these methods, update their user permissions for those tools or objects.
- In your HubSpot account, click the settings settings icon in the main navigation bar.
- In the left sidebar menu, navigate to Objects > Deals.
- Click the Pipelines tab.
- Click the Select a pipeline dropdown menu, then select the pipeline to edit.
- In the Editing access column, click the dropdown menu and select who should have access to edit deals in that stage:
- Limited to super admins: only users with super admin permissions can edit the deals in the stage.
- Users with access to deals: any user with permissions to access deals can edit the deals in the stage.
- Limited to super admins: only users with super admin permissions can edit the deals in the stage.
- At the bottom of the page, click Save to confirm.
General Provisions on Transactions \ ConsultantPlus
General Provisions on Transactions
a transaction is an expression of will aimed at establishing, changing or terminating civil rights and obligations (for example, a civil law contract, issuance of a power of attorney, recognition of a debt, statement of set-off, unilateral refusal to fulfill an obligation, consent of an individual or legal entity to a transaction).
Consultant Plus: note.
In cases related to non-execution or improper execution of unilateral transactions and their contestation, the clarifications given in the Resolution of the Plenum of the Supreme Arbitration Court of the Russian Federation dated July 23, 2009 N 57
51 are applied.
in accordance with the law, other legal acts or agreement of the parties, it is necessary and sufficient to express the will of one party. If a unilateral transaction is made when the law, other legal act or agreement of the parties does not provide for its conclusion or the requirements for its conclusion are not met, then, as a general rule, such a transaction does not entail the legal consequences for which it was directed.
52. The consequences of bad faith actions (inaction) of the party to the transaction, which contributed to the occurrence or non-occurrence of the condition, are established by paragraph 3 of Article 157 of the Civil Code of the Russian Federation. If the occurrence of the condition was unfairly prevented by the party to whom the occurrence of the condition is unfavorable, then the condition is deemed to have occurred. If the occurrence of the condition was promoted in bad faith by the party to whom the occurrence of the condition is beneficial, then the condition is recognized as not having occurred.
Within the meaning of paragraph 3 of Article 157 of the Civil Code of the Russian Federation, it is not prohibited to conclude a transaction under a resolutive or suspensive condition, the occurrence of which depends, among other things, on the behavior of the party to the transaction (for example, the conclusion of a supply contract under a suspensive condition on the provision of a bank guarantee that ensures the fulfillment of the buyer’s obligations under payment for the goods; conclusion of a lease agreement for a newly built building under a suspensive condition on registration of the landlord’s ownership right to it).
53. Unless otherwise directly follows from the law or other legal act, article 157.1 of the Civil Code of the Russian Federation applies to any consent of a third party, body of a legal entity or state body or local government body to a civil law transaction. At the same time, for example, the rules on consent to transactions provided for by Federal Law No.
208-FZ of December 26, 1995 “On Joint Stock Companies” and Federal Law No. 14-FZ of February 8, 1998 “On Limited Liability Companies” are special in relation to the general provisions of Article 157.1 of the Civil Code of the Russian Federation.
-legal education in civil legal relations (clause 1 of article 124 of the Civil Code of the Russian Federation), are not required to give consent to the transaction.
Silence is not considered consent to the transaction, except in cases established by law (paragraph 4 of Article 157.1 of the Civil Code of the Russian Federation). If a third party or an appropriate body acting on behalf of a public legal entity as a participant in civil legal relations did not respond to the request of the party to the transaction within a reasonable time (paragraph 2 of Article 157.1 of the Civil Code of the Russian Federation), it is considered that the consent is denied. However, this circumstance does not prevent further expression of consent to the transaction or its subsequent approval.
If the need to obtain the consent of a state body or local self-government body is caused by the exercise of a public function (for example, paragraph 4 of Article 292 of the Civil Code of the Russian Federation) and does not affect the interests of the relevant public legal entity as a participant in civil legal relations, then the relevant body is obliged to give an answer about its consent or disagreement. In case of violation of this obligation, the person concerned has the right to demand compensation for the losses caused (Articles 15, 1069Civil Code of the Russian Federation). The decision of such a body can be challenged in court both in connection with the violation of the procedure for its adoption, and on the grounds of disagreement with the grounds for the decision.
55. A third party’s consent to a transaction may be expressed in any way, except when a specific form of consent is established by law (for example, paragraph 3 of Article 35 of the RF IC).
The consent of the public legal education body must be expressed in writing (in the form of a non-normative legal act, letter, etc.
).
In this case, the consent of the third party may be addressed to any of the counterparties of the transaction.
According to paragraph 3 of Article 157.1 of the Civil Code of the Russian Federation, consent to a transaction can be both preliminary and subsequent (approval).
56. The person giving prior consent may additionally indicate the conditions on which he agrees to the transaction being completed. Non-compliance by the parties to the transaction with these conditions gives the third party the right to challenge it on the basis of Article 173.1 of the Civil Code of the Russian Federation.
A third party has the right to give one consent to several transactions. At the same time, Article 157.1 of the Civil Code of the Russian Federation does not provide for the possibility of issuing the general consent of a third party to make any transactions with specifically undefined property. The admissibility of such consent may be provided for by law or follow from the peculiarities of the legal relations between the parties to the transaction and the third party agreeing on it.
57. A third person who has given prior consent to a transaction may revoke it by notifying the parties to the transaction prior to its completion and indemnifying them for losses caused by such withdrawal (Article 15 of the Civil Code of the Russian Federation).
Since civil law does not establish rules on the withdrawal of a third party’s consent to a transaction, in this case, by analogy with the law, the provisions on the withdrawal of acceptance are subject to application (paragraph 1 of Article 6, Article 439 of the Civil Code of the Russian Federation). The withdrawal of consent, the notification of which was received by the parties to the transaction after its completion, is considered invalid. Revocation of prior consent after the transaction, as well as revocation of subsequent consent (approval), cannot serve as grounds for recognizing the transaction as invalid.
Consent to a transaction may be invalidated in relation to the rules of Chapter 9 of the Civil Code of the Russian Federation.
In particular, consent given by a third party under the influence of material delusion, deceit, violence, threat or adverse circumstances may be challenged in accordance with Articles 178 and 179 of the Civil Code of the Russian Federation.
If the consent to the transaction is recognized as invalid, the transaction may be challenged on the grounds of the lack of consent required by law in accordance with the rules of Article 173.1 of the Civil Code of the Russian Federation.
58. If one of the parties has fully or partially executed a transaction that requires notarization, and the other party has accepted the execution and evades such certification, the court, at the request of the party that executed the transaction, has the right to recognize the transaction as valid. The one-year limitation period for the specified claim is calculated from the moment when the plaintiff knew or should have known that the other party was evading notarization (clause 4 of article 165, clause 1 of article 200 of the Civil Code of the Russian Federation).
59. If a transaction requiring state registration is made in the proper form, but one of the parties evades its registration, the court, at the request of the other party, has the right to make a decision on the registration of the transaction. In this case, the transaction is registered in accordance with the decision of the court. The one-year limitation period for the specified claim is calculated from the moment when the plaintiff knew or should have known that the other party was evading state registration (paragraph 4 of Article 165, paragraph 1 of Article 200 of the Civil Code of the Russian Federation).
60. In accordance with Clause 7 of Article 3 of Federal Law No. 100-FZ of May 7, 2013 “On Amendments to Subsections 4 and 5 of Section I of Part One and Article 1153 of Part Three of the Civil Code of the Russian Federation” (hereinafter Law No. 100- Federal Law), the limitation period established by paragraph 4 of Article 165 of the Civil Code of the Russian Federation applies to claims, the grounds for which arose after the day this Law came into force (September 1, 2013).
Therefore, the provisions of paragraph 4 of Article 165 of the Civil Code of the Russian Federation apply to the requirements for recognition of a valid transaction, during which the required notarial form was not observed, and for state registration of the transaction, if the party accepts the execution of the transaction, the notarization of which was not carried out, or, accordingly, the commission transactions that did not pass state registration took place after September 1, 2013.
61. The party that actually executed the transaction before its required state registration is not entitled to invoke the expiration of the limitation period at the request of the other party for its state registration (clause 2 of article 10, clause 3 of article 433 of the Civil Code of the Russian Federation).
62. The reduced (one-year) limitation period established in paragraph 4 of Article 165 of the Civil Code of the Russian Federation does not apply to the claim of one party to the transaction to the other party for compensation for losses caused by the latter’s evasion of notarization or state registration of this transaction (Article 15 of the Civil Code RF, paragraph 3 of Article 165 of the Civil Code of the Russian Federation).
The general limitation period is subject to the said claim (Article 196 of the Civil Code of the Russian Federation).
63. Within the meaning of paragraph 1 of Article 165.1 of the Civil Code of the Russian Federation, a legally significant message addressed to a citizen must be sent to the address of his registration at the place of residence or stay or to the address indicated by the citizen himself (for example, in the text of the contract), or to his representative (Clause 1 of Article 165.1 of the Civil Code of the Russian Federation).
Taking into account the provisions of paragraph 2 of Article 165.1 of the Civil Code of the Russian Federation, a legally significant message addressed to a citizen engaged in entrepreneurial activities as an individual entrepreneur (hereinafter referred to as an individual entrepreneur), or a legal entity, is sent to the address indicated respectively in the unified state register of individual entrepreneurs or in unified state register of legal entities or at the address indicated by the individual entrepreneur or legal entity.
At the same time, it must be taken into account that a citizen, individual entrepreneur or legal entity bears the risk of the consequences of not receiving legally significant messages delivered to the addresses listed in paragraphs one and two of this clause, as well as the risk of the absence of their representative at the indicated addresses. A citizen who informs creditors, as well as other persons of information about another place of his residence, bears the risk of the consequences caused by this (paragraph 1 of Article 20 of the Civil Code of the Russian Federation). Messages delivered to the named addresses are considered received, even if the person concerned does not actually reside (is not located) at the specified address.
If the person sending the message knows the address of the citizen’s actual place of residence, the message can be sent to that address.
If a foreign legal entity has a representative on the territory of the Russian Federation, messages delivered to the address of such a representative are considered received by the foreign legal entity (Item 3 of Article 54 of the Civil Code of the Russian Federation).
The addressee of a legally significant message, having received and established its content in a timely manner, is not entitled to claim that the message was sent to the wrong address or in an improper form (Article 10 of the Civil Code of the Russian Federation).
64. The rules of Article 165.1 of the Civil Code of the Russian Federation on legally significant messages apply, unless otherwise provided by law or the terms of the transaction, or follows from the custom or practice established in the relationship between the parties (Clause 2 of Article 165.1 of the Civil Code of the Russian Federation).
The agreement may establish that legally significant messages related to the emergence, change or termination of obligations based on this agreement are sent by one party to the other party to this agreement exclusively at the address (addresses) specified in it or exclusively in the manner provided for by the agreement. In this case, sending a message to a different address or in any other way cannot be considered appropriate if the person who sent the message did not know and should not have known that the address indicated in the contract is unreliable.
messages and relationships, information about which is contained in such a message, when it is possible to reliably establish who the message originated from and to whom it is addressed (for example, in the form of posting information on the website of a business company on the Internet for participants in this company, in the form of posting on a special information stand about the general meeting of owners of premises in an apartment building, etc.).
66. A legally significant message may contain information about the transaction (for example, a unilateral refusal to fulfill an obligation) and other information of legal significance (for example, notification of the debtor about the transfer of rights (Article 385 of the Civil Code of the Russian Federation).
67. Burden of proof
A legally significant message is considered delivered even if it was received by the person to whom it was sent, but due to circumstances depending on him, was not delivered to him or the addressee did not familiarize himself with it (Clause 1 of Article 165.
1 of the Civil Code of the Russian Federation) For example, a message is considered delivered if the addressee avoided receiving correspondence at the post office, in connection with which it was returned after the expiration of the storage period.0003
The addressee bears the risk of non-receipt of incoming correspondence. If a legally significant message contains information about a unilateral transaction, then if the message is not delivered due to circumstances depending on the addressee, it is considered that the content of the message was perceived by him, and the transaction entailed the appropriate consequences (for example, the contract is considered terminated due to unilateral refusal to execute it).
68. Article 165.1 of the Civil Code of the Russian Federation shall also apply to court notices and summonses, unless otherwise provided by civil procedural or arbitration procedural legislation.
Safe boxes and individual bank safes. Leasing of safe deposit boxes
A convenient and reliable way to store your valuables with the ability to conduct secure purchase and sale transactions, as well as providing access to a list of people you specify
Choice of any rental period of the safe
Rental of the safe for a short period of 15 days for real estate transactions
Discounts for the rental of bank safes for holders of Premium Service Packages
Translation and authentication services
banknotes
Vacuum packaging of banknotes
A wide range of safes of various sizes
Free power of attorney
access to the safe to third parties
Isolated rooms for confidential work with the safe
Modern security systems that ensure complete security of valuables
Flexible tariff policy
Use service
- Fill out an application, get expert advice
- Select the cell that best suits your goals
- Conclude an agreement, visit the nearest office of the Bank
Conditions of provision
The price policy for renting a safe
is established by the Bank’s Tariffs
The cost of rent depends on the
cell size and lease term
Tariffs and documents
General conditions for leasing individual bank safes to individuals
356 kb, pdf
Application for joining the General Terms and Conditions for leasing individual bank safes to individuals
and conclusion of the Lease Agreement within the General Conditions
356 kb, pdf
Additional agreement on monitoring the conditions of access to the safe to the Lease agreement for individual bank safes
356 kb, pdf
Additional agreement on monitoring the conditions of access to the safe to the Lease agreement for individual bank safes
for mortgage lending
356 kb, pdf
List of rental rates
individuals in individual bank safes in
branches and additional offices located on
territory of Moscow and the Moscow region (except for the Central
office)
123 kb, pdf.
