Rate vs Take-Home: Taxes, Rail Fees, and What Actually Lands

Gross rate is a headline; take-home is the week

You send an invoice for $400. Your brain spends $400. Then the payout lands smaller. GCash shows a different number. You set aside tax later, or you forget and panic in April. That gap is the whole topic.

Rate is what you and the client agreed to pay for the scoped work.

Take-home is what you can actually use after:

• Payment rail and platform fees
• Currency conversion differences
• Receiving / cash-out fees
• Tax reserve (your situation; not advice)
• The unpaid hours that never hit the invoice

Salag cares about take-home because a "good rate" that fails after fees still breaks your month. The recommended professional floor remains $5/hr, measured in a way that still makes sense after realistic friction. Salag does not recommend $4/hr or below as a training strategy.

The take-home stack (plain checklist)

Copy this into a note and fill with your live numbers:

1. Invoiced amount (USD or agreed currency)
2. Minus platform fee (if any)
3. Minus processor / transfer fee
4. Conversion to PHP at the rate you actually receive
5. Minus bank or GCash receiving / cash-out fees
6. Minus tax reserve percent you chose with proper guidance
7. Equals cash you can plan with
8. Divide by total hours worked (billable + unpaid admin) for true hourly take-home

If step 8 falls under your floor, the quote was not really $5+/hr in lived reality.

Taxes: reserve early, confirm your route

Tax rules depend on registration, income, and filings. Salag will not invent a one-size percent as personal advice.

What you can do safely as process:

• Read Freelancer Tax Philippines: 8% for orientation
• Read When Should New VAs Register with BIR?
• Keep payout proofs and invoices organized (Official Receipt for Freelancers, How to Invoice US Clients)
• Confirm your route with a qualified professional

For rate math, pick a reserve habit you can sustain (many freelancers park a buffer each payout). Label it "reserve," not "I already know my exact BIR bill." Wrong confidence is expensive.

Rail fees: label examples as check-your-rail

Wise, PayPal, bank wires, and GCash combinations change. Any percent someone remembers from 2024 can be wrong in 2026.

Rule for this article: every fee figure below is a check-your-rail teaching example. Open the app, run a small test or fee preview, and write the date beside your note before you treat it as current.

Teaching example A: USD invoice → Wise → PHP

Illustrative only (verify live):

• Invoice: $500
• Example transfer fee line: check Wise fee preview for your corridor
• Example conversion: mid-market vs what you receive can differ
• Example bank deposit fee: check your bank

You might land near one PHP number on Monday and another after a fee update. That is why take-home worksheets have dates.

Teaching example B: PayPal balance → cash out

Illustrative only (verify live):

• PayPal receiving and currency conversion can stack
• Cash-out to local bank or card can add another line
• Holds on new accounts delay "landed" even when the invoice is "paid"

Teaching example C: Wise → GCash path

See Wise to GCash Fees for Filipino Freelancers. Then re-check the live path you actually use. Do not memorize a blog percent as eternal truth.

Unpaid admin: the silent take-home killer

You quoted $6/hr for 20 hours ($120). You also spent:

• 2 hours clarifying scope in chat
• 1 hour fixing access
• 1 hour chasing the payout

Paid hours: 20. Lived hours: 24. Before fees, lived hourly is already lower. After fees, lower still.

Fixes that stay honest:

• Cap revision rounds in writing
• Batch questions into one daily window
• Require deposits before deep work
• Log admin for your own floor math even if you do not bill every minute

ALIGN for rate vs take-home

Assess the rail the client prefers and your fee worksheet date.

List deliverables and whether the quote is hourly or package.

Invoice with clear currency, due dates, and payment instructions (invoicing guide).

Guardrails for late fees, pause rules, and scope changes.

Note the next fee-check date beside your rate.

If take-home fails the floor, you either raise rate, change rail, or cut scope (When to Cut Scope Instead of Cutting Rate).

Step-by-step: rebuild one client in 20 minutes

1. Open last month's payout screenshots.
2. Write invoiced vs landed PHP with the date.
3. List hours from your tracker, including unpaid admin.
4. Compute lived hourly take-home.
5. Compare to Salag $5/hr floor and your personal COL floor (COL vs market anchoring).
6. If under floor, draft one change: rate raise, package slim, or rail change.
7. Save the worksheet next to the client name.

Use the Rate Calculator for the floor side. Use payout proofs for the rail side.

Scripts

Asking a client to switch rails for cleaner landing

ScriptCopy

Hi [Name], to keep invoicing clean and avoid payout delays on my side, can we use [Wise / agreed rail] for the next invoice? I'll send the exact receiving details on the invoice. If your finance team needs PayPal only, I can keep that rail and adjust the quote so landed pay still clears my $5/hr floor after fees.

Explaining a rate that includes fee buffer (no drama)

Quick note on pricing: my quoted rate is set so take-home still clears a sustainable floor after typical transfer fees and unpaid admin caps in our scope. If we change payment rails, I'll confirm fees and send an updated quote before the next cycle.

When landed cash surprises you mid-retainer

ScriptCopy

I reconciled last month's payout against the invoice and hours. After [rail] fees and the extra revision hours outside the cap, lived take-home fell under my floor. For next month I can either (a) keep scope and move to $[new rate], or (b) keep $[old rate] with this slimmer list: [A], [B], [C]. Which do you prefer?

Worked numbers (teaching only, not a fee promise)

Assume an illustrative quote of $5/hr × 80 hours = $400 invoiced.

Check-your-rail example (invented structure for method practice, not current official fees):

• Example processor friction totaling about 3% equivalent on this corridor (VERIFY LIVE)
• Example receiving/cash-out friction about 1% equivalent (VERIFY LIVE)
• Tax reserve habit example: 10% of landed (CONFIRM YOUR ROUTE)

Rough flow for learning the worksheet:

• After 4% combined rail friction teaching example: about $384 before tax reserve
• After 10% reserve habit teaching example: about $346 planned usable
• If unpaid admin added 10 hours on top of 80: lived hours 90 → about $3.84/hr usable in this sketch

That last line is the warning. A $5 headline can become an under-floor life if you ignore friction. Fix the quote or the scope. Do not "solve" it by recommending $4/hr work.

Common mistakes

1. Spending the invoice the day it says "paid." Wait for landed cash.
2. Treating blog fee percents as current law. Check the rail; date your note.
3. Skipping tax reserve because the month feels tight.
4. Ignoring platform cuts on marketplaces.
5. Comparing friends' rates without comparing their rails and admin load.
6. Cutting below $5/hr to "make the client happy" after a fee shock.
7. No payout folder. Matching later becomes guesswork.

Example: two rails, same headline rate

Sam quotes $8/hr to two clients for similar packages. Client A pays on a rail Sam verified last week. Client B insists on a path with heavier conversion and cash-out friction. Same headline rate. Different take-home. Sam either adjusts Client B's quote, changes rail, or slims Client B's scope. Sam does not pretend both deals are equal because the hourly number matches on paper.

Comparison table

How Salag helps

• Rate Calculator: floor that survives real costs
• Rate Negotiator: scripts when landed pay breaks the deal
• Rate Evolution Monitor: track raises beside fee checks
• Work Receipt Generator: proof beside payout matching
• Reads: Wise to GCash fees, 8% tax overview, $5 floor why

When to re-run the worksheet

• Rail fee email or in-app change
• New platform cut
• Big FX swing
• New retainer with heavier chat load
• Quarterly review habit (six-month rate review process for the bigger cadence)

Definitions

Gross rate: Agreed pay before friction.

Landed cash: Money available after rail and conversion.

Usable cash: Landed cash minus your tax reserve habit.

Lived hourly take-home: Usable cash divided by all hours spent, including unpaid admin.

Matching invoices to payouts (so the worksheet stays honest)

Landed cash mistakes often start as labeling mistakes. The invoice says "October retainer." The Wise email says a bare amount. GCash shows a reference you do not recognize. Three weeks later you cannot rebuild take-home without guessing.

Fix the labels:

• Put the invoice number in the payment reference when the rail allows it
• Save payout screenshots in the same client folder as the invoice PDF
• Note the date landed, not only the date the client clicked pay
• If a payment covers two invoices, write the split in your log the same day

For dispute-prone clients, pair this with Document Work Clients Can't Dispute. For formal local records, see Official Receipt for Freelancers. Clean matching does not raise your rate by itself. It stops you from planning on money that is still in limbo.

Platform cuts vs direct clients

Marketplace or agency cuts change take-home even when the "client rate" looks fine on a job post.

Teaching pattern (verify your platform's live schedule; not a forever fee table):

• Posted rate to you: illustrative $8/hr
• Platform example cut: check current percent
• After cut, before rail: lower
• After rail + reserve + unpaid admin: maybe near or under floor

If the lived number fails Salag's $5/hr floor, you either negotiate a higher gross, move toward direct clients with proof, or decline. Do not "make it work" by coaching yourself down to $4/hr.

Direct clients still have rails. Direct is not automatically higher take-home. Direct is only clearer when invoices, scope, and payout folders are tight.

Currency risk sits beside rail fees

Your quote may be USD. Your life is PHP. A quiet month of FX movement can shrink landed pesos without anyone changing the contract. That is not a cue to panic-cut rates. It is a cue to:

• Rebuild the COL floor (COL vs market)
• Decide if the package still clears the floor
• At review time, raise, hold, or slim scope

Read currency risk as process, not as a reason to accept underpaying posts.

Mini SOP: first payout with a new client

1. Agree rail and currency in the same thread as scope.
2. Send a test-friendly invoice for the deposit or first cycle (invoicing guide).
3. When funds land, screenshot every hop.
4. Fill the take-home worksheet and date it.
5. If lived hourly is under floor, message before cycle two. Do not wait six quiet weeks.

Deposit + rail confirmation script

ScriptCopy

Hi [Name], before I start the full week, please confirm payment via [rail] to the details on Invoice [Number]. Once the deposit lands and I reconcile take-home against my $5/hr floor after fees, I'll unlock the remaining tasks on the list. If your team must use a different rail, tell me now so I can re-quote with the right fee buffer.

Final thoughts

Freelance rate vs take-home in the Philippines is a worksheet with a date, not a vibe. Quote so $5/hr+ still makes sense after fees and admin. Verify Wise, PayPal, and GCash live. Keep tax questions with proper guidance. When landed pay breaks, raise rate, change rail, or cut scope. Do not train yourself under the floor.