Transcription
BENEFICIARY EARNINGS AND DATAEXCHANGE (BENDEX) HANDBOOK forDaily ProcessHIGHLIGHT OF CHANGES EFFECTIVE FEB 23 2007: BENDEX DATA EXCHANGE NOW A DAILY PROCESS – INPUT,OUTPUT AND CHANGE RECORDS WILL BE PROCESSED DAILY. BEER DATA EXCHANGE NOW DAILY WITH NO ORBIT –UNESTABLISHED RECORDS WILL NOT BE ORBITED. HOC AND SOC ELEMENTS NO LONGER AVAILABLE. ADDITIONAL DATA ELEMENTS PROVIDED IN OUTPUT FILE. THE OLD POMS SECTION NUMBERS HAVE BEEN RETAINED BUT NOLONGER APPLY. THIS HANDBOOK WAS REMOVED FROM POMS ANDWILL BE A POLICY-NET LINK.HIGHLIGHT OF CHANGES EFFECTIVE FEB 2 2016:UPDATED SECTION 1.220: PARTS OF THE BENDEX RECORD TOINCLUDE THE BENDEX HEADER LABELHIGHLIGHT OF CHANGES EFFECTIVE FEB 17 2016:UPDATED SECTION 1.330: HOW THE TAX REPORT YEAR ISSELECTED TO PROVIDE A MORE CLEAR EXAMPLE OF THE TAXREPORT YEAR PROCESSHIGHLIGHT OF CHANGES EFFECTIVE JULY 26 2016:UPDATED SECTION 1.700: WHEN AND HOW TO DELETE A BENDEXRECORD TO INCLUDE NEBRASKA’S REQUEST TO DISCONTINUE BEER
FILESSocial Security AdministrationBENEFICIARY AND EARNINGS DATA EXCHANGE (BENDEX)HANDBOOKLast Revised July 26, 2016 (changes highlighted in yellow)Section TitleSectionRevision DateHOW DIRECT BENDEX EXCHANGE IS ESTABLISHEDGlossary of TermsSSA Processing of Input DataEstablishing Direct BENDEX ExchangeKinds of BENDATA RecordsParts of the BENDATA RecordTransmitting BENDATA to /0702/0702/07HOW BENDEX EXCHANGE IS ESTABLISHED THROUGH THE BUY-IN PROGRAMPolicy on Agency Responsibilities in the Buy-In ProgramHow Buy-In Operations Establish BENDEX ExchangeHow Disability Cases are AccretedHow to Process Attempted Buy-In CasesFacts about the State Control Data FieldReconciling BENDEX and Buy-In /071.3151.3201.33002/0702/0702/16THE BENDEX OUTPUT RECORDParts of the BENDEX RecordHow the BENDEX BRI/COLA File is ProcessedList of MBR Changes That Automatically GenerateThe BENDEX Update RecordThe BENDEX Change Record CycleGENERAL INFORMATIONState Agency CodesCitizenship Country CodesFacts about the Surname Match CriteriaFacts about the BENDEX Match CriteriaTHE BEER OUTPUT RECORDParts of the BEER RecordHow Earnings Exchange is EstablishedHow the Tax Report Year is Selected – ProcessSPECIAL OUTPUT FILES2
Reimplementation FilesHow the Reimplementation Process Works1.4001.410302/0702/07
DISCLOSURE/CONFIDENTIALITY OF INFORMATIONPolicy on Disclosure and Confidentiality of InformationStandards for Physical Safeguard of BENDEX and BEERInformationGuidelines for Reviewing System Security and 6001.6051.61002/0702/0702/07STATE USE OF BENDEX DATAPolicies on MBR Data Released Thru BENDEXState Report of BENDEX System ProblemsResolving Questionable SSA Benefit AmountsDISCONTINUING BENDEX and BEER EXCHANGESWhen and How to Delete BENDEX and BEER RecordsHow BENDEX Buy-In Records are 201.82502/0702/0702/0702/0702/0702/07GENERAL INFORMATIONRequesting Assistance - State Welfare OfficesRequesting Assistance - SSA OfficesList of Addresses for SSA Regional OfficesList of Addresses for Family Assistance OfficesList of Beneficiary Identification CodesThe TREASURY Cutoff Calendar4
SECTION 1.001 GLOSSARY OF NFTPTPMAid to Families with DependentChildren (see TANF)State Beneficiary Input Data FileBeneficiary and Earnings DataExchange Output FileBeneficiary Earnings Exchange RecordBeneficiaries Own Account NumberBeneficiary's own Social SecurityNumberBenefit Rate IncreaseClaim Account NumberCentral OfficeCost of Living AdjustmentCenters for Medicare and MedicaidServices (old HCFA)Easy Back On Provisional paymentFederal Insurance Contribution ActField OfficeFamily Services AdministrationFile Transfer Management SystemHospital InsuranceIncome and Eligibility VerificationSystemMaster Beneficiary RecordMaster Earnings FileOffice of Family AssistancePublic AssistancePayment/Beneficiary Indicator CodePayment Service CenterRegional OfficeRailroadRetirement Survivors Disability InsSecurity Action PlanState Data Exchange SystemSupplemental Medical InsuranceSocial Security AdministrationSupplementary Security Income/RecordSocial Security NumberState Verification Exchange SystemTemporary Assistance for NeedyFamilies (old AFDC)Third PartyThird Party Master File5
B.1.2.3.4.DEFINITIONS - TERMSAPPLICANTBENEFICIARYCLAIMANTCLAIM NUMBER5. CLIENT6. DELETION7. DIRECT INPUT8. ELIGIBLE9. ENTITLED10. MATCHED11. PAYMENT STATUS12. RECIPIENT13. TITLE II14. TITLE XVIA person who has filed for assistance or benefitsA person who is entitled to Social Security benefits.A person on whose behalf an application is made.A number used by SSA to identify an individual who is aclaimant or a beneficiary.A synonym for beneficiary or recipient.Removal of a record from the BENDEX System.A query prepared in a prescribed format by a State agencyfor BENDEX processing.For title II, an individual who meets all the requirementsfor receiving Social Security benefits, except for filing anapplication. For title XVI, the individual meets therequirements to receive SSI payments.To meet all the requirements for receiving Social Securitybenefits including the filing of an application and have theright to receive benefits.A SSA benefit or earnings record was found that isessentially equal to the identifying data provided by theState.The condition of a beneficiary's Social Security benefits,i.e., Payment Status Code is current, suspended orterminated.A person who receives State public assistance and/or SSIpayments.SSA retirement, survivors, and disability benefits.SSI benefits.6
SECTION 1.010SSA PROCESSING OF INPUT DATAA.INTRODUCTIONThis section describes what happens when SSA receivesState input BENDATA files and how BENDEX interfaces withother SSA systems.B.PROCESS DESCRIPTIONSSA processes BENDATA input files through two editfunctions. The first function checks for proper data andagency codes. The second function merges all BENDATAfiles with SVES inputs, rejects any records witherroneous CANs or SSNs, communication codes or categorycodes.The acceptable records are then merged with accumulatedchange records from SSA’s daily update process and therecords housed on the MBR file. Entitlement data isextracted for formulating BENDEX records. A crossreference function also takes place here.1.C.MEF SCREENINGREFERENCESThe BENDEX records are screened for an earnings requestindicator and, if present, a record is created formatching against the MEF. Earnings data is extracted forformulating BEER records returned to the states.Parts of the BENDATA Record, 1.060.7
SECTION 1.020ESTABLISHING DIRECT BENDEX EXCHANGEA.INTRODUCTIONThis section describes how the coordinating State agencysubmits inquires to the BENDEX System.B.PROCESSThe State submits to SSA a file of BENDATA records bywire transmission. Initial BENDATA records may besubmitted on a daily basis.1.ConfidentialityAgreementsBefore the data exchange can begin, the agency and SSAmust execute a confidentiality agreement which outlinesrequirements and responsibilities for each party. Theagreements are generally for a period of 18 months with aone time one year renewal. New agreements must beexecuted after the one time renewal. The Regional DataExchange Coordinators should be contacted for specificinformation about the agreements.2.CoordinatingAgencyThis is the agency responsible for requesting andreceiving BENDEX information for all authorized agencieswithin the State. This agency normally submits theBENDATA file(s) and receives all of the output files.3.RequestingAgencyThis is the authorized agency that requests SSAinformation through the coordinating agency.4.OngoingExchangeThe State submits to SSA a file of BENDATA records bywire transmission. Initial BENDATA records may besubmitted on a daily basis. Once the BENDATA file isprocessed, BENDEX exchange is established on thebeneficiary/applicant/recipient. Initial entitlement andmaterial changes in entitlement to SSA benefits will beautomatically reported to the State. Note: If the stateagency receives a NOTITLEII communication code for arequested client, they will need to submit subsequentBENDATA requests for that client on a regular basis. Werecommend that these re-requests be done at least once ayear, in order to ensure that the agency gets informationfor a client who becomes entitled after the agencyrequests information.C.REFERENCES Parts of the BENDATA Record 1.060The BEER Output Record 1.300List of MBR Changes That Automatically Generates aBENDEX Record 1.2408
SECTION 1.030A.INTRODUCTIONB.DEFINITIONSTYPES OF BENDATA RECORDSThe State submits input records to SSA to establish aBENDEX exchange, to modify State controlled data fields,and to discontinue a BENDEX exchange.1.AccretionRecordUsed to initially establish a BENDEX exchange. (Submit acomplete BENDATA record with “BDA” in position 60-62.)2.AlterationRecordUsed by the controlling State to change the CAC or SCD(welfare number). Submit a complete BENDATA record with"BDA" in position 60-62.3.DeletionRecordUsed when benefit or earnings information is no longernecessary because of: removal from jurisdiction denial discontinuance of assistance Alleged death of client(Submit a complete BENDATA record with “DPA” in position60-62.)4.C.Death DeletionRecordREFERENCESUsed when the State has a proven date of death for therecipient/beneficiary. (Submit a complete BENDATA recordwith “DTH” in position 60-62.)Format of the BENDATA File, 1.040Parts of the BENDATA Record, 1.0609
SECTION 1.060 PARTS OF THE BENDATA RECORDA.BENDATA FILE LAYOUTField NameFieldLengthSSN OR CAN BICEARNINGSREQUEST CODESURNAMEGIVEN NAMEMIDDLE INITIALSEXDATE OF BIRTHBLANKAGENCY CODEBLANKCATEGORY OFASSISTANCECODEDIRECT WIREINPUTDATE OF DEATHSTATECOMMUNICATIONCODEIEVS AGENCYSUBCODEBLANKSTATE 463-661126768-7918010
B.DESCRIPTION OFBENDATA FIELDSThis chart identifies each field and the information itcontains.POSITION#1-09DATA ELEMENTSSN or CAN(Mandatory Field)VALUES1-9 Numeric10-11BIC10-11Alpha/ Numeric12EarningsRequestE OR BBlank13-24Surname(Mandatory Field)Alpha25-31Alpha32Given Name(Mandatory Field)Middle Initial33Sex34-41Date of Birth(Mandatory ency Code(Mandatory ither the SSN assigned toan individual or CAN, theaccount number the benefitis filed under.Designates the type of SSAbenefit received or filedfor. 1-11 is composed ofthe SSN of the insuredfollowed by a leftjustified BIC.Example: 244525699B2244525699TNot-acceptable example: allzeros, all blanks or ---579335AReferences: List of SSA BICCodes, Handbook Section1.820NOTE: If inputting a CAN,and an auxiliarybeneficiary is involved,the BIC must be shown. Ifinputting SSN for a primarybeneficiary, the BIC can beleft blank.E Earnings request onlyB both earnings requestand BENDEX data exchange.If the code is “E” or “B”then an earnings requestwill go to the state BEERfile.Leave blank if no earningsdata is desired.Left justified if fewerthan 12 positions areneeded.Left justified if fewerthan 7 positions.Self-explanatoryMaleFemaleExamples: 0828194808001948All zeros “00000000” areacceptable if unknownReference: State AgencyCodes, Handbook Section1.250
50Category of AssistanceCode(Mandatory Field)ABCAid to the AgedAid to the BlindTemporary Assistance toNeedy FamiliesDFHAid to the DisabledFood StampsHealth Maintenance, Buy-Inor Attempted Buy-InIncome MaintenanceTANF and FSMedicaid and Food StampsTitle XIX, MedicaidDeterminationChild Support EnforcementWritten Statement ofConsent of IndividualUnemployment CompensationNOTE: Earningsrequests cannot beused with Codes H,I orS.Some Codes are only tobe used by certainStates (A, B, D or U).Other Codes allow allStates to submitearnings requests.IJKNPSU51Direct Wire Input(Internal SSA useonly)Do not manuallyinputWRecord submitted thru SVES.(Internal SSA use only)52-59Date of DeathNumeric(MMDDCCYY)Alleged or invalid datashould not be entered. SeeDPA and DTH in positions60-62. This field isoptional.60-62State CommunicationCode(Mandatory Field)BDAUsed to initiate BENDEXdata exchange and orearnings request, reaccrete or to changepositions 50 and/or 68-79.DPADeletes BENDEX dataexchange and or earningrequest- recipient is nolonger eligible for publicassistance or death isalleged.DTHDeletes BENDEX dataexchange and or earningrequest- evidence of deathor reliable information ison file.STATES SHOULD LEAVE THISFIELD BLANK.12
63-66IEVS Agency Sub code(optional)Alpha-Numeric13Up to 4 one-positionidentification codesassigned by coordinatingState agency to identifythe requesting Stateagency. This data is notmaintained by the BENDEXSystem and will only bedisplayed on direct inputresponses.
67ReservedBlank68-79State Control DataAlpha-Numeric80ReservedBlankState identification orwelfare case number. Alphanumeric or packed data maybe used. Binary data arenot acceptable.Note: The mandatory fields, identified above, must be present on every record, inorder for your data exchange transaction request to process and avoid exception.If the BENDATA earnings request indicator code in position 12 is set to “E” or “B”then a finder is input to the Beneficiary Earnings Exchange Data System BEERTAPprocess for an earnings request reply to go to the appropriate state BEER file.14
SECTION 1.070TRANSMITTING BENDATA TO SSAAll input files to the BENDEX system are transmitted to SSA via the CONNECT:Direct (C:D) software that comprises SSA's File Transfer Management System(FTMS). The files may be sent directly to the BENDEX system via the BENDATAfile FORMAT as described in the BENDEX manual or via the SVES system asdescribed in the SVES manual.To establish a transmission thru FTMS it is necessary for the State to provideSSA the dataset name of the file on the State side. The CONNECT:Direct softwarewill establish the proper name for the file on the SSA side as a result of datahard-coded into the transfer process.BENDATA REQUEST OPTIONS AND ADVANTAGES ON QUESTIONABLE SSN CLAIM ACCOUNT NUMBERSThe advantage to using SVES as the input mechanism comes from the SVESverification of the SSN that uses all of SSA's databases to verify the SSN andidentifying information. The input thru BENDEX is limited to the MBR which usesSOUNDEX to match the name and SSN to the proper record. Since SVES has verifiedthe SSN/name/DOB the BENDEX system accepts the input even if the MBR does notmatch. This results in a higher success return rate from the State input file.15
HOW BENDEX EXCHANGE IS ESTABLISHED THROUGH THE BUYIN PROGRAMSECTION 1.100 POLICY ON AGENCY RESPONSIBILITIES IN THE BUYIN PROGRAMA.INTRODUCTIONB.PROCESS1.CMS COSeveral offices share responsibility in theadministration of the Buy-In Program. This sectiondescribes the responsibility of each office.Has overall responsibility for administration of the buyin program and specifically for: 2.CMS ROmaintaining the TPM record and HI master fileestablishing and coordinating buy-in procedurethird party buy-in operationsassisting and training State, SSA FO and CMS ROpersonnelresolving complex buy-in problemsprocessing manual actions and computer exceptionsServes as State liaison for: training State and SSA personnelresolving State inquiries on third party liabilitycoordinating data exchange issues with SSA RO whenthere are overlapping program concerns16
3.SSA FOResponsibilities include: 4.SSA COThe Office of Systems is responsible for: 5.STATE SSA ROREFERENCEupdating its file with information furnished by SSAand CMSdisseminating information to the requestingagenciessafeguarding personal information disclosedassuring that caseworkers understand and utilizethe informationassisting SSA in resolving problem casesdeleting BENDEX exchange when recipient eligibilityceasesProvides assistance to CMS RO on: C.maintaining the health insurance billing,entitlement and remittance systems, the MBR and theBENDEX Systemassisting CMS CO with State inquiriesdeveloping BENDEX proceduresThe State welfare agency is responsible for: 6.assisting beneficiaries in filing for Medicareassisting States in obtaining correct beneficiaryidentifying informationresolving problem casesproviding buy-in training to State personnelBENDEX policy and technical operation of the systemthe contents of files in the BENDEX Systemnotification to SSA CO of suspected systems problemsdata exchange issues where there are overlappingprogram concernsCMS Pub. 24, State Buy-In Manual on Supplementary MedicalInsurance Enrollment, Chapter III, Section 200.17
SECTION 1.110HOW BUY-IN OPERATIONS ESTABLISH BENDEXEXCHANGEA.INTRODUCTIONB.PROCESSThis section describes the interfaces between the CMSThird Party System and SSA's BENDEX, MBR and HI Systems.1.STAGE ONECMS accretes SSI recipients to the buy-in rolls forStates that have signed a 1634 Buy-In Agreement. Internalprocesses between CMS and SSA identify individualspotentially eligible for buy-in. Each month the ThirdParty System examines the data fields from a SSA file toaccrete those individuals receiving assistance benefitsor who are entitled to Medicare. The Third Party Systemdetermines the effective buy-in date. Buy-in accretionresponsibility rests with the State.2.STAGE TWOBuy-in transactions are screened against the SSA HImaster to assure that the individual is entitled toMedicare. If a match is not made, additional screeningprocesses are performed. Subsequently matched records reenter the system for processing.3.STAGE THREESSI accretion records initiated by CMS are sent in theState buy-in file. The buy-in operations then produce thetransactions that are used by SSA to update the MBR andHI master files. These updated records are generated tothe BENDEX operation.4.STAGE FOURThe BENDEX operations normally process after the MBR buyin update so that the latest information may be providedto the State. In any case, benefit and Medicareinformation is extracted to generate a BENDEX outputrecord and establish a BENDEX data exchange. This will beincluded in the daily process. A BENDEX record with dataexchange in place will be generated to the state wheneverthe buy-in is processed, changed or terminated.18
SECTION 1.120HOW MEDICARE CASES BASED ON DISABILITY AREACCRETEDA.INTRODUCTIONB.PROCESSWhen no record is found on the HI master file for aperson who is under 65, the MBR is checked to determineif future SMI eligibility will be based upon disabilityor end stage renal disease entitlement. This explainswhat happens if the disabled beneficiary is entitled forless than 24 months.When the State attempts to buy-in for a disabled personwho has not completed the 24-month SMI waiting period, aBENDEX record is generated to establish data exchange.The buy-in State will be notified: of any later change which could affect eligibilityfor buy-in coverage; andwhen the beneficiary is automatically enrolled forSMI during the 22nd month of disabilityentitlement.BENDEX attempted buy-in accretions can be identified bythe presence of Code A in position 218 of the BENDEXrecord. The HI master is usually established 2 monthsprior to SMI entitlement.19
SECTION 1.125HOW TO PROCESS ATTEMPTED BUY-IN CASESA.INTRODUCTIONAlthough a State’s buy-in accretion request may be rejected byCMS’ TP System because the item did not match on the HI masterfile, it may match on the MBR and was fully processed by theBENDEX System. The accreted disabled beneficiary will beentitled to Medicare within the next 2 years. The BENDEXexchange will remain active unless SSA places the beneficiaryin a terminated status. The State therefore is responsible fordeleting BENDEX exchange if the client becomes ineligible forpublic assistance.B.PROCEDURETake additional action as described below: If ongoing BENDEX exchange is appropriate, prepare a BENDATArecord using a Category of Assistance Code of H.If ongoing exchange is not appropriate, prepare a BENDATArecord using State Communication Code DPA.If you do not want to receive Source Code A records prepare awritten request to the SSA RO to request these records bedropped.C. REFERENCESTypes of BENDATA Records, Handbook Section 1.030Parts of the BENDATA Record, 10 Handbook Section 1.060SECTION 1.130A.FACTS ABOUT THE STATE CONTROL DATA FIELDDESCRIPTIONThe State control data field will sometimes be blank ordisplay a number that was not assigned by your State.Described below are some occasions when this may occur.1.Pseudo SCDWhen CMS has responsibility for accreting a SSI recipientunder the buy-in program, positions 68-79 of the BENDATArecord may display the recipient's BOSSN plus the SSAcounty code of residence. The BOSSN is present so thatthe State can identify the recipient if records arecompared with the SDX file. The pseudo SCD may be updatedby input of a current BENDATA accretion record.2.Missing Dataa.Input a current BENDATA accretion with theappropriate state control data. This will updatethe state control data.b.State control data are not displayed on publicwelfare accretions because the SSA Field Officedoes not have a facility for entering a casenumber.3.Conflict CasesIn some conflicting Agency situations, BENDEX will notreturn to the State its own SCD. This may result fromdeletion of an existing welfare number on the MBR duringthe buy-in process before a new welfare number can beannotated.20
SECTION 1.140 RECONCILING BENDEX AND Buy-In DISCREPANCIESA.INTRODUCTIONB.PROCEDURE1. Case File ReviewSince the inception of the Medicare program,incompatibilities have existed between the MBR and the HImaster files that cannot be resolved through a normal dataexchange. This section lists some situations whereassistance should be requested.Review the case file and determine if the discrepancy wasdue to: 2.When to ContactSSAContact SSA if: C. REFERENCESLate accretionComputer exceptionChange in SSA claim numberState is billed and BENDEX continues to show no SMIentitlement.Buy-in coverage period has ended and BENDEX showsthe State as premium payer.Both the State and recipient are billed.State is billed and SMI payments are being deductedfrom the Social Security check.State - State Buy-In Manual, Chapter II, Systems SSA –State Enrollment of Eligible Individuals, POMS Section HI00815.00021
SECTION 1.220A.PARTS OF THE BENDEX RECORDBENDEX RECORD LAYOUTThe first record on the BENDEX output file is a header label.DESCRIPTION ofBENDEX HEADER FIELDSPOSITION #This section identifies the data tag name, each positionnumber and a brief explanation of the information �UHL1’Header Label constant5-10File Name‘BENDEX’Header Label constant11-12Filler‘ A’Header Label constant13-15Agency CodeNumericThree position State Agency Codes,See Handbook Section 1.25016FillerBlank17-22File RunDateNumeric(MMDDYY)BENDEX run date23-30Filler‘ CK DUE ‘Header Label constant31-34Check DueDateNumeric(MMYY)Date the next Social Security checkwill be paid35FillerBlank36-38File Type39-800FillerBlank or ‘BRI’ Daily BENDEX files will containblanks. BRI BENDEX files willcontain ‘BRI’BlanksDESCRIPTION ofBENDEX FIELDSPOSITION #1-9This section identifies the data tag name, each positionnumber and a brief explanation of the information ricClaim number under which SSAbenefit is filed.22
Numeric Recipient's own SSN when theyare a primary beneficiary. Inthis situation the CAN is equalto the BOAN/SSN plus the BIC.If the beneficiary is receivingbenefits as an auxiliary orspouse on someone else’saccount, the CAN does not equalthe BOAN/SSNWhen SUR UNM records arereturned with the State inputSSN in positions 71-79, the CANdisplayed here is probably anunrelated cross-referencenumber and should not be usedto overlay an SSN youpreviously validated. SeeHandbook Section 1.600.10-11BICAlphaNumericcodesIdentifies the type of benefitreceived. See Handbook Section1.820 for values and explanations.12-31BLNBeneficiaryLast NameBGNBeneficiaryGiven NameBMNBeneficiaryMiddle NameBSNBeneficiarySuffix NameSexAlphaLeft justified if fewer than 20positions.AlphaLeft justified if fewer than 15positions.AlphaLeft justified if fewer than 15positions.AlphaLeft justified if fewer than 4positions.AlphaAlpha/numericMatched records will display theSSA sex code M-male or F- female.22 Positions payee name andaddress data (variable field)Alpha/numeric22 Positions payee name andaddress data (variable field)Alpha/numeric22 Positions payee name andaddress data (variable field)Alpha/numeric22 Positions payee name andaddress data (variable field)Alpha/numeric22 Positions payee name andaddress data (variable field)Alpha/numeric22 Positions payee name andaddress data (variable 5-176177-198199-203204-208Payee Nameand Addressline-1Payee Nameand Addressline-2Payee Nameand Addressline-3Payee Nameand Addressline-4Payee Nameand Addressline-5Payee Nameand Addressline-6ZIP CodeFILLER5 position address ZIP Code5 positions for future useBLANK23
209-213State andCounty CodeNumericA five-position code reflectingthe residence of the beneficiary.The first two positions representthe State code; the remainingpositions are the SSA assignedcounty codes.214DirectDepositIndicator(DAN)C or S orblank215-217Agency CodeNumericReflects the type of account towhich payment is being deposited.C Checking accountS Savings accountBlank when no direct depositThree position State Agency Codes,See Handbook Section 1.250218Source CodeARequest originated from State'sattempt to buy-in for a disabledperson who is in the 24-month SMIwaiting period.Request originated as a result ofState buy-in activity.Response generated by SSA toreport a change.Request originated from directsubmission by a State.Reimplementation responsegenerated by SSA at the request ofthe State.BCDR219Category ofAssistanceCodeAlphaThe most recent code submitted bya State on the BENDATA input file.See Handbook Section 1.060An invalid code was received fromthe buy-in system. A blank wasannotated to the MBR.220DWI CodeWBlankRecord submitted through SVES.Not applicable.221EarningsRequestIndicatorE orBLANKE-Earnings information wasrequested. Earnings informationwill be released on the BEERrecord.222-233StateControl DataAlphaNumeric orpackeddecimalcharacters State identification or welfarecase number entered on BENDATArecord. Nine digit SSN and three digitSSA county code of residence forautomatic buy-in of SSIrecipients. When Source Code (Position # 218)is equal to “C”, the datapreviously annotated to the MBR.BlankSee Handbook Section 1.130.24
234-237IEVS AgencySub code(This dataelementoriginatesfrom theBENDATArecord andis notmaintainedby SSA.)AlphaNumericUp to 4 codes assigned by thecoordinating agency that identifiesthe requesting agency to which thedata is to be released. This field isoptional.238-239Old BICAlphaNumeric 240-248SSNBlank State did not furnish a BIC, orData input by State agrees withSSA record.Numeric The SSN furnished on the State'sBENDATA record; orThe BOSSN. Blank249-250PaymentStatus ment:RRBInvolvementEDeferredDPDWD1D2D3 The record was not acceptable orthe SSN is not available.NOTE: The SSN may be unverified.A one or two- position codereflecting the SSA payment status forthis beneficiary. This payment statuscode and the effective datedetermines if entitlement is currentand overrides any other entitlementfactors.Adjusted for dual- entitlementAdjusted for simultaneous entitlementAll other adjustment actions.Current Payment Status Code.RRB paying benefitsReceipt of public assistance.Receipt of worker's compensation.Engaging in foreign work.Beneficiary overpaid because of work.Auxiliary's benefits withheld becauseof D2 status for primary beneficiary.Failure to have child in care.Auxiliary's benefits withheld becauseof a D1 status for primarybeneficiary.Deferred to recover overpayment forreason not attributable to earnings.Miscellaneous defermentD4D5D6D9Denied:State input BIC is incorrect anddiffers from the MBR BIC orChange in type of SSA benefitreceived.NDisallowed claim25
NDDisability claim denied.Delayed:KLPPBPTRAdvanced filing for deferred payment.Advanced filingAdjudication pending.Benefits delayed, due but not paid.Claim terminated from delayed status.Kill Credit (deletes payment record)Suspended:S0Determination of continuingdisability is pending.Beneficiary engaged in work outsidethe U.S.Beneficiary is working in the U.S.and expects to earn in excess ofannual allowable limit.Auxiliary's benefits withheld becauseof S2 status of primary beneficiary.Failure to have child in care.Auxiliary's benefits withheld due toS1 status for primary beneficiary.Check was returned - correct addressbeing developed.Disabled beneficiary suspended dueto- refusal of vocationalrehabilitation; imprisoned; extendedtrial work period.Suspended while payee is beingdetermined.Suspended for reason not separatelydefined.Technical entitlement only.Beneficiary is entitled on anotherclaim.Special age 72 beneficiary fails tomeet residency requirement.Special age 72 beneficiary isreceiving a Government pension.Alien suspensionBeneficiary has been deported.Beneficiary resides in a country towhich checks cannot be sent.Beneficiary refused cash benefits(entitled to HI-SMI only).Special age 72 beneficiary suspendeddue to receiving public assistance.Post secondary student summersuspension.Suspended because of worker'scompensation.Disabled Beneficiary suspended due toparticipation in DEMO Project.Terminated prior to entitlement
6 B. DEFINITIONS - TERMS 1. APPLICANT A person who has filed for assistance or benefits 2. BENEFICIARY A person who is entitled to Social Security benefits. 3. CLAIMANT A person on whose behalf an application is made. 4. CLAIM NUMBER A number used by SSA to identify an individual who is a claimant or a beneficiary. 5. CLIENT A synonym for beneficiary or recipient.
