portablefoki.blogg.se

Gnucash move transaction to another account
Gnucash move transaction to another account







gnucash move transaction to another account

If no option directive is included, it will default to ISO8601. An option directive could be created that lets users chose their preference of date format. However, I still think this is an area that can and *should* be improved. With this information, I do agree that ISO8601 is the best choice to default to. Many people have pointed out that it creates an ambiguity in how it would be parsed if you supported both and unfair if you supported just one. I admit I had a brain fart and forgot that there is a DD/MM/YYYY format in everyday use in other countries when I wrote that suggestion. I clearly walked into this landmine, not realizing it would be such a contentious issue. After looking over the documentation, I am guessing the best course of action currently would be to log an event directive? I still want to keep the records of the accounts the check was issued to/from, though, so would that go into metadata on the event. Ideally, there would be a flag to mark voided transactions as there are '!' for incomplete or uncleared transactions, and '*' for completed transactions, there could be a 'v' or some other symbol to mark voided transactions. This feature is helpful because there is never a missing check number that is unaccounted for. If I issue a check, say check #126 to John Smith, it is a negotiable instrument, so it goes into the ledger if something were to happen after the issuance which required it to be voided, maybe it was never received or was misprinted I need a way to keep the record in the ledger because a check was printed, and simply mark that it has been invalidated. As for voided transactions, this again comes from the issuance of checks. So, when I asked about reverse transactions, I had misread something in the documentation, which caused me confusion. Ledger-cli and hledger support different date formats. Supportingīoth, however, is not possible as this would be ambiguous. One (actually, I see reasons to prefer the European one). Supporting the US locale date format should be preferred to the European PleaseĪlso note that the most common date format in Europe is DD/MM/YYYY (withĭiffernet separators depending on the specific locale). The choice of the date format is deliberate. > between the ISO8601 and the US method, as the four-digit year is either > modified to accept both types as I do not believe there is any ambiguity > record, the US typically uses MM/DD/YYYY dates, and it's almost unheard

gnucash move transaction to another account

My most minor gripe, though, it is pretty jarring being in the US, is









Gnucash move transaction to another account