Stop Digging Through Reports: Meet Penny, Your Plain-English Assistant for Claims and Payments

A look at Penny, the assistant inside Fincura that turns “did this get paid yet?” into a one-line answer instead of a ten-minute search.

It’s Monday morning and a patient calls asking why they’re getting a bill. Your first move is to figure out what actually happened with that claim: was it paid, was it adjusted, did the insurance company shortchange you, or is Fincura still working on it.

Before you can answer the patient, you have to answer that for yourself. And that usually means logging into Claims, filtering by name, opening the claim, flipping over to Remittances to find the EOB, checking whether the deposit landed, and squinting at a code like CO-45 to remember whether that’s a write-off or a denial.

That’s five minutes you don’t have, multiplied by every claim someone asks about that day.

Fincura already automated the hard part of this problem: pulling in the remittance, matching it to the deposit, and posting it into your practice software. What we hadn’t fixed yet was the looking up part — the part where you, a human, still have to go find the answer inside all that data. That’s what Penny is for.

The problem isn’t posting. It’s finding.

Automated posting solved the labor-intensive part of payment processing. Fincura pulls the ERA, matches it to the bank deposit, and pushes the payment into Dentrix, Eaglesoft, Open Dental, eClinicalWorks, or whatever you run — often without anyone touching it.

But that automation created a new kind of task: the lookup. Someone still has to answer “has this been paid,” “did the deposit clear,” or “why was this claim adjusted.” Those questions used to get answered by manually working the claim. Now they get answered by manually searching for a claim that’s already been worked. Progress, but still a scavenger hunt: open Claims, apply filters, cross-reference Remittances, check the bank feed, open the claim detail, decode the adjustment code, confirm the posting status.

None of that work is hard. It’s just slow, and it happens dozens of times a week, for every biller, in every practice.

What Penny actually is

Penny is the assistant inside your Fincura portal that answers questions about your practice’s own claims, remittances, and deposits — in plain English, using the data Fincura already has because it already ingested the ERA, matched the deposit, and attempted the post.

You’ve likely already met her. She’s the same “Penny @ Fincura” who signs your daily summary emails and walks you through onboarding. Chat is Penny showing up inside the portal itself, with access to your practice’s live payment data — not a general knowledge assistant, and not a separate tool you have to learn. You type a question the way you’d ask a coworker, and she looks up the real record and tells you what it says.

She’s read-only. She can’t post a payment, change a claim, or take any action in your practice software. That’s not a limitation we’re apologizing for — it’s the point. A billing office doesn’t want an assistant that can quietly change something in the system of record. It wants one that can find things fast and get out of the way.

She also only ever sees your practice’s data. If your team has location-restricted logins, she respects that too — someone who only has access to one site won’t see claims from another.

Three ways operators actually use her

Here’s what that looks like in practice. These are the same kinds of questions the product’s own empty-state suggests when you open Chat for the first time.

”When was EOB payment 000111222 deposited into the bank account?”

This is the “did the money actually show up” question, and normally it means leaving Claims entirely to go check the bank feed.

You: When was EOB payment 000111222 deposited?

Penny: That remittance deposited on 3/12 for $4,180.00 via ACH. It’s reconciled. Of the 14 claims on it, 12 are posted and 2 still need a look.

She’s not guessing at this — she looked up the actual bank deposit tied to that payment reference and read back what’s there: date, amount, method, reconciliation status, and a rollup of what happened to the claims on it. If you needed to see those two unfinished claims, you’d ask, and she’d hand you a table, not a paragraph.

”Has the payment for claim 123456789 been received in the bank account yet?”

This is a single-claim question, and it’s where the claim detail card does the work instead of a wall of text.

You: Has claim 123456789 been paid?

Penny drops in a claim card, right in the conversation: patient Jane Smith, Delta Dental, service date 2/14, billed $1,240.00, paid $890.00, patient responsibility $110.00. Posting status: posted. Bank reconciliation: reconciled, matched to a $890.00 deposit on 2/28. Service lines show D2740 with a CO-45 adjustment.

Penny: Yep — Delta paid this one and it’s already posted. The $240 difference is a contracted write-off (CO-45), not a denial, so there’s nothing to appeal.

Notice what she doesn’t do: she doesn’t repeat the numbers that are already sitting on the card in front of you. She adds the one sentence of meaning the card can’t say for itself — that CO-45 is a write-off, not money you’re owed. If you want the full claim, the claim number on the card is a live link straight into Fincura.

”Can you show me all partially paid claims from the last week?”

This is the “show me a set” question, and it’s where a lot of billing time actually goes — building a worklist by hand.

You: Show me everything partially paid this week.

Penny returns an interactive table right in the thread: patient, payer, status, service date, billed, paid, patient responsibility, reconciled, posted — one row per claim, with a total count at the top. Click any row and she pulls that claim’s full card into the same conversation, so you never lose your place in the list.

Penny: Found 9 partially paid claims this week. Three are from Delta Dental, and two of those are still waiting on bank reconciliation.

That’s a worklist built in one question instead of a filtered report you’d have exported and read line by line.

What she’s careful about

A few things by design, because a billing assistant that guesses is worse than no assistant at all.

Write-offs and denials aren’t the same thing, and she’ll say which is which. CO codes are contractual write-offs — the amount your fee schedule already agreed you wouldn’t collect. PR codes are the patient’s share. Mixing those up is how a biller ends up chasing an appeal that was never owed, or missing a patient balance that is. Penny names the difference every time it’s relevant.

“Still working” isn’t the same as “you need to do something.” If a claim is waiting on bank reconciliation, or hasn’t posted yet with no error attached, that’s Fincura’s automation still running — not a task sitting in your queue. Penny will say so instead of implying you’re behind. If a posting actually failed, she’ll point you to Inbox or the claim itself, where the fix belongs, rather than walking you through steps inside your practice software.

She doesn’t make numbers up. If a claim number, a total, or a dollar figure isn’t in your Fincura data, she says she can’t find it. No invented claim IDs, no estimated totals dressed up as real ones. When she gives you a count — like “9 partially paid claims” — that number came from an actual search of your records, not a guess.

She stays in her lane. Ask her to draft an appeal letter, call a payer, or answer something that has nothing to do with your claims and payments, and she’ll tell you plainly that’s not something she does, rather than attempting it badly.

Where she lives

Chat sits right next to your regular Fincura portal view — a Portal / Chat toggle, not a separate app to learn. Conversations save as threads, grouped by Today and Earlier, so a question you asked last week is still there if you need to reference it. Start a new thread, rename one, delete one — it works the way you’d expect a conversation to work.

The composer just says: Ask about your claims, remittances, or reconciliation… That’s a fair description of the whole feature. It’s not a general chatbot bolted onto the product. It’s the fastest way to ask the system that already processed your payments a question about what it did.

Why this only works because of what Fincura already does

It’s worth saying plainly: a generic AI chatbot can’t do any of this. It doesn’t have your ERA files, it hasn’t matched your deposits, and it has no idea whether your practice software accepted a posting or rejected it. Penny can answer these questions only because Fincura already ran that pipeline — collected the remittance, matched it to the bank, attempted the post, and logged what happened at every step.

Penny isn’t a new layer of automation stacked on top of the old one. She’s how you ask the automation you already have a question, instead of opening four screens to answer it yourself.

Try it

If you’re already on Fincura, open the portal and switch to Chat. Ask it something real — an EOB you’re waiting on, a claim a patient called about, a list of everything underpaid this week — and see what comes back.

If you’re not on Fincura yet and you’re tired of your team hunting for answers that already exist somewhere in a report, schedule a demo and we’ll show you Penny working against real claims data, not a slide deck.