@bojack no pro yet, Iām just a developer by profession that has some accounting education Much to learn about beancount - have not even touched anything related to tracking stock tradingā¦
I agree with @tarioch - developers are in the situation that they can write or adjust the importers as needed. And thatās a lot of manual labor saved. Imagine to get your whole yearās bank statement into a beancount in one click, and then spend couple of minutes to skim over it to fix and re-categorize some exception cases. PDF are a nightmare indeed, but csv are easy (unless your bank is very creative in breaking the data structure within, like I have oneā¦). Everyone exports csvās (or at least in xls, which you open in excel and then re-save as csv). The problem is that importers are kinda personal due categorization. If you ever wanted to pickup some scripting/programming, I highly, highly recommend to write an importer for one of your banks. If you can find an existing importer above, thatās perfect - just use it as starting place, and donāt hesitate to fix/adjust as needed. Hereās an importer for revolut I have not tried. Good luck!
As per plugins, yes, they may make whole thing less maintainable. May also make more maintainable I personally love my oneliner plugin, itās a perfect plugin for manual input - first one-line-one-tx resonates with me very well, second as 4x more txs are within my screen the whole file becomes more readable/scannable, and third for input just copy a similar line and adjust some values (most txs are repetitive anyways). If you wonāt try you wonāt know if it works for you.
From accounting perspective my advice would be - donāt bother to count every cent, and usually the last cents are the hardest Itās just waste of time for barely any information gained. For such catchup events my strategy is as follows:
- write balances for everything (cash, bank1, bank2, ā¦)
- run importers where I have them (all banks), fix or adjust categorization as needed.
- write-off the difference to
Expenses:Unknown
(usually just cash), and spread it over the period since last catchup. Iām a cash person, so usually thatās an uncomfortable huge amount per day at first
- search for receipts or try remember where I spent it. Write it down. Lower the write-off.
- repeat step 4 until unknown expenses are comfortably small enough. Leave it like that and stop here.
Iāve had catchups for 3 months - thatās an one dedicated evening (in theory). Unless I get distracted in philosophy of categorization, overhaul my ledger to account for partner, or need to create a new importer, or start to work on long-wished for plugin. I enjoy writing plugins more than entering data, soā¦ as you see, I just published the share plugin (+/- week work) but havenāt yet done my own catchup
I have never filled a backlog of a year Actually for a year it wonāt make a difference, because importers donāt care about amount of transactions. Itās just more transactions to review (fast anyways), and more receipts to enter (still in magnitude of one evening). Buuutā¦ a backlog for a year means itās a lot more likely I got a new bank (or existing bank changed the csv structure) or any other distraction happened. I had never had a ācalmā year so far, therefore, practically, could even be weeks.
Hope that helps and putās your own time in perspective. Cheers!