Reference Batch System Settings (Accordion Style)

Reference Batch System Settings (Accordion Style)

ALLOWBATCHFUNC

ALLOW ALL BATCH POSTING FUNCTIONS BY DEFAULT
Controls whether Reference Batches are created with all allowable functions selected automatically, or if the User needs to select the functions they want to be allowed within the Batch.
  1. YES (and ---): When a Batch is created, all functions (Payment Posting, Charge Posting & Patient Registration) are pre-selected.
    1. This is typically used when one Reference batch is used for the Charges and Payments.
  2. NO: Users will select the allowable functions each time a new Reference Batch is created.
    1. This is typically used when separate Reference Batches are used for Charges & Payments.

CHARGES

REFERENCE BATCH REQUIRED

- REFERENCE BATCH REQUIRED

  • Strict Mode: The User must be attached to a Reference Batch during Charge entry to save a Charge.
  • If not attached to a Reference Batch, the Charges can only be saved as Incomplete.
  • This is the recommended setting!
  • Normal Mode (and ---): Reference batches are optional

DEFAULTUNDOPOSTING

SELECT THE DEFAULT ACTION FOR UNDO/REDO POSTING
This setting allows you to control the behavior of the Undo/Redo Posting Popup when modifying a transaction in an Open Period.
  1. Default Behavior and (---): In an Open Period, the Undo Posting popup will provide options to either create a NEW Receipt for the Escrow created by the Undo Posting, or add the Escrow to the EXISTING/original Receipt.
  2. New: Always create a New Receipt for the Escrow when doing an Undo Posting
  3. Existing: Always Modify the Existing Receipt when doing an Undo Posting

    Note: When doing an Undo Posting of a Transaction in a Closed Period, the only option available will be to create a new Receipt.

 DEMO

REFERENCE BATCH REQUIRED
  • Normal Mode (and ---): Reference batches are optional for Patient Registration.
  • Strict Mode: The User must be attached to a Reference Batch to save a new Patient Registration.

DETACHINC

DO NOT ATTACH INCOMPLETE CHARGES TO A REFERENCE BATCH
This setting controls whether or not Encounters saved as Incomplete Encounters are attached to the Reference Batch of the User saving the Encounter.

The Yes/All options account for the situation where an Encounter that was already complete (and attached to a Reference Batch) and is then saved as Incomplete.

  1. No (Default): Charges saved as Incomplete are attached to the User's Reference Batch.
  2. Yes: New Incomplete Charges are NOT saved to the user's Reference Batch.
    1. A Reference Batch will be assigned when the Charge is completed.
    2. Existing Encounters that are in a Reference Batch, that are subsequently saved as Incomplete, will retain the original Reference Batch.
  3. All: New Incomplete Charges are NOT saved to the User's Reference Batch.
    1. Existing Charges that are already attached to a Reference Batch and are subsequently saved as Incomplete, will have the Reference Batch removed.
    2. A new Reference Batch will be assigned when the Charge is again saved as a completed Encounter.

ERARECEIVEDATE (Release v 4.7)

DATE USED WHEN CREATING AN ERA
This setting controls what date is used as the Received Date on Receipts created when applying ERAs.
  1. ERA Paid Date and (---): Use the ERA paid date
  2. Reference Batch Received Date: Use the Received Date on the Reference Batch.
    1. If no Received Date is entered on the Reference Batch, the ERA Paid Date will be used as the Receipt Received Date.

INCLUDE INCOMPLETE CHARGES ON REFERENCE BATCH REPORT
This setting determines whether Incomplete Charges are included on the Reference Batch report.
  1. Yes: Include Incomplete Charges on the Reference Batch Details report
  2. No and (---): Do not include Incomplete Charges on the report

NEEDSELECTRONICALLYPROCESSED

DISPLAY A CHECKBOX ON REFERENCE BATCH SCREEN TO SPECIFY IF THE RECEIPTS NEED TO BE ELECTRONICALLY PROCESSED

This only applies if a merchant service integration is in place. If you are not using an integrated credit card processor, this setting will not have an effect.


This controls the visibility of the Process Electronically checkbox on the Receipt and Reference Batch screens.
  • It is only needed if not all credit card payments are processed through the integrated credit card service.
  • When it is unchecked, the System bypasses the Credit Card Processor Integration.

  This setting controls the visibility of the Process Electronically option at the PRACTICE level.

  • A System Permission can be used to determine visibility at the USER level.
  • (Admin > User Maintenance > User > System Permissions > Payments > Receipts > Process Electronically Checkbox)
  • Options:
  • Receipt Only (and ---): Display the Process Electronically checkbox on Receipts.
  • This will allow it to be controlled by any user that has the permission to do so.

  • Don't Display: The Process Electronically checkbox is never displayed, therefore cannot be deselected.
  • Ref Batch & Receipt: Checkbox displays on both the Reference Batch screen and Receipt screen.
  • The selection or deselection of the Process Electronically checkbox in the Reference Batch determines the default value for all new Receipts created in that Batch.
  • The checkbox can be selected or deselected as needed on the Receipt.

Use Case: This is useful for creating Reference Batches for users processing credit cards through the credit card integration vs. Reference Batches where card transactions are entered that have already been processed outside the System.

PAYMENTS

REFERENCE BATCH REQUIRED
  • Strict Mode: Must be attached to a Reference Batch to Post Payments.
  • This is the recommended setting!
  • Normal Mode (and ---): Reference Batches are optional for Payment Posting.

    • Related Articles

    • Add/Modify a Reference Batch

      On the Reference Batch List screen, you can add or modify a Reference Batch. Add a Reference Batch From the Reference Batch List page, select Add to create a new Reference Batch. The Batch Status defaults to Opened. Add a Description for the items to ...

    • Daily Charges Report

      The Daily Charges Report is a detailed breakdown of each Patient's Charges for a day or a date range. This report can be run at the end of the day to capture your Charges, or it can be run for a different period to report Charges and Payments for the ...

    • Undo a Posted Payment or an Adjustment

      Undo a Posted Payment or an Adjustment The System has an Undo Posting feature on the Encounter Dashboard where you can manage incorrectly posted Payments and Adjustments. Undo can be used to correct the posting on a Receipt. Example: A payment was ...

    • Reconcile Reference Batch Receipts

      Reconcile Reference Batch Receipts Reference Batches can be used to reconcile your receipts. Compare the Receipts column with the Payments column. The Receipts column represents the amount that was entered when the receipt was created, and the ...

    • Charges System Settings

      Charges ACCIDENTONCASE - ENFORCE ACCIDENT IS ALWAYS ON A CASE Mandatory: Always require an Accident on new Cases, for ALL Case Types. Not Mandatory (and ---): Cases will not require an Accident on the Case. Note that it rarely makes sense to set this ...