Overview

Discovered and expected accounts are two features designed to go hand in hand. Discovered accounts allows your organization to handpick which accounts are activated, rather than activating all accounts by default. Expected accounts allows your organization to provide Arcadia with a list of account + provider combinations you expect us to find from your supplied credentials, such that when we do come across the account, we can activate it on your behalf without any additional input required from you.

Expected accounts builds on top of discovered accounts, reducing onboarding hassle and friction.

Discovered Accounts

Discovered accounts enable you to manage your account activation on a case by case basis. Previously, all accounts were activated by default. This meant you would need to deactivate accounts that were not required for your use case. If you opt into the discovered accounts feature, going forward, all accounts will begin in a discovered state and must be activated by you, the customer, before Arcadia fetches and makes data available.

How it works

When auto-activation is disabled for your organization, any accounts found behind a credential will initially enter a "discovered" state instead of being automatically activated. This gives you the opportunity to review and select which accounts you wish to activate.

When you submit a credential, all associated accounts (normal, summary, and sub-accounts) are discovered through a Top-of-Stack (TOS) data pull and assigned status: NEW_ACCOUNT and statusDetail=STATEMENT_EXTRACTION_NOT_REQUESTED

We will then expose high level data only that you can use to determine if you would like to activate the account. This includes data such as account number, billing address, and meter numbers, but excludes detailed information such as usages and charges. If the account data is desired, you can activate the account as needed.

Next expected post (NEP) will be null for any discovered account given we do not have enough information to confidently predict the next NEP date. Additionally, some detailed endpoints may be blocked until the account is activated (ex. Retrieve Detailed Account).

Note that for a summary account with 1 more more sub-accounts, activation (or deactivation) of either the summary account or one of the sub-accounts would imply activation of the summary accounts & all sub-accounts.

Accounts not associated to a credential with web navigation

For any account discovered from the bill uploader, email (beta), or third party portals (TPP), the account will be auto activated regardless of your organization configuration. This is because these accounts are specifically provided by you, the customer, to Arcadia and are not "discovered" via web navigation.

If you no longer expect to upload bills manually for a given account, deactivate the account. However, if you upload a bill for the same account, it will be activated by default again.

Tradeoff: Speed for choice

For customers who opt into this feature, you will gain control over which accounts data is initially fetched for and subsequently you are billed for. However, this also means that there will be a delay in data delivery as we will not begin the process to obtain the statement data until you activate a given account. For more details on this, reach out to your Account Manager or Customer Success Manager.

How to opt in

If you are interested in this feature, reach out to your Account Manager, Customer Success Manager, or Zendesk with the ask and we will update your organization settings!

Webhooks

Discovered accounts feature enabled

For organizations with the discovered accounts feature enabled, NEW_DATA_AVAILABLEwebhooks will be triggered upon account record creation, and STATUS_CHANGEwebhooks will be triggered when an account is manually activated or an expected account is matched to an account record.

📣

With these new features, you can now choose to disable auto-activation and instead manage accounts through a "discovered" state or by providing a list of "expected" accounts. This empowers you to activate only the accounts essential for your business operations, avoiding unnecessary costs and data.

Discovered accounts feature disabled

For organizations with the discovered accounts feature disabled, there will be no change to existing behavior.

Expected accounts

Expected accounts allows you to proactively provide us with list of accounts you intend to activate. This streamlines the onboarding process and ensures that only desired accounts are activated with minimal customer involvement.

How it works

From the Dashboard, navigate to the Accounts page, select the "Management" tab. From here, select the button "Upload expected accounts" in the top right hand corner and download the template. Fill in the template based on your data and upload the file containing your expected accounts.

After uploading your expected accounts, you can view, search, and filter your list of expected accounts. You can also delete expected account records through the UI, though editing is not supported at this time. You can include custom data for your expected accounts in the upload file, which will be passed to the account record once matched and activated.

Once an expected account is discovered and subsequently auto activated, it will be removed from the expected account table view. The account record will reflect in its event history that it was auto-activated after discovery.

📘

You can also use the Create Expected Accounts endpoint to handle this in an automated fashion.

Uploading expected accounts after a credential is submitted

If an expected account record is created before the account is discovered, it will be automatically activated once found.

If an expected account record is created after an account is discovered, the discovered account will be activated once the expected account is submitted and matched. Typically we recommend uploading your expected accounts first to receive data more quickly, however, the accounts will be activated all the same regardless of order if a match is found.

🚧

Pre-existing accounts and post-account discovery expected accounts

If an account record existed, but was not activated prior to the release of expected accounts, the account will NOT change status nor status detail when the expected account is matched to the existing account record. This also means a webhook will not be triggered.

This only impacts records created before the feature release on November 19, 2025 that were not activated.

Filling out the template

1. In the template expectedAccounts.csv, add the accountNumber and provider information for the expected account you want to create. Optionally, you may include any relevant custom data. Note you cannot edit expected accounts once created, so be sure to include this information if it is relevant or delete and resubmit if needed.
2. Follow the same steps for every expected account record you would like to create and submit the the file.
3. If any warnings or errors are found, address them as needed and re-upload the file or ignore the warnings altogether. All expected accounts will be created and viewable in the Accounts --> Management tab of the Dashboard.

File requirements

• Supported file format: CSV only
• Maximum file size: 1 GB
• Maximum number of rows: 10,000

Template details: expectedAccounts.csv

All field lengths have maximums of 255 characters excluding providerId. providerId has a value of 40 characters: prv_00000000-0000-0000-0000-000000000000.

Warnings

Warnings may be ignored. They are flagged as irregularities from Arcadia's perspective.

Errors