Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

How to Bulk Write-Off in Pulse 2.0

Steps to follow when using Bulk Write off

  1. Log into Pulse and click on nine dots

...

2. Go to actions and the click actions

...

3. You will see a button up named Bulk write-off and click it

...

4. A new window with an option to upload a file will open

...

5. A file (in txt, csv format) should contain accounts you would like to bulk write off and they should meet the mentioned criteria

View file
nameBulk_Write_Off_Template.csv

Scenario: As an admin user, I want to see a preview of which accounts to write off before I submit, so I can ensure I’m not writing off accounts by mistake

Info

Note:

  1. When a list of accounts is uploaded for write-off, there is a summary of the accounts that will be written-off for user to check:

    1. account ID

    2. customer name

    3. fulfilment centre

    4. # days since default state

  2. there are some light checks on eligibility and ineligibility for write-off is shown for each account if:

    1. account doesn’t exist

    2. account is not in default state

    3. account has already been terminated

  3. The list should be ordered by days since default ascending to identify any cases where write off might be carried out too early

  4. Users can upload a file with a maximum of 2000 customer entries in a single submission.

...

6. Then hit the save button and you will get notified about the bulk operation

...

7. If it fails there will be a message indicating the accounts that failed and the reason

Info

Note

  1. when a bulk upload is done to write off accounts, if any account failed to be written off, there is an error message:

    1. account ID

    2. failure reason

  2. possible reason for failure include:

    1. account ID doesn’t exist

    2. account is not in default state (and no repo exists)

    3. account has already been terminated

  3. it is possible to identify write offs done by bulk action in the database (vs. single write-offs)