Why multi-currency tracking is sensitive
Debt tracking is already detailed in one currency. With TRY, USD, EUR, GBP, or local travel currencies, small assumptions can become expensive. A friend may owe euros, a hotel may be paid in dollars, and a freelancer may price work in USD while paying expenses locally.
The question is not only how much is owed. It is which currency, which exchange-rate logic, which date, and how the debt will be settled.
Define the currency at the start
The most common mistake is discussing currency later. If someone says they will send 100 dollars for a hotel payment, will the debt remain in USD or become the local-currency equivalent on the payment date? Both are valid, but the expectation must be recorded.
Managing exchange-rate differences
Three methods are common: keep the debt in the original currency and settle in that currency, convert it to local currency on the date it was created, or use a rate agreed by both sides. A short note prevents confusion later.
Travel and group spending
International travel creates mixed records: flights in local currency, hotels in EUR, transport in another currency, card statements converted by the bank. The safest habit is to record the original currency and add local equivalent only when needed.
Freelancers and small businesses
Freelancers and service businesses may invoice or agree in USD or EUR while paying local expenses. Sudeb helps keep each receivable visible by client, currency, amount, payment status, and remaining balance.
Same person, multiple currencies
A person may owe you in local currency while you owe them in USD. These should not be netted automatically unless both sides agree on a rate. Separate records make the relationship clearer.
How Sudeb helps
Sudeb keeps debt and receivable records tied to people, amounts, currencies, notes, and payment status. Multi-currency clarity reduces exchange-rate arguments and keeps daily financial relationships easier to manage.