Skip to content

Raise receipt limit to $20 USD or EUR

Joshua Lambert requested to merge jl-receipt-limit into master

Why is this change being made?

Currently we have a policy where itemized receipts are required for all expenses. This can introduce inefficiencies for travel, both monetarily and in time required for employees.

We should consider raising the receipt limit to allow employees to focus on Results, and align with many of our sub-values in Efficiency. The IRS require receipts for expenses of $75 or more, which is the value most US-oriented articles recommend. International requirements may differ, or generate inefficiencies with VAT.

This MR proposes a value of $20 USD or EUR as a starting point, to allow for incidentals like small meals/refreshments or intra-city transit, but still require receipts for larger purchases.

International considerations

It is certainly possible some countries where GitLab operates may require receipts for all purchases. If this is the case, we should consider per-country/region policies, so that we can limit the inefficiencies to only where it is required. We already tailor benefits and HR policies in this manner, so that we align to what is common in the countries we operate in.

Articles on finding the right receipt limit

Personal example

I recently traveled on mass transit from Philadelphia to New York City.

In Philadelphia, regional rail works on a specialized payment service (SeptaKey) where fares are automatically deducted. If you'd like a paper receipt, you either need to stand in line at a ticket office or pay on-board, which incurs extra cost. The most convenient and efficient option is to utilize SeptaKey, but this does not generate receipts.

Once in New York City, I traveled on the subway as it is the most efficient and cost effective method of going longer distances. The MTA now supports Apple/Google Pay in turnstiles, as a quick and effective method of paying for a one-way fare. The alternative is to wait in a line to get a refillable MetroCard, which cost $1 and are filled in values misaligned with fare costs, and eventually expire. The most efficient option once again does not generate a receipt.

Author Checklist

  • Provided a concise title for the 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.
  • Assign reviewers for this change to the correct DRI(s)
    • 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 in 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.
  • 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.
Edited by Joshua Lambert

Merge request reports