[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lmi-commits] [lmi] master fd66131 5/6: Finish DBO renaming: risky treat
From: |
Greg Chicares |
Subject: |
[lmi-commits] [lmi] master fd66131 5/6: Finish DBO renaming: risky treatment of initial premium |
Date: |
Thu, 8 Nov 2018 17:45:07 -0500 (EST) |
branch: master
commit fd661310d8087dee4ac5607ce4813088a89ac664
Author: Gregory W. Chicares <address@hidden>
Commit: Gregory W. Chicares <address@hidden>
Finish DBO renaming: risky treatment of initial premium
Replaced
Initial7702BftIsDb
with
RiskyInitial7702Db
because the former is ambiguous (it sounds like it should always be
true for the MDB DBO), while the second emphasizes the real danger of
treating anything higher than the initial specamt as the 7702 death
benefit--contrast section 3/1 here:
https://www.nongnu.org/lmi/7702.html
This risky option isn't implemented anyway. For a contract issued thus:
DBO: increasing (or perhaps ROP)
100,000 specamt
7,000 net premium with application
the idea is to set the specamt at 100K, but treat the 7702 death benefit
as 107K, exposing the purchaser to adverse tax consequences should poor
investment performance cause the actual death benefit to decrease.
This concludes the renaming of DBO-related database entities.
'AllowChangeToDbo2' will not be renamed; it has been marked as
obsolescent, and will be expunged ere long.
---
dbdict.cpp | 4 ++--
dbdict.hpp | 2 +-
dbnames.hpp | 2 +-
dbnames.xpp | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/dbdict.cpp b/dbdict.cpp
index df0d975..9083c63 100644
--- a/dbdict.cpp
+++ b/dbdict.cpp
@@ -149,7 +149,7 @@ void DBDictionary::ascribe_members()
ascribe("CvatMatChangeDefn" , &DBDictionary::CvatMatChangeDefn );
ascribe("GptMatChangeDefn" , &DBDictionary::GptMatChangeDefn );
ascribe("Irc7702BftIsSpecAmt" , &DBDictionary::Irc7702BftIsSpecAmt );
- ascribe("Initial7702BftIsDb" , &DBDictionary::Initial7702BftIsDb );
+ ascribe("RiskyInitial7702Db" , &DBDictionary::RiskyInitial7702Db );
ascribe("Irc7702Endowment" , &DBDictionary::Irc7702Endowment );
ascribe("Effective7702DboRop" , &DBDictionary::Effective7702DboRop );
ascribe("TermIsQABOrDb7702" , &DBDictionary::TermIsQABOrDb7702 );
@@ -922,7 +922,7 @@ void DBDictionary::write_database_files()
z.Add(database_entity(DB_CvatMatChangeDefn ,
mce_earlier_of_increase_or_unnecessary_premium));
z.Add(database_entity(DB_GptMatChangeDefn , 0));
z.Add(database_entity(DB_Irc7702BftIsSpecAmt , 0));
- z.Add(database_entity(DB_Initial7702BftIsDb , false));
+ z.Add(database_entity(DB_RiskyInitial7702Db , false));
z.Add(database_entity(DB_Irc7702Endowment , 0));
z.Add(database_entity(DB_Effective7702DboRop , 0));
z.Add(database_entity(DB_TermIsQABOrDb7702 , 1));
diff --git a/dbdict.hpp b/dbdict.hpp
index ae87d1f..9508c02 100644
--- a/dbdict.hpp
+++ b/dbdict.hpp
@@ -133,7 +133,7 @@ class LMI_SO DBDictionary final
database_entity CvatMatChangeDefn ;
database_entity GptMatChangeDefn ;
database_entity Irc7702BftIsSpecAmt ;
- database_entity Initial7702BftIsDb ;
+ database_entity RiskyInitial7702Db ;
database_entity Irc7702Endowment ;
database_entity Effective7702DboRop ;
database_entity TermIsQABOrDb7702 ;
diff --git a/dbnames.hpp b/dbnames.hpp
index c69a6c6..da5bab7 100644
--- a/dbnames.hpp
+++ b/dbnames.hpp
@@ -169,7 +169,7 @@ enum e_database_key
,DB_CvatMatChangeDefn
,DB_GptMatChangeDefn
,DB_Irc7702BftIsSpecAmt
- ,DB_Initial7702BftIsDb
+ ,DB_RiskyInitial7702Db
,DB_Irc7702Endowment
,DB_Effective7702DboRop
diff --git a/dbnames.xpp b/dbnames.xpp
index 6e0c1db..6596ead 100644
--- a/dbnames.xpp
+++ b/dbnames.xpp
@@ -78,7 +78,7 @@
{DB_CvatMatChangeDefn,DB_Topic_7702And7702A,"CvatMatChangeDefn","Definition of
7702A material change for CVAT: 0=unnec prem, 1=increase, 2=increase after
unnec prem [not implemented], 3=any unnec prem or increase",}, \
{DB_GptMatChangeDefn,DB_Topic_7702And7702A,"GptMatChangeDefn","Definition of
7702A material change for GPT: 0=any adjustment event, 1=any adjustment event
that increases the guideline limit",}, \
{DB_Irc7702BftIsSpecAmt,DB_Topic_7702And7702A,"Irc7702BftIsSpecAmt","7702(f)(3)
'death benefit' is specamt rather than DB: 0=no, 1=yes",}, \
-{DB_Initial7702BftIsDb,DB_Topic_7702And7702A,"Initial7702BftIsDb","For DBO 2,
riskily reflect 1035 and initial payment in initial 7702(f)(3) 'death benefit':
0=no, 1=yes",}, \
+{DB_RiskyInitial7702Db,DB_Topic_7702And7702A,"RiskyInitial7702Db","For
increasing (and ROP?) death benefit option, riskily reflect 1035 and initial
payment in initial 7702(f)(3) 'death benefit': 0=no, 1=yes [not yet
implemented]",}, \
{DB_Irc7702Endowment,DB_Topic_7702And7702A,"Irc7702Endowment","7702(e)(1)(D)
endowment amount for 7702 and 7702A calculations: 0=specamt, 1=none",}, \
{DB_Effective7702DboRop,DB_Topic_7702And7702A,"Effective7702DboRop","For 7702,
treat return of premium death benefit option same as: 0=level 1=increasing",}, \
{DB_TermIsQABOrDb7702,DB_Topic_7702And7702A,"TermIsQABOrDb7702","Treat term
rider as QAB or death benefit for 7702: 0=neither, 1=DB, 2=QAB",}, \
- [lmi-commits] [lmi] master updated (a604e1e -> 53201ac), Greg Chicares, 2018/11/08
- [lmi-commits] [lmi] master 53201ac 6/6: Add new database entities to govern death benefit option changes, Greg Chicares, 2018/11/08
- [lmi-commits] [lmi] master fd66131 5/6: Finish DBO renaming: risky treatment of initial premium,
Greg Chicares <=
- [lmi-commits] [lmi] master cf5779e 2/6: Continue renaming DBOs: no-lapse availability, Greg Chicares, 2018/11/08
- [lmi-commits] [lmi] master b1e039d 4/6: Continue DBO renaming: effective 7702 DBO, Greg Chicares, 2018/11/08
- [lmi-commits] [lmi] master 566c52b 3/6: Continue DBO renaming: effect of withdrawals on specamt, Greg Chicares, 2018/11/08
- [lmi-commits] [lmi] master a75971e 1/6: Begin renaming DBOs; add another DBO: 'AllowDboX' only, Greg Chicares, 2018/11/08