Garms and BCOL Reconciliation Analysis
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
#### Description
Currently SBC clients can go into a Service BC Office location to complete a name request. Given payment is taken from a client through the SBC office system (eGarms) and then recooperated through our unconnected BCOL account reconciliation is required. This ticket is for analysis of the current reconciliation process. We need to understand:
A. What reports are generated and used for reconciliation purposes
B. Why we need those reports.
C. If we need to reproduce something with the retirement of BCOL (some may be out of BCOL)?
D. If Registries pulls money from eGarms or if they push money to us (impacts to Sumesh as we need to ensure we don't take double payment).
Payment Process
- SBC Office staff log on to BC Online using their SC number and enter the Name Request through their Ministry Account
- SBC Office staff ensure the NR number has been generated
- SBC Office staff take payment through eGarms using service code 0747 (regular) or 0783 (priority) and entering the NR Number. The client pays this using any of the standard payment methods
Fee Details
0747 (Regular NR) charges
29.00
1.00
1.50
0783 (Priority NR) charges
129.00
1.00
1.50
Reconciliation?
#### Tasks
- [ ] When ticket has been created, post the ticket in RocketChat '#Operations Tasks' channel
- [ ] Add **entity** or **relationships** label to zenhub ticket
- [ ] Add 'Priority1' label to zenhub ticket
- [ ] Assign zenhub ticket to milestone: current, and place in pipeline: sprint backlog
- [ ] Reply All to IT Ops email and provide zenhub ticket number opened and which team it was assigned to
- [ ] Dev/BAs to complete work & close zenhub ticket
- [ ] Author of zenhub ticket to mark ServiceNow ticket as resolved or ask IT Ops to do so
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the payment process and fee codes 0747 and 0783 described in the issue, then identify the eGarms and BC Online reconciliation reports and current owners. Done means documenting which reports are used and why, whether BCOL retirement requires replacement work, and whether funds are pulled or pushed so double payment can be avoided.
Written by the indexing model from the issue text.
Assessment
- Domain
- payments
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100