What criteria has to be met in order for accounts to be placed with Flywire?
In order for an encounter to be loaded into Flywire’s active inventory, it must meet ALL of the following criteria:
- There should be balance at the Self Pay benefit order and the encounter balance should be greater than $0.00.
- There should be a generated statement on the encounter.
- The encounter should be assigned to the Flywire pre-collection agency.
- There should not be any billing holds on the encounter outside of the standard Pre-Collection Agency Assigned hold due to the Flywire agency assignment.
New Work Item for Reconciliation
*If you are interested in this work item, please reach out to your Client Success Rep to learn more information*
- If all criteria are met and an encounter still does not load into Flywire’s active inventory, Flywire has implemented a new process to provide visibility and follow-up directly in Cerner Patient Accounting.
- Each day after Flywire completes a data load, a return file is automatically generated and sent back to Cerner Patient Accounting.
- This return file places each encounter in a work item for additional review. The Timeline tab provides additional details explaining why the encounter did not load into Flywire.
Common Reasons:
| Reason: | Action: |
| 'Missing benefit_order_balance: Needed to get balance and link to health plan' | Check the self pay benefit order and ensure balances from all prior benefit orders are transferred to self-pay. |
| 'Missing health_plan: Needed for qualifying "self pay" | Check the self pay benefit order and ensure balances from all prior benefit orders are transferred to self-pay. |
| 'Missing bill_relation: needed for qualifying "statement first" | Check the ‘Statements’ tab and ensure a statement was generated on the encounter |
| 'Missing bill: needed for qualifying "statement first" | Check the ‘Statements’ tab and ensure a statement was generated on the encounter |
This list represents the most common reasons for why an encounter does not load, but is not comprehensive. If you see another reason listed on the timeline tab, please open a support ticket and be sure to include the following details:
- Date the encounter was returned
- Encounter #
- Reason shown on ‘Timeline’ tab
In extremely rare cases, you may see an encounter as assigned to Flywire in CPA, but that encounter will not be in Flywire or this work item. Those cases represent a more technical issue and please log an SR/Flywire support ticket for further assistance.