Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service History - Calculation Results and Billing Categories #39

Open
pizza-and-dog opened this issue May 29, 2014 · 5 comments
Open

Service History - Calculation Results and Billing Categories #39

pizza-and-dog opened this issue May 29, 2014 · 5 comments
Labels

Comments

@pizza-and-dog
Copy link
Contributor

  1. Go to View Account > Service History
  2. Enter Service History info (use this scenario: https://drive.google.com/file/d/0B4MmZDLfhZYfQlBEMEg3VFFUQ28/edit?usp=sharing).
  3. Select Run Calculation button.
  4. Select Save Calculation button.
  5. Select Trigger Bill button
  6. ERROR: When we ran the calculation, the principal and interest were posted in the CSRS deposit billing category instead of the CSRS Peace Corps category.
  7. ERROR: In many of our successfully run calculations, not all the amounts calculated showed up in the billing categories. We noticed that none of the Peace Corps amounts showed up in the billing category nor did some CSRS redeposits; although they did get rolled into the totals
@pizza-and-dog pizza-and-dog changed the title Create Account: Service History: Calculation Results and Billing Categories Service History - Calculation Results and Billing Categories Jul 3, 2014
@joelc
Copy link

joelc commented Jul 17, 2014

Is this a dupe of #31 ?

@pizza-and-dog
Copy link
Contributor Author

It's similar to #31, but different. #31 focuses specifically on Peace corp scenarios. This ticket is for any scenario. Basically need to make sure that after running a scenario that it breaks down correctly in the Redeposit and Deposit boxes at the bottom of the Service History tab.

@joelc
Copy link

joelc commented Jul 20, 2014

Got it - hate to cop out, but this one really needs fleshing out some more.

The "any scenario" bit is too open to make anything actionable. With #31 fixed I'm not sure what the algorithm/rules are for determining what goes where and how etc...!

@pizza-and-dog
Copy link
Contributor Author

Try it with this scenario and if you fix it for this scenario, the fixes will also work for the other scenarios: https://drive.google.com/file/d/0B4MmZDLfhZYfQlBEMEg3VFFUQ28/edit?usp=sharing

Thanks,
-Rashid

Sent from an iPhone, please excuse any typos.

On Jul 19, 2014, at 8:11 PM, Joel Caplin [email protected] wrote:

Got it - hate to cop out, but this one really needs fleshing out some more.

The "any scenario" bit is too open to make anything actionable. With #31 fixed I'm not sure what the algorithm/rules are for determining what goes where and how etc...!


Reply to this email directly or view it on GitHub.

@joelc
Copy link

joelc commented Jul 20, 2014

(Confirmed, this works in the Part 2 submission assembly)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants