---
title: "Configuring ACE2ACE Forwarding"
slug: "configuring-ace2ace-forwarding"
updated: 2026-07-13T16:11:42Z
published: 2026-07-13T16:11:42Z
canonical: "docs.interprose.com/configuring-ace2ace-forwarding"
---

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

# Configuring ACE2ACE Forwarding

## What is ACE2ACE Forwarding?

ACE2ACE Forwarding allows accounts to be sent between ACE systems while maintaining a continuous synchronization between the sending and receiving agencies. Throughout the forwarding lifecycle, account activity such as transactions, disputes, bankruptcies, and recalls are synchronized automatically. When appropriate, accounts can also be returned to the originating (Send Vendor) agency.

**ACE2ACE Forwarding:**

- Sends accounts between ACE systems using API communication.
- Maintains a linked relationship between the sending and receiving systems.
- Synchronizes transactions, disputes, bankruptcies, and other supported account activity.
- Uses callbacks to communicate updates between systems.
- Supports returning accounts to the originating ACE system.

## When to Use ACE2ACE

**Use ACE2ACE Forwarding when:**

- You are sending accounts between two ACE systems
- You need updates (payments, disputes, etc.) to sync automatically

**Use standard forwarding when:**

- Accounts are sent to external vendors

## Prerequisites (ACE2ACE Only)

Required for ACE2ACE forwarding only (not standard vendors):

- Enable API key package add-on for both systems by contacting sales@interpose.com
- Both systems (send and receiver):
  - Generate API key: [Generate API Key](https://docs.interprose.com/docs/adding-api-key-for-user)
  - Share API key via Secret Manager: [How to Use secret.interprose.com](https://docs.interprose.com/docs/how-to-use-secretinterprosecom)

## How ACE2ACE Forwarding Works

1. The forwarding lifecycle consists of the following steps:
2. Accounts are selected using a Forwarding Distribution.
3. Accounts are forwarded to the receiving ACE system.
4. A forwarding relationship is established between both systems.
5. Supported account activity is synchronized automatically.
6. When appropriate, accounts can be recalled or returned to the originating ACE system.

## Step 1: Configure Vendors

This step is required in both systems.

- The sender (source system) configures the Send Vendor
- The receiver (target system) configures the Receive Vendor

### Configure Send Vendor

Used to send accounts to another ACE system.

1. Go to: **Forwarding → Vendors → New**
2. Enter Data:
  1. Forward Provider: Ace2Ace
  2. Identifier (Use the same identifier on both the send and receive vendors)
  3. ACE Mode = Send
  4. Receiver Customer ID
  5. Receiver Login URL
  6. Receiver API Key
  7. Payment Destination
  8. Location
3. Apply
4. Add Placement Type:
  1. Placement Type: (e.g., Primary, Secondary)
  2. Commission Rate: Default forwarding commission
  3. Minimum Balance: Optional minimum balance requirement
  4. Minimum Settlement: Optional minimum settlement percentage
5. Save

![](https://cdn.document360.io/6c7303ca-5ffc-4149-8868-8ea498eee635/Images/Documentation/Screenshot 2026-04-30 165739.png?sv=2026-02-06&spr=https&st=2026-10-31T22%3A48%3A47Z&se=2026-10-31T23%3A48%3A47Z&sr=c&sp=r&sig=vFtwI2t18JqfqGFe3Kom4%2BPoFrUENwk3RoKSZFlA2kw%3D)

Image Displays Example ACE2ACE Forwarding Configuration For Send Mode

#### Vendor Field Descriptions

| Field | Description |
| --- | --- |
| **Forward Provider** | Select ACE2ACE as the provider |
| **Identifier** | Use the same identifier on both the send and receive vendors. This value is used to pair the two systems together. |
| **ACE Mode** | Set to Send on the system forwarding accounts. Set to Receive on the system accepting forwarded accounts. |
| **Receiver Customer ID** | Customer ID on the receiving system |
| **Receiver Login URL** | Full login URL of receiving ACE system |
| **Receiver API Key** | API key provided by receiving system |
| **Force Recall Through Active Payment Plans** | Optional behavior: If enabled, receiver-side recalls will deactivate active payment plans before the account is recalled. |
| **Ignore Bundle Method** | If enabled, overrides the global Bundle Method setting and allows accounts to be distributed without considering bundle relationships. |
| **Note** | Internal reference |
| **Payment Destination** | It is recommended that you create a Manual Mixed payment destination for the forwarding vendor. Select the created payment destination. |
| **Location** | If you want to create a unique payment batch location for forwarding, you can go to Setup → Transactions → Payment Batch Locations. Select the related location here. |
| **Max Placements** | This will restrict the maximum number of accounts that can be placed with this forwarding vendor. Use 0 if there is no such restriction. |
| **Max Placement Amount** | This will restrict the maximum amount that can be placed with this forwarding vendor. Leave blank if there is no restriction. |
| **Exclude States** | This will automatically exclude accounts from being placed with this forwarding vendor if the account as a primary address state selected here. It’s used to prevent forwarding agencies from working accounts in states where they aren’t licensed to work. |
| **Default Status Code** | The status code for accounts placed with this forwarding vendor if not declared in the distribution settings. See: Forwarding Distributions. |
| **Accepted Vendor Status Codes** | When updating account statuses using the ETL Profile Account Update load method, the Forwarding Vendor Status Field can map status codes. ACE excludes status codes not selected here. |
| **Active** | Enables the vendor |

### Configure Receive Vendor

Used to accept inbound accounts.

1. Go to: **Forwarding → Vendors → New**
2. Enter Data:
  1. Forward Provider: Ace2Ace
  2. Identifier: Same as Send Vendor
  3. ACE Mode = Receive
  4. Expected Sender Customer ID
  5. Source Callback Endpoint
  6. Source Callback API Key
  7. Receiver Client ID
  8. Receiver Client ID
  9. Payment Destination
  10. Location
3. Apply
4. Complete any additional vendor fields and sections as needed
5. Save

![](https://cdn.document360.io/6c7303ca-5ffc-4149-8868-8ea498eee635/Images/Documentation/Screenshot 2026-04-30 174454.png?sv=2026-02-06&spr=https&st=2026-10-31T22%3A48%3A47Z&se=2026-10-31T23%3A48%3A47Z&sr=c&sp=r&sig=vFtwI2t18JqfqGFe3Kom4%2BPoFrUENwk3RoKSZFlA2kw%3D)

Image Displays Example ACE2ACE Forwarding Configuration For Receive Mode

#### Receive Vendor Field Descriptions

| Field | Description |
| --- | --- |
| **Forward Provider** | Select **Ace2Ace** |
| **Identifier** | Use the same identifier on both the send and receive vendors. This value is used to pair the two systems together. |
| **ACE Mode** | Set to **Receive** on the system accepting forwarded accounts. |
| **Expected Sender Customer ID** | Receiver-side safeguard. Set this to allow only the specified sender customer to forward or recall accounts. |
| **Source Callback Endpoint** | Endpoint used by the receiving system to send updates (payments, disputes, bankruptcies, and recalls) back to the source ACE system. |
| **Source Callback API Key** | API key used by the receiving system to authenticate callback requests to the source system. |
| **Receiver Client ID** | Select the local client where inbound accounts will be created. ACE stores that client’s numeric ID for forwarded accounts. |
| **Ignore Bundle Method** | If enabled, overrides the global Bundle Method setting and ignores bundle relationships during distribution. |
| **Note** | Internal description of the vendor configuration. |
| **Active** | Enables the vendor. |

### Important

- Vendor identifiers must match between systems
- Callback settings allow the receiver to send updates back to the source
- Receiver-side activity (payments, disputes, recalls) uses these callback settings

## Step 2: Create a Distribution (Sender Only)

The sender creates and controls the distribution.

1. Go to **Forwarding → Distributions**
2. Configure:
  1. Selection Logic
  2. Distribution Method
  3. Schedule
  4. Status to Set After Forward (optional)
3. Add Direct Assignment
4. In the Direct Assignments section, click Add
  1. Select:
    1. Vendor: your configured ACE2ACE vendor
    2. Logic: Select the same logic used for the distribution

Accounts returned by the logic block will be sent to the selected ACE2ACE vendor when the distribution is run.

![](https://cdn.document360.io/6c7303ca-5ffc-4149-8868-8ea498eee635/Images/Documentation/Screenshot 2026-05-08 101242.png?sv=2026-02-06&spr=https&st=2026-10-31T22%3A48%3A47Z&se=2026-10-31T23%3A48%3A47Z&sr=c&sp=r&sig=vFtwI2t18JqfqGFe3Kom4%2BPoFrUENwk3RoKSZFlA2kw%3D)

Image Displays Example Distribution Configuration

> [!NOTE]
> Please Note
> 
> When you save the distribution, ACE automatically creates a Job with the same name.
> 
> This job is used to run the distribution and must be executed to forward accounts.
> 
> ![](https://cdn.document360.io/6c7303ca-5ffc-4149-8868-8ea498eee635/Images/Documentation/Screenshot 2026-05-08 101510.png?sv=2026-02-06&spr=https&st=2026-10-31T22%3A48%3A47Z&se=2026-10-31T23%3A48%3A47Z&sr=c&sp=r&sig=vFtwI2t18JqfqGFe3Kom4%2BPoFrUENwk3RoKSZFlA2kw%3D)

#### Notes

- This step is performed only by the sender
- The receiver does not create or run distributions
- Group assignments are only needed when distributing across multiple vendors
- Status updates apply only when accounts are forwarded
- If no status is set, the account status will not change
- Use Model & Forward and run the job to send accounts

## Step 3: Run the Distribution (Sender Only)

The sender runs the distribution to forward accounts.

**You can run the distribution from:**

- The Distribution page (click Run)
- The Job that was automatically created when the distribution was saved

## Step 4: Account Forwarding Behavior

When a distribution runs, ACE forwards the selected accounts to the receiving ACE system and establishes a synchronized relationship between the two systems.

During the forwarding process:

- The account is created under the configured client in the receiving ACE system.
- A forwarding relationship is established between the sending and receiving systems.
- All active demographic information, including phone numbers, addresses, and email addresses, is transferred to the receiving system.
- The sender's Agency Number (Debt ID) becomes the Client Account Number on the receiving system, preserving the relationship between both accounts.

## Step 5: Data Synchronization

#### Account Number Mapping

When an account is forwarded:

- The sender’s Agency Number / Debt ID becomes the Client Account Number on the receiving system

![](https://cdn.document360.io/6c7303ca-5ffc-4149-8868-8ea498eee635/Images/Documentation/Screenshot 2026-05-08 102534.png?sv=2026-02-06&spr=https&st=2026-10-31T22%3A48%3A47Z&se=2026-10-31T23%3A48%3A47Z&sr=c&sp=r&sig=vFtwI2t18JqfqGFe3Kom4%2BPoFrUENwk3RoKSZFlA2kw%3D)

Image Displays Sender Account View

![](https://cdn.document360.io/6c7303ca-5ffc-4149-8868-8ea498eee635/Images/Documentation/receiver account view.png?sv=2026-02-06&spr=https&st=2026-10-31T22%3A48%3A47Z&se=2026-10-31T23%3A48%3A47Z&sr=c&sp=r&sig=vFtwI2t18JqfqGFe3Kom4%2BPoFrUENwk3RoKSZFlA2kw%3D)

Image Displays Receiver Account View

#### Transactions

- Source → Receiver: transactions are forwarded
- Receiver → Source: transactions are sent back via callback

#### Bankruptcies and Disputes

Only verified records are synchronized.

- Verified = synced
- Unverified = local only
- Changing to unverified removes the mirrored record

## Step 6: Create a Recall Method

1. Go to Forwarding → Recall Method
2. Configure:
  1. Recall Logic
  2. Schedule
  3. Recall Status Code

## Step 7: Recall Accounts

When a recall runs:

- Accounts are identified using recall logic
- Receiver sends recall updates back to the source via callback
- Contact data may be synced back to the source before recall completes

## Step 8: Returning Accounts

ACE2ACE supports returning accounts from the receiving ACE system back to the originating (Send Vendor) agency.

When an account is returned:

- All active demographic information, including phone numbers, addresses, and email addresses, is synchronized back to the originating system.
- The forwarding relationship is updated so the account can continue to be managed by the originating agency.
- Existing account history is preserved throughout the return process.

The returned account remains associated with its original forwarding relationship, allowing ACE to maintain synchronization history while returning account ownership to the sending agency.

## ACE2ACE Action Path Triggers

ACE2ACE supports the following Action Path triggers during forwarding operations.

| Trigger | Description |
| --- | --- |
| **onAfterForwardReturnSender** | Initiated when the receiving agency cancels an account that was forwarded from the sending agency and the account is returned to the originating agency. |
| **onAfterDebtRecallSender** | Initiated when the sending agency recalls an account that was previously forwarded to another ACE system. |

## Returned Account Behavior

When an account is returned to the originating agency:

- Ownership returns to the originating (Send Vendor) agency.
- All active demographic information is synchronized automatically.
- Existing account history is preserved.
- The forwarding relationship is closed on the originating system.

## Additional Behavior

#### Re-Forwarding Accounts

- Previously recalled accounts may be reused instead of recreated
- Matching must be unambiguous
- Balances are automatically reconciled

#### Retry Processing

- Failed forwards are retried using a background job
- Real-time processing is still the primary method

#### Payment Plan Handling

- Optional setting allows recalls even if payment plans are active

#### Returning Previously Forwarded Accounts

Previously forwarded accounts can be returned to the originating ACE system without manually recreating the forwarding relationship.

ACE automatically maintains the account relationship throughout the forwarding lifecycle.

#### Demographics

When an account is forwarded or returned, ACE2ACE synchronizes all active:

- Phone numbers
- Addresses
- Email addresses

## Troubleshooting

#### Receiver-side updates not syncing

- Verify callback endpoint and API key
- Confirm expected sender customer ID

#### Transactions not mirroring

- Confirm forward link exists
- Verify vendor configuration

#### Disputes or bankruptcies not syncing

- Confirm record is marked Verified
- Verify user permissions

#### Returned Accounts Not Synchronizing

If returned accounts are not synchronizing correctly:

- Verify the ACE2ACE vendor configuration.
- Confirm callback endpoints and API keys are configured correctly.
- Verify the forwarding relationship still exists between both systems.
- Confirm both systems are using the correct vendor identifiers.

## Related Articles

- [Forwarding Bundle Preferences](https://docs.interprose.com/docs/forwarding-bundle-preferences)
- [Forwarding Distributions](https://docs.interprose.com/docs/forwarding-distributions)
- [Recall Method](https://docs.interprose.com/docs/forwarding-recall-method)