EDGAR Next Webinar: Platform enhancements and support features
完了📆 Date: Thursday, March 13
⏰ Time: 12:00 PM EST
🌎 Location: Virtual
Workiva Customer? Register here
Workiva Partner? Register here
About this event
The SEC highlighted the requirement to have a current CCC and Passphrase before enrolling in EDGAR Next in their announcement on February 25, 2025.
Filers need a current passphrase and CIK confirmation code (CCC) to enroll. Filers who have not reset their passphrase or CCC since September 2019 should obtain a new passphrase and a new CCC.
We've outlined some steps here to help you with this process. To help you navigate this EDGAR Next change and more, please consider joining our third and final webinar in our EDGAR Next webinar series. Our webinar will focus on platform enhancements and features to support you prepare for the EDGAR Next changes.
Speakers:
- Jarrod Byerly, Product Success
Session topics:
- User and Filer Token Management within Workiva
- Simplified In-platform Enrollment and Delegation Processes
- Test and Live Filing with EDGAR Next Credentials through Workiva
To learn more about EDGAR Next, visit the Workiva resource hub and our EDGAR Next community space. Still have questions? Ask them here or email us edgarnext@workiva.com. We hope to see you there!
https://workiva.wistia.com/medias/keowc48n6e
Click here to download the slides
EDGAR® and SEC® are trademarks of the U.S. Securities and Exchange Commission. Workiva Inc.'s products and services are not affiliated with or approved by the U.S. Securities and Exchange Commission.
-
Do you expect that most customers will choose the option to file with Workiva going forward? I'm a little confused about the two options. We can (1) delegate authority to Workiva to file, which would eliminate the need for users to reset user tokens monthly but we would still need to ensure that our entity tokens are refreshed once per year and added to Wdesk of (2) Manage our user tokens and entity tokens and file using the Wdesk platform without delegation to Workiva?
0Hi Jamie!Thanks for the question. We expect we may see an increase in the usage of File with Workiva as it is a simplified option to ease the burden of token management by our customers. That being said, customers will always have the option to utilize and manage their own tokens and upload them for use within Workiva. If you choose to delegate, you'll have the option to use Workiva's filer token (which Workiva will manage) and your own user token (expires every 30 days) to process filings. Delegation to Workiva also unlocks the ability to utilize the File with Workiva option where token management is handled behind the scenes by Workiva. So technically you wouldn't have to regenerate a Filer token for your company annually and users wouldn't have to generate a new token every 30 days. An account admin would still have to perform the annual confirmation within the EDGAR Next dashboard confirming details and users on the account and that the account is still active.Let me know know if you. have any follow-ups or need anything else. Cheers!0Hi Mike,
For User Token, what happens if we don't refresh it every 30days? If we keep it expiring for 60ds and we regenerate a new code, will it be okay and will our User Token still stay active?
For the Delegation to Workiva to manage the token for the Company. Does Company need to pay any extra fees or is it already included in the subscription?
Thanks.
0^ Same question as Dararith- I am about to go on a multi-month maternity leave shortly after I set up our EDGAR Next. Is there some kind of pause available since I won't be able to log in and refresh every 30 days?
0Hi Dararith!
For User Tokens, the following rules apply:
- User Tokens expire after 30 days from when they are generated
- You must generate a new User Token at least every 30 days to keep it active
- If you let a User Token expire (go more than 30 days without generating a new one), your previous token will become invalid
- Generating a new User Token before the 30 day expiration will create a new valid token and invalidate the previous one
- There is no way to extend a User Token beyond 30 days - you must generate a new one
So in your scenario, if you let the token expire for 60 days, it will become invalid after 30 days. When you generate a new token after 60 days, it will create a new valid 30-day token. Your account access will remain active, but you'll need to use the newly generated token.
There are no additional fees for delegating to Workiva to manage your company's EDGAR Next tokens. This functionality is included as part of your existing Workiva subscription at no extra cost.
0Unfortunately, there is no "pause" option for EDGAR Next token management during extended leave. The strict token expiration policies are intended to enhance security, but can create challenges for extended leave situations. Proper planning and delegation of authority are key to maintaining uninterrupted EDGAR access during your absence.
For extended leave situations, here are some recommended options:- Delegate authority to another trusted individual in your organization to manage token renewal and account confirmation during your absence. This can be done by adding them as an Account Administrator in EDGAR Next.
- Set calendar reminders to log in remotely and renew your User API Token every 30 days if possible during your leave.
- Create multiple User API Tokens before your leave starts (up to the maximum allowed) to extend the renewal window.
- Contact the SEC EDGAR Business Office to explain your situation and see if any accommodations can be made for extended leave scenarios.
- As a last resort, plan to re-enroll in EDGAR Next upon your return if your account becomes inactive due to expired tokens/missed confirmations.
Hope that helps some. Last but not lease, congrats to you on your upcoming addition to your family! Enjoy your time away :)
1Hi Mike,
Following up on your response to Jamie's question, I would like to confirm - it sounds like even though a company does not need its filer token when submitting filings (if it uses File with Workiva), the filer still needs to set up its filer tokens in order to be able to delegate to Workiva (through Workiva) in the first place (based on the video)? If one would like to delegate to Workiva through Edgar, would that still be the case? In other words, in what context do we as the filing entity need to provide our filer API token, and in what context do we need to obtain a delegated entity's filer API token? Thank you!
0Hi Amy!
Sure, no problem. Lemme wax poetic here on delegating to Workiva
Through Workiva's interface
You will need to set up at least one filer API token for your company and this token is used to authenticate the delegation request to the SEC. You won't need to provide this token to Workiva directly
Directly through EDGAR
You can initiate delegation without creating a filer API token simply by logging into the EDGAR Filer Management dashboard and using the delegation interface.
As to when you need your filer API token, you'll need it to 1) create API connections for your own use, 2) initiate delegation through Workiva's interface, and 3) if you choose not to delegate and want to file using your own credentials.
After successful delegation you would use Workiva's filer API token when using "File with Workiva", or any filings where you've chosen to use Workiva's token instead of your own. It's generally a good idea to create at least one filer API token for your company, even if you plan to delegate. This gives you flexibility and a backup option for filing.Hope that helps. Do let me know if you have any follow-ups. Thank you!
0サインインしてコメントを残してください。
コメント
8件のコメント