About XSuperbill Automation
PracticeSuite’s X-Superbill automation simplifies the management of large volumes of charges received through the interface by automatically running pre-existing validation rules to identify warnings or errors and thereafter processing the charges.
Initial Setup
To activate X-Superbill automation, navigate to Billing Options in Advanced Setup and select the enable option for Auto Process X-Superbill. If you need to exclude specific payers, providers, procedure codes, or modifiers from the automation process, enter that information in the designated fields within Billing Options. Use payer IDs for payers and provider codes from the Provider Master for providers. Check the box Auto-Process Charges Only if Eligibility is Verified to ensure that auto-processing of charges occurs only if a valid eligibility status response has been received through the automated eligibility checking cycle. If this option is not selected, the system processes all the charges regardless of their eligibility status.
* Use commas when there are multiple entries.
How to Run the Automation
Once the setup on the Billing Options page is complete, the following steps are to be followed: 1. Go to the X-Superbill screen under the Charges menu. 2. Click More Filters to view the complete search filters. 3. Click on the Auto Process button.
X-Superbill Automation Logic
Mode A: CMS Pricer Selected
- CCI Error Found: If any line in an encounter has a CCI error, the entire encounter is moved to the CCI_ERROR bucket. All lines are set to HOLD status.
- No CCI Errors (Internal Errors Only): If the encounter has no CCI errors but contains internal validation errors, the charge is processed and set to BILL_TO_PR.
- Warnings Only: If no errors exist but a warning is present, the entire encounter moves to the HOLD_WARNING bucket with a HOLD status.
Mode B: Internal Validation Selected
- Internal Error Found: If any line in an encounter has a validation error, the entire encounter moves to the HOLD_VALIDATION_ERROR bucket. All lines are set to HOLD status.
- Warnings Only: If no errors exist but a line has a warning, the entire encounter moves to the HOLD_WARNING bucket with a HOLD status.
*If no charges are processed, the message will show 0 charges processed.



