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

Fix bill licences with no transactions in bill run #765

Merged
merged 4 commits into from
Feb 26, 2024

Conversation

Cruikshanks
Copy link
Member

@Cruikshanks Cruikshanks commented Feb 26, 2024

https://eaflood.atlassian.net/browse/WATER-4379

We are working to replace the legacy SROC annual billing engine with one in this project that exploits what we did with SROC supplementary billing.

The first pass of testing has highlighted a discrepancy with how many licences are being included in some bills. For example, the legacy bill run will only display 1 but the new engine will display 3.

When we looked into it we found it was because only 1 of the 3 licences had applicable transactions. Two of the licences had no billable days.

The legacy is correct in this case, we shouldn't be creating bill licence records where there were no transactions. This change fixes the annual billing engine to deal with this scenario.

For reference the licences had no billable days because they were revoked before the abstraction period on the charge reference i.e. revoked before the abstraction period so the charge period is null.

https://eaflood.atlassian.net/browse/WATER-4379

We are working to replace the legacy SROC annual billing engine with one in this project that exploits what we did with SROC supplementary billing.

The first pass of testing has highlighted a discrepancy with the how many licences are bing included in some bills. For example, the legacy bill run will only display 1 but the new engine will display 3.

When we looked into it we found it was because only 1 of the 3 licences had applicable transactions. Two of the licences had no billable days.

The legacy is correct in this case, we shouldn't be creating bill licence records where there were no transactions. This change fixes the annual billing engine to deal with this scenario.

> For reference the licences had no billable days because they were revoked before the abstraction period on the charge reference i.e. revoked before the charge period.
@Cruikshanks Cruikshanks added the bug Something isn't working label Feb 26, 2024
@Cruikshanks Cruikshanks self-assigned this Feb 26, 2024
@Cruikshanks Cruikshanks marked this pull request as ready for review February 26, 2024 15:50
@Cruikshanks Cruikshanks merged commit f6bcc4e into main Feb 26, 2024
6 checks passed
@Cruikshanks Cruikshanks deleted the fix-bill-licences-no-transactions branch February 26, 2024 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant