In this example, Ana, Ben, and Chris take a weekend trip and use EUR and RSD. The goal is not to calculate one artificial grand total. It is to preserve who paid, who benefited, and what remains in each currency. The numbers are fictional and intentionally simple so the recording pattern is easy to reuse.
The shared trip and its first bookings
Ana pays 240 EUR for accommodation shared equally by all three. Ben pays 60 EUR for airport transport shared by Ana and Ben because Chris arrives separately. The ledger records the payer and beneficiaries for each expense, producing different EUR shares without manual debt calculations.
Local purchases remain in their original currency
Chris pays 9,000 RSD for a group dinner, while Ana pays 3,000 RSD for museum tickets used by Ana and Chris. Those entries create a separate RSD balance. No guessed exchange rate is applied, and the EUR accommodation balance remains unchanged.
A repayment closes the debt it actually pays
Ben transfers Ana his EUR share after the trip, so the group adds a direct EUR repayment from Ben to Ana. Chris pays Ana separately in EUR and later settles the RSD balance with Chris. Each transfer is recorded in its real currency rather than rewriting the original purchases.
What the final record explains
Every traveller can see the accommodation, transport, dinner, and museum entries plus the completed repayments. If a number is questioned, the source expense remains visible. The example ends with clear currency-specific balances and no spreadsheet formulas or shared account.