<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Welcome Wesabeans</title>
	<atom:link href="http://blog.xero.com/2010/07/welcome-wesabeans/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.xero.com/2010/07/welcome-wesabeans/</link>
	<description>Xero Accounting Software</description>
	<lastBuildDate>Thu, 09 Feb 2012 03:53:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Catherine Walker</title>
		<link>http://blog.xero.com/2010/07/welcome-wesabeans/comment-page-1/#comment-7313</link>
		<dc:creator>Catherine Walker</dc:creator>
		<pubDate>Tue, 20 Jul 2010 05:13:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xero.com/?p=12687#comment-7313</guid>
		<description>@Dave, at this stage Xero Personal is only available for NZ users if you already have a Xero account or are a BNZ customer.
Regards, Catherine</description>
		<content:encoded><![CDATA[<p>@Dave, at this stage Xero Personal is only available for NZ users if you already have a Xero account or are a BNZ customer.<br />
Regards, Catherine</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://blog.xero.com/2010/07/welcome-wesabeans/comment-page-1/#comment-7305</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Mon, 19 Jul 2010 22:03:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xero.com/?p=12687#comment-7305</guid>
		<description>Is there a plan to open up personal for all NZers?

I don&#039;t bank with BNZ and don&#039;t use Xero business. I&#039;ve been using Wesabe for years, and I&#039;m keen to switch to something good.</description>
		<content:encoded><![CDATA[<p>Is there a plan to open up personal for all NZers?</p>
<p>I don&#8217;t bank with BNZ and don&#8217;t use Xero business. I&#8217;ve been using Wesabe for years, and I&#8217;m keen to switch to something good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://blog.xero.com/2010/07/welcome-wesabeans/comment-page-1/#comment-7271</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Sun, 18 Jul 2010 20:14:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xero.com/?p=12687#comment-7271</guid>
		<description>Is there anything you can do about making splits import properly?</description>
		<content:encoded><![CDATA[<p>Is there anything you can do about making splits import properly?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Catherine Walker</title>
		<link>http://blog.xero.com/2010/07/welcome-wesabeans/comment-page-1/#comment-7184</link>
		<dc:creator>Catherine Walker</dc:creator>
		<pubDate>Fri, 16 Jul 2010 05:01:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xero.com/?p=12687#comment-7184</guid>
		<description>@Paul &amp; K Rouse - hey, just letting you know we&#039;ve uploaded a fix for the single account export issue - any further problems let us know and thanks again for shouting out. Regards, Catherine</description>
		<content:encoded><![CDATA[<p>@Paul &amp; K Rouse &#8211; hey, just letting you know we&#8217;ve uploaded a fix for the single account export issue &#8211; any further problems let us know and thanks again for shouting out. Regards, Catherine</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sara Goepel</title>
		<link>http://blog.xero.com/2010/07/welcome-wesabeans/comment-page-1/#comment-7172</link>
		<dc:creator>Sara Goepel</dc:creator>
		<pubDate>Thu, 15 Jul 2010 23:06:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xero.com/?p=12687#comment-7172</guid>
		<description>@Paul &amp; K Rouse- thank you for bringing the single account export issue to our attention as we hadn&#039;t come across it in test files we received.  We&#039;re working on a fix and we&#039;ll update you when it&#039;s released.</description>
		<content:encoded><![CDATA[<p>@Paul &#038; K Rouse- thank you for bringing the single account export issue to our attention as we hadn&#8217;t come across it in test files we received.  We&#8217;re working on a fix and we&#8217;ll update you when it&#8217;s released.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://blog.xero.com/2010/07/welcome-wesabeans/comment-page-1/#comment-7150</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Thu, 15 Jul 2010 05:03:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xero.com/?p=12687#comment-7150</guid>
		<description>Yup, K Rouse had it right. I was importing a single account, not a csv with all accounts. Good catch!

My suggestion for the splits is to just add the general/misc category to any split transaction and mark them for review. I&#039;m sure you could also guess at the category based on the tags. I know it could get weird because Wesabe allowed multiple tags for each transaction, so it might be difficult to split, but if you make sure to automatically mark split transactions for review, that might be best.</description>
		<content:encoded><![CDATA[<p>Yup, K Rouse had it right. I was importing a single account, not a csv with all accounts. Good catch!</p>
<p>My suggestion for the splits is to just add the general/misc category to any split transaction and mark them for review. I&#8217;m sure you could also guess at the category based on the tags. I know it could get weird because Wesabe allowed multiple tags for each transaction, so it might be difficult to split, but if you make sure to automatically mark split transactions for review, that might be best.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: K Rouse</title>
		<link>http://blog.xero.com/2010/07/welcome-wesabeans/comment-page-1/#comment-7139</link>
		<dc:creator>K Rouse</dc:creator>
		<pubDate>Thu, 15 Jul 2010 01:05:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xero.com/?p=12687#comment-7139</guid>
		<description>When exporting transactions from wesabe for a single account the column name in the csv is &#039;Bank Name&#039;, not &#039;Raw Name&#039;. It is only &#039;Raw Name&#039; when all accounts are in one file.

Changing the title in the single account csv to &#039;Raw Name&#039; enables the upload to work. The original bank details came through as the &#039;Payee&#039; and &#039;Original Payee&#039; in Xero.</description>
		<content:encoded><![CDATA[<p>When exporting transactions from wesabe for a single account the column name in the csv is &#8216;Bank Name&#8217;, not &#8216;Raw Name&#8217;. It is only &#8216;Raw Name&#8217; when all accounts are in one file.</p>
<p>Changing the title in the single account csv to &#8216;Raw Name&#8217; enables the upload to work. The original bank details came through as the &#8216;Payee&#8217; and &#8216;Original Payee&#8217; in Xero.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Owen Evans</title>
		<link>http://blog.xero.com/2010/07/welcome-wesabeans/comment-page-1/#comment-7133</link>
		<dc:creator>Owen Evans</dc:creator>
		<pubDate>Wed, 14 Jul 2010 22:29:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xero.com/?p=12687#comment-7133</guid>
		<description>Hi Paul,
Great to hear that the import managed to get your transactions into Xero Personal.
We realise there are a few things that would be nice to have happen automatically, with splitting and categorisation we have the problem that we don&#039;t have a direct mapping between wesabe tags and categories in Xero Personal and we don&#039;t have a concept of splitting an uncategorised transaction, we&#039;ll certainly be looking for some feedback as to common tags that can be used to map to Xero Personal categories.

As for the original bank import data, this should be coming in as the &quot;Original bank details&quot; in the expanded view of the transaction.
can you make sure that the information isn&#039;t in the popup that comes up when you click on the &quot;more...&quot; link.

Also can you check that the details are in the CSV under the Raw Name column

Many Thanks
Owen</description>
		<content:encoded><![CDATA[<p>Hi Paul,<br />
Great to hear that the import managed to get your transactions into Xero Personal.<br />
We realise there are a few things that would be nice to have happen automatically, with splitting and categorisation we have the problem that we don&#8217;t have a direct mapping between wesabe tags and categories in Xero Personal and we don&#8217;t have a concept of splitting an uncategorised transaction, we&#8217;ll certainly be looking for some feedback as to common tags that can be used to map to Xero Personal categories.</p>
<p>As for the original bank import data, this should be coming in as the &#8220;Original bank details&#8221; in the expanded view of the transaction.<br />
can you make sure that the information isn&#8217;t in the popup that comes up when you click on the &#8220;more&#8230;&#8221; link.</p>
<p>Also can you check that the details are in the CSV under the Raw Name column</p>
<p>Many Thanks<br />
Owen</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://blog.xero.com/2010/07/welcome-wesabeans/comment-page-1/#comment-7131</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 14 Jul 2010 22:09:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xero.com/?p=12687#comment-7131</guid>
		<description>I tested the Wesabe import today and it worked for the most part, but I noticed a couple of problems. 

First, the splits set in Wesabe are not being imported as splits, but as alternative labels. A split on a $100 purchase from the grocery store in Wesabe looks similar to this [groceries,  cash:20] meaning $20 was for cash and the $80 balance was for groceries. Xero merely imports the entire string of cash:20 as a label so you end up with multiple cash:x labels in your list of labels. It would be great if the import algorithm could parse the split and create a corresponding split in Xero. 

The second problem was that the original &#039;Bank Name&#039; field for each transaction wasn&#039;t imported. This is the original name imported into Wesabe before a person readable name is applied to the transaction. It typically looks like this [Point Of Sale Withdrawal / 7-ELEVEN blahblahblah]. I DO NOT want to lose this data as it is an invaluable record. Also, this means that any transactions that I didn&#039;t relabel in Wesabe is imported with the transaction name &#039;Unknown&#039; and is pretty much rendered useless, as I would have no idea where that transaction was originally performed. When I import from a bank OFX file, this data is split between the Original Payee and Reference fields so I am not sure why the Wesabe importer doesn&#039;t properly import it.</description>
		<content:encoded><![CDATA[<p>I tested the Wesabe import today and it worked for the most part, but I noticed a couple of problems. </p>
<p>First, the splits set in Wesabe are not being imported as splits, but as alternative labels. A split on a $100 purchase from the grocery store in Wesabe looks similar to this [groceries,  cash:20] meaning $20 was for cash and the $80 balance was for groceries. Xero merely imports the entire string of cash:20 as a label so you end up with multiple cash:x labels in your list of labels. It would be great if the import algorithm could parse the split and create a corresponding split in Xero. </p>
<p>The second problem was that the original &#8216;Bank Name&#8217; field for each transaction wasn&#8217;t imported. This is the original name imported into Wesabe before a person readable name is applied to the transaction. It typically looks like this [Point Of Sale Withdrawal / 7-ELEVEN blahblahblah]. I DO NOT want to lose this data as it is an invaluable record. Also, this means that any transactions that I didn&#8217;t relabel in Wesabe is imported with the transaction name &#8216;Unknown&#8217; and is pretty much rendered useless, as I would have no idea where that transaction was originally performed. When I import from a bank OFX file, this data is split between the Original Payee and Reference fields so I am not sure why the Wesabe importer doesn&#8217;t properly import it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

