Fincura

Fincura's core is structured matching: it ingests ERA 835 files, pairs each payment with the open claim through the claim identifiers the 835 carries, posts it to the practice system and confirms it against the bank deposit. That work runs on the remittance's own structure.

The AI is Penny, an assistant inside the portal that answers questions about claims, remittances and deposits in plain English from the practice's own records, returning claim cards and tables rather than paragraphs. It saves billers time on lookups, while posting and reconciliation run on the structured matching alone.

Posting runs on its own and stops where it cannot match. Unmatched remittances go to review, and a posting the practice system rejects shows up in the Inbox or on the claim itself, where the fix is made. Penny is read only by design: it looks up claims, remittances and deposits but cannot post a payment, change a claim or act in the practice software, and it respects logins restricted to one location.

The rule for sending a match to review is not published, and neither is how a payment posted to the wrong claim is caught.

Two pieces are described. The reconciliation engine links ERA 835 records to claims through their claim identifiers and to bank deposits, and Penny reads the practice's own records to answer questions, showing claim cards that link back to the record and tables for lists of claims.

The model behind Penny, its provider and how it is updated are not named, and the company's description of itself as AI native comes with no technical detail.

Fincura's privacy policy refers to third party vendors for hosting, data processing and other essential services, and to integration partners such as practice systems and banks. Penny's answers draw on claims, remittance and bank data.

None of those vendors, nor the model service behind Penny, is named.

The numbers are Fincura's own: payments 20 days faster, 40 staff hours a month saved, no revenue lost and claims posted at 100 a second. Its one customer quote, from a 30 location general dentistry group handling more than $100 million a month in reconciliation volume, reports payment 20 business days sooner and 10 hours a week of data entry saved.

None of the figures comes with a named customer, a baseline or a period.

Data is encrypted in transit and at rest, and access is limited by role. Fincura keeps information as long as needed to run the service and meet legal duties, then deletes it; after termination, data stays retrievable for a reasonable period before secure deletion. The terms license customer data to Fincura to provide and improve the service.

Whether practice data trains any model, including the one behind Penny, is not said, and neither is how data is de identified or what happens to Penny's conversations, which are saved as threads. Safety engineering for Penny goes no further than its read only scope.

Fincura states that it executes business associate agreements with all customers, and its terms commit it to sign one wherever the service handles protected health information. The privacy policy covers the service itself, including data pulled from practice systems and payer portals.

The agreement is sent on request rather than published, so its subcontractor and breach terms cannot be read before contracting.

SOC 2 is in progress, with no report or trust center yet. The privacy policy describes encryption in transit and at rest, role based access, and regular security audits and penetration testing, without saying who performs them or how often.

Fincura holds bank account access for reconciliation and logins to payer portals, so those credentials sit inside its security program.

Payment posting, reconciliation and EFT enrollment are financial operations, and Fincura makes no medical device claim. Penny answers questions about claims and payments only and declines anything else, such as drafting appeals or calling payers.

The terms disclaim responsibility for the accuracy of third party systems, including practice software, clearinghouses and payer portals.

Penny's limits are design choices Fincura spells out: it sees only the practice's own data, stays within location restricted logins, tells contractual write offs from denials and patient responsibility, says when it cannot find a figure instead of inventing one, and refuses tasks outside claims and payments.

How well it keeps to those limits is not measured publicly. No testing of Penny's answers or of the matching engine's accuracy is published.

Practices can follow every payment from remittance to posting to deposit in Fincura's logs, Penny's claim cards link straight to the record, and failed postings surface for correction. Penny reports that it cannot find a figure rather than estimating one.

The terms leave the risk with the practice. The service is provided as is, with no warranty that it is error free, liability is capped at the fees paid in the prior 12 months, and no correction commitment or remedy for a wrong posting is published.

Payments post into the practice system, and the systems are named: Dentrix, Dentrix Ascend, Eaglesoft, Open Dental, Denticon, Curve Hero, Dolphin, Cloud9, OrthoTrac and PracticeWorks on the dental side, and eClinicalWorks, NextGen, athenahealth and ModMed on the medical side, out of more than 400 Fincura says it supports. It also connects to banks such as Chase, Bank of America and Wells Fargo, and offers a public API.

No integration documentation or marketplace listing is published, and production use is not tied to a named practice system.

Delivery is a hosted web application connected to the practice management system, the practice's bank accounts and payer portals, with setup quoted at five minutes per practice. The company and its contracts sit in Colorado, and the service is sold to US practices.

The third party providers that host and process its data, and where they store it, are not named.

The price is on the site: $250 a month plus $2 per claim posted, discounts for high claim volume, a $1,000 one time implementation fee and no long term contract. It covers ERA processing, EFT enrollment, posting, bank reconciliation, the payer analytics dashboard, API access and multi location support, and the fee follows claims posted rather than dollars collected.

A savings calculator sets that against a practice's card processing fees, which it puts at 1 to 3 percent through processors such as Zelis and Echo, and its staff time on posting. Starting still runs through a demo, and the terms allow price changes on 30 days' notice.

Its customers are dental practices, single office or multi location, with DSOs supported by NPI and tax ID, and its integration list reaches medical practices on eClinicalWorks, NextGen, athenahealth and ModMed; one blog post addresses ambulatory surgery centers. Fincura says more than 100 providers use it.

Its one customer quote comes from a 30 location general dentistry group that is not named.