ACE2ACE Forwarding

What is ACE2ACE Forwarding?

ACE2ACE Forwarding allows accounts to be sent from one ACE system to another and remain continuously synchronized.

ACE2ACE Forwarding:

• Sends accounts between ACE systems using API communication

• Maintains a linked record between source and receiver

• Supports real-time updates (transactions, disputes, bankruptcies)

• Uses callbacks to send data back to the source 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

  • Share API key via Secret Manager: How to Use secret.interprose.com

How ACE2ACE Forwarding Works

1. Accounts are selected using a distribution

2. Accounts are sent to the receiving ACE system

3. A forward link is created between both systems

4. Data is synchronized through real-time updates

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

Vendor Field Descriptions

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

Receive Vendor Field Descriptions

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.

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.

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 an account is forwarded:

1. Source selects the account

2. Account is sent to the receiver

3. The account is created under the receivers configured client

4. The accounts are linked

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

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

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

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

Related Articles

• Forwarding Bundle Preferences

• Forwarding Distributions

• Recall Method