-
Notifications
You must be signed in to change notification settings - Fork 59
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
Short Name Details - Choose amount for refund #21535
Comments
Front End, Back End to change in Pay PI and it is a job component, break into 2 requirement |
Hey team! Please add your planning poker estimate with Zenhub @avni-work @hanlunBCRegistries @Jxio @ochiu @rodrigo-barraza @seeker25 |
Checking with @danaannab: |
From: Wilson, Shawna M CITZ:EX [email protected] Hi Dana, please see below the list of individuals: Initiate a refund: Expense Authority: Thank you! Shawna Wilson |
@danaannab Can you please double check with Shawna on Kim? There shouldn't be anyone able to request and authorize a refund I don't think. |
Note from Shawna upon confirming that the people in the initiate refund group should be different from the Expense Authority group and if Kim should be in both the initiate refund group and the Expense Authority group: |
added keycload to DEV/TEST: eft_refund |
as Figma design, There are help text below CAS Supplier Number and Email, Such helper text is missing |
Refund Amount should be less or equal to Unsettled Amount. (otherwise, there will always be 0.01 remaining balance) |
issue is verified, additional enhancement ticket is created |
SBC Finance:
GIVEN that I have received a notification for an overpayment (#21516)
WHEN I wish to refund to the supplier record on the client's short name
THEN the system will allow me to choose the amount I would like to refund
AND the refund can be reviewed by an Expense Authority (separate ticket)
Notification: an email notification will be sending to Expense Authority to remind there's a refund review pending
AP Job will be done in another ticket(#22263), Datamodel Changes, New PAY-API routes etc, AUTH-WEB changes
https://www.figma.com/design/Y1PWkuB8II5lxdDdUq67Aj/Electronic-Funds-Transfer?node-id=2899-24646&t=Pf154RjpPeMIrVoM-4
Requires new keycloak roles to be created
The text was updated successfully, but these errors were encountered: