| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
solution.
Ledger has had (probably for some time) an "accounts" command that will list
all the accounts from all transactions meeting the other criteria set on the
command line. That's really what we're looking for here when we build this
chart of accounts, and thus that should be used.
Note that this corrects a subtle bug that wasn't apparent with the old
solution. With the '-F "%150A\n" reg' solution, accounts that balanced out
to zero for period (e.g., accrual accounts that were emptied during in the
month) did not show up on the reports. This bug that I didn't know I had
here is thus now fixed by switching to the "accounts" report.
|
| |
|
|
|
|
| |
There were a few spots where they were still sneaking in.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sub-accounts.
The previous queries had a bug whereby an account in the form "A:B" would
include all transactions for sub accounts such as "A:B:C".
That's not the intended effect. Entries should appear in the lowest level
account, and not in their parent.
The regular expression now is anchored at start and finish in both queries to
ensure this works correctly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
MANIFEST.
Previous version of csv2ods.py simply assumed that fields beyond five
would have links to files. This obviously lacked flexibility and was a
silly hard-code. Now, those CSV fields that have link:SOMETHING will
cause a hyperlink to be created to SOMETHING.
Meanwhile, the pagebreak support was similarly hard-coded. Now, any CSV
field that has the word "pagebreak" in it will generate a pagebreak.
The general ledger and cash receipts/disbursement journals have been
modified to make use of these new features in csv2ods.py.
Finally, the --skip-page-break option is now moot in csv2ods.py, so that
is herein removed.
|
|
|
|
|
|
| |
Based on a request from our accountants, I've changed the RUNNING TOTAL
field (which is generally useless to accountants anyway) to be a BALANCE
amount for starting and ending accounts.
|
|
|
|
| |
This fix now has the sort working correctly.
|
|
|
|
| |
This includes adding a formatted start date string too.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our auditing accounts tell us they want accounts sorted by:
Assets
Liabilities
Net Assets
Income
Expenses
in a general ledger report. Generally, I think we should just apply the
same sorting.
Since Ledger doesn't use account codes by default, this is my hack to
solve this problem for now. Maybe there should be an account code tag for
sorting purposes at least?
|
|
|
|
|
| |
Keep a hash so that file output to the MANIFEST file doesn't have
duplicates of the same file name in it.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Due to reporting options given to ledger, not every file will be
referenced by the general-ledger spreadsheet. The generated MANIFEST file
now indicates which files were actually referenced in the general-ledger.
The demo.sh script now uses this MANIFEST to create a zip file that
contains only those files.
|
|
|
|
|
|
|
|
|
|
| |
I've now made a hard-coded list of potential tags that are supported and
will be linked to in the general ledger spreadsheet. This list should
probably be in a configuration file of some sort eventually, rather than
hard coded.
Indeed, note that the hard-coding goes into two different scripts, and
thus the lists could easily get out of sync.
|
|
|
|
|
|
|
|
|
| |
Change the column of Receipt and Invoice in the CSV file first, then the
generated ODS file must have the same change propagated, which requires
changes to the column numbers hard-coding in csv2ods.py.
Perhaps if/when this application is refactored these things shouldn't be
hard-coded in this way in the first place.
|
| |
|
|
|
|
| |
Both Tom and I have made copyrightable changes to this file this year.
|
|
|
|
| |
Added sample PDF artifacts for the example (see README)
|
| |
|
|
|
|
|
| |
* --wide-register-format is no long an option, use -F
* %D now must be %(date)
|
| |
|
|
auditors.
I developed this, and therefore have the full git commit history, in my
personal "Small-Hacks" repository, which can be cloned from:
git://gitorious.org/bkuhn/small-hacks.git
More details on that are available by visiting:
https://gitorious.org/bkuhn/small-hacks
|