Export Shared Expenses for Taxes & Reimbursements

To export shared expenses for taxes, do three things in order: flag which items are reimbursable or deductible as you record them, run a ledger report filtered to the date range and category you need, then export it as a CSV with amounts, dates, currency, and who paid. The mistake most people make is leaving all of this to April, trying to reconstruct a year of shared dinners, trips, and utility bills from memory and a pile of screenshots. If you flag expenses at the moment you enter them and let the app keep a running ledger, the tax export is a two-minute download instead of a two-weekend reconstruction. This guide covers the reimbursable-flag workflow, what belongs in a tax-ready CSV, how multi-currency and split amounts are handled, and how to hand it off to an accountant or expense system.

Flag reimbursable expenses when you enter them, not at tax time

The single biggest time-saver is deciding reimbursable or not at the moment the expense happens, while you still remember the context. A $92 client dinner, a $340 flight for a work trip, the co-working day pass — mark them the day you record them.

In Split The Bill, every bill and personal-ledger entry carries a category and a note field. Use a consistent category for anything you'll claim — Business, Reimbursable, or a client name — and the note field for the why (who the dinner was with, which project the trip was for). That context is exactly what a tax authority or a finance team asks for later, and it costs nothing to capture in the moment.

Why this matters for shared expenses specifically: when three people split a $180 work dinner and only your $60 share is deductible, you need the split math and the flag on your portion. Recording the flag at entry time means the export already knows your $60 is the reimbursable number, not the $180 total, and not an even $90.

What a tax-ready expense export actually needs

An accountant or expense system will reject a CSV that's just "description, amount". A defensible export needs enough columns to reconstruct each line without asking you a follow-up question:

- Date: the transaction date, in ISO format (YYYY-MM-DD) so it sorts correctly. - Description: what it was, plus the note (client, project, purpose). - Category: your deduction bucket (meals, travel, supplies, utilities). - Amount: the number you are responsible for, not the group total. - Currency: the original currency code, especially for travel. - Paid by: who fronted the money, which matters for reimbursements. - Your share: for split bills, the portion attributable to you.

Split The Bill's CSV export includes these fields so a line reads unambiguously: `2026-03-14, Client dinner (Acme project) with J. and R., Meals, 60.00, USD, You, 60.00`. That single row tells the whole story: the date, the purpose, the category, and that your deductible amount is $60 even though the table receipt was $180.

Run a ledger report, then filter before you export

A ledger report is a chronological list of every expense with a running total, the same shape a bank statement has. It's the format accountants think in, and it's the right starting point for a tax export.

Filter before you download, not after. Pulling your entire year and then hand-deleting rows in a spreadsheet is where errors creep in. Instead, narrow the report first:

- By date range: the tax year, or a quarter for estimated-tax filings. - By category: just Business, or just Travel, depending on what you're claiming. - By group: if you keep a dedicated group for work trips or a specific client, export that group's ledger on its own.

The personal spending ledger is the right tool when the deductible expense is entirely yours (a solo business lunch, a subscription you pay for). For shared expenses, run the report at the group level so the split math is already applied and your line shows your share, not the full bill. Either way, the export reflects exactly what the on-screen report shows: filter it down to what you'll actually claim, confirm the total, then download.

Handle split amounts and multi-currency correctly

Two things trip people up on shared-expense tax exports: splits and foreign currency. Both have to be right or the numbers won't reconcile.

Splits: when you deduct a shared expense, you can only claim your own portion. If a $180 dinner was split three ways and your share was $60, the export must show $60, not $180, and not a naive third if the split wasn't even. Because Split The Bill computes every split with Python (the app never lets the AI do arithmetic), the per-person amounts in the export are the exact figures from the split method you chose: equal, exact, by-items, percentage, by-shares, or by-adjustment. Whatever the receipt actually apportioned to you is the number that lands in the CSV.

Multi-currency: a trip that mixed euros, dollars, and dinars needs both the original amount and a consistent conversion for the return. Split The Bill locks an FX rate at the time of the transaction, so a €40 taxi recorded in March keeps its March rate. It won't silently re-value if the exchange rate moves before you file. The export carries the original currency code alongside the amount, so you (or your accountant) can present both the source figure and the converted total, which is what most tax authorities want for foreign expenses.

Separate reimbursements from tax deductions: they're not the same

It's worth being precise, because mixing them up creates real problems.

A reimbursement is someone paying you back: your company covering a flight you fronted, or a housemate settling their share of the utility bill. The money moves and the balance goes to zero. What you want here is a settle-up report: who owed what, what got paid, and what's outstanding. Split The Bill tracks partial payments, outside-the-app settlements, and cross-currency settlements, so the reimbursement record shows the real payment history, not just the original split.

A tax deduction is a business expense you report to reduce taxable income. You keep the cost, you don't get paid back, but it lowers what you owe. Here you want the ledger/category report filtered to deductible categories.

The practical rule: export reimbursements from the settle-up view, deductions from the ledger view. A work trip can generate both: the portion your employer pays back (reimbursement) and the portion you personally absorb and deduct. Keeping them in separate exports keeps your books clean and stops you from accidentally deducting money someone already refunded you.

A month-by-month workflow that makes tax season a non-event

The people who dread tax season are the ones reconstructing a year in one sitting. The fix is a small monthly habit:

As you go: record shared expenses when they happen (photo the receipt, or add via chat), set the category, and flag anything reimbursable or deductible in the note. Thirty seconds per expense.

End of each month: run the ledger filtered to your deductible categories for that month and glance at the total. Catch a mis-categorized item now, while you remember it, instead of in April.

Each quarter: if you pay estimated taxes, export the quarter's ledger CSV and hand it to your accountant or drop it into your bookkeeping tool. The numbers are already reconciled because the splits and FX were locked at entry time.

At year end: export the full tax-year ledger and the settle-up report. Two CSVs, one for deductions, one for reimbursements, and you're done. No screenshot archaeology, no "was this the dinner with the client or the one with friends?", no re-deriving splits from a group chat.

The whole point of keeping shared expenses in a structured tool instead of a chat thread is that the tax export is already sitting there, correct, waiting for a download.