Chuck! I am also late to the party. To complement on Mark's comment, I worked on building a mini solution based on your problem. The assumptions are:
1. The companies do not have a static income value for each employee. To make it more realistic, each employee sets his/her income per company.
2. The employee cannot create his/her company, but select it from an existing database.

This is how the data relationship looks:

Logic:

For the most part the logic was done autonomously by using the scaffolding technique with the Employee and Company entities. I created a new aggregate to fetch Income.Amount and Group By Sum:

On the Employee Detail screen, I included some additional variables and actions to be able to capture the user's income and update the Sum. I used a PopUp widget to be able to capture this information and save it in "IncomeId".

Feel free to test this mini app by using this link. I'm happy to share the oml file if you'd like to see the logic.