On Wed, Feb 17, 2021 at 10:04 AM Tomás de Almeida <[email protected]> wrote:
> Thanks for your input Colin. > > I was thinking about doing something very simple and barebones. Akin to > having job that extracts and parses daily transaction reports from the > company's bank account into the main ledger data file. > > I imagine some of the transactions would be easy to automate as writing > them into the proper category: repeat customers, periodic fees of > subscribed services, etc. > There are CSV converters in https://github.com/ledger/ledger/wiki/CSV-Import Another simple one using sed: Say you can export from the bank in this format: *bankExtract.txt* 2021-02-01 SOME TRANSACTION FEE $87.77 ... *textToLedger_sed_commands.sed* ## s/[[:space:]]\+/ /g ## uncomment to convert tabs to spaces s/SOME TRANSACTION FEE/* Bank fee \n ; someMetadata: someValue \n myCategory:mySubCategory /g /Bank fee/ s/$/\n bankName\n\n/ *textToLedger.sh* #!/bin/bash f1=~/path/to/bankExtract.txt f2=~/path/to/bankExtract_processed.ldg tsed -f ~/path/to/script/textToLedger_sed_commands.sed $f1 > $f2 cat $f2 > 2021-02-01 * Bank fee ; someMetadata: someValue myCategory:mySubCategory $87.77 bankName > > The "new" transactions would always be a mistery on which category they > should be parsed, so they would go into a "to insert manually later" file > that we would hsve to take a look from time to time. > > It would be impossible to automate book-keeping 100% this way, but if we > could at least eliminate having to manually insert the predictable ones > (server costs, office costs, salaries) I believe it would save us some > buraucracy. > > What do you think? > > On Wed, 17 Feb 2021, 05:28 Colin Dean, <[email protected]> wrote: > >> I've got some custom code in a Sinatra app written in Ruby that's taking >> Stripe webhook posts, transforming them into Ledger records, and submitting >> them as PRs on a GitLab repo. It's slick... when it works. GitLab's "merge >> on successful CI build" doesn't always work and multiple open PRs turn into >> a merge conflict exponential nightmare. The downside is that Stripe doesn't >> seem to include fee information on these posts so I have to go back into >> Stripe once in a while to look up fees. It's not so bad for the ~5-10 txns >> per month I see normally but when there are bursts of 40-50 in a month, >> it's another task on the procrastination pile. >> >> Most of my "automation" is using ledger-autosync to *manually* monthly >> or quarterly sync CSVs, etc. I downloaded and cleaned up. I have only one >> financial institution in my life that provides clean CSV output, sigh. >> >> On Tuesday, February 16, 2021 at 7:40:30 AM UTC-5 Tom.PLAA wrote: >> >>> Hello everyone, >>> >>> I've recently come across ledger and the concept of PTA and I amvery >>> intrigued. >>> >>> As I am not an experienced programmer nor have a software engineering >>> background, I am eager to see your opinions on how realistic it is to use >>> ledger (or one of its brothers) to help industrialize accounting and/or >>> book-keeping for a small business. >>> My idea is roughly to use ledger as the "backend" and find some way to >>> automate most of the data insertions - maybe by parsing bank extracts and >>> automating the "add" function to the main transaction data file (thinking >>> about using it as a single file for all book-keeping now, as suggested in >>> the hledger FAQ). >>> >>> My main goals for this particular task are: >>> >>> 1. Spend zero money on accounting software and use something I can >>> read the code of; >>> 2. Minimize manual transaction recording and general book-keeping >>> tasks; >>> 3. Be able to produce clean reports and export data to give to an >>> accountant (hoping I can strike some deal where an accountant will lower >>> the fees if I provide clean data and reduce their worload). >>> >>> As this been done, and if so, how feasible is it to maintain? >>> >>> Is ledger a good choice for the tasks mentioned above, or is hledger (or >>> another project) better suited for this? >>> >>> >>> Thank you for the attention, >>> >>> Tomás >>> >>> >>> -- >> >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "Ledger" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/ledger-cli/ODCt1PM1oJc/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ledger-cli/cca73f98-00f3-4e73-b3eb-c85d1ea9c835n%40googlegroups.com >> <https://groups.google.com/d/msgid/ledger-cli/cca73f98-00f3-4e73-b3eb-c85d1ea9c835n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > > --- > You received this message because you are subscribed to the Google Groups > "Ledger" 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/ledger-cli/CABO43G1poiUa1Dj7Khv05LLeo63ydYDoWU72qufWeNzaj2atpA%40mail.gmail.com > <https://groups.google.com/d/msgid/ledger-cli/CABO43G1poiUa1Dj7Khv05LLeo63ydYDoWU72qufWeNzaj2atpA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- --- You received this message because you are subscribed to the Google Groups "Ledger" 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/ledger-cli/CAPYcn%3D5pr4%3Dhe7w9vJZKMi%3Dxk-5tVJYFY7Zi_QpM5xAaieiKxg%40mail.gmail.com.
