bcgov / bcgov/entity

FAS - Un-cashed cheques

Open
#31,973 7 comments 0 reactions 0 assignees View on GitHub
Pay Pay Ops
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

There are ~195 refund cheques that have made it to their recipients, but they were never cashed.

PT will be writing this money off, so this ticket is just to update the RSs for future reference saying they were un-cached.

For consideration: EFT issues paper cheques as well and will need all of the cheque refund lifecycle statuses that FAS has.

Approach: Review CAS data for a record that PT has adjusted. Plan how we can detect this and represent it in the UI automatically. This method will result in better data long term, and won't inject multiple sources of truth.

Question for finance - How old can an un-cashed cheque live before it's 'written off?'
After 6 months in negotiable status the cheque can be considered stale-dated
Once a cheque is stale-dated then efforts are made to find a new address
Failing all of this, then Finance notifies FASB and they (?procedure pending?) write off

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing CAS data for a refund cheque record that PT adjusted, as described in the issue, and trace how FAS refund statuses are represented in the UI. Confirm the write-off and stale-dated rules with Finance, then define how un-cashed cheques and the corresponding EFT lifecycle statuses should be detected and displayed without creating another source of truth.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, payments
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.