The business logistics part of time cards as I understand it: You fill in the time cards when working, per project. And you make a difference for hours to be billed (invoiced) and hours made allright, but not bill-able to the client (project).
Then at the end of e.g. a week you create sales orders from time cards. And then you create invoices from the sales orders. Resulting in say 30 hours for 3 different projects to be invoiced to clients (projects) and 10 hours not to be invoiced . Now the over-all boss knows you put in the required number of hours, (40) and all customers that need to get an invoice do so. In your case, the money received up front (retainer, whatever) can than be applied to the invoices raised, and all is well from an accounting point of view. That method should also take care of the open time cards as well; all hours are closed. Either for x per hour or for zero per hour. An a side note, psychologically it is sound to show the zero hours on the invoices as well anyways. Just so the client KNOWS (sees) you do research, but think that is part of the job / your permanent education and not to be billed seperately. Same for service calls or things like guarantee on previous work: show it and bill for zero makes it very clear to everybody concerned. 2010/6/11 Rich Shepard <[email protected]> > On Fri, 11 Jun 2010, Paul Tammes wrote: > > Workaround hint: >> >> Do not touch the old project X and open a new project X-2010 or even >> X-2010-06 >> > > Paul, > > I don't think that would work. The project is the same; we had to > determine if the plaintiff would settle or the judge would issue a summary > judgement for the defense. No and no, so we go to trial and I have to > prepare my expert witness testimony. Same project. > > Why the February time cards were not closed when I prepared that month's > statement I've no idea. Probably because the entire process of preparing a > statement of time expended against a received retainer payment is still not > completely clear to me. > > There must be a field in one of the postgres tables that changes each > individual time card row to 'closed.' Doing so manually from the psql > interface is fine with me as long as I know what table is involved. Then > it's a matter of 'UPDATE <table> SET <status_column> = 'closed' where > <timecard_number_column> in (<list of timecards>;'. > > > Rich > > _______________________________________________ > SQL-Ledger mailing list > [email protected] > http://lists.ledger123.com/mailman/listinfo/sql-ledger >
_______________________________________________ SQL-Ledger mailing list [email protected] http://lists.ledger123.com/mailman/listinfo/sql-ledger
