Navigate to Claims → Import Claims. Drag and drop your CSV or Excel file. ReconX automatically maps your columns — it recognizes "Claim No", "CLM#", "Claim ID", and dozens of other header variants.

3

Upload a remittance

Go to Remittances → Upload Remittance. Drop your payer's remittance advice file. Set the payer name and payment date. Click Upload & Reconcile.

4

Review results

Navigate to Matching Engine. Every claim is now matched against the remittance with a confidence score. Green = matched exactly. Amber = partial. Red = unmatched or exception.

5

Resolve exceptions

Open Exceptions & Variances to review any discrepancies. Add a resolution note and mark each exception as resolved. Export your reconciliation report to PDF or Excel.

Importing Claims

ReconX accepts any CSV, Excel (XLSX/XLS), or ODS file for claim imports. No special template is required.

💡

Smart column detection recognizes over 50 alternative header names. Whether your file uses "Claim No", "CLM#", "Claim ID", or "Claim Number" — ReconX maps it automatically.

Required columns

Field	Recognized header variants
claim_number	Claim #, Claim No, CLM#, Claim ID, claim_id
submission_date	Submission Date, Submit Date, Date Submitted, Claim Date
billed_amount	Billed Amount, Charged Amount, Total Billed, Claim Amount
payer_name	Payer, Insurance, Insurer, Payor, Payer Name

Optional columns

patient_name patient_id provider_name service_date paid_amount allowed_amount status denial_reason procedure_code diagnosis_code reference_number

ℹ

Import size limit: 20 MB per file. For larger files, split into multiple batches or contact support for bulk data migration assistance.

📄 Download Claims CSV Template

Matching Engine

The ReconX matching engine uses a multi-criteria scoring system to match claims to remittances. Each match is assigned a confidence score from 0–100%.

Criterion	Weight	Notes
Claim number (exact)	100 pts	Triggers exact match — no further scoring needed
Billed amount match	35 pts	Exact or within 5% tolerance
Patient name match	25 pts	Fuzzy match using string similarity (≥90% = full score)
Payer name match	20 pts	Case-insensitive exact match
Service/payment date	10 pts	Within 30-day window = full; within 90 days = partial
Reference number partial	10 pts	Last 6 digits of reference number match

≥ 85%

Matched

Records are considered matched. No exception is raised.

65–84%

Partial Match

Match is accepted but flagged for review. Variance is calculated.

< 65%

Unmatched

No match found. Record becomes an open exception.

Duplicate Detection

The duplicate engine runs automatically after every batch upload. It checks for two types of duplicates:

Duplicate Claims

Two claims with the same claim number, patient, amount, and service date — regardless of whether they were imported in the same batch or months apart.

Duplicate Payments

A single claim that has been paid more than once — detects overpayment across multiple remittance batches from the same or different payers.

Security Model

🔒

Data Encryption

All data encrypted at rest (AES-256) and in transit (TLS 1.3). Uploaded files stored in AWS S3 with server-side encryption.

🏢

Tenant Isolation

Every query is scoped to your organization_id. There is no shared database — your data is completely isolated from all other organizations.

👤

Role-Based Access

Five roles: Super Admin, Admin, Manager, Analyst, Viewer. Each role has granular read/write permissions across all modules.

🔑

API Security

HMAC-SHA256 signed tokens with 1-hour TTL. Per-key rate limits, IP allowlisting, and environment separation (sandbox vs production).

📋

Audit Trail

Every user action — logins, imports, changes, exports, API calls — is logged immutably with timestamp, user, IP, and before/after values.

🔐

Two-Factor Auth

2FA via TOTP (Google Authenticator compatible). Admins can enforce 2FA for all users in Settings → Security.

Need help?

Our support team responds within 24 hours (4 hours for Professional and Enterprise).

Contact Support API Reference