Posting Company Payables to Applied Epic

Last updated: August 19, 2026

Overview

When Ascend processes a carrier payout, it can automatically post a company payable statement directly into Applied Epic on your behalf. This eliminates the need to manually enter the disbursement in Epic.

This article explains how that process works and provides step-by-step instructions for resolving every error that can occur.

How it works

When a company payable is ready to post, Ascend:

  1. Logs into Applied Epic with a dedicated Epic user account, using the credentials stored in your Ascend integration settings.

  2. Creates a company payable statement in Epic, associating it with the relevant PPE

  3. Applies each transaction from the payout to the payable statement.

  4. Finalizes the disbursement, moving the statement out of suspense and posting it to your accounting records.

If any step fails, Ascend will surface an error to help troubleshoot the issue.

Resolving posting errors

When payables posting fails, you will see a banner message. Click view details will take you to a screen with more information.

CleanShot 2026-08-07 at 08.56.40.png

Types of posting errors

Invalid payable entity

What it means

Epic requires all transactions in a single statement to belong to the same PPE. Posting failed due to mismatched transaction PPEs when attempting to create the payable statement.

How to fix it

  1. One or more payables in the batch will show an error. Click on a row to open the drawer.

  2. View the linked AMS Transactions in Ascend and review the PPEs assigned to each transaction in the payout.

  3. Correct the PPE assignment in Applied Epic for the mismatched transaction.

  4. Return to the reconciliation screen and retry.

Note: Do not use the Retry button until the carrier data is corrected in Epic. Retrying before fixing the root cause will produce the same error.

Payable amount mismatch

What it means

Posting failed due to a mismatch between payable transaction balances across platforms, most frequently caused due to some transactions being partially reconciled in applied epic.

How to fix it

  1. In Epic, reconcile the remaining transactions in the statement manually.

  2. In Ascend, select Skip Posting to mark the payout as manually posted.

Transaction(s) already reconciled

What it means

Posting failed due to one or more transactions having already been reconciled as part of a different company payable in Epic.

How to fix it

  1. In Epic, reconcile the remaining transactions in the statement manually.

  2. In Ascend, select Skip Posting to mark the payout as manually posted.

Locked accounting month

What it means

Posting failed because the target accounting month is already locked or closed.

How to fix it

Option A — Reopen the accounting month:

  1. In Applied Epic, navigate to Accounting > Accounting Periods.

  2. Find the month shown in the error and reopen it.

  3. Return to Ascend and retry.

Option B — Post manually:

  1. If reopening the period isn't possible, post the company payable manually in Applied Epic.

  2. In Ascend, select Skip Posting to mark the payout as manually posted.

Payable statement already exists in suspense

What it means

Applied Epic only allows one statement per PPE in suspense at a time. A previous statement is still sitting in suspense and must be resolved first.

How to fix it

  1. In Applied Epic, go to Company Payables and find the existing suspended (draft) statement for the same recipient.

  2. Either finalize that statement or delete it.

  3. Return to Ascend and retry.

Account locked

What it means

The Epic account used by the Ascend is locked. An Epic administrator must unlock the Ascend account in Epic before this statement can post.

How to fix it

  1. Have an Applied Epic administrator navigate to the user account used by the Ascend Payables Bot and unlock it.

  2. Return to Ascend and retry.

Password expiring

What it means

Your organization has a mandatory password rotation policy in Epic, and the password Ascend is using is about to expire (or has expired). Epic is blocking login until the password is changed.

How to fix it

  1. Log into Applied Epic and change the password for the account Ascend uses to integrate.

  2. In Ascend, go to Settings > Integrations > Applied Epic and update the stored credentials with the new password.

  3. Return to the reconciliation screen and retry.

Multi-factor authentication required

What it means

Epic is prompting for multi-factor authentication (MFA), which Ascend's automated login cannot complete.

How to fix it

  1. Try retrying the posting — this sometimes resolves temporary MFA failures.

  2. Update the MFA credentials in Settings > Integrations > Applied Epic and retry.

  3. If it fails again, contact Ascend support. This may require adjusting the Epic account configuration to allow automated login without MFA.

Login failed

What it means

Ascend's login attempt failed for a reason not covered by the more specific errors above — for example, the Epic website failed to load during the attempt.

How to fix it

  1. Retry the posting — this is often a temporary issue.

  2. If it fails repeatedly, contact Ascend support.

Unposted cash receipts

What it means

Cash receipts must be posted before payables.

How to fix it

  1. Select View all unposted receipts

  2. A modal window will appear with a list of unposted cash receipts

  3. Click on the Customer name to jump to the unposted receipt

  4. After posting, the company payable should be ready to post.

Unable to post the payable statement

What it means

Payable statement creation and finalization failed. This may be a transient issue.

How to fix it

  1. Retry, if the issue persists, contact Ascend support.