ACCTNO 

- PREPEND ACCOUNT NUMBER ON STATEMENTS

• Allows you to prepend the Account Number sent on Statements. This is very helpful for companies sending statements from multiple practices, making it very easy to identify which practice a Patient is calling about when they provide their account number.
• Example: By adding SMI for Dr. Smith's database, account number G10034 would go on the statement as SMIG10034.

APPLYESCROW

- AUTOAPPLY PATIENT PAYMENTS BEFORE

• If set to Apply Payments, when statements are batched the system will look for Copays & SELF-Pay Payments that are in Escrow and apply them automatically if:

• The Received Date is the same as the DOS 
• If the first Charge line is an E&M service (this logic only applies to copay payments)

• This helps prevent situations where the Patient is getting billed for Copays & SELF-Pay services when they have already paid (but the payment simply hasn't yet been applied).
• Do Not Apply (Default ---): Do not auto-apply copays or SELF-Pay payments when statements are generated

CYCLEDAYS 

- DAYS BETWEEN STATEMENT CYCLES

• This sets the number of days between Statements sent to a Guarantor.
• It allows Statements to be generated daily, preventing a Guarantor from receiving two statements in the same month.
• The System delivered value is 28 (days).
• Note: The value added here will be the default value on all Statement Profiles created.
• However, If the Cycle Days are set on the Statement Profile, it will override this setting.  
• The date of the Statement Batch Creation is used to determine how long it has been since the last Statement.

DUEDATETEXT (Coming Soon)

- CUSTOM TEXT TO PRINT ON STATMENT INSTEAD OF DUE DATE

• Enter text to print instead of the Due Date.

EXCEPTIONSBATCH

- GENERATE EXCEPTIONS BATCH WHEN BATCHING STATEMENTS

• While the goal is to streamline and automate the Statement process, there are situations that you may prefer to review, before sending the Statement. We refer to these situations as Exceptions.

• Exceptions include the existence of Escrow (unapplied funds) and/or Credit balances.

• This setting controls the ability to have the System place Statements with Exceptions into separate batches.
• The clean Statements can be sent quickly (or automatically send them using the Job Scheduler) while holding the Exceptions to review.

• Yes and (---): Split Guarantors with Escrow and/or Credit balances into an Exceptions Batch when batching statements. Note that if any patient(s) under a guarantor has an exception, all patients under that guarantor will be in the Exceptions Batch.
• No: Do not create a separate Exceptions Batch when batching statements

HASINSBAL

- HOLD STATEMENT IF ANY CHARGE LINE HAS AN INSURANCE BALANCE(L)

• Send and (---): If an Encounter has an insurance balance, INCLUDE it in the statement batch.

• The Send option works in conjunction with the STMTBAL setting below, which will determine if the insurance balances will print on statements.

• Hold: If an Encounter has an insurance balance, EXCLUDE it from statements until All lines are paid or are patient responsible.
• Hold Non-Employer Only: Encounters with a balance out to Insurance will not be included on Patient statements, but Employer invoices will be sent.

HOLD

- LIST OF HOLD STATEMENT BILLING CODES

Any Statement Profile (Admin > Statement Profile) entered in this field will do the following:

• If the Statement Profile is set on the Patient Dashboard, all Patient Encounters will be grouped together under this same Statement Batch.

Note: If the Patient's Statement is set to HLD or NBL, the Encounters are automatically grouped into Hold Statement Batch. Again, this is true regardless of the Statement Profile on the Encounter.

• Example: If a returned piece of mail is non-deliverable.

• A new Statement Profile of ND (non-deliverable) is created.
• ND is added in this Hold System Setting.
• Going forward, when returned mail is received, the Patient's Profile can be changed to Statement Profile, ND.
• ALL of the Patients Encounters will be batched into a ND Statement Batch
• When the correct address is entered into the System, and the Patient's Statement Profile is changed back to the correct Statement Profile, all the Encounters will be batched on the next Statement Run.

HOLDPRECOLLECTION

-TURNING THIS SETTING ON WILL PREVENT ANY ENCOUNTER THAT IS IN PRECOLLECTIONS FROM GETTING BATCHED(G)

• No and (---): Encounters in Pre-Collections will be Batched.
• Yes: Prevents Encounters in Pre-Collections from Batching.

INCLINSCREDIT

- INCLUDE ENCOUNTERS WITH INSURANCE CREDITS

• NO (Default and ---): Encounters that have credits out to insurance will not be included on Statements
• YES: Encounters with credits out to insurance will be included on statements

INSURNAME 

- INSURANCE NAME(L)

• Yes - Without Insurance ID: (Default and ---): Prints the Insurance Abbreviation next to Insurance payments on the statement
•  Yes - With Insurance ID: Prints the Insurance Abbreviation and the Insurance ID on the statement 
• Yes - Full Insurance Name without Insurance ID: Prints the Full Insurance Name without the Insurance ID on the statement 
• No: Does not print Insurance information next to Insurance payments and adjustments on the statement

To manage the Insurance full name or Abbreviation: Libraries > Insurances > Add/Edit an Insurance > Abbreviation/Insurance Name Fields

LIMITOPENBATCH 

- REMOVE PATIENTS WITH A RECEIPT IN AN OPEN REFERENCE BATCH FROM THE STATEMENTS BATCH

• No (and ---): Do not take into account open Reference Batches when batching statements 
• Yes: When statements are batched, if a Patient that is eligible for a statement has a Receipt in an open Reference Batch, that statement will be removed from the Statement Batch.

• This prevents a Statement from being generated where the balance could be affected by actions in an open Reference Batch.

LINEBAL 

- INCLUDE ALL PROCEDURE LINES ON PRINTED STATEMENT

• Include ALL CPT lines for each DOS on the Statement, even if they are already paid. This setting only applies to Statements you upload/outsource for processing.

• (---): By default, line items with $0 balances are not included on statements
• ALL: Include all lines for each date of service on the statement whether there is a balance on the line or not.

• By default, paid-in-full lines will not be included on Statements.

• Since the Patient Payment on fully paid lines will also not display on the Statement, the Patient may think the Payment was not received.

• If groups that charge tax on their services, this setting set to ALL also prevents a situation where the Tax line is the only line showing for a visit.

LINEORDER 

- CHANGE ORDER OF CHARGELINES ON OS STATEMENT - DEFAULT IS BY ENCOUNTER ID/LINE NUMBER

• Determines the order that Encounters (Visits) are printed on a Patient statement. This setting applies to statements you upload/outsource for processing and locally printed statements.

• Newest First and (---): Display the most recent Encounters first on the statement.
• Oldest First : Display the oldest Encounters first on the statement.

MINBALANCE

- The minimum account balance

• Enter the minimum account balance (total of all Encounters for a Guarantor) that will trigger a statement.
• Example: If the minimum account balance that will trigger a statement is five dollars, enter 5.00.

REMOVEZEROBALANCEPRECOLLECTIONS

- REMOVE ANY ZERO BALANCE ITEMS FROM PRE-COLLECTIONS WHEN STATEMENT BATCH IS RUN (L)

• This setting controls the ability to have Encounters with no balance removed from the Pre-Collections worklist when statements are batched.

• Yes and (---): Remove $0.00 balance Encounters from Pre-Collections when statements are batched
• No: Do not automatically remove $0.00 balance Encounters from the Pre-Collections worklist

SELFPAYDISCOUNT

- ALLOWS FOR A DISCOUNT PERCENTAGE TO BE APPLIED TO SELF PAY ENCOUNTERS ON THE STATEMENT

• This setting activates the ability to provide a discount % on self-pay Encounters. The % is defined on the Statement Profile (Admin > Statement Profiles > Payment Rules) when this setting is active.
• The discount can be applied to the first statement only or for all statements (defined on the Statement Profile).

• No and (---): Do not allow a discount for self-pay Encounters.
• Yes: Add the ability to define a self-pay discount to the Statement Profile screen.

SHOWINVOICEESCROW

- SHOW ESCROW ON INVOICES

• This setting will add a line on Invoices to display Escrow (money paid but not allocated to a specific Encounter/Charge). The line will display the Invoice Number for each Receipt that has Escrow and is attached to a specific Invoice. For Escrow not attached to a specific Invoice, the line amount will display as a Total.
• This setting does NOT apply to Third Party Administrators (TPAs).

• Yes: Display Escrow balances on Invoices
• No and (---): Do not display Escrow on Invoices

STATEMENTBILLING

- STATEMENT BILLING (L)

• Default Billing (and ---): Statement Profiles will be assigned to New Patients based on the Default checkbox found in Statement Profiles (Admin > Statement Profiles). This can be overridden during Registration. New Encounters will default to the Statement Profile on the Patient but can also be overridden during Charge entry.
• Provider Billing: If this option is chosen, a Provider field is added to the Statement Profile setups, allowing you to associate specific Providers to Statement Profiles. The Statement Profile used will be based on the Billing Provider on the Encounter. This option allows for separate branding by Provider.

• Each Provider would need to be included in a Statement Profile (Admin > Statement Profiles).

• Facility Billing: If this option is chosen, a Facility field is added to the Statement Profile setups, allowing you to associate Facilities to Statement Profiles. The Statement Profile used will be based on the Service Facility on the Encounter. This option allows for separate branding by Facility.

• Each Service Facility would need to be included in a Statement Profile (Admin > Statement Profiles).

 For the Provider or Facility options, if you are looking for different Statement Branding options by Provider or Facility, coordination with our statement department is necessary to complete this setup.

STMTAGING 

- HOW TO DETERMINE DUNNING MESSAGE

• Sets the method used for determining the Dunning Message for an Encounter

• Times Billed: This is the Default (---) and recommended method. The system will select a dunning message based on the number of statements already sent
• A/R: The system will determine statement dunning messages based on the age of the balance

STMTBAL

- TYPE BALANCES ON THE STATEMENT

• Patient Only (Default ---): Only include Patient Balances on Statements
• Patient and Insurance Balance: Insurance and Patient balances will be included on the statement, but only if a Patient Balance exists that meets the Minimum Balance criteria.

 While this setting controls which Encounter Balances are included on a statement, the HASINSBAL setting (above) controls whether or not Encounters with an Insurance Balance are even included on statements.

STMTCASE 

- DISPLAY ALL THE ENCOUNTERS ATTACHED TO THE SAME CASE

• Do Not Use (Default ---) Encounters will drop off the statement once they are paid in full
• Use Cases: This setting will determine that if any Encounter is printing on a Statement, ALL other Encounters linked to the same Case should also print on the Statement, regardless of their balance.

STMTDUE 

- NUMBER OF DAYS ADDED TO RUN DATE TO CALCULATE DUE DATE

• This is used to calculate the statement Due Date.
• Enter the number of days you would like added to the date the Statement batch is uploaded.

• The Default is 21 (days).

STMTNOTES 

- OUTPUT BILLING NOTES ONTO THE STATEMENT

• Yes (Default ---): Statements sent electronically will contain the most recent Billing Note with Note Type S (statement note).
• No: Billing Notes will not be output to statements

https://support.pmhelpcenter.com/portal/en/kb/articles/statements-system-settings

https://support.pmhelpcenter.com/portal/en/kb/articles/statements-category-in-system-settings

Help Center

Administration

System Settings

Statement System Setting