Context and motivation: Veracity Requirements are software requirements concerning truth, trust, authenticity, and demonstrability. Such requirements could be related to data, financial data, regulatory, process, and cultural dimensions. Question/problem: Sub-optimal decisions made w.r.t. veracity requirements in the development of software could lead to adverse consequences such as huge cost overruns, legal concerns, bad reputation, and the loss of customers. This is captured by the phenomenon, Veracity Debt'. This paper reports the results of a survey conducted with software practitioners to gather their perceptions on Veracity Requirements and quantifying Veracity Debt. Principal ideas/results: Results are promising since practitioners relate to the concepts discussed in the survey. They agree that quantifying the consequences of not fixing Veracity Debt instances helps make informed decisions. Legal liabilities, user feedback, team-level trust, reduced trust, impact on reputation, and loss of customers were among other factors to consider. Contribution: Coining the termVeracity Requirements Debt’ and insights gained from practitioners’ perceptions.