Adding expenses in Splex

Inside a group, every member has the same access to the shared expense ledger. There is no owner-only mode for expenses: any active group member can add an expense, edit an existing group expense, or record a settlement.

That is intentional for small shared groups, where the person who notices a mistake should be able to fix it. The safety net is the activity history: Splex records who created, changed, or deleted a ledger entry.

If location tracking is enabled and the device can provide a current position, Splex asks for suggestions within about 100 meters of that position.

The suggestions come from your own previous expenses that have saved coordinates near you. Splex walks newest expenses first, removes duplicate descriptions, and shows up to five suggestions. It is not a public place search and it does not query a map provider for restaurant names.

If location permission is missing, the device cannot get a position, or the request fails, the description field simply behaves like a normal text field.

Money fields have a calculator button that opens a calculator. You can calculate a value before entering it, without switching to another calculator app.

When you apply the result, the calculator writes it back into the field.

This is useful for receipts with subtotals, tips, partial reimbursements, or multi-payer amounts where you want to calculate the value directly in the field.

The amount you enter stays visible in the original currency. For balances, Splex converts it into the group or friendship currency.

The conversion uses the expense date, not necessarily today's date. If an exact historical rate is not available, Splex falls back to the nearest cached rate it can use, and stores which rate date was actually used. The date is shown later in the expense detail view.

Costs and exact splits are entered in the original expense currency. The stored shares are saved in the currency of the group or friendship.

• Equal: split the full amount between everyone, or only the selected participants. Use it for shared meals, taxis, groceries, or any bill where everyone should pay the same share.
• Exact: enter the exact amount each person owes. Use it when each participant takes over a specific part of the bill. For example, person A only pays for a drink and person B pays for a much more expensive meal.
• Percentage: enter percentages that must add up to 100. Use it for rent, utilities, or any recurring cost where shares are defined as percentages.
• Adjusted equal: before the bill is split equally, you can set that some people take over more or less of the bill. For example, if three people spent 60 in a pub, the drinks should be split equally, but person C also had food worth 12 that they should pay for themselves. Enter 12 as an adjustment for person C. Person C then pays 28 (12 for the food plus 16 for the drinks), while persons A and B each pay 16. Adjustments can also be negative. Use this when almost everything is shared, but someone had an extra item or should pay less.

Splex checks the split before saving, so every cent of the bill is actually assigned and the numbers add up.

An expense can have one payer or multiple payers. In single-payer mode, Splex stores that person as having paid the full amount. In multi-payer mode, the entered payer amounts must add up to the expense total.

Multiple payers do not change what people owe; they change who already covered money. If Alex paid 70 and Bea paid 30 for a 100 expense, Splex uses those proportions when turning owed shares into debts.

This is useful when several people paid at the counter, contributed cash, or split one larger card payment before the expense was entered.

A location is only sent when location tracking is enabled in the account, the device provides a usable coordinate, and the location switch in the expense is on.

For a new expense, turning the location switch off means no location is stored. When editing an existing expense, leaving the switch on keeps the existing location unchanged; turning it off removes the saved location.

If the expense date is in the past or future, Splex assumes that you are not currently at the place of the expense and does not save a location.

If creating a new expense fails because you are offline, Splex stores a pending create mutation on the device. The draft appears immediately in the activity feed and in the group or friend page as pending sync, and the overview shows a pending count.

Pending expenses are not part of the balance yet. The balance can therefore look wrong until the expense has synced successfully. You can open the draft, retry sync, or delete it.

Splex makes sure that the expense is not accidentally created twice when the connection is bad.