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

Automatically Marking Invoices Paid When they are NOT Paid #39538

Open
1 of 5 tasks
ChoffmanCannaBlendz opened this issue Jan 13, 2025 · 3 comments
Open
1 of 5 tasks

Automatically Marking Invoices Paid When they are NOT Paid #39538

ChoffmanCannaBlendz opened this issue Jan 13, 2025 · 3 comments
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.5-p1 Indicates original Magento version for the Issue report.

Comments

@ChoffmanCannaBlendz
Copy link

Preconditions and environment

  • Magento version - Magento ver. 2.4.5-p1
  • I have had numerous orders that have automatically mark themselves as paid, when the customer did not make a payment.
  • I went ahead and re-did the order to re-invoice the customer, and it is now marking it as PAID automatically

Steps to reproduce

Produce an order
Process the order
Invoice the customer

Expected result

It should send an invoice to the customer to allow them to pay, and it has already been marked paid, so the customer can not pay their invoice.

Actual result

No error messages - it is just marking the order and invoice as PAID. I can't undo this! It's creating multiple orders and incorrect inventory is being marked as 'sold' and / or paid. I also tried to change the status from "Complete" to "Payment Pending" but there isn't a 'save' button.

I did use the "INVOICE" button and not the "TERM PAYMENT INVOICE" option. Not sure if that makes a difference?
Screenshot 2025-01-13 110733
Screenshot 2025-01-13 110702

Additional information

No response

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Copy link

m2-assistant bot commented Jan 13, 2025

Hi @ChoffmanCannaBlendz. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

@engcom-Bravo engcom-Bravo self-assigned this Jan 16, 2025
Copy link

m2-assistant bot commented Jan 16, 2025

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
  • 5. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.5-p1 Indicates original Magento version for the Issue report. label Jan 16, 2025
@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Jan 16, 2025
@engcom-Bravo
Copy link
Contributor

Hi @ChoffmanCannaBlendz,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and we are not able to reproduce the issue.Kindly refer the screenshots.

Image Image

We have placed order with Check / Money order and we have done the invoice.

Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

@engcom-Bravo engcom-Bravo added the Issue: needs update Additional information is require, waiting for response label Jan 17, 2025
@engcom-Bravo engcom-Bravo moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.5-p1 Indicates original Magento version for the Issue report.
Projects
Development

No branches or pull requests

2 participants