by Sharif Mehedi · in Developers · assigned to Sharif Mehedi

Summary

Children

Comments

• 4 months, 2 weeks ago by Sharif Mehedi about #6855 (How to account for "keep the change" and future discounts (coupons)) : Thanks for approving this.
• 4 months, 2 weeks ago by Luc Saffre about #6855 (How to account for "keep the change" and future discounts (coupons)) : Yes, if a simple checkbox "keep the change" is enough, then we don't need a new db model. You don't need to know another journal, the change to keep would just go into another movement on that voucher, into an account CommonAccounts.roundings.get_objects().
• 4 months, 2 weeks ago by Sharif Mehedi in reply to Luc Saffre about #6855 (How to account for "keep the change" and future discounts (coupons)) : I will wait for your opinion.
• 4 months, 2 weeks ago by Sharif Mehedi in reply to Luc Saffre about #6855 (How to account for "keep the change" and future discounts (coupons)) : Thinking about it more, I think we can simply do it with a boolean field "Apply rounding" on the CashInvoice model, and when this field is set to true, it should put the remaining amount in to Roundings account. But we still need a way to figure out the account and the journal, for the account, we c...
• 4 months, 2 weeks ago by Luc Saffre about #6855 (How to account for "keep the change" and future discounts (coupons)) (2 replies) : I suggest a new model "PaymentDifference" inherits from BabelDesignated and adds a FK to accounts.Account. And a pointer to PaymentDifferenc on a sales note. One row is "Rounding" and points to an account "Roundings". One row of PaymentDiffence is "Partial payment" and has the PD.account pointer emp...
• 4 months, 2 weeks ago by Sharif Mehedi about #6855 (How to account for "keep the change" and future discounts (coupons)) : Created new Ticket #6855 (How to account for "keep the change" and future discounts (coupons)).