I'm on my way to Canada, I thought I'd take just a moment and talk about interim period reporting processes. I've been pretty clear that we need to use balances in order to provide eight volumes of data required to just report from transactions. This principle though, isn't so cut and dried when it comes to inter period recording, it's possible to take a posted balance from our last posting process. Plus the transactions that have happened since that posting process, add them together quickly created temporary bounce that can be used in our reports, or analysis processes. This is possible because the transactions are always limited by the duration of the posting process. If it's a day, they'll always be limited by the number of transactions for a day.

That limit on transaction volumes allows us to create a process that can summarize very quickly, the balance plus those transactions, the balance may not be stored that we create. It's not actually posted. It's a temporary process. Next time we run the posting process, we reprocess those transactions to create a permanent balance. This is a way of getting to our analysis, using an up to date balance without having to go through the overhead of updating every balance that's needed to produce our analysis in the interim period. Let me just follow up on another topic here briefly, don'ts of temporal events.

Temporal business events are those that are generated by the passage of time. They don't show up as something that happens at a specific point in time and that generates a transaction. Rather it's the passage of time that generates the transaction. An example of this would be an accrual of the amount you owe on Your rent on your apartment, not the passage of time has made you liable for some portion of your rent, even though you haven't been handed a bill by your landlord. So by doing some of our measurements, that particular point of times, we need to reflect these temporal events of the passage of time. This is related a little bit to other types of business events that are generated off the balances.

Sometimes a balance reflects many transactions that have occurred over a period of time. And it's easy for us to take the balance as the basis for generating a new transaction. For example, transactions if we tried to post a transaction every day, for the amount of rent that you accrue, then you're on the 15th of the month. You could take the balance as of the 15th of the month and say this is the total transaction amount business event is responsible for this balance and you could change So and have the timing be something different, could have the timing be recording the amount you offer every hour through the 15 days, that's going to generate a lot more transactions that have to be added up to be a balance by using the balance. That doesn't matter whether you use daily transactions are hourly transactions. The balance gives us one position one point from which to generate the business event we need the accrual process.

This is another example of where the line between balances and business events, balances and transactions can get slightly blurred.