Best Practice for transfers between own accounts

[David Carlson]

On 7/19/2012 5:43 AM, Dustin Henning wrote:
> If your accounts were all in one file, they woud probably match up
> automatically.  As such, I'm assuming they aren't, you only need to correct
> linked accounts between imports and then you can reconcile the same
> transaction on the next file it comes in on.  In the meantime, it isn't
> hurting anything being there unless you're concerned about trying to use it
> before it clears.  Personally, I enter almost all of my transactions
> manually and use the import to reconcile them / catch errors & missed
> transactions.  I don't know what the proper method is, but your approach
> would work too; whether you would gain anything other than a layer of data
> to verify is a matter of personal opinion.
>
> -----Original Message-----
> From: gnucash-user-bounces+the00dustin=gmx.net at gnucash.org
> [mailto:gnucash-user-bounces+the00dustin=gmx.net at gnucash.org] On Behalf Of
> martysto
> Sent: Wednesday, July 18, 2012 21:06
> To: gnucash-user at gnucash.org
> Subject: Best Practice for transfers between own accounts
>
> I have various accounts were I import the data for each account directly or
> via CSV/QIF. I face the problem that I end up having plenty of duplicate
> transactions when I transfer money between them. 
>
> The main problem is that the amount is sometimes only received after a
> couple of days which makes matching them rather cumbersome and
> double-checking with the original records error prone.
>
> I am thinking to start over and introduce a "Transfer" account which should
> be 0 under normal circumstances.
>
> Each transaction between my own accounts would then be logged twice.
>
> It still feels doggy and I will get quite some "overhead". Do you think that
> is feasible? What would your approach be?
>
> Thank you very much in advance
> --Martin 

Hi,

I have found that with the OFX import the matching transfers are often
missed by the import assistant.  That may also happen with CSV or QIF
imports. 

You should be able to catch most of them in the import dialog window by
carefully examining each line for proper disposition to the correct
transfer account.  Any transaction that has a red background will not be
imported at all and must be modified somehow to be imported.  Those with
a yellow background are new and/or almost certainly not matched
correctly and need to be edited.  Lastly, the green ones can be wrong
too.  I often see gasoline purchases charged to dining and vice versa.

I personally do not distinguish between 'new' transactions and 'matched'
transactions when I am looking for import errors, other than to
determine what the correct disposition is for that transaction.

Good Luck.

David C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xDC7C8BF3.asc
Type: application/pgp-keys
Size: 1729 bytes
Desc: not available
URL: <http://lists.gnucash.org/pipermail/gnucash-user/attachments/20120719/c9bad947/attachment.bin>