vareo

Product documentation

How Vareo works from the first call to the first recovered dollar. Release notes are on the changelog, and the terms used here are defined in the glossary.

Getting started

Vareo audits every payer remittance your practice receives against your payer contracts, flags the lines that were paid below what the contract says, and recovers the difference. There is nothing to install and no change to your billing system or vendor: Vareo works from the remittance data you already receive, alongside your current billing team or RCM company.

  1. 1
    Book an audit call
    A 30-minute call to confirm fit: specialty, payer mix, and how your remittances arrive. Book one from the scheduling page.
  2. 2
    Sign the BAA
    Vareo is a HIPAA business associate. A Business Associate Agreement is signed before any protected health information is exchanged. Your account cannot receive files until it is in place.
  3. 3
    Connect your data
    Point your clearinghouse at Vareo’s SFTP server or upload files in the app (see Connecting your 835 feed), and upload your payer contracts (see Uploading contracts).
  4. 4
    Free 90-day audit
    Vareo reviews your last 90 days of remittances against your contracts and shows every underpayment it finds, by payer and by type, before you commit to anything. If a full audit finds nothing actionable, you owe nothing.
  5. 5
    Recovery
    From then on, every new remittance is priced as it arrives. Vareo drafts and files disputes, tracks payer responses and follows up until each claim is resolved. Pricing is a contingency fee on money payers actually pay back; see pricing.

Connecting your 835 feed

Vareo reads X12 835 electronic remittance advice (ERA) files, the same files your billing system posts payments from. Three ways to get them to Vareo:

  • Clearinghouse SFTP (recommended). Clearinghouses such as Waystar, Availity and Office Ally can deliver a copy of each 835 to a Vareo SFTP server. Vareo issues your practice its own SFTP username and password, scoped to a folder only your practice can see. You enter those credentials in the clearinghouse’s delivery form; Vareo provides the host, port (22), username, password and path.
  • Upload in the app. Dashboard → Uploads accepts 835 files, 837 claim files and CSV payment exports from your practice-management system.
  • API. Billing companies and integrators can push files programmatically with a scoped API key (Dashboard → Settings → API keys) and poll parse status and findings.

For the SFTP feed, use the /daily path for the recurring feed and /historical for the initial backfill. If the clearinghouse form takes only one path, use /daily: Vareo picks up files from anywhere in your folder. Each file is identified by its content, so an 837 dropped in the remits folder is still handled as a claim file. New files are picked up within 15 minutes, de-duplicated, parsed, and moved to a processed folder.

Sending 837 claim files alongside the 835s is optional but recommended: it lets Vareo match each remittance line back to the claim as it was actually submitted, including modifiers and units.

Vareo verifies the first test file with you end to end before the recurring feed is turned on.

Uploading contracts

Findings are only as good as the contract they are priced against, so Vareo reads your actual payer agreements rather than assuming a rate.

  • Upload at Dashboard → Contracts. Accepted formats: PDF, Word (.doc, .docx) and scanned images (.png, .jpg, .tif). Include the fee schedule exhibits and any amendments; a contract that references “the current Medicare fee schedule” is enough when that is how the payer prices.
  • Vareo extracts the pricing terms (rate basis, percentage of a reference schedule, flat schedules, site-of-service and modifier rules, effective dates) into structured rules, each with a citation to the page it came from.
  • Each extracted term is marked Read, awaiting Vareo review until a Vareo reviewer approves it, then Approved by a Vareo reviewer. Only approved terms price claims, so an extraction error cannot create a finding.
  • Contract review in the dashboard shows what each contract carries, which terms are used in disputes, and when a referenced Medicare schedule is about to change.

If a payer pays you without a written contract on file, tell us: those lines are reported as a data gap, not as underpayments, until the terms are known.

Reading findings

A finding is one remittance line (or a group of lines on one claim) that the payer paid for less than the contract owed. Every line is priced, not a sample.

  • Expected vs. paid. Each finding shows the contracted rate Vareo applied, the amount the payer allowed, the amount paid, and the variance, with the date of service and payment date.
  • Verified vs. estimated. A verified finding is priced from an approved contract term and the payer’s own remittance shows the shortfall; these are the dollars reported on your dashboard and the ones Vareo disputes. An estimated finding uses a reference rate because the contract term is not yet known; it is shown only behind an explicit filter and is never disputed as is.
  • Types. Fee-schedule errors, allowed-amount mismatches, modifier downcoding (for example a bilateral procedure paid at the unilateral rate), incorrect bundling, unit and multiple-procedure reductions, and secondary-payer or coordination-of-benefits errors. Lines reduced under a payer’s payment-policy adjustment (CO-150) are never counted as underpayments.
  • Patterns. When the same payer underpays the same code the same way across many claims, Vareo groups the findings into a pattern so they can be disputed together.
  • Status. Findings move from new to reviewed, appealed or dismissed. When a practice’s results need a second look, a banner says the results are held for Vareo review until they are released.

Market Rates is different from a finding: it compares what each payer pays you with the rates the same payer publishes for practices nearby. That gap is not disputable; it is leverage for your next contract negotiation.

Disputes workflow

You do not send anything yourself. Vareo prepares, files and tracks every dispute; your team sees the status in the dashboard.

  1. 1
    Bundle
    Verified findings are grouped by payer and issue into a reconsideration packet: a cover letter, the contract language with page citations, the remittance evidence, and a claim-by-claim schedule. Payers that require their own form get it filled per claim.
  2. 2
    Review
    Every packet goes through a Vareo review queue. A reviewer approves, holds or regenerates it; nothing is transmitted to a payer without that approval, and each filing records who approved it.
  3. 3
    File
    Packets are sent the way the payer accepts them: fax, the payer’s provider portal, or an API where the payer offers one. A corrected claim is used only when the original claim itself was wrong. Deadlines follow each payer’s dispute window; packets close to a deadline are flagged urgent.
  4. 4
    Track
    Statuses run from letter generated to submitted, awaiting response, and then approved, partially approved or denied. What was sent is the record; a sent packet is never modified afterward.
  5. 5
    Recover
    Incoming 835s are reconciled against open disputes so payments are matched to the claims they settle. Quiet disputes escalate: a re-fax, then a follow-up call. Payer outcomes are recorded so Vareo learns which packet types each payer pays on.

Recovered dollars are invoiced monthly at the contingency rate. Money that is not recovered is never billed.

Security and HIPAA posture

  • HIPAA. Vareo is a business associate and signs a BAA with every client before any PHI is exchanged.
  • SOC 2 Type II. In progress; controls are monitored continuously and audited by an independent firm. Current status and reports are in the Trust Center.
  • Hosted on AWS in the United States under AWS’s BAA. Application servers and databases run in private networks; file storage blocks all public access.
  • Data is encrypted in transit with TLS 1.2 or higher and at rest with AES-256 keys managed in AWS KMS.
  • Each client has its own SFTP credential, scoped to that client’s folder. Each organization sees only its own data in the app.
  • Databases and files are backed up and replicated to a second AWS region for disaster recovery.
  • Access to production systems and PHI is limited by least privilege and reviewed quarterly; multi-factor authentication is required on identity, cloud, source-code and administrative systems.
  • Audit logging, threat detection, dependency and container scanning, and a documented incident response plan including client notification as required by HIPAA and our BAAs.

The full summary is on the Security page, including how to report a vulnerability.

Support