Split Spendings

[SaleLeone]

Hello

After the holidays we wanted to sort out who has to pay whom how much. We used the App Splitwise, though not all people spent the whole holidays together. So i set up 4 different Groups in Splitwise.
Now everybody would have to do multiple transactions because we have 4 groups.

I started doing everything manually in Excel using this template: http://www.herber.de/bbs/user/70975.xls

From each of the four tables I calculated the average amount (what everybody should have spent in the end) together --> Column C
Persons A,B,C,D,E spent the whole holidays together. Thats way the all need to pay the same amount
Person F left ealier. So he has to pay less
Persons G and H came later and left ealier. Thats why the have to pay even more less.

Now my question is how do I calculated who has to pay whom how much. So not everybody has to make multiple transactions.

Using Office 2013

Attachment 530405

thank you

[Glenn Kennedy]

Will you please attach a SMALL sample Excel workbook (10-20 rows of data is usually enough)? Please don't attach a picture of one (no-one will want to re-type all your stuff before starting).

1. Make sure that your sample data are truly REPRESENTATIVE of your real data. The use of unrepresentative data is very frustrating and can lead to long delays in reaching a solution.

2. Make sure that your desired solution is also shown (mock up the results manually).

3. Make sure that all confidential information is removed first!!

4. Try to avoid using merged cells. They cause lots of problems!

Unfortunately the attachment icon doesn't work at the moment. So, to attach an Excel file you have to do the following: Just before posting, scroll down to Go Advanced and then scroll down to Manage Attachments. Now follow the instructions at the top of that screen.

[quekbc]

Now my question is how do I calculated who has to pay whom how much. So not everybody has to make multiple transactions.

This was something I thought about some time ago. My small brain could only come out with a solution where everyone does at most 1 transaction - however, it's not easy to formulate this - and more often than not I do it manually. I'll try to explain the procedure as concisely as possible.

1) Sort from positive to negative (positive means they should receive money, negative means they need to pay)
2) The smallest number (i.e. most negative) pays the biggest number (i.e. most positive) in full
3) Recalculate net position - sort them again and repeat step 1 and 2 until everyone nets off to 0.

It's a series of calculation - best explain in the attached. The blocks for Round 2 is structured to be copied across to round 3, 4, 5, etc. until all becomes 0 (or close to 0).

P/S: This method is not perfect and I'm pretty sure there'll be some cases where this doesn't work - in which case I do it manually.
P/S: Also, it's kinda hard to explain this to my friends when I did this because this method almost always means everyone needs to pay someone, even if at the start people owe you money. In which case, I usually make an adjustment by randomly selecting 1 (or a few) people to make 2 transactions.

[SaleLeone]

This was something I thought about some time ago. My small brain could only come out with a solution where everyone does at most 1 transaction

Cool!
thanks a lot.