&gt;&gt; I think this comment by patio11 is very relevant here:<p>&gt; &quot;We don&#x27;t donate to OSS software which we use, because we&#x27;re legally not allowed to.<p>I routinely send key projects, particularly smaller projects, a request to quote me a commercial license of their project, with the explanation that I would accept a quote of $1,000 and that the commercial license can be their existing OSS license plus an invoice. My books suggest we&#x27;ve spent $3k on this in 2015. My bookkeeper, accountant, and the IRS&#x2F;NTA are united on this issue: they don&#x27;t care whether a software license is OSS or not. A $1k invoice is a $1k invoice; as a software company, I have virtually carte blanche to expense any software I think is reasonably required, and I think our OSS is reasonably required.<p>This shoots red flags, so I&#x27;d like to share:<p>Anti Money Laundering:<p>Any auditor, bank, investor, or interested party, is required to ensure money laundering is not part of a business plan, just a compliance step.  Donating to &#x27;associate&#x27; with &#x27;suggestions&#x27; of the price need this in some for of documentary proof for the &#x27;suggestion&#x27;.  As the software is Open Source, where&#x27;s the value-added vs. throwing $1000 to a friend?  S&#x2F;PaaS is the answer, but it should be documented.<p>Anti-terrorist financing:<p>Yes, this is a thing (on the receiver side).  Not to worry about unless your don&#x27;t have multiple small transactions coming to your bank account in a short period of time (perhaps sending an email asking for donations) at which the account and ownership should be inspected by the receiving bank.  Get 100 donations of varying small sizes, $1+ in a short period of time, expect to get flagged as possible.<p>Just a heads-up on compliance for how unexpected regulation can stop throw a small cog in the wheels of what you want to do.