fee credit vs. fee debit

[quinncomendant]

Hi Spencer

I've just tried http://dwolladwollabill.herokuapp.com/ and have been working with the CSV it creates. I noticed one issue: the CSV export doesn't differentiate (suitably well) between fees which are debits and those which are credits.

Here are two fee transactions downloaded from dwolla.com/statements:

"fee","10/02/2013","13:31:27",0.2500,3828419,3828418,"fee","Dwolla","","","","","","","",""
"credit","10/02/2013","13:31:27",-0.2500,3828420,3828418,"feecredit","Dwolla","","","","","","","",""

And here are the same two exported from dwolladwollabill:

3828419,0.25,"2013-10-02T20:31:27Z","fee","Dwolla","","Dwolla","812-723-3207","Strangecode, LLC","2013-10-08T00:00:00Z","processed",null,0,null,null
3828420,0.25,"2013-10-02T20:31:27Z","fee","Dwolla","812-723-3207","Strangecode, LLC","","Dwolla","2013-10-08T00:00:00Z","processed",null,0,null,null

Notice you're using fee for both, while the one from dwolla.com uses fee and feecredit.

Thanks, Quinn

[quinncomendant]

I noticed another discrepancy between the CSV provided by dwolla.com and that created by dwolladwollabill. In this case related to cancelled transactions. Take for example these transactions downloaded from dwolla.com/statements:

"canceled_debit","02/03/2014","22:32:34",116.6700,4538733,"","transfer","Jeremiah Mahler","812-656-2724","Jan 2014 payroll","","","","","",""
"canceled_credit","02/03/2014","22:32:34",-116.6700,4538736,"","deposit","Rabobank - Strangecode","XXX0054","","","","","","",""
"canceled_fee","02/03/2014","22:32:34",0.2500,4538734,4538733,"fee","Dwolla","","","","","","","",""
"canceled_credit","02/03/2014","22:32:34",-0.2500,4538735,4538733,"feecredit","Dwolla","","","","","","","",""

The same from dwolladwollabill:

4538736,116.67,"2014-02-04T06:32:34Z","deposit","Dwolla","812-723-3207","Strangecode, LLC","XXX0054","Rabobank - Strangecode","2014-02-07T00:00:00Z","cancelled",null,0,null,null
4538733,116.67,"2014-02-04T06:32:34Z","money_sent","Dwolla","812-656-2724","Jeremiah Mahler","812-723-3207","Strangecode, LLC","2014-02-07T00:00:00Z","cancelled","Jan 2014 payroll",0.25,null,null
4538734,0.25,"2014-02-04T06:32:34Z","fee","Dwolla","","Dwolla","812-723-3207","Strangecode, LLC","2014-02-07T00:00:00Z","cancelled",null,0,null,null
4538735,0.25,"2014-02-04T06:32:34Z","fee","Dwolla","812-723-3207","Strangecode, LLC","","Dwolla","2014-02-07T00:00:00Z","cancelled",null,0,null,null

The complicating issue here, again, is the use of different and less-specific Type values than provided in the CSV downloaded directly from dwolla.com (deposit vs. canceled_credit and fee vs. canceled_fee). I'm aware your CSV includes cancelled in the Status field, and of course you're probably working directly with the values provided by the Dwolla API, but in case there were an easy way to do so, it would perhaps be worth considering standardizing the Type fields on what dwalla.com's own CSV files use.

[spencerhunter]

Thanks for the feedback @quinncomendant ! This was a app that was hacked together fairly quick and could definitely use some more thought and TLC.

The goal of this app was to make pulling your Dwolla transactions more "customizable". There are a lot things lacking from the current solution at dwolla.com/statements that can be tackled by utilizing the API.

In re: fees- I believe I recall lumping the "total" fees into one category, when in reality they should be broken out and differentiated. You are correct in that I am pulling in values provided as they are returned from the API. I will look into updating this app sometime in the next few weeks and incorporate some of the feedback suggested here!