Most receipt advice quietly assumes one currency — the one your books are kept in. But the receipts that actually go missing are the ones that don't match: the conference registration billed in dollars, the hotel in pounds, the SaaS subscription that renews in USD no matter where you live, the cab fare from a client trip abroad. They arrive in a currency your accounting isn't in, they need a conversion you haven't done yet, and so they sit — and a foreign receipt that sits is a foreign receipt you lose. This is about how receipt OCR handles them, what it honestly can't do, and the small set of things you need to keep so the conversion is somebody's two-minute job later instead of a guess.
Why the foreign receipt is the one you lose
A receipt in your home currency is easy: read it, file it, done. A foreign one carries a second job you can't finish on the spot. You can't log it cleanly until you've converted it, converting it means finding the rate for that day, and "I'll do that later" is where it dies. By the time you remember, the trip is months gone, the slip has faded, and you're reconstructing an amount from a card statement that already converted it for you — at the card network's rate, with a markup, which may not be the rate your accountant should use.
So the foreign receipt fails for the same reason the domestic one does — deferred work — just with an extra step bolted on. The fix is the same shape too: capture the evidence now, while it's in your hand, and push the one genuinely-later task (the conversion) to the one moment it's cheap to do — at the keyboard, with your books open, instead of at the counter.
Does OCR even read a foreign receipt?
Mostly, yes — and this surprises people. Receipt OCR is two jobs: reading the characters, and working out which number is the total. The reading step doesn't care what currency you're in. The digits 2, 4, 9, 9 look the same whether the symbol in front of them is a dollar, a pound, a euro, or a rupee. So OCR pulls the amount off a foreign slip about as well as it does a domestic one, give or take the usual thermal-fade and layout problems that have nothing to do with currency.
Where it gets less reliable is the symbol and the format, not the number. Decimal commas instead of points (1.234,56 in much of Europe), a currency code printed as text three lines from the total, a symbol shared by several currencies — these are exactly the kind of ambiguous, no-fixed-layout cues that the extraction step finds hard. The honest summary: trust OCR to draft the figure, and read the currency off the receipt yourself. It's the one field a human eye settles instantly and a parser guesses at.
That's why Starlog runs OCR to pre-fill the store and the amount, and leaves every field editable. The amount field doesn't force a home currency on you — type the figure exactly as the receipt prints it. The number is drafted; the judgement stays yours.
The thing nobody tells you: keep three things, not one
Here's the part that actually matters, and it's not about the app. For a foreign-currency expense to survive contact with your accountant — or, if it ever comes to it, a tax authority — you need to be able to show three things, and most systems keep one and lose two:
- The original amount, in the original currency. Not the converted figure, and not the number your card statement shows after its own conversion and markup. The amount as the merchant charged it, in the currency they charged it in.
- The source document itself. The actual receipt or invoice — the evidence that the expense happened, that it was business, and what currency it was in. A converted number in a spreadsheet with no image behind it is a claim, not a record.
- The rate and date you converted at. Which day's exchange rate you used, and ideally where you got it. This is the piece that turns "trust me, it was about $250" into a defensible line your accountant can reconcile.
A spreadsheet row usually keeps only the converted total and throws away the other two. A card statement keeps its own converted number and no image. The whole point of capturing the receipt properly is to not be the person reconstructing all three from memory in April.
How to actually do it, per receipt
The workflow is short, and it front-loads the only part that's hard to redo later — getting the evidence — while deferring the conversion to when it's easy:
- Capture it on the spot, in its own currency. Photograph the receipt the moment you have it, let OCR draft the amount, and record it in the currency it was printed in. Don't try to convert at the counter — you'll get the rate wrong and lose the original figure. Note the currency in the receipt's notes if it isn't obvious from the image.
- Let the image file itself somewhere durable. This is the load-bearing step. The source document needs to outlive the trip, the phone, and the faded paper. In Starlog it uploads to your own Google Drive, into the same per-business year-and-month tree as everything else, so the foreign receipts aren't a separate pile — they're filed next to the domestic ones, image intact.
- Tag it to the trip or project while you remember. A foreign expense is almost always part of something — a conference, a client visit, a specific job. Group it into that report now, so the whole trip totals itself and you're not hunting for "that hotel in March" later.
- Convert at book time, in one pass. When you reconcile — monthly, quarterly, or with your accountant — convert the foreign ones together, looking up each day's rate once. Because the original amount and the image are both still there, this is data entry, not detective work.
A note for US and India
The reason to keep the original currency rather than the card-statement number is the same on both sides, even though the rules differ.
In the US, business expenses on a Schedule C are reported in dollars, so a foreign expense has to be converted — and the IRS generally expects you to use the exchange rate that applies when the expense is incurred (a consistent, defensible daily rate), not whatever your card issuer happened to charge. Keep the original-currency amount and the receipt, and your CPA can apply the right rate cleanly.
In India, foreign-currency expenses fold into your books in rupees, and if you're claiming GST input tax credit the document rules are strict — a payment confirmation isn't a tax invoice, and most foreign vendor receipts won't carry GST you can claim at all. Imported services can bring their own reverse-charge and conversion questions. Keep the source document and the original amount; let your CA sort the treatment.
Either way the same two artifacts — original amount, original document — are what make the conversation with your accountant short. As always with anything tax-specific, confirm the treatment for your situation with your CA or CPA; the job of the workflow above is just to make sure you still have the evidence when you ask.
What Starlog does and doesn't do here
To be straight about it: Starlog is not a foreign-exchange engine. It doesn't fetch live rates, it doesn't auto-convert your dollar receipts into rupees or your pound receipts into dollars, and there are no cross-currency aggregate totals. What it does is the part that's actually hard to get back later — it reads the amount off the slip, lets you record it exactly as printed in whatever currency that is, and preserves the original image in your own Drive, grouped by trip and ready to export to your accountant. The conversion is a known, easy task you (or they) do once, at book time. Losing the receipt is the unrecoverable one, and that's the one this prevents.
The takeaway
Foreign-currency receipts go missing not because they're hard to read but because they carry an unfinished task — the conversion — that you defer until the evidence is gone. Break the two apart: capture the document and its original amount the moment you have it, file the image somewhere durable, and convert later in one pass with the rate for the day. OCR will draft the number for you; your job is to read the currency and keep the original. Do that, and a receipt in the wrong currency stops being a lost deduction and becomes just another line your accountant can reconcile in two minutes.