abijah 4ee9c99e30 It's clear that the current statement entry solution is a problem, since a) the account_id member of StatementEntry is not accurate when multiple ledger entries contribute to a single statement entry, and b) there is no definitive way to tie StatementEntry to LedgerEntry. The latter isn't too big an issue, but it would certainly be a problem if we allowed transaction editing. If user wanted to change a statement entry account (say from rent to late charge, or from check to cash), there wouldn't be an absolute way to know which ledger entry(ies) to change as well. ...

git-svn-id: file:///svn-source/pmgr/branches/statement_ledger_entry_tie_20090802@467 97e9348a-65ac-dc4b-aefc-98561f571b83

2009-08-03 02:14:20 +00:00

db

Added a new statement entry type, 'WAIVE', and added the beginnings of a function to add a new waiver transaction. Haven't even started the work yet though...

2009-08-02 22:44:55 +00:00

scripts

Must have had a brain freeze to be placing closing monies directly in Equity, since it is a credit account and doing so only ran the account into a negative balance. Transfers out of A/R need to go to an asset account, and so I reverted this back to Closing.

2009-07-31 03:36:11 +00:00

site

Added a new statement entry type, 'WAIVE', and added the beginnings of a function to add a new waiver transaction. Haven't even started the work yet though...

2009-08-02 22:44:55 +00:00

build.cmd

Got rid of the massive variable dump to stdout, and so moved all of the STDERR prints back to STDIN. Also hooked up root_transaction_id, although it's not being used yet (and may never be).

2009-07-09 01:21:21 +00:00

requirements.txt

Updated todo and requirements

2009-07-31 18:13:26 +00:00

todo.notes

Updated todo and requirements

2009-07-31 18:13:26 +00:00

Description

Storage Property Manager Software

3.9 MiB

Languages

PHP 76.4%

CSS 18.7%

JavaScript 4.9%