Robert,

first study the generated XML, this will help you writing your stylesheet:
http://dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/56/threadid/57044/scope/posts/Default.aspx

You will discover that

• the column names gets xml encoded -> [Transaction Type] will be <Transaction_x0020_Type>
• you will find an addional element <Date_UDT_Value> which contains the formated date for your [Date] column respecting the current localization

Localization of the date is rendered to the XML content because of missing date function in the .NET XSLT implementation.
Otherwise you would need to parse the date as string - which is ugly and don't support localization.

Me too - very strange. I will think about.

1. XSL (without an EXSLT library) doesn't provide any date related functions, they are treated as strings.
2. The data inside UDT is loaded into a dataset containing multiple tables. The main data is inside the table "data". UDT provides its own datatypes that provide some more features, they are not mapped build in into .Net. We help ourself adding some invisible columns, it depends on the current udt type.
3. The date data type adds an invisible column containing the localized date as string. This helps you presenting a nice date using xml.
4. These invisble colums are described in the documentation for UDT3.3.7. (unpublished), 
   and here http://www.dotnetnuke.com/tabid/795/forumid/56/threadid/69772/scope/posts/Default.aspx