If you freelance for clients who pay in dollars while your rent, food and EMI are in rupees, track every entry in the currency you actually paid or received, and view the totals in one base currency. The rate used for each entry should be saved with it, so a month's picture does not shift when the market does. Here is how to set that up and read it.
Why gig income makes this harder
A salaried person gets one credit a month. A gig worker gets irregular payments from different platforms, sometimes minus a platform fee, sometimes in a different currency from the one the bank finally credits. Costs, meanwhile, land in rupees on specific dates. A single total at the end of the year hides the one thing you need: which months were thin.
Choose the base currency first
Pick the currency you think in, which for most people living in India is the rupee. In SpendixAI the base currency has to be chosen before importing, and it cannot be changed once transactions exist. Each expense can be in its own currency, and totals appear in the base currency using the rate saved with each transaction.
What to record for each payment
| Item | Record this | Why |
|---|---|---|
| Client invoice paid | Amount in dollars as invoiced | Matches the invoice you sent |
| Platform fee | Separate expense in dollars | Shows the real cost of the platform |
| Credit to your bank | The rupee amount received | The truth for cash flow |
| Software subscription billed in dollars | Amount in dollars with the card rate | Shows what the card really charged |
| Rent and groceries | Rupees | No conversion needed |
A worked month with hypothetical numbers
Say a designer invoices $900, the platform keeps $90, and the bank credits ₹68,040 after conversion (810 dollars at the assumed rate). A $20 design-tool subscription is charged to a card as ₹1,700. The platform fee is a cost of $90; at the saved rate of ₹84 per dollar (an assumed figure for the example), that is ₹7,560. The money you actually received is ₹68,040, and fee plus tool costs come to ₹9,260 (7,560 plus 1,700).
Now add rupee spending of ₹38,000 for rent, food and transport. Rupee outflow is ₹47,260 (38,000 plus 9,260) against ₹68,040 received, leaving ₹20,780. In a month with no invoice, the same ₹47,260 would simply be a deficit. That is the lumpy pattern a base-currency view makes visible.
- Record the payment on the date it is received, not the invoice date
- Add the platform fee as its own line
- Add the rupee credit so your bank account reconciles
- Review the foreign-currency spend report at month end
What about tax and compliance?
Reporting foreign income, conversion rules and any related obligations are matters for your CA, and rules and limits change. Your job is a clean record: invoice, platform statement, bank credit and the rate used, all attached to the entry. SpendixAI keeps receipts with their transactions and estimates GST inside spending, but it does not do GST filing or tax computation.
How do you plan around lumpy income?
Look at the last six months of rupee inflow and note the weakest one. If your fixed outflow is ₹47,260 and the weakest month brought in only ₹30,000, the shortfall of ₹17,260 is the size of the buffer that would have kept you comfortable. That figure comes from your own history, not from a rule of thumb, which makes it far more useful. Revisit it every quarter.
A monthly routine
- Import the bank statement and review the rows before saving
- Add foreign-currency entries by hand with the currency stated
- Tag platform fees consistently
- Set aside a fixed share of each credit for a thin month, a rule you choose yourself
- Compare this month's rupee outflow with the last three
Useful ideas start with a clearer picture of your own spending.
Explore your reports


