Hi, Erik, Michael,|
On 04/09/2012 12:49 PM, Erik Huelsmann wrote:
Ok. "Post as saved" does the actual posting of the transaction -- if you save but don't post as saved, the transaction ends up in the transaction approval -> drafts screen.
Which seems like a reasonable place to put them, and exactly the functionality that I think Michael is looking for, for invoices.
Ah, but this happens *during* reconciliation, not *after*. I struggled with this quite a bit when getting our books up to date -- if a transaction appears in the reconciliation screen, you're hosed, you can no longer edit or delete it. It is quite painful to fix.
Keeping the transaction un-posted, in draft state, works.
My use case, which I think is just like Michael's, is that I have recurring transactions with varying amounts. There's not a good workflow for setting the amount of a particular transaction, without going in and editing, resaving, confirming that you want to save the existing transaction, then posting as saved.
And for invoices? forget about it. You have to copy as new.
I just hit a new scenario that needs an update to a posted transaction: making use of different entity credit accounts within a company. I've added a new company contact, and I want to re-associate invoices for one project to the new contact. No go.
Also had a case where we were working as a subcontractor, and now have a direct relationship with the main company -- we need to change the customer on the invoice to an entirely new customer. The thing is, they sent us a check to pay it with the original invoice number, so voiding the one invoice and creating a new one messes up the association in our system with our customers' accounting.
That one would make more sense to re-post, since it's a different customer entirely -- but I would very much like to be able to switch the ECA for a given invoice within a particular invoice.
I definitely need to try this out. It was on my radar, but haven't had a chance to deploy it and check it out...
+1 Yes! That would make the job quite a bit easier than having to manage each transaction independently -- being able to bulk update during reconciliation.
Not sure how to get there from here, though.
That definitely sounds like one scenario.
Another is leasing cloud resources that are charged per usage. We have this from both Amazon and Rackspace -- invoices that vary, sometimes substantially, month to month.
------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________ Ledger-smb-users mailing list ..hidden.. https://lists.sourceforge.net/lists/listinfo/ledger-smb-users