Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-4525

TBC - TBC/Collected Sale/Overpayment/Paid Out/TBC Refunded

    Details

    • Sprint:
      CFAMX 2019R4 Sprint 3
    • SCRUM Team:
      Brotherhood of Mutants
    • SOW (Time Tracking) Project:
      44918
    • Work Type Classification:
      Sustaining

      Description

      As an operator I want to be able to perform TBC gymnastics so that I can correct mistakes

      Use Case

      • A TBC is tendered on the POS, for $80, with a customer selected
      • The TBC is processed by InFORM
      • When the user views the TBC page the TBC is displayed
      • A collected sale is tendered on the POS, for $100, for the same customer
      • The collected sale is processed by InFORM
      • The user applies the Collected Sale of $100 to the TBC of $80, this results in a $20 balance
      • The user creates a Paid Out with the remaining $20 balance
      • The original TBC is Refunded on the POS, with a customer selected
      • The TBC Refund is processed by InFORM
      • On the TBC page the Refunded TBC must be resolved in order to complete the TBC process for the day
      • The TBC is locked, and it is indicated that the TBC was refunded
      • Actions to resolve:
      • User has to go to the Paid In/Out page, and has to delete the Paid Out
        • How does the user know that they need to do this?
      • User goes to Collected Sale page
      • The user unapplies/unallocates the Collected Sale from the TBC
      • At this point the two components of the TBC (Collected Sale and Paid Out) are recombined
      • The TBC becomes unlocked and can be deleted
      • Delete action is available under this condition
      • When the CDS is generated for the day, neither the TBC nor the Refund are included in the export file

      Acceptance Criteria

      1. Confirm when a TBC is associated to a Collected Sale and Paid Out, and the TBC is later refunded, that the user cannot update any of the details of the TBC (Account Name, Invoice #, Description)
      2. Confirm when a TBC is associated to a Collected Sale Paid Out and the TBC is later refunded, that it is indicated on the TBC page that the TBC is locked and has an associated refund
      3. Confirm when the the TBC and Collected Sale and Paid Out are no longer linked that the TBC/Refund is no longer linked and is available to be deleted
      4. Confirm that the delete process is documented
      5. Confirm that the TBC/Refund can be deleted
      6. Confirm that once deleted, neither the Paid Out, the TBC nor the refund are included in the CDS export
      7. Confirm that the MMS code has NOT been blindly copied without a full understanding of the processes being demonstrated

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                will.englefield Will Englefield (Inactive)
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 13h 40m
                  13h 40m
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 11h 5m Time Not Required
                  11h 5m

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.