DEV Community

Cover image for The Spreadsheet I Built to Compare Wise, Payoneer, and SWIFT: A Lahore Analyst's Notes on Getting Paid
Gruv AI
Gruv AI

Posted on

The Spreadsheet I Built to Compare Wise, Payoneer, and SWIFT: A Lahore Analyst's Notes on Getting Paid


I am a data analytics consultant in Lahore. I build dashboards and forecasting models, mostly for SaaS companies in the United States and the UK, and occasionally for a regional bank that pays me in PKR and reminds me, every quarter, why I prefer dollar invoices. I have been doing this for five years. For most of those five years I was vaguely losing money on the way payments arrived in my account, and only in the last eighteen months did I sit down and quantify how much.

The trigger was a $7,200 invoice from a Boston client that, by the time it landed in my HBL account, had become approximately $6,830 of usable funds after the foreign exchange margin, the correspondent bank fee, and a small charge I never fully understood that my bank labelled "remittance handling." That is a 5.1 percent total cost on what should have been a clean transfer. I had been telling myself for years that the cost of receiving money was a fixed unavoidable tax. It is not. It is a choice, and I had been making the wrong one.

What I did, eventually, was build a spreadsheet. The spreadsheet had three columns, one each for Wise, Payoneer, and direct SWIFT into my Pakistani bank. It modelled the round trip from invoice to PKR-in-hand, on three representative invoice sizes: $1,500, $5,000, and $12,000. It included not just the visible fee but the exchange rate margin, which is where most of the real cost hides. I want to share what I found, because I suspect a meaningful number of Pakistani freelancers are paying the same hidden tax I was, and have not run the numbers.

For the $5,000 representative invoice, here is what the spreadsheet showed.

Direct SWIFT into my HBL account, with the client's bank using Citi as the correspondent: total cost, including the $20 outgoing wire from the client's side, a $25 correspondent fee, and an exchange margin of roughly 2.3 percent applied by HBL when converting to PKR, came to approximately $160. That is 3.2 percent of the gross. The funds were available in PKR in three working days. The receipt was a Proceeds Realization Certificate, which is what State Bank wants for documenting foreign currency inflows.

Payoneer, with the client paying into my Payoneer USD balance and me transferring to my HBL account: receiving fee from the US client was nominally free for ACH, but Payoneer's conversion margin to PKR ran around 2 percent, and there is a small withdrawal fee. Total cost was approximately $115, or 2.3 percent. Time to PKR was about two days. Payoneer issues its own documentation that State Bank has generally accepted, though some banks ask for additional paperwork.

Wise, with the client paying USD into my Wise account and me converting to PKR and withdrawing: Wise's conversion fee on USD to PKR is published and was around 0.55 percent at the time I tested, with a small fixed component. Total cost was approximately $42, or 0.84 percent. Time to PKR was under twenty-four hours for most transfers. The complication is documentation. Wise's transaction record is not always accepted by Pakistani banks in the same form as a SWIFT PRC, and the regulatory treatment of Wise inflows into Pakistan has changed twice in the past three years.

What helped me think through the documentation side, which is the part most fee comparisons skip, was [a guide to receiving USD payments into a Pakistani bank account. It covers the State Bank requirements, the Proceeds Realization Certificate, and what counts as adequate documentation when the inflow comes through a fintech rather than a direct SWIFT wire. I had been ignoring this question and hoping it would not catch up with me. It would have, eventually.

For the regulatory comparison between the fintechs themselves, a comparison of Wise and Payoneer for Pakistani freelancers was the cleanest writeup I found. It does not just compare fees. It walks through the operational reality of each platform under current Pakistani regulations, including which one is more reliable for larger invoices and which one is less likely to flag your account for review. The piece changed how I structure the question for myself. The right answer, for me, turned out to be different at different invoice sizes.

What I do now, after eighteen months of running the spreadsheet, is route invoices by size and client preference. Invoices under $3,000 go through Wise, where the proportional fee saving is largest. Invoices between $3,000 and $10,000 go through Payoneer, which gives me the best balance of fee and documentation. Invoices above $10,000, and any from clients whose accounts payable team prefers traditional wires, go through direct SWIFT, where the fee is highest in percentage terms but the documentation is unambiguous and the PRC arrives without me having to ask twice.

The total I have saved over the last twelve months, by my own measurement, is approximately $2,400. That is roughly a month of expenses for my household. It is also, for context, more than I spend in a year on the tooling I use to do the actual analytics work. The lesson, which feels obvious in retrospect, is that the cost of payment infrastructure is not a small detail. It is a meaningful line item in a freelance P&L, and it deserves the same analytical attention I give to a client's customer acquisition cost.

If you are reading this from somewhere with similar friction, the spreadsheet is the work. Three columns, three invoice sizes, every fee made visible including the exchange margin. An afternoon of work. A meaningful change in net income. The arithmetic, as in most things, rewards the person who actually does it.

Top comments (0)