Notice: fwrite(): Write of 1126 bytes failed with errno=28 No space left on device in /var/www/news.numlock.ch/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 42

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the math-captcha domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/news.numlock.ch/public_html/wp-includes/functions.php on line 6114

WordPress database error: [Disk full (/tmp/#sql-temptable-20e-36a7b-d11.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_wfLiveTrafficHuman`

WordPress database error: [Disk full (/tmp/#sql-temptable-20e-36a7b-d12.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_wfLiveTrafficHuman`

WordPress database error: [Disk full (/tmp/#sql-temptable-20e-36a7b-d13.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_options`

Per order vs. per volume – A changelog by Daniel Mettler

Per order vs. per volume

I like the new advertisement campaign by the Swiss bank MIGROSBANK. Among others, and that’s why I like it, it questions some of the antiquated banking practices which can hardly be “justified” in the age of e-banking, yet are still in widespread use.
For example, one of the advertisements questions why most banks charge commissions for stock market orders based on the transaction volume (or on a combination of volume and per order) instead of charging a flat fee per order.

The advertisement shows two identical pictures of someone hitting the ‘Enter’ key on the keyboard. The text below the pictures reads (IIRC, in about): “Do you see a difference? We neither. That’s why we charge the same fee for every order.”
Some people might argue that customers who potentially gain (or lose) more money (by having higher transaction volumes) should also pay more of the costs of the e-banking system. From the perspective of managerial accounting however, it makes more sense to break down these costs into costs per order rather than per volume. If no paperwork and no other per transaction costs are involved at all, it might even make sense to charge a flat rate per participating customer only (neglecting the fact however, that the software and the hardware infrastructure need to be able to absorb the peak number of transactions per time). This of course only applies to orders given using the e-banking system. For any other, more traditional services like consulting, wealth management etc. customers shall be charged for separately.

So why do most banks still charge on a per volume basis (or on a mix of per volume and per order fees)? It’s because they can. Some people might not be fully aware of  how much IT changed (and will further change) banking. And most people lose their flair for “small” numbers once they deal with “big” numbers. Besides, it’s also a question of how people value their time.

Nonetheless, I hope the above mentioned bank will be able to stir up the domestic market a bit.

One Reply to “Per order vs. per volume”

  1. meanwhile in the us, they still like checks so much that they have to maintain extensive branch networks. i get queasy when i think of all that money wasted on marbled halls that should go into savings accounts instead.

Leave a Reply

Your email address will not be published. Required fields are marked *

+ 53 = 59

This site uses Akismet to reduce spam. Learn how your comment data is processed.


Notice: fwrite(): Write of 1126 bytes failed with errno=28 No space left on device in /var/www/news.numlock.ch/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 42

Fatal error: Uncaught wfWAFStorageFileException: Unable to verify temporary file contents for atomic writing. in /var/www/news.numlock.ch/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:51 Stack trace: #0 /var/www/news.numlock.ch/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(658): wfWAFStorageFile::atomicFilePutContents() #1 [internal function]: wfWAFStorageFile->saveConfig() #2 {main} thrown in /var/www/news.numlock.ch/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 51