Not so easy, this one, as in Excel it is very natural to refer to the previous balance (D4 in your example) - but in SQL there is no concept of row position, so extracting the previous balance to form a running sum of balances is tricky.
It is a simple matter to sum a whole group, but providing a running SUM showing the changing balance for each transaction involves joining a table back to itself on the last transaction somehow, and is not one for which an easy solution comes to mind. It can be done, but there has to be some means to join the tables by 'staggering' the rows using transaction dates or identifiers to imply the order so that the current joins the previous, the previous the one before, and so on.
Do you really need this in Access? If you do, and you can't live without it, we will need the metadata (the field names, types and keys involved) for the table concerned to play with some SQL and see what happens.
-Stewart