Levy is one of the most complicated delinquent property tax remedies.  Identifying and locating the taxpayer’s property that is eligible for levy is often one of the biggest challenges of this delinquent property tax remedy. 

Attachment and Garnishment is an effective and often-used method of enforced tax collection.  But, the statutes that govern it and the process of enforcing it are anything but easy. 

In FY ended June 30, 2010, more than $58 million in NC property taxes went uncollected. With counties and municipalities around North Carolina struggling to maintain a proper fund balance, now is the prime time to review your forced collections strategies.

Unfortunately, addressing problems don’t typically capture the attention of most county officials until “bad things” occur: a fire that forces evacuation of residents, a death because an ambulance couldn’t find an address (or were routed to a wrong address), people voting in the wrong districts, or someone picking up on the fact that “some” county residents haven’t been paying their fair share of taxes (or any share at all).

Last week I attended the 2011 North Carolina GIS Conference in Raleigh. The conference is bigger than a lot of national conferences and attracts folks from North Carolina and surrounding states. I’ve actually been attending this conference throughout my career, starting with my US EPA days through IBM and now as a representative of Farragut. I’ve been to a lot of state GIS conferences, and I have always been particularly impressed with this conference and the state of GIS technology in North Carolina. The quality of papers and general information that you pull out of this conference has always been impressive.

From my earlier posts, you heard me discuss (a.k.a., rant) about the importance of enterprise repositories for managing critical information. In short, instead of storing the same information in multiple vertical applications, store and manage the data centrally.

One of the keys to designing and implementing large enterprise software systems is to put together a project plan that addresses the “big picture,” but breaks down the implementation steps into a series of “bite-size” projects that provide immediate benefit.

I’m not exactly clear what generation I am. My Dad fought in the Pacific in WW2, and that probably should make me part of the baby-boomer generation (although being the youngest of 5, it puts me at the tail-end of that generation). My son came home from college one day, however, and promptly declared me to be a part of the X-generation. I’m not exactly sure why, but it appeared to have something to do with my views on life and my embracing of technology.

Everybody who deals with addressing seems to understand the problems – too many people/departments maintaining addresses in too many vertical applications. The result: bad addresses, inconsistencies, etc. that cause a slew of problems—including issues with public safety. There isn’t a single presentation I’ve given on the issues and problems of addresses where I don’t have people nodding their heads up-and-down in violent agreement.

My wife and I recently went on vacation in the Seattle area to visit my wife’s family. Our plan was to meet up at my sister-in-law’s house and then go sea-kayaking in the San Juan Islands (great area, by the way, I highly recommend a visit). As I was driving along looking for her 742 house number, I passed the 900 block, then the 800 block, and then 1172 showed up. I said to myself: “OK…I’m an addressing guy, I can figure this out.”