-
Notifications
You must be signed in to change notification settings - Fork 58
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
Developer EFT Verification #18574
Labels
Relationships
Work for Relationships team
Comments
Hey team! Please add your planning poker estimate with Zenhub @Jxio @ochiu @rodrigo-barraza @seeker25 |
Please add your planning poker estimate with Zenhub @AbrahamRostampoor |
This was referenced Nov 17, 2023
This was referenced Nov 27, 2023
Thanks for that -^, will help in the future - probably could cut some of it out for documentation as well |
This was referenced Nov 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Developer to validate / verify the implemented functionality for EFT payments deployed currently deployed to DEV.
Note: There are some requirements like 1st of the month to generate EFT statements, may need to deploy a temporary feature branch with date check changes to generate ahead of time
Enable EFT flag on payment account - test notebook
Confirm welcome email is sent
Enable EFT payment method via UI
Confirm can pay via EFT and invoice records are created
Fixed issue where payment was not released
Confirm statement generation job
Monthly statement email
Template wording fix
7 days until due reminder
Due today reminder
payment reminder job refactored to be driven by overdue date (more accurate and easier to test, overdue date can be updated to trigger reminders)
fix queue message parameter typo causing mailer to fail
Update invoices to overdue status job
Fix timezone issue where overdue status is not updated in some cases
Statement PDF/CSV
EFT Reconciliation - Test TDI17 (upload to minio bucket and publish event message)
Note: test initial reconciliation for unmapped account, then run another test file with mapped account
Short name account mapping endpoints (postman) - confirm mapping and credits are applied to owing invoices
Created notebook to help with this (https://github.com/bcgov-registries/ops-support/blob/main/support/ops/accounts/templates/update_eft_shortname_account.ipynb)
Forward / Screenshot any emails / PDFs for UX Verification
EFT Verification PDF doc with screenshots
Document and create any tickets for issues identified (link to issue / list here)
EFT Verification PDF documenting testing process (EFT Verification.pdf)
Statement settings always hidden #18761 - Statement settings always hidden
Update statement frequency when changing to EFT payment method #18762 - Update statement frequency when changing to EFT payment method
EFT accounts cannot modify statement recipients #18763 - EFT accounts cannot modify statement recipients
The text was updated successfully, but these errors were encountered: