Look, I’m going to be straight with you.<\/p>\n\n\n\n
Most articles about hiring remote workers from the Philippines read like they were written by someone who’s never actually done it. <\/p>\n\n\n\n
They’re either too technical (here’s form W-8BEN subsection 4.2!) or too fluffy (Filipinos are so hardworking and loyal!).<\/p>\n\n\n\n
This isn’t that.<\/p>\n\n\n\n
What follows is what actually matters when you’re building a team across 12+ time zones. <\/p>\n\n\n\n
The IRS doesn’t care what you call someone. They care about three things: Do you control how they work? Do you control their finances? What’s the actual relationship?<\/p>\n\n\n\n
If you’re telling someone when to log in, what tools to use, and they only work for you\u2014that’s starting to look like an employee, even if your contract says “independent contractor” in bold letters.<\/p>\n\n\n\n
Here’s what keeps you safe:<\/strong><\/p>\n\n\n\n Your remote worker should control how<\/em> they complete tasks, not just what<\/em> tasks they complete. <\/p>\n\n\n\n They should be able to work for other clients. They should use their own equipment (or you provide a stipend, not company property). <\/p>\n\n\n\n No employee benefits that could blur the line.<\/p>\n\n\n\n For US employers: Get a W-8BEN form before the first payment. It’s the IRS form that confirms your worker is foreign and exempts you from withholding. <\/p>\n\n\n\n File it away for four years.<\/p>\n\n\n\n And here’s something that surprises people: You do NOT send 1099 forms to foreign contractors. That’s only for US-based contractors. The IRS is explicit about this.<\/p>\n\n\n\n If your remote worker handles customer data, you’ve got data privacy obligations.<\/p>\n\n\n\n The Philippines has a Data Privacy Act. It’s modeled after GDPR. If your worker is processing personal information\u2014customer emails, names, payment details\u2014there are rules.<\/p>\n\n\n\n For UK and EU-based companies, this gets more complex. <\/p>\n\n\n\n The Philippines isn’t on the UK’s “adequacy” list, which means you need Standard Contractual Clauses in place. These are templates that create legally binding privacy obligations.<\/p>\n\n\n\n Sounds bureaucratic? It is. But it’s also not optional if you’re handling EU\/UK customer data.<\/p>\n\n\n\n The practical version: Have a Data Processing Agreement. <\/p>\n\n\n\n Train your remote workers on data handling. <\/p>\n\n\n\n Don’t store sensitive information in random Google Docs with public links.<\/p>\n\n\n\n Let’s talk money movement.<\/p>\n\n\n\n PayPal is convenient for you. It’s terrible for remote workers in the Philippines. The fees are brutal (3-4% per transaction), and the PHP conversion rates are worse. People lose 7-8% of their payment by the time it hits their bank account.<\/p>\n\n\n\n Wise (formerly TransferWise) is the standard<\/strong> for a reason. Lower fees, transparent conversion, direct PHP withdrawal. Most experienced remote workers will specifically ask for Wise.<\/p>\n\n\n\n Payoneer is the second choice. Direct bank transfer via SWIFT works for larger amounts but gets expensive for smaller, regular payments.<\/p>\n\n\n\n The US-Philippines tax treaty (and similar ones with UK and Australia) exists to prevent double taxation.<\/p>\n\n\n\n Here’s what it means in practice: Your remote worker pays taxes in the Philippines on their income from you. <\/p>\n\n\n\n You don’t withhold anything (assuming they’re properly classified as a contractor and you have that W-8BEN).<\/p>\n\n\n\n They’re responsible for their own tax registration with the Philippine Bureau of Internal Revenue (BIR). <\/p>\n\n\n\n Most pay 8% on gross receipts if they earn under \u20b13 million annually (about $53,000), or graduated rates of 15-35% on net income.<\/p>\n\n\n\n As the foreign employer, you’re not responsible for enforcing their tax compliance. <\/p>\n\n\n\n But it’s worth mentioning during onboarding that they should register\u2014many don’t until they’re earning significantly, which creates problems down the line.<\/p>\n\n\n\n Here’s what actually creates friction in remote teams:<\/p>\n\n\n\n High-context cultures (like the Philippines) avoid direct confrontation. Saying “no” to a manager feels disrespectful.<\/p>\n\n\n\n So you ask, “Can you finish this by Friday?” and hear “Yes,” even when the honest answer is “That’s impossible without dropping everything else.”<\/p>\n\n\n\n The fix:<\/strong> Change how you ask questions.<\/p>\n\n\n\n Instead of “Do you have questions?” (which invites “No” as the polite answer), ask “What questions do you have?”<\/p>\n\n\n\n Instead of “Can you do this?” ask “What would you need to make this happen?” or “What concerns do you have about this timeline?”<\/p>\n\n\n\n Follow verbal conversations with written summaries. “Just to confirm, we agreed on X, Y, Z. Let me know if I missed anything.”<\/p>\n\n\n\n Scheduling all meetings at 9 AM Pacific means 1 AM in Manila.<\/p>\n\n\n\n If you do this consistently, you’re telling remote workers they’re second-class team members. They’ll show up because they need the work. But you’re burning them out and killing any sense of belonging.<\/p>\n\n\n\n Better approaches:<\/strong><\/p>\n\n\n\n Rotate meeting times. If you meet weekly, alternate between convenient-for-you and convenient-for-them.<\/p>\n\n\n\n Make async the default. Meetings should be the exception, not the rule. Use recorded updates, written standups, and Slack threads.<\/p>\n\n\n\n If you absolutely need live overlap, find 2-3 “core hours” where everyone’s available and protect them fiercely.<\/p>\n\n\n\n Let me tell you what kills trust faster than anything: Screenshot monitoring every 10 minutes.<\/p>\n\n\n\nThe Privacy Thing Nobody Talks About<\/h2>\n\n\n\n
Payment: What Actually Works<\/h2>\n\n\n\n
Tax Treaties Save Everyone Money<\/h2>\n\n\n\n
The Real Culture Gaps (And How to Fix Them)<\/h2>\n\n\n\n
The “Yes” Problem<\/h3>\n\n\n\n
The Timezone Trap<\/h3>\n\n\n\n
Time Tracking Without the Surveillance State<\/h2>\n\n\n\n