The Recon tab of Organization Configuration provides configuration of Recon related settings.

Figure 219 - Organization Configuration Recon

Figure 220 - Organization Configuration Recon

Recon Settings

Generate Recon for

This checklist controls all the recon files that should be generated. This is largely controlled by the configured MIDs on the Payments tab. If you have a Credit/Debit, Insurance, Subscription or ACH MID configured, these will be checked by default. ACH Reject, ACH Refunds, Lockbox and Cash are optional.

Format

The Format drop-down lets you choose which field layout to use for the file to match the customer’s requirements. These report formats are added to the backend by PatientPay staff. You are required to choose a format before saving.

Lookback Days

The Lookback Days numeric up/down lets you choose how many days to look back for transactions that are included on the Recon. Given the different funding SLAs for each transaction type, this is important so that Recon doesn’t exclude transactions that don’t get recorded as funded until a few days later by the processor. Generally, we look back 1 day for captured/settled and 2 days for funded.

Transaction Status to Include

This controls the types of transactions to include for the Credit/Debit and Insurance recons. Captured means that we have simply performed an auth/capture on the card. Funded means we’ve confirmed with the payment processor that funds have been deposited in the bank account.

Batch Cutoff Time

This controls the cutoff time for the end of day batch, after which any transactions will fall to the next day. This value should be entered in 24-hour time. This must be coordinated with the payment processor. The default for CardConnect is 9:30PM EST therefore the default value is 21:30.

Format

This controls the file format to use for the recon file(s). 

• Delimited (default): Creates a delimited text file using the specified delimiter and header record configuration.
   
• EDI 835: Creates an X.12 EDI 835 standard document containing payment transaction data. Please consult with your PatientPay account manager if your facility needs a custom 835 mapping/format.
   
• JSON: Creates a configurable JSON (JavaScript Object Notation) text-based file to the customer for posting back to their system of record. Please consult with your PatientPay account manager if your facility needs a custom JSON mapping/format.

Include Header Record

This configuration applies to Delimited file format and determines whether the first row in the file represents the header record.

Delivery Method

This controls how we deliver the Recon file to the partner.

• None: Does not deliver a Recon file. Partners are still able to use the Recon Report in Admin to view transaction data, download the file based on the format configured above, and reconcile their payments.
   
• Email: Delivers the file as an attachment to an email using the comma-delimited list of recipients specified in the Email Distribution List field.
   
• SFTP (default): Delivers the file to the partner via SFTP using the S3 URL specified in the Drop Folder field.
   
• AthenaHealth: Delivers the transaction data using our athenaHealth API integration.
   
• AzaleaHealth: Delivers the transaction data using our Azalea Health API integration. This can be configured to send payments/refunds in real-time as they occur in PatientPay to provide up-to-date bill balances in the system of record.
   
• PointClickCare: Delivers the transaction data using our PointClickCare API integration.

Include Now Transactions

This controls whether the Recon file for Credit/Debit includes Now transactions. We will still include these transactions in the Recon Report in Admin – just not in the file.

Include Now Insurance Transactions

This controls whether the Recon file for Credit/Debit includes Insurance transactions. We will still include these transactions in the Recon Report in Admin – just not in the file. If using a separate MID for insurance payments, you can easily just uncheck this recon type.