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

Date of lapse may need back dating if on policy anniversary #22

Closed
MatthewCaseres opened this issue Feb 3, 2023 · 1 comment
Closed

Comments

@MatthewCaseres
Copy link

section 4.3 of the Society of Actuaries (SOA) experience study document states that

For a lapse on a policy anniversary, using 11:59 pm on the day before the anniversary assures that the lapse is allocated to the proper policy year.

https://www.actuarialopensource.org/actxps_experienceanalysis_2023_02_03.html#term-is-anniv

@MatthewCaseres MatthewCaseres changed the title Date of lapse may need back dating Date of lapse may need back dating if on policy anniversary Feb 3, 2023
@mattheaphy
Copy link
Owner

I agree with the sentiment, but disagree there's an issue here. The package should not make assumptions about the accuracy of input data. The user of package should ensure the data they're supplying data that is fit for purpose.

There are also practical challenges with attempting to build this feature. One would have to prescribe or guess at policy status values / codes, and those should be expected to vary greatly by user.

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

No branches or pull requests

2 participants