All resources

Applied Epic

Applied Epic Accounting: Common Reconciliation Problems and How to Fix Them

Independence note NJTS provides independent consulting and administrative support. It is not an Applied Systems partner or reseller and is not affiliated with or certified by Applied Systems. Menu names and features vary by Applied Epic version and configuration. Confirm procedures against your version’s help documentation.

Applied Epic connects policy, billing and general ledger activity in one system, but that does not mean the accounting reconciles itself. Differences still appear between detail reports and the general ledger, between carrier statements and expected commission, and between what the system shows and what actually happened. Most of them come from a small number of patterns: how entries were made, when reports were run, how the agency structure is set up, and whether month-end steps happen in the right order.

Why integrated systems still need reconciliation

In Epic, most general ledger activity is generated from transactions: invoices, receipts, disbursements, commission statements. That integration is a strength, but it means the ledger reflects whatever was entered, including:

  • receipts applied to the wrong account;
  • statements entered twice;
  • manual journal entries that bypass the transaction detail;
  • reports run before the month’s posting was complete.

Reconciliation is how the agency proves the detail, the ledger and outside evidence (bank statements, carrier statements) agree.

1. Premium payables don’t balance to the general ledger

What it looks like: the agency’s premium payable detail and the general ledger premium payable balance disagree at month-end.

Where to start: Applied’s month-end guidance describes running the Balancing Premium Payables report by agency for the month being closed, and comparing its grand total with the general ledger premium payables balance. If they differ, common causes include:

  • a manual journal entry posted to the premium payable account without a matching transaction;
  • the report run for a different agency, or before all activity was posted;
  • payables recorded under the wrong insurer or agency;
  • items reopened or reversed after the report was run.

Illustrative Example | Fictional Data The agency, figures and events below are fictional and are included only to illustrate the method.

The Balancing Premium Payables grand total is $286,450, and the general ledger shows $289,150. The $2,700 difference breaks down as follows:

  • $2,000 from a manual journal entry posted directly to the premium payable account in a prior month;
  • $700 of payables belonging to a second agency in the same database, included in the ledger balance but not in a report run for one agency.

The second item disappears when both are scoped the same. The first needs the entry corrected through the transaction workflow.

2. Direct Bill commissions sit in suspense or don’t match

What it looks like: downloaded or imported Direct Bill commissions waiting in suspense, statements that won’t finalize, or receipts that don’t match statements.

Common causes:

  • Downloaded items waiting in Suspense. Applied documents that Direct Bill Commission Download transactions are placed in Suspense, where the system attempts to match them to existing policies. Items it cannot match stay unassigned until someone assigns and updates them, for example when the renewal has not yet been entered in Epic.
  • Duplicate entry of the same statement or receipt, by both download and manual entry.
  • Statement scope: one carrier payment covering several statements or agency codes. Treating the receipt as one statement creates false differences.
  • Rate differences between the commission expected on the policy and the carrier’s actual rate.

How to fix:

  • Assign ownership of the suspense queue, with a defined frequency.
  • Look for existing entries before entering a statement manually.
  • Match receipts to their component statements.
  • Resolve rate differences by checking the carrier agreement, not by forcing the expected amount to match.

Be careful with finalized statements. Applied documents that reopening a finalized statement can also reopen other statements tied to the same master statement number. Reopening should be a reviewed decision. The diagnostic sequence is covered in Direct Bill Reconciliation.

3. Receivables, unapplied cash and credit balances

What it looks like: client receivables that look overdue while cash sits unapplied; credit balances netted inside receivables; aged reports that don’t match the ledger.

Common causes:

  • receipts posted to an account but not applied to the invoice;
  • partial payments;
  • return premiums recorded as credits;
  • receipts recorded to the wrong client or agency.

Mistakes at receipt entry are costly, because correcting a receipt is more involved than entering it.

How to fix:

  • Review unapplied cash and credit balances as separate lists each month.
  • Apply or research every item with an owner.
  • Clean up receivables before month-end. Applied’s own month-end checklist recommends cleaning receivables several days before month-end.
  • In New Jersey, return premium owed to an insured has specific timing and notice requirements (N.J.A.C. 11:17C-2.2(b)).

4. Producer and broker payables

What it looks like: producer/broker payables that don’t agree with what producers believe they are owed, or balances that never clear.

Where to start: compare the producer/broker payables aging with the ledger and with the commission calculations. Where Epic is configured to reconcile producer or broker payables, it provides aged and balancing producer/broker payable reports that help identify differences in what is owed. Check two things:

  • that commission agreements configured in Epic match the signed producer plans;
  • how producer commissions are set up, keeping three things separate: when producer commission expense is recognized in the accounting (where the agency’s set-up supports it, Epic can defer it so the expense is recognized in the month an item is invoiced rather than the month it is paid); when the commission becomes payable to the producer under the producer’s payable basis; and when the producer is actually paid in the agency’s payment run.

Configuration that doesn’t match the agreement produces payables that are “correct” in the system and wrong in substance. Producer Commissions: Splits, Chargebacks and Controls covers the controls.

5. Structure and allocation set-up

What it looks like: reports by branch, department or profit center that don’t make sense; revenue landing in the wrong department; allocations that change unexpectedly.

Why it matters:

  • Epic organizes accounting by an agency structure of agency, branch, department and profit center.
  • Departments and profit centers are tied to income statement accounts.
  • Allocation methods spread shared general ledger amounts across the structure, for example by head count or by a percentage entered for each structural entity. A structure grouping can only be paired with an allocation method that has an exact match for every structural combination in the grouping, so changes to the structure and to allocation methods need to be reviewed together.

How to fix:

  • Document the intended structure and the reports owners actually use.
  • Review structure and allocation configuration against that design.
  • Correct errors going forward through a controlled change, with administrative access limited and changes logged.

6. Month-end steps out of order

What it looks like: reports that change after they were reviewed; month-end entries missing from reports; months that can’t be closed.

What Applied describes:

  • Locking the accounting month being closed, to prevent further entries.
  • Generating month-end journal entries before closing.
  • Running reports after closing, because reports run before the month is closed won’t include the recurring month-end entries.
  • Where the agency uses interagency revenue sharing, Epic generates interagency month-end journal entries, and a month with interagency activity must be closed for all associated agencies together. Applied’s documented order is to lock the month for every agency involved, generate journal entries for all of them, run reports to verify the figures, and then close the month for all agencies. Reopening or finalizing such a month likewise applies to all the associated agencies.

How to fix: write the agency’s Epic month-end sequence into the close calendar, with an owner for each step, and include the reconciliations from Sections 1–5 before the month is closed.

Reconcile, then fix the cause

For every recurring difference, ask three questions:

  • Where did it start?
  • What evidence supports the correct answer?
  • What stops it recurring?

Correcting the balance without changing the cause, whether that is entry habits, configuration, report timing or ownership, means doing the same reconciliation again next month.

How NJTS helps

NJTS works with agencies on Applied Epic accounting workflows: reconciliation clean-up, month-end process design, troubleshooting, and system administration and configuration support for accounting-related settings, as part of insurance agency accounting and accounting operations engagements.

Describe the Epic reconciliation that won’t balance. No system access or confidential records are needed for the initial inquiry.

Discuss an Applied Epic issue