Following was expected from this ticket:
1. Creation of test data for Invoice
2. Creation of test data for Billing

There is no approval to work on Invoice Test Data creation task.
Hence closing this JIRA.

Thank you!

cc: Gaurav Sodani, Jyoti Agrawal

Reopening this issue.
We should work on completion of this company, as it will help us in following ways:
1. While doing any code fix in core logic it will ensure, that the changes done have not impacted existing implementation which was expected to remain intact.
2. Going forward, we have Edit Template enhancement in WT-7519 which has major core logic changes. Apart from this, we will also have many more Invoice related changes coming our way. Completion of this company, will help in saving the testing time and also boost our confidence related to existing scenarios being unaffected.

cc: Jyoti Agrawal, Venkatesh Pujari, Amruta Lohiya

This appears to be a "process" recommendation rather than a support task. We need to discuss to categorize them better. CC Jennifer Reed Satya

Following is the status update regarding Test Company:

Following is configured in this test company:
Classes
Payroll Schedules
Eligibility Rules
Rates (Health / Non Health / With and without self insured components)
Plans (Health / Non Health)
Rate - Plan mapping
Import template creations (Employee data / Dependent data / Election data)

Detailed scenarios are listed in Invoice_Scenarios_TestData.xlsx. Please refer same for adjustment scenarios.

Adjustments in first invoice:

• There will be only retro adds that will appear in first invoice
• Detailed listing and review of valid scenarios with expected output is complete
• Scenario wise employee and election import is complete
• Output for the first invoice can be validated using this company.

Adjustments appearing on invoices generated after first invoice(we are considering this as Second Invoice):

• Adjustments on invoices after first invoice can be only retro add/ only retro term / both retro add and term.
• High level scenarios are documented in tab "Second Invoice Scenarios" of attached excel.
• We could complete detailed listing and review of scenarios for points 1 and 5 mentioned in tab "Second Invoice Scenarios".
• We listed few scenarios for point 3 for which we have queries. We have already requested AE to validate the scenarios. After which, further listing can be done.
• Detailed listing of other points in tab "Second Invoice Scenarios" is pending.
• None of the scenarios related to second invoice are created in test company

We have not considered scenarios where multiple rate / subrate / self insured components are involved. Creating first invoice scenarios gave us little idea about how this company can be used in a way of automation testing.

Please note, that creating these scenarios is definitely a time taking activity, but will prove to be of great help if done and used regularly.

cc: Gaurav Sodani, Satya, Jyoti Agrawal, Venkatesh Pujari

Resolving it. Not setting resolution.