On Saturday, September 28, 2024 at 11:40:50 PM UTC+2 Rick F wrote:



;; fields are as follows :
;;      donor-id : a string defining a unique identifier that can be used 
to identify this donor
;;      donor-name : a string containing the name of the donor
;;      donor-address : a string of the address for the donor
;;      donor-city : a string containing the city the donor lives in
;;      donor -state : donor's state
;;      donor-zipcode : donor's zip code
;;      donor-phone : donors phone number
;;      donor-email : email address of donor
2024-09-28 custom "Donor" "john-smith" "John Smith" "123 First Street" 
"Palo Alto" "CA" "93501" "123-456-7890" "[email protected]"



Why do you want to keep all this information in the beancount ledger?

I would just keep keep it somewhere else (e.g. in Excel file). What is 
important in beancount is to put in a transaction some piece of 
information, which will allow you to uniquely identify a donor. In a 
simplest term this can be just a payee field

E.g.:  

2024-09-28 * "john-smith" "Donation"
  Assets:US:WellsFargo:Checking4431 -100.00 USD
  Income:US:Donations

You can then run a query, which will show you a total amount of donations 
per payee. E.g.:

select payee, sum(position)
where account = 'Income:US:Donations' and year 2014

You then import query result in Excel and just VLOOKUP address, name, city 
etc in Excel.

There is no reason to do all of this directly in beancount. 

And if you want to automate it further, you can build all this logic 
somewhere in Jupyter notebook.

Does it make sense?
 

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/9019235b-c62d-42da-9de5-28793bb41153n%40googlegroups.com.

Reply via email to