• Information :

    Documented At 1/8/2022
    Documented By Yosefina Angelita
    Project Owner Teguh Kartika Ningrum
    Approved At 18/08/2022

  • Discovery :

    Objective Accounting Admin is able to trace and recon all payments needed to be paid for the items purchase in real time
    Problem HMW creates traceability for all items purchase payments so that the item purchase can be processed further
    Solution Puchase down payment feature to trace and record all items purchase payments
    Initiative Name Purchase Down Payment
    Persona Accounting Staff

  • Features :

    Features Purchase Down Payment
    Description - User is able to create a down purchase payment
    • Accounting staff is able to track all purchase down payments real time
    • 100% traceability for purchase down payments | | MVP | - Role Permission Purchase Approval
    • Create Purchase Down Payment
    • View Purchase Down Payment
    • Filter/Index Purchase Down Payment
    • Approval Create Purchase Down Payment By Web
    • Edit Purchase Down Payment
    • Approval Edit Purchase Down Payment
    • Close Purchase Down Payment
    • Delete Purchase Down Payment
    • Approval Delete Purchase Down Payment
    • Approval Purchase Down payment notification
    • Bulk Approval Purchase Down Payment by Email
    • Print Purchase Down Payment | | Customer Journey | CLICK ME | | Flow Chart | CLICK ME |

  • User Story :

    User Story

  • Timeline :

    Timeline

  • MOM :

    Date Description Person
    06/07/2022 Purchase Down payment can’t create dp with out reference Aini
    1/8/2022 Onboarding project
    MoM notes:
    1. One purchase orders might have several down payments
    2. Limit the down payment only to PO with down payment value true
    3. Close purchase down payment automatically when it is paid in cash out or bank out
    4. Amount for PO needs to be validated —> sum of all purchase down payment related to the PO ≤ than the down payment recorded in the PO | | | 6/8/2022 | MoM Touchbase:
    • Purchase DP should be guarded by the approval + form status
    • Purchase DP amount remaining should be guarded in the create, edit and approve state
    • History is not needed, as long as the data is saved in BE
    • 1 puchase DP can cater several purchase order, and reversely | | | 11/8/2022 | MoM Approval:
    1. Create
    • remaining amount tidak perlu ditampilkan di tabel form
    • Supplier needs to be chosen first in order to choose PO reference
    • Show remaining amount in each PO reference when choosing
    1. Edit
    • Reference can be edited, as long as the amount is always guarded in the BE
    • for form with status done/paid in the trx —> no edit
    1. Delete
    • modify logic: if user has access to delete —> directly delete form w/o approval Else, ask approval from the approver for delete —> ini asumsinya approver selalu bisa pny akses delete jg? - - for form with status done/paid in the trx —> no delete ****- When delete approval is submitted, send email as well
    1. Approve All
    • only able to choose form with status pending approval and type= create/edit | | | 13/8/2022 | - Revision | |

  • Change Log :

    Date Description Person
    3/8/2022 PRD basic information
    6/8/2022 All user story done
    Checkpoint Aini