Payment files overview
Payment files streamline the process of making multiple payments by consolidating payment instructions into a single file. This document provides you an overview of how Optum Connections processes payment files.
Payment files can be submitted to Optum Connections in any of the following file types; 835, 028+, or as a custom file.
The payment processing workflow begins with the submission of the payment file to the ECG. You can think of this as the communication gateway to the entire process. The ECG forwards the file to an Azure Storage Queue. From the Azure Storage Queue, the file is parsed and bulk loaded into a database, where it is recorded and organized into payment batches.
Once the payment batches are created, the payments are processed, and payment IDs are generated and stored in the database. At this stage, all payment records are updated with the latest issuing payment IDs or issuing reference IDs. This updated information is then returned to the Azure Storage Queue, which notifies the ECG that the payments have been settled. Finally, the payments are triggered and closed out. This is a high level summary of the end to end process. Refer to Sending payment files for a more detailed look.
Payment file types
Optum Connections handles 835s, 028+ files, and custom files, but regardless of the file type, all files are submitted through the ECG.
Updated 9 months ago