Get Paid in Dollars, Live in Pesos: The 2026 Manual
You get paid in dollars and live in pesos. Each new client, each blue-rate spike, each monotributo cuota forces you to recalculate the budget and wonder if rent still fits. This is the concrete operating manual that freelancers in Buenos Aires, Mexico City and Bogotá use to keep USD income from evaporating into pesos: a fixed planning rate, the USD envelope rule, a dollar-denominated tax set-aside, and a 30-minutes-a-month weekly routine.
I get paid in dollars and split my life between Florianópolis and Buenos Aires since 2019. I built Capi exactly because no US app models this flow well. What follows is not theory; it is the operating procedure that holds when the dollar moves, monotributo categories shift, and the client pays on the 13th instead of the 5th. If you only have time for one section, jump to the callout in Step 2 (the USD envelope rule); if you want the routine, skip to the step-by-step at the end.
How do you get paid in dollars and live in pesos without the budget breaking?
Lock a fixed planning rate once a month and stop chasing the daily quote. Split every payment into three USD envelopes: monthly spending (40-55%), taxes (15-30%), reserve (the rest). Convert to pesos only what you will use in 30 days. Log every expense in the currency it actually happened in. Recalibrate at month close. The system is the same across the three countries; only the percentages and the conversion route change.
The thing that breaks the budget is almost never the income. It is the decision, repeated 30 times a month, of staring at today's quote and rewriting plans in pesos. The system cuts that decision: it pulls it off the daily calendar and reserves it for month close. What changes is the noise, not the income.
Why do US budget apps fail when you live in pesos?
YNAB, Monarch, Copilot, Simplifi and EveryDollar all assume a single stable currency and a Plaid-style bank aggregator connection. In Argentina, Mexico and Colombia, that model breaks in three places: Plaid has almost no native coverage outside a handful of big banks, the exchange rate moves 8-30% a year, and the actual freelancer flow runs through Wise, Payoneer, Bybit P2P or crypto wallets. No US app treats that flow as a first-class citizen.
The practical consequence is that you end up doing two bad things at once: you use an English-language app to spend in pesos with made-up conversion at input, and you keep a side spreadsheet for the real numbers. That side spreadsheet is the proof that the system does not fit. Capi does not solve everything, but it removes the modeling problem: it stores native currency and renders in any. My earlier post walked the wider two-currency setup; this is the operating manual.
What is the USD envelope rule?
The full payment lands in USD and is split into three envelopes that stay in dollars: monthly spending (40 to 55% by country), tax set-aside (15 to 30% by regime), reserve and savings (the rest). Only the spending envelope moves to local currency, and only the amount you will use within 30 days. The other two envelopes live in USD until you actually need them. Local inflation never touches them.
The envelope rule in one line. Convert to pesos only what you will spend in pesos in the next 30 days. The rest of the payment stays in USD in Wise, Payoneer, a USDC wallet or whatever you use. Converting the entire payment on the day you get paid is the single decision that destroys the most LATAM freelancer wealth in 2026.
The percentages depend on the country and the tax regime. In Argentina, a freelancer under monotributo F-H usually needs 15 to 20% for taxes and 50 to 55% for monthly spending; the rest is reserve. In Mexico under RESICO, the tax set-aside drops to 5-10% thanks to the 1-2.5% rate on gross income, so the spending envelope can grow to 60% if rent supports it. In Colombia, withholding for services (10% declarante, 11% non-declarante) is already deducted by many local clients, but if you bill from abroad, you build the set-aside yourself.
How do you set tax money aside without inflation eating it?
The tax set-aside stays in dollars until the moment of payment. A Wise USD account, the USD balance on Payoneer, or a stablecoin like USDC in a safe wallet all work. When the tax bill comes due (Argentine monotributo, Mexican RESICO, Colombian retención), you convert only the exact pesos needed and pay. Local inflation between earning and paying does not touch that money because it was never in pesos.
Argentina's monotributo tech, which got media sanción in Diputados in 2025 and is still under discussion in 2026, points in exactly this direction: three categories for service exporters (up to USD 10,000, 20,000 and 30,000 annual) that let you bill and keep dollars without forced conversion at the official rate. While the regulation is pending, regular monotributo still requires peso billing at the official rate, but the logic of the USD envelope for taxes does not change: only the exchange rate you pay at the end does.
For Mexico under RESICO, the effective 1-2.5% rate on gross income makes the set-aside lighter than in Argentina. Even so, keeping it in USD avoids the classic freelancer trap: you got USD 4,000 on the 3rd, converted everything on the 5th, and discovered on the 15th that the peso slipped and the peso set-aside no longer covers the annual quota. For Colombia, local client withholding covers most of it; what you build in USD is the difference, plus health (12.5%) and pension (16%) on 40% of the IBC.
What exchange rate do you log each expense at?
Every expense is logged in the currency it actually happened in. If you paid rent by peso transfer, log it in pesos. If you paid for GitHub Copilot on a USD card, log it in USD. The monthly summary is viewed in a single currency you pick: pesos for the in-pocket view, USD to compare against income. Do not convert on input; convert only when summarizing.
That rule looks obvious and almost nobody follows it. Most apps force you to pick a base currency at account creation and convert everything on the fly using a rate the app invents. Result: the ARS$3,500 coffee shows as USD$2.46 today, USD$2.38 tomorrow, USD$2.52 next week, and the May report changes every time you open the app. Logging native and deferring conversion to the summary removes that noise.
| Platform | Stores native currency? | Models dual view? | Fits this manual? |
|---|---|---|---|
| YNAB | No (one base currency per budget) | No | Poor for LATAM with USD |
| Monarch | Limited (multi-currency on Premium, auto-converts) | Partial | Useful when bulk is USD |
| Mobills | Yes, but BRL-focused | Limited | Good for Brazil, poor for ARS/MXN |
| Spendee | Yes, multiple currencies per wallet | Reports in base currency | Works for logging |
| Capi | Yes, native per transaction | Yes, swap on demand | Designed for this flow |
What does Capi do differently with dual currency?
Capi stores every transaction in its native currency (ARS, MXN, COP, USD, BRL, EUR) and never converts on input. When you ask for the report, you say which currency you want and Capi applies the fixed planning rate you set or the month average. The same dataset comes out in pesos if you asked for pesos, in dollars if you asked for dollars. The dual view is native, not a patch over a single-currency schema.
Internally this comes from two pieces. What the team calls the currency view lets each category and each budget hold a currency different from the ledger's; the rate table stores your fixed planning rate per month, so last month's report does not shift when the blue rate moves today. Together they mean you can say "show me May in pesos" and "show me May in dollars" without rewriting anything. For the USD envelope manual, that property is central.
Pricing for heavy use is Capi Core at USD 9.90/month or USD 69.90/year (about USD 5.83/month billed annually). There is a free tier of up to 30 transactions a month to test the flow. Capi Together adds a shared couple account for USD 99/year (USD 4.13/person/month). The free tier already supports native currency and dual view; paid plans add higher limits, unlimited receipt photos and the Ask Capi natural-language chat over your own history.
What does the week-to-week routine look like?
Monday (payment day): the moment the notification fires, split the amount into three USD envelopes using the percentages you decided. Tuesday to Friday (logging): log expenses as they happen, in the currency they happened in, no conversion. Sunday (review, 10 minutes): check the spending envelope in pesos and the tax envelope in USD. Month close (recalibrate, 20 minutes): compare the fixed planning rate against the actual month average, adjust set-aside percentage if it missed.
- Monday, payment. USD 3,200 lands in Wise. Split immediately: 50% spending (USD 1,600), 20% taxes (USD 640), 30% reserve (USD 960). The spending envelope moves to pesos via Bybit P2P at the day's rate (say ARS 1,412); you now have ARS 2,259,200 for the month. The other two stay in Wise USD.
- Tuesday to Friday, logging. Coffee 3,500 pesos, Uber 4,200, GitHub Copilot 10 USD, Netflix 4,490 pesos, supermarket 28,000 pesos. Each in its native currency. Capi (or any app that respects native currency) stores them as-is.
- Sunday, 10-minute review. Look at the spending envelope summary in pesos: you spent ARS 540,000 this week, ARS 1,719,200 left for the next three. Burn rate inside plan. The tax envelope sits intact at USD 640.
- Month close, recalibrate 20 minutes. Fixed planning rate: 1,380. Actual month average: 1,405. Gap 1.8%. Under the 8% threshold, keep it for next month. Set-aside: the monotributo category G services cuota for May 2026 is ARS 197,108 (under the scales active since February through July). USD 640 at the day's rate is ARS 904,000, enough for more than four months; the surplus moves to reserve.
Thirty minutes a month total for the system. The rest is just logging what already happened, which is not system work; it is attention work. If you spend more than an hour a month recalibrating, the problem is somewhere else: income varies too much for fixed percentages, the planning rate is mis-calibrated, or three clients pay in different currencies and you did not split sub-envelopes by client.
When does this system NOT work?
Three cases break the manual. You earn in pesos and want to save in dollars: the flow runs backwards, a different system fits. Income is highly variable month to month: fixed percentages collapse, build a 2-3 month buffer fund first. General tax regime with VAT and complex withholdings: the fixed USD set-aside falls short, move to a monthly-computed percentage with your accountant.
There is a fourth quieter case: when a meaningful portion of income comes in crypto. The envelope rule still holds, but the tax set-aside needs an extra cushion for price risk between earning and paying. The practice that I see working is converting that portion to USDC the moment it arrives and parking it there until tax day. Crypto-to-crypto, no peso conversion until the last second. The multi-currency budget post for expats covers the crypto flow in more detail.
Frequently asked questions about getting paid in dollars and living in pesos
How do you get paid in dollars and live in pesos without the budget breaking?
Lock a fixed planning rate once a month (do not chase the daily rate), split each payment into three USD envelopes (monthly spending, tax set-aside, reserve), convert to pesos only what you will use in 30 days, log every expense in the currency it actually happened in, and recalibrate the planning rate at month close. Three countries, same system; only the envelope percentages and conversion route change.
Why do US budget apps fail when you live in pesos?
Because YNAB, Monarch, Copilot, Simplifi and EveryDollar assume a single stable currency and a Plaid-style bank aggregator connection. In Argentina, Mexico and Colombia, Plaid lacks native coverage for most banks, the exchange rate moves 8 to 30% a year, and the actual freelancer flow uses Wise, Payoneer, Bybit P2P or crypto wallets. No US app models that flow as a first-class citizen.
What is the USD envelope rule?
The full payment lands in USD and is split into three envelopes that stay in dollars: monthly spending (40 to 55%), tax set-aside (15 to 30%), reserve and savings (the rest). Only the spending envelope is converted to local currency, and only the amount you intend to use within 30 days. The other two envelopes live in USD until needed or moved to investments.
How do you set tax money aside without inflation eating it?
The set-aside stays in dollars (Wise USD account, Payoneer USD balance, or a stablecoin like USDC in a safe wallet). When the tax payment is due, you convert only the exact amount to pesos. For Argentine monotributo, Mexican RESICO or Colombian retención, the effect is the same: the dollar protects the real value of the set-aside against inflation or devaluation between earning and paying.
What exchange rate do you log each expense at?
Every expense is logged in the currency it actually happened in. If you paid in pesos with a local card, it goes in pesos. If you paid a USD international service or subscription, it goes in USD. The monthly summary is viewed in a single currency of your choice (pesos for the in-pocket view, USD to compare against income). Do not mix currencies in a single row or convert on the fly; that adds noise.
What does Capi do differently with dual currency?
Capi stores every transaction in its native currency (ARS, MXN, COP, USD, BRL, EUR), never converts on input, and renders the report in whichever currency you ask for in the moment. Say "show me May in dollars" and it uses the fixed planning rate you set or the month average. Say "show me May in pesos" and the same dataset comes out in pesos. The dual view is native, not a patch on top of a single-currency schema.
What does the week-to-week routine look like?
Monday (payment day): USD lands, split into three envelopes the moment the notification fires. Tuesday to Friday: log spending as it happens, no conversion. Sunday: 10-minute review of the spending envelope in pesos and the tax envelope in USD. Month close: recalibrate the planning rate and adjust the set-aside percentage if needed. About 30 minutes per month for the system; the rest is just logging what already happened.
When does this system NOT work?
When you are paid in pesos and want to save in dollars (the flow runs backwards and a different system fits). When income varies a lot month to month and fixed percentages collapse (build a 2-3 month buffer fund first). When you operate under a general tax regime with VAT and complex withholdings (the fixed USD set-aside falls short; move to a percentage computed monthly with your accountant). The manual does not apply as-is in those three cases.
A manual that fits inside Telegram.
Capi lives inside Telegram. Log in the currency the expense actually happened in, ask for the summary in whichever currency you want, and the dual view comes for free. Free for up to 30 transactions a month; Core at USD 9.90/month or USD 69.90/year.
Try Capi free on Telegram →