Accept approvals only from SoldTo contacts for the Ownership verification

Why is this change being made?

Should we only accept approval from the existing SoldTo contact, and not the BillTo contact?

On one of our EMEA L&R pairings, we discussed this particular detail, so I decided to create an MR to clarify that. One of the verification options we have is the "Approval from the existing contact".

An example of a different BillTo/SoldTo contact: internal link

Our understanding of this is that this approval can be given only by the SoldTo contact, because:

• Only the SoldTo contact is guaranteed to have a CustomersDot account; this is what we're interacting with after verifying the request (changing the cDot contact, or adding an additional one). Since we are making changes in cDot, the contact who owns cDot account should approve the changes.
• The BillTo contact has a viable alternative to this already, as we accept "Recent GitLab invoice (last 12 months)" as a validation proof. If the BillTo is participating in the verification, attaching an invoice should work for them.

If the SoldTo and BillTo contact is the same, then we can proceed the same way we did before 🙂

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---