Revenue Fact and Account Balance Fact

Hello,
I am designing couple of dimensional models for a bank. The requirements are to be able to slide-n-dice bank revenue and account balance. Bank has a G/L code that identifies income/revenue type such as interest, fees, commissions etc. This is an intelligent code where the first two numbers signify whether it is an income or expense etc. In the kimball book, he mentions to create a revenue fact alone.
I also have to design a fact for each transaction that occurs at the bank for account balance. I am thinking of combining the two fact tables into one. Knowing that only some transactions will generate revenue for a bank, I will put all the transactions into one fact table and this fact table will have 3 metrics: transaction amount, ending balance, and revenue amount. I will also add a G/L code dimension which will tell me what kind of revenue it is for only those transactions that generate revenue.

Is this a good idea to combine Revenue fact and transaction fact into one? Please suggest.

The problem with balance is it is semi-additive while transactional measures are fully additive. Care should be taken when combining them in the same table. The BI layer you use should be able to distinguish between fully additive and semi-additive measures and prevent certain aggregations of semi-additive measures.

The other thing is stuff like balances don't really mean much in real time, from an analysis standpoint. Usually an end-of-day type balance, and maybe an average and min/max, overdraw counts and some other things are more useful. Such a daily snapshot would go into a different fact table.