Tim,

You can probably skip the job part of the workflow.

‘Job’ isn’t the right term. It functions like a purchase order, not really a 
categorization tying multiple documents together. I just got around to filing 
the RFE to rename the feature accordingly, 
https://bugs.gnucash.org/show_bug.cgi?id=797153.

Regards,
Adrien

> On Mar 27, 2019, at 10:27 AM, Tim Quinn <[email protected]> wrote:
> 
> Hi, Geert.
> 
> Thanks for the response, and sorry about the earlier block.
> 
> My sequence-of-events is slightly different from what you summarized, but I’m 
> not sure the difference is significant for this discussion.
> 
> Anyway, just to be horribly and boringly complete in case it does make a 
> difference, here is my overall workflow involving these prepayments:
> 
> A first-time client attends a session.
> 
> 1. Create the new customer record representing the new client.
> 2. Create an invoice for the new customer at the non-discounted rate.
> 3. Post the invoice.
> 4. Pay the invoice with the exact amount. No prepayment (yet).
> 
> At some time later, the client decides to opt for a prepaid group of 
> discounted sessions. As a good-will gesture, we retroactively consider the 
> first session to be part of the group of discounted sessions, which 
> essentially means we have overcharged (and the client has overpaid) for that 
> first session.
> 
> 4. Create a new job for that client representing the group of sessions being 
> purchased together.
> 5. Create a credit memo, associated with that job, for the overpayment — the 
> difference between the normal rate and the discounted rate.
> 
> (I should probably go back and associate the earlier invoice with this new 
> job, but I’m too lazy to do that because IIRC it would involve unposting the 
> invoice, editing the job field, reposting the invoice, and repaying the 
> invoice. I do not really do anything with the job association — no reporting, 
> etc..  I’m not even sure why I still bother creating the job except out of 
> fear that, some day, I will discover a good use for it.)
> 
> When the client comes for the next session (typically with payment for the 
> remainder of the discounted package):
> 
> 6. Create a new invoice associated with the earlier-created job.
> 7. Post the invoice.
> 8. Pay the invoice. On the payment screen I select the invoice I just 
> created, the credit memo I created earlier, and fill in the payment amount. 
> 
> GnuCash at that point automatically calculates and fills in the refund amount.
> 
> I have not tried the auto-pay feature. I will give that a try.
> 
> If you’ve made it this far, thanks for reading and thanks for the suggestion.
> 
> - Tim


_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to