Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Oct 17, 2015, 08:10 PM (IST)
Edited: Oct 17, 2015, 08:16 PM (IST)
Melbourne: Aaron Finch and Matthew Wade have been fined for violating Cricket Australia’s (CA) code of behaviour during the domestic limited-overs tournament (Matador BBQs) between Victoria and South Australia. Both players were reported for breaching CA’s code of behaviour Article 2.1.4 – Using language that is obscene, offensive or insulting during a match. The incidents occurred following each player’s dismissal. Finch was also reported for breaching Article 2.1.3 – Showing dissent at an umpire’s decision, after he was dismissed in Victoria’s batting innings. Both Finch and Wade admitted the offences and each accepted Match Referee Stephen Bernard’s proposed penalty of an official reprimand and fine for each player, therefore no hearings were required. As it was his second Level 1 Code of Behaviour offence in the past 18 months, Wade was fined 50 percent of his match fee.
According to a report on cricket.com.au, Finch expressed unhappiness after being given leg-before wicket off the bowling of Daniel Worrall, while Wade was frustrated after getting involved in a mix-up with Dan Christian. The duo are the sixth and seventh players against whom action has been taken against in the ongoing tournament, joining the likes of James Pattinson, Shaun Marsh, Nathan Coulter-Nile, Ben Cutting and Alex Ross for the same.
Finch, who usually opens the innings for Australia in limited-overs cricket, recently had a see-saw battle with Virat Kohli for the No. 1 spot in the ICC Twenty2o International (T20I) batsmen’s rankings. Finch eventually replaced the right-handed Indian batsman from the spot earlier this month. Both Finch and Wade were in good touch during the recent tour of England, averaging 69 and 82 respectively.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.