Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the amp 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 /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the gotmls 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 /home/independ/public_html/wp-includes/functions.php on line 6170
Kerajaan Pertimbang Cadangan Pengeluaran Akaun 1 KWSP – Independent

Independent

Kerajaan Pertimbang Cadangan Pengeluaran Akaun 1 KWSP

—

by

Admin
in , ,
   
Reading Time: < 1 minute

PUTRAJAYA | Kerajaan sedang mengkaji cadangan untuk membenarkan pencarum tertentu seperti pekerja yang diberhentikan untuk mengeluarkan dana dari Akaun 1 Kumpulan Wang Simpanan Pekerja (KWSP).

“Saya telah berbincang dengan Kementerian Kewangan dan pada dasarnya kami bersetuju dan bersedia untuk mengkaji cadangan pencarum yang benar-benar perlu mengeluarkan wang dari Akaun 1,” kata Perdana Menteri Tan Sri Muhyiddin Yassin di sini, hari ini.

Kerajaan telah melaksanakan kelonggaran pada tahun 2020 yang berkaitan dengan KWSP, terutama dengan membolehkan kadar caruman pekerja dikurangkan kepada 7.0 peratus dari 11 peratus dan juga pengeluaran i-Lestari dari Akaun 2 sebanyak RM6,000 setiap pencarum.

Hampir 70 peratus pencarum KWSP memilih untuk mengurangkan caruman pekerja kepada 7.0 peratus yang kini telah meningkatkan pendapatan boleh guna menjadi hampir RM700 juta sebulan, katanya dalam wawancara dengan BERNAMA dan stesen televisyen tempatan menjelang Belanjawan 2021 pada hari Jumaat.

Pada masa yang sama, lebih daripada 30 peratus pencarum KWSP mempunyai simpanan kurang dari RM5,000 dalam akaun mereka, oleh itu, simpanan KWSP tidak semestinya dapat mengatasi masalah aliran tunai para pencarum.