SOP QUICK LINKS

• Small Program Minimum / Revenue Measurement
• Vendor Payment Request
• Vendor Agreements
• Convention for saving Client Agreement in SharePoint
• Convention for saving Vendor Agreement in SharePoint
• Bank Instructions Confirmation

TIMELINE 

• Info coming soon

CONTRACT 
TERMINOLOGY

• Info coming soon

Small Program Minimum / Revenue Measurement

A small program must reach at their minimum of $20,000 of revenue to be manage by MMI.

Vendor Payment Request

1.    Client agreement must be countersigned.
2.    Client payments must be up to date.
3.    Vendor agreement must be countersigned.
4.    The last version of the “Payment Request Form” must be filled in and submitted to Accounting.

Vendor Agreements

Please see below the following 5 components for save Vendor’s Agreement:
Vendor’s Name | Client’s Name | Contract Type | Version | Status
E.g.: Ritz Carlton, doTERRA Agr v.2024.05.03 countersigned

Sometimes you will not have the 5 components, so it will be ok to miss.
E.g.: Ritz Carlton, doTERRA Agr v.2024.05.03Note that this is the original version, so we don’t have a status.

Important Note: Vendor’s Agreement version will be determined on Agreement issue date; if this Agreement does not have issue date, we will use the date we received it. If we receive an updated agreement with the same previous issue date, we will add rev.1 after the version date.
E.g.: Ritz Carlton, doTERRA Agr v.2024.05.03 rev.1

Contract Type reference:

• AGR: Agreement
• AFS: Agreement For Services
• LOU: Letter of Understanding
• SOW: Statement of Work
• AMD: Amendment 
• NOC: Notice of Cancellation

Convention for saving Client Agreement in SharePoint

Please see below the following 7 components for save Client’s Agreement: 
Client’s Name | Year | Month | Destination | Contract Type | Version | Status
E.g.: doTERRA 2025 Jun Bali Agr v2 countersigned

Sometimes you will not have the 7 components, so it will be ok to miss.
E.g.: doTERRA 2025 Jun Bali Agr
Note that this is the original version, so we don’t have a “version” nor status.

Important Note: Client’s Agreement version will be determined if this Agreement has already send it to our Client and after that we was required to make some changes. To differential the original version (that our Client already received) from the 2nd one, needs to be renamed it as v2.
Contract Type reference:

• AGR: Agreement
• AFS: Agreement For Services
• LOU: Letter of Understanding
• SOW: Statement of Work
• AMD: Amendment 
• NOC: Notice of Cancellation

Convention for saving Vendor Agreement in SharePoint 

Please see below the following 5 components for save Vendor’s Agreement:
Vendor’s Name | Client’s Name | Contract Type | Version | Status
E.g.: Ritz Carlton, doTERRA Agr v.2024.05.03 countersigned

Sometimes you will not have the 5 components, so it will be ok to miss.
E.g.: Ritz Carlton, doTERRA Agr v.2024.05.03
Note that this is the original version, so we don’t have a status.

Important Note: Vendor’s Agreement version will be determined on Agreement issue date; if this Agreement does not have issue date, we will use the date we received it. If we receive an updated agreement with the same previous issue date, we will add rev.1 after the version date.
E.g.: Ritz Carlton, doTERRA Agr v.2024.05.03 rev.1

Contract Type reference:

• AGR: Agreement
• AFS: Agreement For Services
• LOU: Letter of Understanding
• SOW: Statement of Work
• AMD: Amendment 
• NOC: Notice of Cancellation
   

Bank Instructions Confirmation

If the wire transfer instructions are separate from the agreement, the Account Executive must confirm this information by phone with their contact prior to paying this.

Note: This implementation was the result of hackers.