Thursday, May 29, 2025

Fwd: Business Halacha Daily


---------- Forwarded message ---------
From: Bais HaVaad Halacha Center <info@baishavaad.org>
Date: Tue, May 27, 2025, 8:02 PM
Subject: Business Halacha Daily
To: <agentemes4@gmail.com>


Can Bais Din Make a Peshara After a P'sak is Issued?


Question: I won a din Torah but the dayan is now asking me to give in and forgo some of my award. Is he acting properly? 



CLICK BELOW TO WATCH THE VIDEO

Rav Dovid josilowsky


Answer: The halacha is that once a Bais Din issues a ruling, they are not allowed to make a Peshara. The reason for this is because at that point the Halacha has already determined the just outcome, and asking the winning party to give up what he won would be undermining the rule of law. 


However, the Shach says that even after a p'sak is issued, there still is a mitzvah to make peace between the parties. To this end, Bais Din may try to convince the winning party to appease the losing party by giving up some of his winnings. They cannot force him to give in on anything, but they can recommend that he do so and tell him that even though the p'sak is binding and true, it is in everyone's overall interest to make peace by giving in. 


There was, in fact, a story in which the Chazon Ish ruled on a din Torah and then said to the winning party, "The Din is on your side. Now, you should be mevater" in order to make shalom. 

For more information on the Business Halacha Daily project, visit https://baishavaad.org/business-halacha-daily/

To sign up to the BHD WhatsApp group click click HERE.

Any comments? We welcome your questions and feedback. Please reach out to us! info@baishavaad.org | 888.485.8223

OR SEARCH "BUSINESS HALACHA DAILY" VIA YOUR FAVORITE PODCAST VENUE

For more information on the Yorucha project, visit Yorucha.org/about/.

For the full topic syllabus,visit Yorucha.org/curriculum/

Feedback? yorucha@baishavaad.org | 888.485.8223 ext.302

Bais HaVaad Halacha Center | 290 River Ave. | Lakewood, NJ 08701 US

Unsubscribe | Update Profile | Constant Contact Data Notice

No comments: