---
title: "How to Use Two Software Systems With the Same Claim.MD Account"
slug: "how-to-use-two-software-systems-with-the-same-claimmd-account"
updated: 2026-01-23T17:49:49Z
published: 2026-01-23T17:49:49Z
canonical: "docs.claim.md/how-to-use-two-software-systems-with-the-same-claimmd-account"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.claim.md/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Use Two Software Systems With the Same Claim.MD Account

## Scenario 1: API and SFTP

Two separate software systems can submit claims to the same Claim.MD account when one system uses **API** submission and the other uses **SFTP**. This type of setup is common in multi-system or transitional environments and does not impact claim submission.

### ERA Processing Considerations

While claim submission functions normally across both systems, **ERA delivery and visibility may differ between systems**.

ERAs may appear in one system before the other, even though both systems are connected to the same Claim.MD account. This difference is due to how each system retrieves and processes ERA files, including polling intervals, import schedules, and internal handling logic.

This behavior is expected and does **not** indicate a processing error within Claim.MD.

### Recommendation

If consistent or simultaneous ERA visibility is required across systems, each system’s ERA retrieval and import configuration should be reviewed. This includes confirming how and when ERAs are downloaded or consumed, and whether files are shared, duplicated, or removed during processing.

Proper coordination between systems will help ensure ERAs are received and reconciled as expected.

## Scenario 2: SFTP and SFTP

It is technically possible for two different software systems to use the same Claim.MD SFTP credentials. Both systems can upload claim files to Claim.MD without issue, and uploads will generally process as expected.

However, special care must be taken on the **download side**.

### Important Consideration: Downloaded Files

Acknowledgements, claim status files, and ERAs are typically **downloaded and removed** from the SFTP server when a system retrieves them. If two systems are configured to download from the same SFTP directories, whichever system connects first will usually pull the files and remove them from the server. As a result, the second system may never receive those files.

This can lead to missing acknowledgements, incomplete claim status information, or lost ERAs.

### Recommendation

Running two systems in parallel against the same Claim.MD SFTP site is **not recommended** unless there is strong technical oversight and a clearly defined strategy. At a minimum, there should be a documented plan that addresses:

- Which system is responsible for downloading specific file types (such as acknowledgements, claim status files, or ERAs), and
- How files will be managed to ensure they are not removed before the other system has a chance to retrieve or process them.

Without this level of coordination, sharing a single SFTP setup between multiple systems can create data gaps and reconciliation issues.

## Scenario 3: API and API

Two separate software systems can be connected to the same Claim.MD account using **API access**. To configure this, enter the API key from the first software system into the second software system. **Two applications can use the same API key** without issue.

If you do not know your API key, the existing key will need to be **deleted and a new one created**. Instructions for managing API keys can be found here: [https://docs.claim.md/docs/api](https://docs.claim.md/docs/api)

When a new API key is generated, it must be entered into **both the original application and the new application**. This ensures uninterrupted connectivity for all systems using the Claim.MD API.

### Important Consideration

Deleting and recreating an API key immediately invalidates the previous key. Any application still using the old key will no longer be able to connect until it is updated with the new API key.