Order MQL5 Programs from professional developers

I. General Provisions

1. The Jobs section of mql5.com website is the service for fulfilling Orders of programming in MQL4 and MQL5.
2. The Jobs service is available to all registered users of MQL5.com.
3. To search for developers who are ready to write a program, an Order needs to be placed.
4. A user who has placed an Order is hereinafter referred to as the Customer.
5. To take part in the competition for the Order, a proposal to perform the work needs to be posted in an Application to the Order.
6. A user who has placed an Application is hereinafter referred to as the Applicant.
7. The Customer chooses one of the Applications, and begins to negotiate the details of the Order with the Applicant who have submitted this Application.
8. An Applicant selected to perform the work under the Order is hereinafter referred to as the Developer.
9. All details of the Order are provided in the Requirements Specification.
10. Job description should be complete, meaningful and contain at least 30 words. Replication of phrases via copy and paste is prohibited.

II. Execution of Orders

1. An Order passes through the following execution steps:
1. Work Agreement
2. Requirements Negotiation
3. Prototype/Model
4. Demonstration
5. Work Acceptance
6. Payment
2. At each step, the Customer and the Developer shall confirm the fulfillment of their obligations on this step.
3. Only after the confirmation of both parties involved in the Order, they can go to the next step.
4. Only one Developer can be selected for each Order.
5. Upon the completion of step Requirements Negotiation, on the Customer's account, a sum of money will be locked in to cover the Order payment after the completion of step Work Acceptance.
6. Payment for the completed Order will be made automatically from the Customer's account to the Developer's account after the Customer confirms the step of Work Acceptance.
7. In case any disputes arise out of the Order execution, any of the parties may request arbitration to resolve the conflict.
8. During arbitration, the basis for decision making is only the Requirements Specification.

III. Description of Steps

1. Work Agreement
1. Several Applications may be posted for one Order; the Customer may select only one of them to execute the Order.
2. For each Application, a separate discussion topic is created, available only to the Customer and the Applicant/Developer.
3. The ultimate goal of such discussion is concluding the Work Agreement to move to the step of Requirements Negotiation.
2. Requirements Negotiation
1. To finalize details of the Order, discussion continues on the step of Requirements Negotiation.
2. The purpose of discussions between the Customer and the Developer is the approval of the requirements specification for the Order.
3. The Customer publishes the negotiated Requirements Specification as a separate message right before its approval. This message should begin with words "Requirements Specification".
4. No other preliminary agreements, written or oral, not included in the requirements specification, have force in carrying out the work.
5. The Customer shall not demand performance of works not described in the requirements specification.
6. The requirements specification and the system comments of each step confirmation are the main source governing resolution of any claims and disputes arising during the work.
7. After both parties approve the Requirements Specification, the payment for the Order is locked on the Customer's account in the Payment System.
8. The Customer may cancel the previously selected Developer and select a new one, provided the requirements specification has not been approved yet.
3. Prototype/Model
1. The Developer provides a Prototype or Model of the ordered solution to the Customer, in order to agree on the operation mode and/or appearance.
2. The Prototype/Model is not required to contain the entire functionality described in the requirements specification, being only an outline or draft.
3. On this step, the Customer and the Developer shall specify the fine details of the final order, which does not affect the overall operation of the ordered solutions, but can bring additional comfort during utilization.
4. For the Prototype, the Developer can provide outlines, configuration dialogs, templates of information panels positioning, examples of technical messages to print in the "Experts" journal and so on.
5. The ultimate goal of the discussion at this step is the approval of an agreement on how a complete solution should look like.
4. Demonstration
1. Before delivering the work to the Customer, the Developer shall demonstrate the operation of the complete solution.
2. The parties may have further discussions to fix detected errors or add some clarifications.
3. The ultimate goal is the approval of the Customer that the presented materials allow the transfer of work from the Developer to the Customer.
4. Specific details of what is a demonstration and criteria of checking whether a solution complies with the Order, must be specified in the Requirements Specification.
5. Work Acceptance
1. The completed work is delivered by way of providing files. The number of files is not limited. Files with *.dll extension are delivered only in a compressed form
2. The files shall be posted right in the Order attached to the comments.
6. Payment
1. The required sum of money is automatically deducted from the Customer's account and added to the Developer's account by the Payment System upon the Customer's confirmation of the work delivery or the recognition of the Order as fulfilled after the expiry of the work acceptance period.

IV. Payments

1. All payments are made in the internal payment system of the MQL5.com website, hereinafter referred to as the Payment System.
2. The Customer and the Developer must have an account in the Payment System.
3. For account opening, registration on MQL5.com is required.
4. You can deposit and withdraw funds from the Payment System via WebMoney and PayPal.
5. When payment for the work is added to the Developer's account, commission is charged automatically.

V. Arbitration Order

1. If dispute arises between the Customer and the Developer, which cannot be solved without the involvement of a third party, any of the parties may apply to arbitration.
2. Arbitration of disputes is based only on the Requirements Specification and system comments on the confirmation of each step.
3. If necessary, outside experts may be involved and additional materials may be requested. The decision of such a necessity is taken by the resource Administration.
4. The situation in arbitration is discussed and the decision is made directly in the relevant Application.
5. The decision of the arbitration shall be final and binding both for the Customer and the Developer.