Information regarding the source of, process to find, and resolution steps for Out of Balance Transactions
Out of balance transactions within dataset
OOB - out of balance transactions occur due to two issue
a) Computer glitch
b) Program glitch
b) Program glitch
- You can see which transactions are OOB by going into the transaction journal and hitting the "control" key and the letter "i" key.
- Email us and we will fix them.
- When it is a computer glitch, we fix them and there is nothing else to do.
When it is a program glitch, there are two possible scenarios:
a) We have already fixed the situation within DVU but you may have old data that still needs to be fixed or you may not have yet received the update to fix it permanently.
b) It is a new situation we do not know about (happens rarely) in which case we will work at it until we can reproduce it and submit to dev for resolution, at which point it turns into scenario a.
b) It is a new situation we do not know about (happens rarely) in which case we will work at it until we can reproduce it and submit to dev for resolution, at which point it turns into scenario a.
We ALWAYS treat this as urgent from a case prioritization perspective.
Comments
0 comments
Please sign in to leave a comment.