As in once you start using projects, you will have to use a project (or project blank) per invoice where applicable. Vversus not using projects at all that is.
2011/3/10 Rich Shepard <[email protected]> > On Wed, 9 Mar 2011, Paul Tammes wrote: > > Did you think about using PROJECTS for this? >> > > Paul, > > Not only did I think about this, but I've used projects since I started > with SL about 7 years ago. > > > If you attach the project to both income (issued retainer invoices or even >> G/L entries eg. bank debit, project income account credit) and expenses >> (billed hours, used astationary, whatever) you can then use a simple >> income statement for the specific project for any given date. Or leave >> dates blank for an overview over all periods including previous years. >> > > Yes, this should provide an income statement by project (which my > accountant would like to frame when they are sufficiently high in dollar > value), but not a Statement of Account to be sent to the client. > > > Only problem I see: You will have to enter the project on all relevant >> bookings / postings, but I guess timecards are your friend on the income >> side. >> > > Always done. > > > Any incoming nvoices related to the project would have to be 'amended' >> instead of just entering them. >> > > Why? Ammended how? > > > 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
