Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dev/core#1317 - Fix total_amount on repeattransaction when tax amount is involved. #15517

Merged
merged 2 commits into from
Oct 15, 2019

Conversation

jitendrapurohit
Copy link
Contributor

Overview

Fix total amount on repeattransaction when done for FT having tax.

Before

To replicate -

  • Create an FT that includes a 10% GST on the main amount.
  • Sign up an auto-renew Membership using this FT. So if membership amount is $10, the total amount paid by the user is $11.
  • Now, when the next recur needs to be processed, if repeattransaction is called on this recur contribution, it recalculates the tax on the already taxed amount. So the second payment will be recorded with total amount = $12.1.
  • Every repeattransaction api on this recur contribution will calculate incorrect total amount for the new payment. So, the next payment will have 12.1 + 10% followed by 12.1 + 10% + 10%.

After

Fixed. Each repeattransaction will have the same amount as the original contribution.

Comments

Gitlab - https://lab.civicrm.org/dev/core/issues/1317

@civibot
Copy link

civibot bot commented Oct 15, 2019

(Standard links)

@civibot civibot bot added the master label Oct 15, 2019
@seamuslee001
Copy link
Contributor

This seems to make sense to me @mattwire @eileenmcnaughton

@eileenmcnaughton
Copy link
Contributor

Yes this makes sense & test is good - thanks @jitendrapurohit - merging

@eileenmcnaughton eileenmcnaughton merged commit c81b066 into civicrm:master Oct 15, 2019
@jitendrapurohit jitendrapurohit deleted the tax-recur-test branch October 16, 2019 02:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants