Ascend Posting Warnings and Failures (Epic)

Last updated: October 7, 2026

Direct Bill Automation

This guide covers:

  • Common warnings and errors when posting from Ascend to Epic

  • How to resolve billing, Producer/Broker commission, and accounting period issues

  • How Ascend handles multi-term commission schedules

  • Which posting checks can be configured for your agency

Overview

Ascend integrates directly with Applied Epic and allows you to post matched entries as a suspended Direct Bill statement in Epic.

Before posting, Ascend checks that the policy and commission setup meet your agency’s requirements. Epic also applies its own posting requirements. If either system identifies an issue, you may need to update the policy in Epic or the accounting period in Ascend before retrying.

Use this guide to understand common warnings and errors, find the steps to resolve them, and know when to contact Ascend Support.

Before You Begin

  1. Review the warning or error in Ascend.

  2. Find the matching issue below.

  3. Confirm the correct setup with your Epic administrator before changing billing or commission information.

  4. Make the correction, then retry the affected posting in Ascend.

Producer/Broker (Pr/Br) refers to the producer and broker records associated with a policy in Epic. Some checks depend on your agency’s Ascend configuration.

Billing Setup

1. The Payer Is Not a Billing Company

Why this happens

The policy’s payer is either incorrect or is not designated as a Billing Company in Epic.

How to resolve it

  1. Confirm that the policy is linked to the correct payer in Epic.

  2. If the payer is correct, update its record so Billing Company = TRUE.

2. Send Invoice To Is Broker, but the Policy Has No BREC Commission

Why this happens

On the policy’s Billing tab, Send Invoice To is set to Broker, but the policy only has BPAY or PPAY commissions. Broker-billed policies require a BREC commission.

How to resolve it

Confirm how the policy should be billed:

  • If the policy should be billed to the client: Change Send Invoice To to Client.

  • If the policy should be billed to the broker: Have your Epic administrator review and correct the BREC commission setup.

3. Send Invoice To Is Client, but the Commission Type Is Unsupported

Why this happens

On the policy’s Billing tab, Send Invoice To is set to Client, but the policy has a BREC commission or another unsupported commission type. Client-billed policies require BPAY or PPAY commissions.

How to resolve it

If the policy should be billed to the client:

  1. Remove the BREC or unsupported commission record.

  2. Add the appropriate BPAY or PPAY commission.

If the policy should be billed to the broker, have your Epic administrator review the billing and commission setup together.

4. Your Agency Restricts BREC Commissions

Why this happens

Your agency has enabled an Ascend check that flags policies with BREC commissions, even if Epic would otherwise allow the posting.

How to resolve it

Have your Epic administrator review the policy and remove the BREC commissions if they should not be used.

If BREC commissions are intentional, contact Ascend Support to review your agency’s configuration.

Producer/Broker Commissions

5. The Pr/Br Commission Split Does Not Total 100%

Why this happens

The commission percentages across the policy’s Pr/Br records do not add up to 100%.

How to resolve it

  1. Review the Pr/Br records on the policy in Epic.

  2. Correct the percentages so they total 100%.

A single producer assigned 100% passes this check.

6. The Policy Has No Pr/Br Record

Why this happens

Ascend checks for at least one Pr/Br record when posting. If none exists, the posting fails to prevent commission from being left unassigned.

How to resolve it

  1. Add the appropriate Pr/Br record or records to the policy in Epic.

  2. Set the commission percentages so they total 100%.

  3. Retry the posting in Ascend.

7. A BPAY Record Uses a Numeric Commission Type

Why this happens

The Pr/Br code is BPAY, but the commission type is numeric, such as #. If your agency has enabled this check, Ascend flags the record.

How to resolve it

Have your Epic administrator confirm the required commission type for BPAY and update the Pr/Br record accordingly.

If the existing setup is intentional, contact Ascend Support to review whether this check should apply to your agency.

8. The Share Revenue Code Is Invalid

Why this happens

The share revenue code on the Pr/Br record is not a valid primary agency code for that producer.

How to resolve it

Update the share revenue code in Epic to a valid primary agency code for the producer.

9. A BPAY Record Is Missing a Contract ID

Why this happens

A BPAY Pr/Br record has no payable contract attached. The warning or error references a Contract ID.

How to resolve it

  • If your agency uses payable contracts: Attach the correct contract to the BPAY Pr/Br record in Epic.

  • If your agency does not use payable contracts: Contact Ascend Support to enable the setting that skips this check.

  • If you are unsure: Confirm your agency’s requirements with your Epic administrator.

Contract IDs and commission agreements are separate checks. Ascend’s Contract ID check does not evaluate the Use Commission Agreement field. If that field is enabled without an agreement selected, Epic may reject the posting based on your Epic setup. Skipping the Contract ID check does not bypass Epic’s commission agreement requirements.

Accounting Periods

10. The Accounting Month Is Closed in Epic

Why this happens

Ascend attempts to post to the accounting period assigned to the transaction in Ascend. If that period is closed in Epic, the posting fails.

How to resolve it

Confirm the appropriate open accounting period with your accounting team, update the period in Ascend, and retry the posting.

Multi-Term Commission Schedules

11. Ascend Cannot Select a Multi-Term Commission Schedule

What a multi-term schedule does

A policy in Epic can have multiple Pr/Br commission schedules, each with its own effective and expiration dates. These schedules determine which producer and broker commissions apply for a given date.

When multi-term posting is enabled, Ascend must identify exactly one schedule that covers the date used by your agency’s configuration.

Why this happens

Posting fails when:

  • The policy uses multi-term schedules, but multi-term posting is disabled for your agency.

  • No schedule covers the date Ascend uses.

  • More than one schedule covers that date.

For example, a schedule may have ended before the applicable date, or two schedules without expiration dates may both appear active.

How to resolve it

  1. Confirm which multi-term option your agency uses. The options are listed below.

  2. Open the policy’s multi-term commission schedules on the Pr/Br tab in Epic.

  3. Review the effective and expiration dates. Exactly one schedule must cover the date Ascend uses.

  4. Correct any relevant gaps or overlaps and confirm that the applicable schedule has the correct Pr/Br commissions.

  5. Retry the posting in Ascend.

If the policy should not use multi-term schedules, reach out to the Servicing team to update the policy configuration.

How Ascend Selects a Schedule

Configuration

Date Ascend uses

When it may be appropriate

Off (default)

Ascend flags policies with multi-term schedules and does not post their entries.

Your agency does not intend to use multi-term schedules.

Policy effective date

The policy effective date.

The applicable commission schedule is based on the policy’s start date.

Transaction date

The statement transaction date. If unavailable, Ascend uses the payment date, then the posting date.

Commission splits change during a policy term.

Transaction date, with effective date fallback

The same date sequence as Transaction date. If the resulting date is before the policy effective date, Ascend uses the policy effective date.

Statements sometimes include dates earlier than the policy’s start date.

Contact Ascend Support to confirm or change your agency’s configuration.

Agency Configuration Options

Ascend Support can review the following settings with your agency:

Setting

What it controls

Restrict BREC commissions

Flags policies that contain BREC commissions.

BPAY commission type check

Flags BPAY Pr/Br records with a numeric commission type.

Skip the Contract ID check

Allows BPAY Pr/Br records without a payable contract to post. Available for Epic Direct Bill posting.

Multi-term commission schedules

Controls whether multi-term posting is enabled and which date Ascend uses to select a schedule.

These settings adjust Ascend’s checks. Epic may still reject a posting if its requirements are not met.

Need Help?

Contact [email protected].