Re: Help a Beginner with Red's CSV Importer?

[fin]

Chris Bond wrote:
> --=_Part_10662_427767134.1701975257612
> Content-Type: multipart/alternative; 
>   boundary="=_Part_10663_1945899272.1701975257612"
>
> --=_Part_10663_1945899272.1701975257612
> Content-Type: text/plain; charset="UTF-8"
>
>  I have what I think may be a very simple CSV file:
>
> Column headers are these:
> Date,Description,Amount,Unapplied,Balance 
>
> Corresponding data fields look like this:
> Dec 1, 2023,PAYMENT,$951.28,$951.28,$25,000.62

  you have a comma in the first field, you don't want to use
dates with commas in them if you are using csv format.

  sorry i don't have the time to look into this further but
i noticed this and thought it worth a comment.  :)

  good luck,

  keep on trying, i learned a lot by doing a lot of 
experiments and writing my own importers.


> I have had some success using Red's ofx importer framework, but am really 
> struggling to figure out the CSV importer from the examples in the git 
> repo. I started with the Discover example that looks like this:
>
> from beancount_reds_importers.libreader import csvreader
> from beancount_reds_importers.libtransactionbuilder import banking
>
> class Importer(csvreader.Importer, banking.Importer):
> IMPORTER_NAME = """ Discover credit card .csv importer."""
>
> def custom_init(self):
> self.max_rounding_error = 0.04
> self.filename_pattern_def = 'Discover.*'
> self.header_identifier = 'Trans. Date,Post 
> Date,Description,Amount,Category'
> self.date_format = '%m/%d/%Y'
> self.header_map = {
> "Category":'payee',
> "Description": 'memo',
> "Trans. Date": 'date',
> "Post Date":   'postDate',
> "Amount":  'amount',
> }
>
> def skip_transaction(self, ot):
> return False
>
> def prepare_processed_table(self, rdr):
> # Need to invert numbers supplied by Discover
> rdr = rdr.convert('amount', lambda x: -1 * x)
> return rdr
>
> I'm pretty sure I don't need the def skip_transaction(self, ot) and def 
> prepare_processed_table(self, rdr): bits, but am at a loss to figure out 
> what fields I need to modify in the def custom_init(self) for my situation. 
> There is not an example CSV file for that importer in the repo so it makes 
> it a little more challenging for me to hack on it. I think I don't need the 
> "Unapplied" column but am not sure. Even just some hints would be really 
> helpful. 
>
> Thank you in advance!
> Chris
>

  fin

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/32vc4k-hk9.ln1%40anthive.com.

Re: Dealing with futures

[Martin Blais]

Sorry for the late reply, I've been busy.

Yeah, maybe I shouldn't have called it "margin," it's inaccurate.
In particular, this method doesn't actually track the margin usage (which
seems unnecessary).
Maybe it should be some Equity account.

There's some other discussion about futures contracts here:
https://docs.google.com/document/d/1H0UDD1cKenraIMe40PbdMgnqJdeqI6yKv0og51mXk-0/edit

The other problem is inferring the multiplier. That's not done.
https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/edit#heading=h.b30u633jlv5x
I'm thinking the instrument names maybe should have a multiplier in them,
or we should have some global option to register a prefix-to-multiplier
mapping.




On Fri, Dec 8, 2023 at 3:24 PM Dan Andersson 
wrote:

> I just found another approach:
> https://groups.google.com/g/beancount/c/OIjyBo-Ehu0/m/b3ujN_oMAQAJ
>
> If I understand correctly, he simply has a phantom account that offsets
> the initial notional value and track only PnL afterwards. This phantom
> account offers a nice hack to deal with futures. However, for some reason
> he calls this "margin" (not sure why, maybe this is special Ameritrade
> terminology).
>
> On Friday, December 8, 2023 at 6:06:57 PM UTC Dan Andersson wrote:
>
>> I think I can get a fully customizable experience by using "NONE" and
>> zero cost basis. Please critique this:
>>
>> ;--
>> 2014-05-20 open Assets:Futures:GOLD-DEC-24 GOLD-DEC-24 "NONE"
>> 2014-05-20 open Assets:Citibank:Cash USD
>> 2014-05-20 open Income:CapitalGains USD
>> 2014-05-20 open Expenses:CapitalLosses USD
>>
>> 2014-05-20 * "Buy GOLD-DEC-24 @1000.0"
>>   Assets:Futures:GOLD-DEC-24  2 GOLD-DEC-24  { 0 USD }
>>
>> 2014-05-21 * "Sell GOLD-DEC-24 @1010.0"
>>   Assets:Futures:GOLD-DEC-24  -1 GOLD-DEC-24  { 0 USD }
>>   Assets:Citibank:Cash 10 USD
>>   Income:CapitalGains -10 USD
>>
>> 2014-05-22 * "Sell GOLD-DEC-24 @990.0"
>>   Assets:Futures:GOLD-DEC-24  -1 GOLD-DEC-24  { 0 USD }
>>   Assets:Citibank:Cash -10 USD
>>   Expenses:CapitalLosses 10 USD
>> ;--
>>
>> Advantage: Full control.
>>
>> Drawbacks:
>>
>>1. The cost basis is just a dummy value (only to "enable a custom
>>experience").
>>2. I lose Beancount's automatic mismatch checks on futures quantity
>>vs. cash.
>>3. I also lose Beancount's automatic matching; have to do matching
>>and PnL calculations myself.
>>4. Beancount reporting doesn't automatically reflect unrealized gains.
>>
>> Is this on the right track? (Point 4 is very unfortunate but I could
>> alleviate that by e.g. annual (December 31) entry to record unrealized
>> gains.)
>>
>> Thanks,
>> Dan
>>
>> On Tuesday, December 5, 2023 at 10:10:03 PM UTC Dan Andersson wrote:
>>
>>> Hi,
>>>
>>> For stocks (and even options), you pay for a thing (or short sell a
>>> thing) and cash leaves (or comes into) your cash account. Very clear. The
>>> cash is price * quantity * multiplier.
>>>
>>> Futures are different. No cash leaves/arrives in the beginning.
>>> Basically the value starts at zero. Only price differences over time matter
>>> and only when closing position does realized PnL bring cash in/out of cash
>>> account.
>>>
>>> How to deal with this in Beancount? Should I set the Beancount price to
>>> zero at first (and e.g. for informational purposes put the actual market
>>> price into the comment)?
>>>
>>> (I realize there is margin but that's just a virtual allocation of sorts
>>> (cash is still in the cash account), cannot really be determined from the
>>> price, plus it varies from time to time depending on volatility etc.)
>>>
>>> Thanks,
>>> Dan
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Beancount" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beancount+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beancount/2aabf18c-ce90-4475-9b07-0c4023e0f657n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/CAK21%2BhM9GqmNvx1_-XOBvGaGaBk_h%2BzzL%3DOb9xsEi7J2UPMiKA%40mail.gmail.com.

Re: Dealing with futures

[Dan Andersson]

I just found another approach: 
https://groups.google.com/g/beancount/c/OIjyBo-Ehu0/m/b3ujN_oMAQAJ

If I understand correctly, he simply has a phantom account that offsets the 
initial notional value and track only PnL afterwards. This phantom account 
offers a nice hack to deal with futures. However, for some reason he calls 
this "margin" (not sure why, maybe this is special Ameritrade terminology).

On Friday, December 8, 2023 at 6:06:57 PM UTC Dan Andersson wrote:

> I think I can get a fully customizable experience by using "NONE" and zero 
> cost basis. Please critique this:
>
> ;--
> 2014-05-20 open Assets:Futures:GOLD-DEC-24 GOLD-DEC-24 "NONE"
> 2014-05-20 open Assets:Citibank:Cash USD
> 2014-05-20 open Income:CapitalGains USD
> 2014-05-20 open Expenses:CapitalLosses USD
>
> 2014-05-20 * "Buy GOLD-DEC-24 @1000.0"
>   Assets:Futures:GOLD-DEC-24  2 GOLD-DEC-24  { 0 USD }
>
> 2014-05-21 * "Sell GOLD-DEC-24 @1010.0"
>   Assets:Futures:GOLD-DEC-24  -1 GOLD-DEC-24  { 0 USD }
>   Assets:Citibank:Cash 10 USD
>   Income:CapitalGains -10 USD
>
> 2014-05-22 * "Sell GOLD-DEC-24 @990.0"
>   Assets:Futures:GOLD-DEC-24  -1 GOLD-DEC-24  { 0 USD }
>   Assets:Citibank:Cash -10 USD
>   Expenses:CapitalLosses 10 USD
> ;--
>
> Advantage: Full control.
>
> Drawbacks:
>
>1. The cost basis is just a dummy value (only to "enable a custom 
>experience").
>2. I lose Beancount's automatic mismatch checks on futures quantity 
>vs. cash.
>3. I also lose Beancount's automatic matching; have to do matching and 
>PnL calculations myself.
>4. Beancount reporting doesn't automatically reflect unrealized gains.
>
> Is this on the right track? (Point 4 is very unfortunate but I could 
> alleviate that by e.g. annual (December 31) entry to record unrealized 
> gains.)
>
> Thanks,
> Dan
>
> On Tuesday, December 5, 2023 at 10:10:03 PM UTC Dan Andersson wrote:
>
>> Hi,
>>
>> For stocks (and even options), you pay for a thing (or short sell a 
>> thing) and cash leaves (or comes into) your cash account. Very clear. The 
>> cash is price * quantity * multiplier.
>>
>> Futures are different. No cash leaves/arrives in the beginning. Basically 
>> the value starts at zero. Only price differences over time matter and only 
>> when closing position does realized PnL bring cash in/out of cash account.
>>
>> How to deal with this in Beancount? Should I set the Beancount price to 
>> zero at first (and e.g. for informational purposes put the actual market 
>> price into the comment)?
>>
>> (I realize there is margin but that's just a virtual allocation of sorts 
>> (cash is still in the cash account), cannot really be determined from the 
>> price, plus it varies from time to time depending on volatility etc.)
>>
>> Thanks,
>> Dan
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/2aabf18c-ce90-4475-9b07-0c4023e0f657n%40googlegroups.com.

Re: Dealing with futures

[Dan Andersson]

I think I can get a fully customizable experience by using "NONE" and zero 
cost basis. Please critique this:

;--
2014-05-20 open Assets:Futures:GOLD-DEC-24 GOLD-DEC-24 "NONE"
2014-05-20 open Assets:Citibank:Cash USD
2014-05-20 open Income:CapitalGains USD
2014-05-20 open Expenses:CapitalLosses USD

2014-05-20 * "Buy GOLD-DEC-24 @1000.0"
  Assets:Futures:GOLD-DEC-24  2 GOLD-DEC-24  { 0 USD }

2014-05-21 * "Sell GOLD-DEC-24 @1010.0"
  Assets:Futures:GOLD-DEC-24  -1 GOLD-DEC-24  { 0 USD }
  Assets:Citibank:Cash 10 USD
  Income:CapitalGains -10 USD

2014-05-22 * "Sell GOLD-DEC-24 @990.0"
  Assets:Futures:GOLD-DEC-24  -1 GOLD-DEC-24  { 0 USD }
  Assets:Citibank:Cash -10 USD
  Expenses:CapitalLosses 10 USD
;--

Advantage: Full control.

Drawbacks:

   1. The cost basis is just a dummy value (only to "enable a custom 
   experience").
   2. I lose Beancount's automatic mismatch checks on futures quantity vs. 
   cash.
   3. I also lose Beancount's automatic matching; have to do matching and 
   PnL calculations myself.
   4. Beancount reporting doesn't automatically reflect unrealized gains.
   
Is this on the right track? (Point 4 is very unfortunate but I could 
alleviate that by e.g. annual (December 31) entry to record unrealized 
gains.)

Thanks,
Dan

On Tuesday, December 5, 2023 at 10:10:03 PM UTC Dan Andersson wrote:

> Hi,
>
> For stocks (and even options), you pay for a thing (or short sell a thing) 
> and cash leaves (or comes into) your cash account. Very clear. The cash is 
> price * quantity * multiplier.
>
> Futures are different. No cash leaves/arrives in the beginning. Basically 
> the value starts at zero. Only price differences over time matter and only 
> when closing position does realized PnL bring cash in/out of cash account.
>
> How to deal with this in Beancount? Should I set the Beancount price to 
> zero at first (and e.g. for informational purposes put the actual market 
> price into the comment)?
>
> (I realize there is margin but that's just a virtual allocation of sorts 
> (cash is still in the cash account), cannot really be determined from the 
> price, plus it varies from time to time depending on volatility etc.)
>
> Thanks,
> Dan
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/d0ace714-befb-428b-96e9-87b04b082475n%40googlegroups.com.

Re: Help a Beginner with Red's CSV Importer?

[Chris Bond]

Thanks! Will test this out.

On Friday, December 8, 2023 at 3:33:44 AM UTC-5 Red S wrote:

> Argh, don’t have my laptop now, so this is hard, but with the init 
> function, the right hand fields in the dictionary are internal, and fixed. 
> The left hand side corresponds to your csv file.
>
> Date,Description,Amount,Unapplied,Balance
> def custom_init(self): self.max_rounding_error = 0.04 
> self.filename_pattern_def = '.*' self.header_identifier = 
> 'Date,Description,Amount,Unapplied,Balance', self.date_format = '%m/%d/%Y' # 
> <--- this is incorrect, change this self.header_map = { "Description": 
> 'payee', "Date": 'date', "Amount": 'amount', "Balance": 'balance', } 
>
> I can’t remember of the top of my head if you need a 
> get_balance_statement() function to generate the balance assertion. If 
> you do, it’ll look like this 
> 
> .
>
> This is all untested. If that doesn’t work, let me know.
> ​
>
>
> On Friday, December 8, 2023 at 12:19:53 AM UTC-8 Red S wrote:
>
>> Hello there,
>> Author here. Given how simple your csv file is, I’d suggest using 
>> Beancount’s built in csv importer 
>> .
>>  
>> Something like this in your my.import file (untested):
>> csv.Importer({Col.DATE: 'Date', Col.NARRATION1: 'Description', 
>> Col.AMOUNT: 'Amount', }, 'Assets:Bank1', 'USD', ('Date','Description',
>> 'Amount','Unapplied','Balance')), 
>>
>> The only advantage you get with my reds-importers is balance assertions. 
>> I'll post and example in a minute.
>> ​
>>
>>
>> On Thursday, December 7, 2023 at 7:06:19 PM UTC-8 micro...@gmail.com 
>> wrote:
>>
>>> I have what I think may be a very simple CSV file:
>>>
>>> Column headers are these:
>>> Date,Description,Amount,Unapplied,Balance 
>>>
>>> Corresponding data fields look like this:
>>> Dec 1, 2023,PAYMENT,$951.28,$951.28,$25,000.62
>>>
>>> I have had some success using Red's ofx importer framework, but am 
>>> really struggling to figure out the CSV importer from the examples in the 
>>> git repo. I started with the Discover example that looks like this:
>>>
>>> from beancount_reds_importers.libreader import csvreader
>>> from beancount_reds_importers.libtransactionbuilder import banking
>>>
>>> class Importer(csvreader.Importer, banking.Importer):
>>> IMPORTER_NAME = """ Discover credit card .csv importer."""
>>>
>>> def custom_init(self):
>>> self.max_rounding_error = 0.04
>>> self.filename_pattern_def = 'Discover.*'
>>> self.header_identifier = 'Trans. Date,Post 
>>> Date,Description,Amount,Category'
>>> self.date_format = '%m/%d/%Y'
>>> self.header_map = {
>>> "Category":'payee',
>>> "Description": 'memo',
>>> "Trans. Date": 'date',
>>> "Post Date":   'postDate',
>>> "Amount":  'amount',
>>> }
>>>
>>> def skip_transaction(self, ot):
>>> return False
>>>
>>> def prepare_processed_table(self, rdr):
>>> # Need to invert numbers supplied by Discover
>>> rdr = rdr.convert('amount', lambda x: -1 * x)
>>> return rdr
>>>
>>> I'm pretty sure I don't need the def skip_transaction(self, ot) and def 
>>> prepare_processed_table(self, rdr): bits, but am at a loss to figure out 
>>> what fields I need to modify in the def custom_init(self) for my situation. 
>>> There is not an example CSV file for that importer in the repo so it makes 
>>> it a little more challenging for me to hack on it. I think I don't need the 
>>> "Unapplied" column but am not sure. Even just some hints would be really 
>>> helpful. 
>>>
>>> Thank you in advance!
>>> Chris
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/07526f71-d609-4619-babc-d035c67871aen%40googlegroups.com.

Re: bean-price with yahoo reporting invalid currency

[kunagu varun kumar]

Awesome. Thanks for this

On Tuesday, December 5, 2023 at 1:58:54 AM UTC-6 chrisb...@gmail.com wrote:

> ...and without repeating Friday prices for weekend days:
>>
>  
> leaving out "--update-rate daily" will do that in bean-price:
>
> bean-price input.beancount --update --inactive --clear-cache
> 2023-12-01 price USD 83.35269927978516 INR
> 2023-12-04 price USD 83.21859741210938 INR
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/af437d57-bdaf-43f1-86da-317b4cbd27ecn%40googlegroups.com.

Re: Help a Beginner with Red's CSV Importer?

[Red S]

Argh, don’t have my laptop now, so this is hard, but with the init 
function, the right hand fields in the dictionary are internal, and fixed. 
The left hand side corresponds to your csv file.

Date,Description,Amount,Unapplied,Balance
def custom_init(self): self.max_rounding_error = 0.04 
self.filename_pattern_def = '.*' self.header_identifier = 
'Date,Description,Amount,Unapplied,Balance', self.date_format = '%m/%d/%Y' # 
<--- this is incorrect, change this self.header_map = { "Description": 
'payee', "Date": 'date', "Amount": 'amount', "Balance": 'balance', } 

I can’t remember of the top of my head if you need a get_balance_statement() 
function to generate the balance assertion. If you do, it’ll look like this 

.

This is all untested. If that doesn’t work, let me know.
​


On Friday, December 8, 2023 at 12:19:53 AM UTC-8 Red S wrote:

> Hello there,
> Author here. Given how simple your csv file is, I’d suggest using 
> Beancount’s built in csv importer 
> .
>  
> Something like this in your my.import file (untested):
> csv.Importer({Col.DATE: 'Date', Col.NARRATION1: 'Description', 
> Col.AMOUNT: 'Amount', }, 'Assets:Bank1', 'USD', ('Date','Description',
> 'Amount','Unapplied','Balance')), 
>
> The only advantage you get with my reds-importers is balance assertions. 
> I'll post and example in a minute.
> ​
>
>
> On Thursday, December 7, 2023 at 7:06:19 PM UTC-8 micro...@gmail.com 
> wrote:
>
>> I have what I think may be a very simple CSV file:
>>
>> Column headers are these:
>> Date,Description,Amount,Unapplied,Balance 
>>
>> Corresponding data fields look like this:
>> Dec 1, 2023,PAYMENT,$951.28,$951.28,$25,000.62
>>
>> I have had some success using Red's ofx importer framework, but am really 
>> struggling to figure out the CSV importer from the examples in the git 
>> repo. I started with the Discover example that looks like this:
>>
>> from beancount_reds_importers.libreader import csvreader
>> from beancount_reds_importers.libtransactionbuilder import banking
>>
>> class Importer(csvreader.Importer, banking.Importer):
>> IMPORTER_NAME = """ Discover credit card .csv importer."""
>>
>> def custom_init(self):
>> self.max_rounding_error = 0.04
>> self.filename_pattern_def = 'Discover.*'
>> self.header_identifier = 'Trans. Date,Post 
>> Date,Description,Amount,Category'
>> self.date_format = '%m/%d/%Y'
>> self.header_map = {
>> "Category":'payee',
>> "Description": 'memo',
>> "Trans. Date": 'date',
>> "Post Date":   'postDate',
>> "Amount":  'amount',
>> }
>>
>> def skip_transaction(self, ot):
>> return False
>>
>> def prepare_processed_table(self, rdr):
>> # Need to invert numbers supplied by Discover
>> rdr = rdr.convert('amount', lambda x: -1 * x)
>> return rdr
>>
>> I'm pretty sure I don't need the def skip_transaction(self, ot) and def 
>> prepare_processed_table(self, rdr): bits, but am at a loss to figure out 
>> what fields I need to modify in the def custom_init(self) for my situation. 
>> There is not an example CSV file for that importer in the repo so it makes 
>> it a little more challenging for me to hack on it. I think I don't need the 
>> "Unapplied" column but am not sure. Even just some hints would be really 
>> helpful. 
>>
>> Thank you in advance!
>> Chris
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/b483cfbd-bfe3-4438-b147-c2b93dfebe81n%40googlegroups.com.

Re: Help a Beginner with Red's CSV Importer?

[Red S]

Hello there,
Author here. Given how simple your csv file is, I’d suggest using 
Beancount’s built in csv importer 
.
 
Something like this in your my.import file (untested):
csv.Importer({Col.DATE: 'Date', Col.NARRATION1: 'Description', Col.AMOUNT: 
'Amount', }, 'Assets:Bank1', 'USD', ('Date','Description','Amount',
'Unapplied','Balance')), 

The only advantage you get with my reds-importers is balance assertions. 
I'll post and example in a minute.
​


On Thursday, December 7, 2023 at 7:06:19 PM UTC-8 micro...@gmail.com wrote:

> I have what I think may be a very simple CSV file:
>
> Column headers are these:
> Date,Description,Amount,Unapplied,Balance 
>
> Corresponding data fields look like this:
> Dec 1, 2023,PAYMENT,$951.28,$951.28,$25,000.62
>
> I have had some success using Red's ofx importer framework, but am really 
> struggling to figure out the CSV importer from the examples in the git 
> repo. I started with the Discover example that looks like this:
>
> from beancount_reds_importers.libreader import csvreader
> from beancount_reds_importers.libtransactionbuilder import banking
>
> class Importer(csvreader.Importer, banking.Importer):
> IMPORTER_NAME = """ Discover credit card .csv importer."""
>
> def custom_init(self):
> self.max_rounding_error = 0.04
> self.filename_pattern_def = 'Discover.*'
> self.header_identifier = 'Trans. Date,Post 
> Date,Description,Amount,Category'
> self.date_format = '%m/%d/%Y'
> self.header_map = {
> "Category":'payee',
> "Description": 'memo',
> "Trans. Date": 'date',
> "Post Date":   'postDate',
> "Amount":  'amount',
> }
>
> def skip_transaction(self, ot):
> return False
>
> def prepare_processed_table(self, rdr):
> # Need to invert numbers supplied by Discover
> rdr = rdr.convert('amount', lambda x: -1 * x)
> return rdr
>
> I'm pretty sure I don't need the def skip_transaction(self, ot) and def 
> prepare_processed_table(self, rdr): bits, but am at a loss to figure out 
> what fields I need to modify in the def custom_init(self) for my situation. 
> There is not an example CSV file for that importer in the repo so it makes 
> it a little more challenging for me to hack on it. I think I don't need the 
> "Unapplied" column but am not sure. Even just some hints would be really 
> helpful. 
>
> Thank you in advance!
> Chris
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/3a0039f7-8d93-4e38-ab6b-416c2316cb09n%40googlegroups.com.