30-min call with RobBook a proof-of-concept call
Job 01 · Billing desk

// Commercial laundries · Invoice checks

Linen delivery tickets and invoices, checked against the contract for your billing desk.

Before an invoice goes out, someone at your plant should be able to say that the tickets, the weights or counts and the written contract all agree. A free AI proof of concept compares copies of 20 to 30 invoices your office already sent, unit by unit and item by item, and lists every difference it finds. Your reviewer, whoever in billing knows these contracts best, checks each list against what your team actually did.

Book a proof-of-concept call30 minutes with Rob
Closed invoices
20 to 30
Invoices adjusted
None
Patient information read
None

// The one job

From a day's tickets to a list billing can act on

A linen account leaves a trail of small papers: soil pickup records or bag counts, delivery tickets by unit or department, the plant's weights or pack counts, any loss or replacement notes, and behind them the customer's written contract and its billing basis. Your billing desk ties those together, works out what each line should be under that contract, and sends the invoice.

For the test, AI reads copies of those papers and drafts a comparison for each invoice: by unit and department, the item type, the count or weight as written on the ticket, the par level where the contract gives one, the billing basis the contract states, and any loss or replacement language that bears on a line. Whatever doesn't agree goes on a list for a person in billing. Nothing is adjusted or sent, and your reviewer holds every list up against the invoice your desk issued.

Delivery ticketClean linen out
Unit or dept.
Delivered
Bags or carts
Contract
ItemCount or weightPar
Invented ticket, for illustration only
Compared with
the contract
Invoice checkDraft
Billing basis
Contract clause
Invoice no.
Open items
LineTicket against billDifference
Made-up check, for illustration only

// What makes it hard

Where a linen invoice and its paperwork part ways

One load gets counted three ways. Rhode Island's 2019 request for Eleanor Slater Hospital shows it plainly. The vendor's receipt records bags collected and bundles of each item delivered, and the request sets those bundles: bath towels in fifteens, face cloths in fifties, pillow cases in twenty-fives, patient gowns in sixteens, flat sheets in tens, and fitted sheets in fours to sixes. The billing statement then lists pickup dates and times, the weights picked up, a price per pound of clean laundry and the total charged. Receipts talk in bags and bundles while the bill talks in pounds, so the draft shows each number in the unit it was written and converts nothing unless your contract says how.

Soil weight and clean weight aren't the same number. The University of New Mexico Hospitals' 2017 cost form priced launder and deliver clean linen and soiled pickup as separate lines per pound. HLAC's standards have customer owned goods operations document clean pounds shipped against soil pounds received, and rental operations document fill rates instead. The Association for Linen Management defines a soiled-to-clean ratio per account, and a 2007 American Laundry News article described hospitals recording both weights on a simple daily form, partly to confirm the bill. HLAC also wants load scales calibrated by an outside auditor at least yearly, with the result available to a customer who asks. Each draft line names which weight it rests on, and a weight with no source goes on the list.

Who owns the linen decides who pays when it goes missing. In the Rhode Island request the hospital owns the linen, the vendor replaces anything ruined at its plant or in transit, and the hospital pays for replacement due to staining and normal wear, with soil replacement cost priced on a line of its own. UNM's request made the contractor answer for lost or damaged new linen in its care, to be replaced with the same brand and quality, and sent packing lists and freight bills to UNM for validation against purchase orders. New linen handling there carried monthly charges for receiving and storage. The draft quotes the contract's loss or replacement sentence beside any such charge and leaves the answer to billing.

Par lives at the closet. HLAC says provider and customer set the par level together, and the Association for Linen Management describes a par as the linen used in a 24-hour period, but contracts write it their own way. UNM wanted par level inventories managed at the storage location, nursing unit and clinic level. Its pickup schedule ran by building, floor, department and closet: inpatient units three times a day, every day, most clinics once a day on weekdays, and one cancer center split into five lines by floor and room. A ticket that just says Cancer Center can't be matched to a line like that, so it goes on the list with the lines it might belong to.

What your reviewer will watch. Did each line use the billing basis in the contract in force on that date, signed and dated? Did every unit on a ticket map to a real billing location? Was a make-up delivery billed correctly? Rhode Island, for one, wanted a delayed or partial delivery made up the same or next calendar day, and that can leave two tickets for one scheduled drop. Did the list leave alone every charge the contract allows? A person in billing decides what happens with each difference.

// What you send

Invoices your billing desk already closed

Copies only
No patient information
01

20 to 30 closed invoices

Invoices already sent, from several customers and more than one billing basis. Include one a customer disputed, one with a make-up delivery and one your team corrected before it went out.

02

The tickets behind them

Delivery tickets, soil or bag counts, weight records and any loss or replacement notes for those invoices, as photos, scans or exports.

03

Each customer's contract

The written agreement in force on those dates, with amendments, rate sheets, par lists and any replacement schedule. A contract that can't leave the building gets rebuilt as a look-alike with your reviewer.

04

Copies, free of patient information

Once the NDA is signed, send copies with nothing about a patient on them. Nobody from Massmarket logs in to your plant system, your billing system or a customer's portal.

// Before it starts

Settled before the first ticket is copied

Your owner puts each of these in writing while the paperwork is still in your office.

Terms for the invoice checkSet by the owner
Your reviewer
The owner's pick: often the billing manager, or whoever releases customer invoices
Success criteria
In writing: which differences must be caught and which charges must be left alone
Customers
Your reviewer's choice, across hospital, clinic, hotel and restaurant accounts as you have them
Who decides
A person in billing, on every difference
Price
A range for the live run, quoted before any ticket is copied
NDA
Signed before a single copy moves

// How the test is judged

What your team did beside each list

Invoice by invoice
line by line
Across the same 20 to 30 invoicesWhat your team didList from the test
Unit and department on each line, matched to a billing locationFilled in on your invoicesFilled in on your invoices
Item type as the contract names itFilled in on your invoicesFilled in on your invoices
Count or weight as written on the ticketFilled in on your invoicesFilled in on your invoices
Billing basis the contract states for that itemFilled in on your invoicesFilled in on your invoices
Par level, where the contract gives oneFilled in on your invoicesFilled in on your invoices
Loss or replacement language quoted beside any such chargeFilled in on your invoicesFilled in on your invoices
Differences listed, with the ticket and clause behind eachFilled in on your invoicesFilled in on your invoices
Blank today. These cells stay empty until your own closed invoices have gone through.Your reviewer scores each line and gives the verdict.

// After a yes

About a month on new invoices

With your reviewer's approval, new invoices get the same comparison for about 30 days before billing releases them.

A person in billing resolves every difference and approves each invoice, which then reaches the customer the way it does today.

The comparison carries on against live work. A next job is a separate decision with its own price.

// Possible next jobs

What could follow the invoice check

Ranked, not promised
Separate prices
  1. 01

    Healthcare linen audit files

    The plant records a healthcare customer or accreditor asks for, gathered with every gap listed for your plant manager.

    Next
  2. 02

    Usage and par reports

    Delivered pounds and pieces by unit, clinic or property, set beside each location's par for your account manager.

    Then
  3. 03

    Hospital linen bid packages

    A buyer's linen request cut down to one sheet of billing units, service days and accreditations named.

    After that

// One hard limit

Every difference goes to a person in billing.

The proof of concept never touches your plant system, a billing system or a live invoice, and it never reads patient information. It never adjusts, credits, voids or sends an invoice, never contacts a customer and never decides who owes what under a contract. Sample documents must be free of patient information. It works only on copies, and nothing it lists is legal advice. A person in billing resolves every difference.

Priced per job. You get a range before the proof of concept and a fixed price before you sign.

Rob gives the range on the call once he knows how many customer contracts you bill under, how many invoices you send in a month and how many ticket formats come back from your routes.

// Questions

Invoice check questions

Our contracts bill some accounts by the pound and others by the piece. Is that a problem?
It is the reason to test this. Each line is read against the billing basis that customer's contract states, and the draft shows the count or weight in the unit it was written, so a pound-based line and a piece-based line aren't forced into one format.
Can it read handwritten delivery tickets and driver notes?
Include them, since a fair test has the tickets your routes really produce. Where a count or a unit can't be read, the draft says so instead of guessing, and that ticket goes on the list for your reviewer.
Does it need our customer contracts?
Yes. The written contract is what every line gets compared with: its billing basis, par terms and loss or replacement language. An account whose terms aren't on paper can stay in the sample, but its lines will be flagged rather than checked.
Will it adjust an invoice or issue a credit?
No. It only lists differences, with the ticket and contract clause behind each one. A person in billing decides what to do about them, and the test never touches a live invoice.
Do you need access to our linen tracking or billing system?
No. Exports and copies are enough, and nobody from Massmarket logs in to a plant system, billing system or customer portal. If the test passes, how the check fits your system gets worked out before a live run.
Could any patient information end up on these documents?
Sample documents must be free of patient information, so your team checks each one before it moves. A loss note, a returned-belongings slip or anything else carrying a patient's details gets blacked out or left out, and the test never reads patient information.
Rob Eason

Rob Eason, founder

// Book a proof of concept call

Start with one customer's closed invoices.

Rob's call takes 30 minutes: your plants, your role, the customers you'd put in the sample and roughly how many invoices you send in a month. Hold on to the tickets and contracts until an NDA covers them.

  • Co-owned a 60-employee financial services firm and sold his share to his partner.
  • Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
  • 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
  • 4.3/5 from 6 Google reviews of Massmarket AI.
  • Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
  • Takes every proof-of-concept call himself.