A pre-claim check tool that leaves care providers’ systems in place

Care records and cash flow have become one operation

Sunbound, a US company that supports senior-care operations, acquired Richter Healthcare Consultants, which has handled billing and accounting work. Sunbound said it made the acquisition after raising investment. The funding amount and post-acquisition results are company claims and need separate verification.

Together, the two companies cover work from checking a resident’s insurance eligibility through prior authorization, claim submission, denial response, collection of patient payments, and confirmation of actual payment. Sunbound said the combined companies aim to process payments worth about KRW 4 trillion annually. This is a company target, not a result already achieved. Sunbound announcement

Korean long-term care providers also cannot easily separate care delivery from cost claims. Providers submit claims monthly from the month after services are delivered. Before doing so, they must send applicable records such as provider management status, staff work status, and labor-cost expenditure details to the National Health Insurance Service (국민건강보험공단), Korea’s public health insurer.National Health Insurance Service processing standards

A claim can be rejected when required information is missing or entered incorrectly, making review difficult. If the insurer asks for supplementary documents, the provider gets an initial seven-day submission period. If nothing is submitted, the insurer may request submission again for an additional three days. Evidence documents, including contracts and service provision records, must be kept for five years from the date the benefit ends.

What is needed to receive payment, then, is not just one screen for creating claims. A provider needs to see who delivered what care and when, whether those records match the claim, what was rejected after submission, and how much was ultimately paid.

You can start without replacing every system

Consider Park, the director of a fictional home-visit care center with 18 staff members, including care workers. At this center, the billing staff member reviews visit records left by care workers, then copies service dates and times into a month-end summary file and a claims screen.

The staff member checks whether the recipient’s care grade and approval period have changed. They then compare staff hiring and departure dates, working hours, and labor-cost expenditure details. If home-visit nursing is involved, they also locate the instruction form. Completing one person’s claim can mean moving between client records, staff data, evidence folders, and the insurer’s screen.

The work remains after submission. The team confirms receipt, then reads the reason for any rejection or adjustment in the review and payment notice. It returns to the original record and corrects it. If the rejection reason is not saved in a separate file, it is hard to spot the same mistake when it happens again next month.

A new tool does not need to eliminate the insurer’s claims screen or the record software the center already uses. At month-end, it can take files containing service provision records and planned claim details, then show only the items a person needs to review: mismatched service dates, activity outside an approval period, or missing required documents. Clean items stay folded away, while items needing review appear first.

Park’s day changes a little, too. Instead of reading every file from the beginning, Park first opens cases such as “a recipient with a record but no planned claim,” “a case where staff work status and the named service provider differ,” or “a case likely to repeat last month’s rejection reason.” Recording who made a correction and where the supporting document sits means the team does not need to start searching from scratch if a problem appears after submission.

Some work does not change. A person must still judge whether care was actually delivered, whether an exceptional service meets the rules, and why a guardian’s explanation differs from the record. The tool’s job is not to decide whether a claim is eligible. Its job is to set the order for human review and reveal missing evidence.

This creates a useful reverse question. If not every provider will move to one large operations system, a small tool that finds gaps and collects rejection history between existing systems may gain a foothold faster than a company trying to replace those systems. The first promise to customers is not “everything in one place,” but “only what needs another look this month, on one screen.”

How care records and claims were connected elsewhere

Pinnacle Senior Living, which operates 47 senior living facilities across 10 US states, used PointClickCare. It started by reflecting changes in care levels recorded by frontline staff in billing information. The company case study says billed care revenue increased by 25% in the first year.PointClickCare customer story

This figure is a result reported by the vendor and its customer, not independently verified statistics. Still, it shows that finding the gap where a changed care level is not reflected in billing can itself become a standalone service.

Wesley Homes in Washington State introduced MatrixCare so its billing team could use records written during home visits. According to the vendor’s case study, record-processing time fell by 71%, time to the first claim fell by 56%, and final claim-processing time fell by 50%.MatrixCare customer story

The starting point was not adding more billing features. It was reducing late submission and re-entry of frontline records. The case suggests that improving claim speed can require improving the screen used by the person creating the record before it reaches the billing team.

There is a counterexample. New York State operated an electronic visit verification system for Medicaid care services that recorded the provider, recipient, date, location, and start and end times. But a state audit found that the share of claims matching visit-verification records was 56% for personal care and 11% for home health care.New York State audit report

Digitizing visit records alone was not enough. The flow changes only when a mismatch between a record and a claim also triggers a process that stops submission or asks a staff member to review it.

Four small things you could build

1. A month-end claim traffic light

• What it does: Compares service provision records with planned claim details and sorts omissions and mismatches into clear, needs review, and hold submission.
• Who uses it: A small home-visit care center where one office worker handles month-end claims.
• Why now: Several types of material must be submitted every month, and people already have to compare records with claims manually.
• First screen: Put one line next to each recipient’s name showing the reason to review and the location of supporting documents.

2. A rejection-reason memory book

• What it does: Groups the rejection reason in a review and payment notice, the correction made, the resubmission date, and its outcome into one case. It alerts the team when the same error appears again.
• Who uses it: An operator of long-term care providers who manages claims for several centers from one headquarters while each branch uses separate files.
• Why now: Resubmission after rejection is possible, but it is hard to identify recurring causes when the original reason and correction history are scattered.
• First screen: Group this month’s rejected cases by reason and place cases not yet resubmitted at the top.

3. A cost explainer for guardians

• What it does: Shows delivered care, the insurer’s share, the recipient’s out-of-pocket payment, and changes from the previous month in language a guardian can read.
• Who uses it: An administrator at a small or midsize elder-care facility who repeatedly explains resident cost inquiries by phone.
• Why now: The insurer can confirm whether services were actually delivered with recipients or guardians, making consistency between records and explanations important.
• First screen: Show each resident’s cost for the month, the reason it changed, and items to ask the staff member about.

4. A claim-deadline companion service

• What it does: The tool finds likely omissions, then an experienced staff member reviews the screen with the provider once a month and helps check the claim before submission.
• Who uses it: A new home-visit care center in its first year, where the owner handles both care operations and claims.
• Why now: For small providers, combining a person’s claims experience with a simple checking tool may be more practical than trying to automate every decision.
• First screen: Show the schedule remaining until the claim deadline, documents not yet received, and cases needing staff confirmation in order.

Ask one person today

Ask one long-term care provider claims staff member for 30 minutes to show you, from start to finish, last month’s claim process with personal information removed. If they copied the same date or staff information into two or more places, and if a person found even one omission or error just before submission, you have grounds to build the first screen for a month-end claim traffic light.

Why this matters where you are

Check whether your own care-claims workflow separates service records, billing data, rejection notices, and payment confirmation across different files or screens. The examples here show that the first useful product may be a review layer on top of existing systems, not a replacement for them.