Unit Match

For medical billers and revenue cycle staff

July 1 through July 31
is 31 units.
Not 30.

Unit Match is a medical billing authorization calculator. Enter the dates of service on a daily-rate authorization and it counts the covered days, then checks that count against the units the payer approved.

A daily-rate authorization covers the first date of service, the last date of service, and every day in between. Subtracting one date from the other drops the first day.

That one unit is a day of care that goes unpaid, on every affected claim. Unit Match does the inclusive count, checks it against the units approved, and shows the work.

  • Works offline
  • No account
  • No PHI collected
  • iPhone, iPad & Android
The statement it writes
The dates of service authorized, July 1, 2026 through July 31, 2026, comprise 31 covered days. The authorization reflects 30 units. One covered day falls beyond the units approved.

See what it does →

Daily-rate authorization Example
Dates of service
07/01 – 07/31/2026
Units authorized
30

July 2026

Covered day Past the units approved
31 covered days
Units required31
Units authorized30
Short by1 unit

The one-unit gap

Two ways to count a span. One of them bills short.

Both methods look reasonable on a spreadsheet, and only one of them matches what the authorization actually covers.

Counting every covered date

31

July 1 is day 1. July 31 is day 31. Every date on the authorization is a day of care, and a daily rate bills one unit for each.

Subtracting one date from the other

30

Leaves out July 1 itself. Subtraction returns the nights between two dates, which is always one fewer than the days covered.

The gap is one unit on every span, regardless of length. At a $600 per diem, a biller working forty of these authorizations a month is looking at $24,000 a month that was authorized, delivered, and never billed.

What it does

Enter two dates. Get the count, the variance, and the wording.

The day count is the product, and it stands on its own. Units are a follow-up question, and optional: leave the field empty and you simply get the number of days.

On the phone at the desk

Built to answer one question fast

Two dates in, a number out. Most checks take a few seconds, which matters when it is the fortieth authorization of the day.

Unit Match on iPhone: the first and last dates of service entered, the covered days shaded on a July calendar, and a count of 15 covered days. A shortfall: 15 covered days against 10 units authorized, with the five days past the units approved marked on the calendar with a perforated edge. The explanation panel comparing counting every covered date, which gives 15, against subtracting one date from the other, which gives 14. The About panel, noting that Unit Match is a calculation aid to verify against the authorization terms and payer rules.

Data and privacy

A calendar question needs no one’s name.

There is no field for a patient, a payer, or an authorization number, and there never will be. That is a design constraint, not a default, and everything else follows from it.

No PHI, by construction

The only inputs are two dates and two optional integers. There is nowhere to type a patient name, so no one ever does.

No network calls

The app talks to no server, ours or anyone else’s. It runs the same on a plane as it does on the floor, and behind any firewall.

No account, no tracking

The app has no sign-in, no analytics, and no advertising SDKs. Saved counts live on your device and are gone when you remove it.

Questions billers ask

Frequently asked

How many units is July 1 through July 31?

31. An authorization written from the first through the last date of service covers both of those dates and every day in between. Subtracting one date from the other returns 30 and leaves out July 1, which was still a day of care.

Why does subtracting the dates give the wrong number?

Subtracting returns the number of nights between two dates, which is always one fewer than the number of days covered. On a per-diem authorization one unit is billed per covered day, so the subtraction is short by exactly one unit on every span, no matter how long the span is.

Does Unit Match store patient information?

No. There is no field for a patient, a payer, a member number, or an authorization number, so no protected health information is collected. Saved counts hold dates and unit numbers only and stay on your device.

Does it need an internet connection?

No. The app makes no network requests at all. It works on a plane, on a locked-down workstation, and behind any firewall.

Who is it for?

Medical billers, AR follow-up, and revenue cycle staff who work daily-rate authorizations. That includes residential, PHP, and IOP behavioral health, skilled nursing, inpatient rehab, and anywhere else a payer approves a number of per-diem units against a span of dates.

Is it a medical device?

No. Unit Match is a calculation aid. It performs calendar arithmetic and a comparison, offers no clinical guidance, and makes no medical claims.

What does it cost?

Unit Match has not been released yet, so pricing is not final. What is settled either way: there is no account to create and nothing to sign in to, because the app runs entirely on your device.

Unit Match

Unit Match

Coming to the App Store and Google Play. Email us to hear when it lands.

Coming soon to theApp Store Coming soon toGoogle Play

Email support@alohagems.llc →

Unit Match is a calculation aid. Always verify the count against the authorization’s own terms and the payer’s rules before you bill or appeal.