Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-hide-security-enhancer 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/tabadul/public_html/wp-includes/functions.php on line 6114

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

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

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the formidable-pro 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/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-formidable-uikit-master 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/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the iwp-client 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/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the libyanspider-base 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/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the google-site-kit 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/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-2fa 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/tabadul/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-smtp 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/tabadul/public_html/wp-includes/functions.php on line 6114
“العكاري” يوضح كيف يمكن أن يساهم حل مشكلة المقاصة في خفض سعر صرف الدولار بالسوق الموازي – تبادل
Skip to main content
|

“العكاري” يوضح كيف يمكن أن يساهم حل مشكلة المقاصة في خفض سعر صرف الدولار بالسوق الموازي

قال الخبير المصرفي “مصباح العكاري” إن المشكلة الرئيسية في موضوع المقاصة تكمن في ضعف رصيد المصارف التجارية لدي المصرف المركزي بطرابلس وارتفاع أرصدتها لدى المصرف المركزي ببنغازي.

وأوضح “العكاري” بأن المقاصة في حقيقتها ليست مقفلة والدليل علي ذلك أن هناك صكوكًا مازالت تحصل بين المصارف من حين إلى آخر، مضيفًا بأنه لو تمت عملية نقل أرصدة هذه المصارف إلى المركزي في طرابلس وهي أرصدة مواطنين وبعض الشركات شبه الحكومية مثل المدار وليبيانا فإن أرصدة هذه المصارف سوف تصبح لها القدرة علي قبول كافة الصكوك المقدمة للمقاصة.

وأضاف بأن المصارف ستصبح حينها لها القدرة علي مواجهة الطلب علي النقد الأجنبي وأيضا سحب السيولة النقدية من المصرف المركزي أو من المصارف الخاصة، مما سيؤدي إلى زيادة قدرة المصارف التجارية علي شراء النقد الأجنبي للزبائن يعني زيادة طرح نقد أجنبي أكثر في السوق، الأمر الذي سيؤدي انخفاض سعره، مؤكدًا بأن من يقول أنه لو فتحت المقاصة سيصبح الدولار بعشرة دينار ليس له علاقة بالأمور المالية المصرفية.

وحذر “العكاري” من استمرار الوضع على ما هو عليه الآن والذي سيؤدي إلى ارتفاع سعر الدولار في السوق الموازية بالصك وزيادة المضاربة عليه وتحميل المسؤولية في ذلك على المصارف التجارية، إضافة إلى استمرار مشكلة السيولة رغم توفر هذه السيولة لدى المصارف الخاصة.

وأشار إلى أنه وبعد إجراء المراجعة الدولية من أفضل شركات العالم في مجال المراجعة؛ فإنه لم يعد هناك أي مبرر لاستمرار هذه الازمة التي يدفع ثمنها المواطن البسيط.

مشاركة الخبر