A trigger runs a function in response to a table event. A row trigger can inspect OLD and NEW values. BEFORE triggers can alter a row before storage or reject it; AFTER triggers are useful when you need an audit of a change that completed. Choose the event and timing deliberately.
A trigger function returns trigger. For a normal row update, return NEW from a BEFORE trigger that should keep the row. An AFTER trigger's return value doesn't change the stored row. Trigger writes take part in the same transaction, so a rolled-back change should not leave a committed audit entry.
Audit logic needs a scope: which fields changed, which actor made the change and how the application supplies that actor safely. The fixture records old and new balances only. It is an exercise in transactional audit behavior, not a complete regulated audit system.
Record the old and new balance for the specific account that changed.