Just u show the requirements

Before Raising an Issue be sure of the Following:

(i) Issue Should be Valid
(ii)Check if the Functionality is Defined in the Provided 
Docs that u refer
(iii)If not defined in the Provided Docs, Raise the Issue 
with the Concerned Category (Say... Spec-Gap, No-Specs, 
etc...)
(iv) Check if the Issue Can be Replicated (Issue Screenshot 
will help in this Regard)
(v) Be Clear in the Description
(vi) See the Issue in the End-User Perspective

If u be able to follow the foresaid points, the Developer 
has to Agree....

Any Clarifications Mail to: hs.nihilo@yahoo.com

reproduce the bug.

1. Send all the procudure to reproduce the defect.
2. send the screen shot as a proof.
3. if then also developer is not accepting then i would ask 
QA manager to permit formal discussion with developer and 
hope output would be one conclusion.
4. sometimes requirement are not crystal clear, and both 
views looks logically acceptable, in that case Team lead 
and design team should take that issue to the client and 
confirm it.

Report that bug 
To:Business analyst and 
cc: Development manager