Managing Account Connections, Attestations, and Data Uploads in Hadrius

Last updated: July 24, 2026

Unable to Sign an Attestation Document

If you're having trouble signing an attestation document in Hadrius, try the following steps:

  1. Refresh the page and try again.

  2. Switch to a different browser (Chrome or Edge) or open an incognito/private window.

  3. If the issue persists, try signing from another device, such as your phone or a different computer.

Accounts Not Appearing in Attestation Questions

If an attestation question shows "No brokerage accounts found" even though your accounts appear under Manage Accounts, try the following:

  1. Click 'Refresh' on the attestation question to prompt the system to pull in the latest account data.

  2. Check the timing of your account connection. If accounts were connected or updated after the relevant attestation period began, they may not appear in that period's attestation questions. The certification system looks for accounts that were active during the specific attestation period.

If accounts still don't appear after refreshing, contact support so they can review the account mapping and status.

Handling Transferred or Closed Accounts

When an account is transferred to another institution (for example, a Vanguard IRA rolled over to Schwab), the original account must be manually marked as closed or inactive in Hadrius using the appropriate transfer date from the statement. The system does not automatically close accounts based on transfer activity shown in uploaded statements.

Key points to keep in mind:

  • Marking an account as closed does not delete it. Closed accounts remain accessible by changing the account filter to All Accounts or Closed Accounts.

  • Leaving a transferred account open will cause the system to continue requesting statements for that account, including for months after the transfer occurred.

  • Account transfers can create duplicate records with different masked account numbers, which may prevent accounts from displaying correctly in attestation questions. If you suspect a duplicate, contact support to identify and resolve the mismatch.

Multiple Access Persons Reporting the Same Accounts

Hadrius supports multiple access persons reporting the same accounts — for example, spouses who share joint brokerage accounts. Each shared account exists as its own record under each user, so there is no system limitation preventing this.

However, if multiple users are connecting to the same broker using a shared login, the broker's system may not handle two separate active connections against one login well. This can cause one user's connection to be periodically invalidated, while the other user's data feed remains healthy.

If you encounter this situation:

  1. Reconnect the broken account through the standard reconnect flow as an immediate fix.

  2. Request separate login credentials from the broker for each user who needs their own connection. Having distinct logins for each access person prevents the broker from invalidating one connection when another is active.