Before You Begin
Administrator access to CRM Settings
KIPU EMR already connected (green "Connected" indicator visible on the KIPU tab)
Dazos Insurance Provider picklist already contains the insurance companies you intend to map
⚠️ Note: If a company is missing from the Insurance Provider picklist, add it there before configuring mappings.
Where to Find Payor Code Mapping
Click the gear/settings icon in the top navigation bar
Choose CRM Settings
Open EMR Settings (sometimes labeled EMR Integration) in the left navigation
Select the KIPU tab
Scroll down to the "Payor Code Mapping" section
⚠️ Note: If you don't see the section, confirm you are on the KIPU tab, that the KIPU integration shows as connected, and that your user role includes administrator-level access.
Steps
Step 1 — Fetch the List of Payors from KIPU
Click the "Fetch Payors" button (green outline, circular reload icon) located just above the Payor Code Mapping table. The CRM contacts KIPU and pulls every payor configured on the KIPU side.
💡 Tip: You only need to run Fetch Payors again when payors are added or renamed in KIPU.
Step 2 — Open the Add Payor Mapping Modal
Click the "Add" button at the top-right of the Payor Code Mapping section. A modal opens with two dropdowns:
Match (EMR) — the KIPU payor side
Matching (CRM) — the Dazos insurance provider side
Step 3 — Pick the KIPU Payor
In the EMR-side dropdown, find the KIPU payor you want to map. Each option displays as "Payor Name — Internal Payor Code" to differentiate payors with similar names.
⚠️ Note: If the list is empty, go back and run Fetch Payors first.
Step 4 — Pick the Matching Dazos Insurance Provider
In the CRM-side dropdown, choose the Dazos insurance provider that corresponds to the KIPU payor selected. This is a one-to-one mapping — only one Dazos insurance provider can be mapped per KIPU payor.
Step 5 — Save the Mapping
Click Save in the modal. The mapping saves immediately and a new row appears in the Payor Code Mapping table showing:
Match (EMR) — KIPU payor on the left
Matching (CRM) — Dazos insurance provider on the right
Action buttons — Edit, Remove, Delete
Step 6 — Repeat for Each KIPU Payor Your Facility Uses
Map only the payors your facility actually bills. There is no need to map every payor that KIPU returns.
Editing, Removing, and Deleting a Mapping
Action | What It Does |
Edit (pencil icon) | Opens the modal in edit mode. Also shows the KIPU Payor Name, Internal Payor Code, and External Payor Code for reference. |
Remove (minus icon) | Soft remove — clears the CRM-side selection but keeps the KIPU payor in the list for future re-mapping |
Delete (cross icon) | Hard delete — removes the mapping row entirely. The KIPU payor can be re-mapped later by clicking Add |
⚠️ Important: Existing patient records are not retroactively updated when you add, edit, remove, or delete a mapping. Mappings take effect on the next sync of insurance data.
Refreshing the KIPU Payor List
If your billing team adds, renames, or retires payors in KIPU, click Fetch Payors again to pull the latest list. Existing mappings whose KIPU payor still exists are preserved.
Frequently Asked Questions
Q: Do I need to upload a CSV?
No. KIPU payors are pulled live from KIPU when you click Fetch Payors.
Q: Can one KIPU payor be mapped to more than one Dazos insurance provider?
No. The mapping is one-to-one. Contact support if your billing model requires a different setup.
Q: Will the system auto-match payors by name?
No. Mappings are created by an admin one by one. Fetch Payors only loads the candidate list — you still pick the Dazos side manually.
Q: What happens if I forget to map a payor?
Insurance data from KIPU for the unmapped payor cannot be automatically associated with a Dazos insurance provider. The CRM side will be left blank or marked for review until you add the mapping.
Q: Who can edit these mappings?
Only users with administrator-level access to CRM Settings. Standard CRM users do not see the Payor Code Mapping section.
Troubleshooting
EMR-side dropdown is empty when opening Add:
Click Fetch Payors first — the dropdown is populated from KIPU's payor list
If Fetch Payors does not appear, the KIPU integration may not be connected — reconnect KIPU on the same tab and try again
Fetch Payors does not appear above the table:
Confirm the KIPU integration shows as connected at the top of the KIPU tab
Confirm your user has administrator access
The Dazos insurance provider I want is not in the dropdown:
The CRM-side dropdown is populated from the Insurance Provider picklist — add the missing provider to the picklist first, then return to Payor Code Mapping
After Save, the row does not appear in the table:
Refresh the page. If the problem persists, contact support
Insurance data still arrives without a CRM provider after adding mappings:
Confirm the KIPU payor the patient is using actually has a mapping in the table
Wait until the next sync cycle — mappings affect subsequent syncs, not records already pulled
Glossary
Internal Payor Code — The identifier KIPU uses internally for a payor. Stable unless the payor record in KIPU is recreated
External Payor Code — An identifier (often a clearinghouse or industry-assigned ID) that KIPU also stores for external billing systems
Dazos Insurance Provider — An item in the CRM's Insurance Provider picklist
Fetch Payors — Action that asks KIPU for the current list of payors and refreshes the EMR-side dropdown
Related Resources
KIPU EMR Integration with Dazos CRM (Bidirectional)
How to Fix KIPU EMR Field Mapping for State and Related Contact Fields
Contact Dazos Support — reference CRM-2596