Retail Sales and Use Tax; additional tax authorized in City of Charlottesville & Albemarle County. (HB2161)

Introduced By

Del. David Toscano (D-Charlottesville)

Progress

Introduced
Passed Committee
Passed House
Passed Senate
Signed by Governor
Became Law

Description

Local sales and use tax; additional authorized in City of Charlottesville and Albemarle County. Permits the City of Charlottesville and Albemarle County to impose an additional sales and use tax at a rate not exceeding one percent, provided that all revenue generated from the additional tax is used solely for transit or other transportation projects. Amends § 58.1-605, § 58.1-606, § 58.1-608.3, § 58.1-611.1, § 58.1-614, of the Code of Virginia. Read the Bill »

Outcome

Bill Has Failed

History

  • 01/14/2009 Committee
  • 01/14/2009 Prefiled and ordered printed; offered 01/14/09 097826752
  • 01/14/2009 Referred to Committee on Finance
  • 01/20/2009 Assigned Finance sub: 2
  • 01/24/2009 Impact statement from TAX (HB2161)
  • 01/28/2009 Subcommittee recommends laying on the table by voice vote
  • 02/10/2009 Left in Finance

Map

This bill mentions Suffolk, Portsmouth City, Norfolk City, Hampton City, Newport News City, Roanoke City, Salem City, Albemarle, Charlottesville, Staunton.

Comments

Sean Tubbs writes:

What committee has this been referred to?

Waldo Jaquith writes:

The bill is in limbo—it's been assigned to a committee in the abstract, but the specific committee hasn't yet been determined.

Sean Tubbs writes:

What are some of the likely candidates?

Waldo Jaquith writes:

The Counties, Cities and Towns committee or the Finance committee would both be perfectly reasonable places to send it.

Oh, I just noticed—they sent it to Finance. Never mind. :)

Sean Tubbs writes:

Waldo, this bill was killed in subcommittee yesterday, according to Brian McNeil's article in the Daily Progress. How long goes it take for subcommittee votes to make their way through the system?

Waldo Jaquith writes:

The subcommittee can't kill a bill, they can only vote to recommend that it be killed. That doesn't kill it, so nothing has changed. The committee may or may not choose to follow that recommendation. Now, they just about always do. (But I can't say how often; recording subcommittee votes hasn't been done during the history of Richmond Sunlight, so I have no stats to check.)

You can see, under the "View Entire History" link, that the subcommittee has recommended that it be killed. I'm thinking of modifying Richmond Sunlight's code to present that as the current status, whenever such a recommendation is made. Generally I filter out the noise and display only the most recent substantive change in status. Now that we've got the (informal) results of subcommittee votes, seems to me there's some sense in displaying that.

Sean Tubbs writes:

Thanks for the explanation and the tip on how to check and see what's going on.