The Representative Accountability Database (RAD) launched in June of 2019. On Monday, May 25, 2020, the use of RAD becomes mandatory. USAC asks that service providers inform their representatives of this requirement.
RAD Adoption Period Milestones
Beginning May 25, 2020*:
The use of RAD becomes mandatory. This means that at this time:
- NLAD and National Verifier transactions will require a Representative ID and may receive an error.
- Transactions submitted via API must include the correctly populated fields in the API Specifications:
- RepID: This field should be used to send a Representative ID for the representative associated with the transaction, or
- RepNotAssist: This field should be used to indicate no representative was involved in the transaction (such as when enrollment is submitted via a service provider’s online enrollment system and is not reviewed by a person before being submitted to NV or NLAD). Failure to include a Representative ID when an enrollment representative is actually involved in the workflow may result in a violation of the Commission’s rules.
* In response to the COVID-19 pandemic and to reduce the burden on Lifeline providers, full implementation RAD will be delayed until Monday, May 25, 2020.
- RAD released in the production environment for optional use.
- Service providers have the option to link Representative IDs to NLAD user accounts and API accounts.
- Once a Representative ID is linked to an account, USAC will begin monitoring the transactions associated with that ID.
- At this time, the use of RAD is fully voluntary. RAD will be mandatory when the FCC’s enrollment representative rule becomes effective. The rule will become effective 90 days after the Lifeline Fifth Report and Order is published in the Federal Register.
- For more information on these changes, review the November monthly webinar.
- Service providers may use the staging environment for testing the validations and errors related to a Representative ID during NLAD transactions. For example, service providers may test the errors that they would receive when trying to perform an enrollment with an account linked to a locked Representative ID.
- Services providers will also be able to test any errors that they could receive during an API or batch transaction related to the two new Representative ID fields.
- With this release, service providers will receive an error when attempting a transaction in the staging environment that does not have a Representative ID linked.
- Service providers can request the API Specifications by contacting LifelineSupport@usac.org with the subject line RAD – NLAD API Specs. The subscriber batch file template is available on the RAD Resources page.
- Service providers may begin linking Representative IDs to accounts in the National Lifeline Accountability Database (NLAD) staging environment
- Service providers must use the test Representative IDs provided in the NLAD Staging Guide: Testing RAD with Individual User Accounts or the NLAD Staging Guide: Testing RAD with API Accounts
- Representatives may begin registering for a Representative ID.
Linking a Representative ID to an Existing User Account
Service providers are responsible for collecting their representatives’ Representative ID. 497 Officers must link Representative IDs to ETC Administrator roles and ETC Administrators must link Representative IDs to all subaccount roles.
To link a Representative ID to an existing user account,
- The 497 Officer or ETC Administrator will download the file upload template,
- The 497 Officer or ETC Administrator will complete the file upload template, and
- The file may contain one or more accounts and all 8 column headers are required in the file template
- Values for “User Name” and “API ID” are conditional (1 of the 2 are required, but cannot have values for both in the same row)
- Master Agent values are optional and Master Agent information should be included with any applicable representative information
- The 497 Officer or ETC Administrator will upload the completed template to NLAD.
- If a Representative ID receives an error, the 497 Officer or ETC Administrator may download a file to see what errors are associated with the Representative IDs in a specific upload.