When the lab invoice does not match what was delivered
Month end at a dental lab is often archaeology: reading a register, remembering what was delivered, and hoping the clinic agrees. It does not have to be.
Founder·25 August 2026·6 min read
The last three days of the month in many dental labs are spent turning a register into invoices. Someone reads back through the pages, works out what was delivered to whom, applies the rate they think applies, and sends a total.
Then the queries start, and the lab usually concedes, because proving what was delivered is harder than accepting the deduction.
Bill from the production record, not from memory
If dispatch is recorded on the case, the invoice can be generated from cases delivered in a period. Nothing is remembered, nothing is missed, and every line points at a case with a date, a patient reference and a work type.
This is the whole fix. Everything else in this article is detail hanging off it.
The revenue that leaks
None of this is theft or incompetence. It is what happens when billing is reconstructed rather than recorded.
- Cases delivered by hand and never entered anywhere.
- Additional units on a case billed as a single unit.
- Extras such as custom shade work, special articulation or rush handling, done and never charged.
- Repairs and adjustments, which feel small and add up to real money across a year.
- The wrong price list applied, usually the older and cheaper one.
Make the statement self explanatory
A clinic should be able to check a statement without calling you. Case number, patient reference, dentist, work type, units, date delivered, rate, amount. Remakes and credits shown as their own lines.
Clarity here reduces disputes far more than a follow up call, and it shortens payment time, because a statement that raises a question sits on a desk until someone has time to ask it.
Then chase receivables like a business
Labs are quietly one of the worst affected businesses for late payment, because the relationship with the clinic feels too important to press. The answer is not to press harder, it is to make the position visible and routine: an ageing report, a statement that arrives on the same day every month, and a polite reminder that is sent by the system rather than by a person who feels awkward.
Making it routine removes the emotion from it, which is exactly what these relationships need.
Where the record comes from
DLMS generates invoices from delivered cases, keeps per clinic pricing, and gives dentists their own view of cases and statements through the portal, so month end is a review rather than a reconstruction. The case level detail behind it is covered in case tracking for dental labs.
If your invoicing is an act of memory, some of your work is free. Record dispatch on the case, generate the bill from it, and month end turns into an afternoon.
Frequently asked questions
Should labs invoice per case or monthly?
Most labs work on monthly statements with the underlying cases itemised, because that suits how clinics pay. The important part is not the frequency but that every line traces to a delivered case with a date, so a query resolves in a minute instead of a meeting.
How do you handle per clinic pricing?
Store it as a price list per clinic rather than as knowledge in someone's head. Labs almost always have negotiated rates and volume arrangements, and the person who remembers them eventually goes on leave in the last week of the month.
How should remakes appear on the invoice?
Explicitly, at whatever value your policy says, including zero. Hiding a free remake makes your delivered volume look smaller and hides the cost from both sides. Showing it with a nil charge makes the goodwill visible and keeps the record honest.