Merge branch 'a.hansen-master-patch-07822' into 'master'

Update source/handbook/finance/procurement/index.html.md

See merge request gitlab-com/www-gitlab-com!37071

source/handbook/finance/procurement/index.html.md

----
-layout: handbook-page-toc
+----
+layout: markdown_page
 title: "The GitLab Procurement Team"
 ---
@@ -10,55 +10,83 @@ title: "The GitLab Procurement Team"
 {:toc}
-# The GitLab Procurement Team is your Partner for the Procure to Pay Process
+# The GitLab Procurement Team 
 ## Requesting Procurement Services
  
-There are several third-party vendor processes that procurement supports, depending on your needs. Team members can purchase goods and services on behalf of the company in accordance with the Signature Authorization Matrix and guide to Spending Company Money. However, any purchases requiring contracts must first be reviewed by procurement, then signed off by a member of the executive team. Be sure to also check out our guide on Signing Legal Documents.
+There are several third-party vendor processes that procurement supports. Team members can purchase goods and services on behalf of the company in accordance with the Signature Authorization Matrix and guide to Spending Company Money. However, any purchases requiring contracts must first be reviewed by procurement, then signed off by a member of the executive team. Be sure to also check out our guide on Signing Legal Documents.
 ### 1. New Vendor Evaluation
-If you have a new business need and are seeking a third party vendor to support it, you must review the market capabilities defined by your overall spend BEFORE selecting your vendor. 
-*Note: Before sharing details and/or confidential information regarding our business needs, please obtain a [Mutual Non-Disclosure Agreement](https://drive.google.com/file/d/1kQfvcnJ_G-ljZKmBnAFbphl-yFfF7W5U/view?usp=sharing) from the potential vendor(s).*
+If you have a new business need and are seeking a third party vendor to support it, you must review the market capabilities defined by your overall spend BEFORE selecting your vendor. Create a Vendor Contract Approval [Issue Template](https://gitlab.com/gitlab-com/finance/blob/master/.gitlab/issue_templates/vendor_contracts_general_and_adminstrative) to begin the process. Unless, however, you have a field marketing vendor contract that do NOT involve data processing such as marketing programs, sponsorships, hotels, and professional services that do not require processing of data. In that case, create a Non-Data Vendor Contract Approval [Issue Template](https://gitlab.com/gitlab-com/finance/blob/master/.gitlab/issue_templates/vendor_contracts_fieldmarketing.md)
+
+**Note: Before sharing details and/or confidential information regarding our business needs, please obtain a [Mutual Non-Disclosure Agreement](https://drive.google.com/file/d/1kQfvcnJ_G-ljZKmBnAFbphl-yFfF7W5U/view?usp=sharing) from the potential vendor(s).**
+All vendors must adhere to the [GitLab Partner Code of Ethics](https://about.gitlab.com/handbook/people-group/code-of-conduct/#partner-code-of-ethics). Please inform your vendor it is mandatory they contractually adhere to this if they would like to do business with us. (Note these are typically not required in marketing events agreements, unless the vendor is providing services)
 | Estimated Spend | Market Review Needed |
 | ------ | ------ |
 | <$25K | None |
-| >$25K and <$100K | Three Bids | 
+| >$25K and <$50K | Two Bids | 
+| >$50K and <$100K | Three Bids | 
 | >$100K | RFP |
-If there is a business reason why the market review is not necessary, please obtain a bid waiver from your functional leader and send to procurement for approval.
-For instructions on how to evaluate a new vendor, please see the LINK COMING SOON!
+If there is a business reason why the market review is not necessary, please obtain a bid waiver from your functional leader and send to procurement for approval. This can be done within the vendor contract [Issue Template](https://gitlab.com/gitlab-com/finance/blob/master/.gitlab/issue_templates/vendor_contracts_general_and_adminstrative)
 ### 2. Existing Vendor Negotiation (for Renewals and True-Ups)
-If you have an existing vendor that needs a contract renewal or a true-up mid contract, work with procurement BEFORE agreeing to business terms. For all  contract renewals, **contact procurement 90-60 days before the existing contract expires**. Procurement will engage our software buying partner Vendr to ensure that the quoted pricing is competitive. Vendr can help negotiate directly with vendors on both new subscriptions and renewals. It is preferred that we negotiate the best pricing up front to keep our ongoing costs to a minimum across our long-term relationships with vendors. 
+If you have an existing vendor that needs a contract renewal or a true-up mid contract, work with procurement BEFORE agreeing to business terms. For all contract renewals, **contact procurement 90-60 days before the existing contract expires** by opening an [Issue Template](https://gitlab.com/gitlab-com/finance/blob/master/.gitlab/issue_templates/vendor_contracts_general_and_adminstrative). Procurement will engage our software buying partner Vendr to ensure that the quoted pricing is competitive. Vendr can help negotiate directly with vendors on both new subscriptions and renewals. It is preferred that we negotiate the best pricing up front to keep our ongoing costs to a minimum across our long-term relationships with vendors. 
 For instructions on how to submit an existing vendor negotiation, please see the LINK COMING SOON!
 ### 3. Vendor Contract Review
-BEFORE agreeing to business terms, identify whether you need a New Vendor Market Review (#1 above), or an Existing Vendor Negotiation (#2 above). If you have completed one of those, you are ready to seek review of a vendor contract. Your request must go through GitLab's Vendor Management process to make sure it has been reviewed by appropriate stakeholders and that the request receives all necessary approvals.  This process involves Finance (for budgetary purposes), Security (when personal data is involved to ensure the vendor's systems and procedures meet our minimum standard), Business Operations, Procurement (for contract review), and an approved Signer (for final approval and signing).  
+BEFORE agreeing to business terms, identify whether you need a New Vendor Market Review (No. 1 above), or an Existing Vendor Negotiation (No. 2 above). If you have completed one of those, you are ready to seek review of a vendor contract. Your request must go through GitLab's Vendor Management process to make sure it has been reviewed by appropriate stakeholders and that the request receives all necessary approvals.  This process involves Finance (for budgetary purposes), Security (when personal data is involved to ensure the vendor's systems and procedures meet our minimum standard), Business Operations, Procurement (for contract review), and an approved Signer (for final approval and signing).  
 For instructions on how to submit a new vendor contract for review, please see the [Vendor and Contract Approval Workflow](/handbook/finance/procure-to-pay/#vendor-and-contract-approval-workflow). Once the contract is completed it should be uploaded by the requestor into our contract management database tool [ContractWorks](/handbook/legal/vendor-contract-filing-process/).
-### 4. Vendor Onboarding
-As new (and existing) vendors will be supporting GitLab, we are implementing new tools such as Tipalti for onboarding and a PO Module for all payments. 
-Tipalti is an AP Payment Processing System that feeds data into NetSuite. Once a Finance Issue has been completed and received all necessary approvals with a fully executed contract, a self-registration link will be sent to the Vendor if the Vendor is not already setup within our Netsuite system. It is important to note that any delay in Vendor self-registration within Tipalti will delay vendor payment(s). For additional information on how we onboard vendors with Tipalti, please refer to our [Vendor Master Agreement](https://about.gitlab.com/handbook/finance/accounting/#3-vendor-master-management).
-We are using Netsuite to create and track Purchse Orders. Please refer to the [Purchase Order Process](https://about.gitlab.com/handbook/finance/procurement/purchase-order-process/) for information on how to create a Purchase Order.
+## Legal Engagement for Vendor Contracts
+
+Procurement is responsible for reviewing vendor contracts and will adhere to legal playbook. Procurement will escalate contracts to the legal team if support and/or legal expertise is required on a case by case basis.
+
+Legal escalation will occur in the event:
+
+
+1.  A request exceeds $100K USD;
+2.  DPIA is required for the procurement of goods / services;
+3.  Purchase impacts or relates to Intellectual Property ownership right(s) (i.e., joint development agreement for product(s); or
+4.  Consultant, Contractor and/or Sub-Contractor requests
+
+In the event Legal escalation is required:
+1.  Legal will be added as an approver to the Vendor Contract Approval Template; and  
+2.  Once reviewed and approved the contract(s) will be updated with a legal / contract manager approval stamp. 
+## Capacity & Back Log
+In the event the procurement team is OOO (as highlighted in PTO calendar or Slack), and the matter is time sensitive, requestor should:
+Contact #legal channel in Slack and provide:
+
+
+1.  Link to Vendor Contract Approval Issue; and
+2.  Reason for escalation, with timeline for requirement(s)
+
+Legal, once engaged with assign a team member to the Vendor Contract Approval Issue.
+
+In addition, in the event of overflow of requests, procurement will engage legal to support contract reviews via the #legal slack channel.
+
+### 4. Vendor Onboarding
+
+As new (and existing) vendors will be supporting GitLab, we are implementing new tools such as Tipalti for onboarding and a PO Module for all payments. Vendors will be required to create an account within Tipalti in order to receive payment.
 ### 5. Vendor Performance Issues
-If there are performance and/or quality issues from an existing third-party vendor, procurement can support the resoluation and/or re-evaluation of a replacement vendor. More info coming soon.
+If there are performance and/or quality issues from an existing third-party vendor, procurement can support the resoluation and/or re-evaluation of a replacement vendor. Please log an issue and assign @procurement for next steps.
 ### 6. All Other Procurement Requests 
-Issue Tracking Coming Soon.
+If you have a question please ask via the #procurement slack channel.
  
 # Contract Templates