Can Your Staff Change or Delete Entries in Your Dental Software Without a Trail?
If someone on your team can change a payment after the fact and nothing records that it changed, your ledger is not a record of what happened. It is a record of what the last person to touch it wanted it to say.
The question owners rarely ask until it is too late
Most dental practice owners assume their practice management system is a permanent record. Money comes in, it gets posted, and the ledger reflects reality. The assumption feels safe because the software is where all the numbers live.
The question worth asking, and the one most owners never ask until something goes wrong, is this: can a member of my staff go back and change or delete a payment, an adjustment, or a write-off after it was entered, and if they do, does anything record that the change happened?
For many practices, the uncomfortable answer is that entries can be modified retroactively, and depending on the system and how it is configured, the trail of that modification may be weak, buried, or effectively absent. That gap is where a great deal of embezzlement lives.
Why retroactive editing is the mechanism, not the exception
Embezzlement in a dental practice is rarely a dramatic act. It is almost always a two-step move: take the money, then make the record agree with its absence.
The second step is the retroactive edit. A payment is collected and pocketed, and then the entry is adjusted, reversed, or deleted so the patient's balance settles and nothing looks outstanding. A deposit is skimmed, and the posted amount is quietly changed to match what was actually banked. In each case, the theft only stays hidden because the record could be altered after the fact to cover it.
This is why the ability to retroactively edit, combined with a weak audit trail, is not a minor software preference. It is the single feature that determines whether the most common form of dental fraud is detectable or invisible. Our guide to adjustment audits covers the specific patterns these edits leave.
What an audit trail should actually do
A real audit trail does more than log that something changed. It should record what the value was before, what it became, who made the change, and when, and it should do so in a way that the person making the change cannot themselves edit or delete.
That last condition is the one that matters most and is most often missing. An audit log that the same user can turn off, clear, or overwrite is not an audit log. It is a courtesy. The entire value of the trail is that it sits outside the control of the person whose actions it records, which is the same principle of independence that governs every other financial control. Our guide to separation of duties and least-privilege access covers why that independence is the whole point.
Immutability is the word for the property you actually want. A previously reconciled or closed entry that gets changed should trigger a recomputation and a notification automatically, so that a retroactive edit to a settled period is not something you have to go looking for. It comes to you.
What you can do inside your practice management system
The specifics vary by system, but the general levers are consistent across Dentrix, Open Dental, Eaglesoft, and the cloud platforms.
Restrict permissions so that only a small, senior group can delete transactions, reverse payments, or post large adjustments. Most staff do not need those abilities to do their jobs, and removing them removes the mechanism. Require a documented reason for adjustments so that the exceptions can be reviewed rather than trusted. Turn on and protect whatever audit logging the system offers, and confirm that ordinary users cannot disable it. And review the change and adjustment reports on a regular schedule, because a trail nobody reads protects nothing.
These steps reduce the exposure, but they share a limitation worth being honest about: they all live inside the same system whose records are the thing being manipulated. Which leads to the real answer.
The check that sits outside the system
The only way to know with certainty that your ledger reflects reality is to compare it against a record that your staff cannot edit at all. That record is your bank.
No matter how an entry was changed inside the practice management system, the money that actually reached your bank account is fixed, and nobody in the office can alter it. Comparing what your ledger says you collected against what your bank actually received is what surfaces a retroactive edit that covered a theft, because the edit changed the ledger but could not change the deposit. The gap between them is the finding. Our guide to what actually catches embezzlement covers why this independent comparison is the mechanism that works when internal controls reach their limit.
Internal permissions and audit logs make the record harder to manipulate. An independent comparison against the bank is what tells you whether it was manipulated anyway. A practice that wants real assurance needs both.
Frequently Asked Questions
Can staff delete or change payments in dental practice management software?
In many systems, yes, entries can be modified or deleted retroactively, and depending on the system and its configuration, the record of that change may be weak or effectively absent. This varies by platform and permission settings, which is why it is worth confirming for your own system.
Why does retroactive editing matter for fraud?
Because embezzlement usually works in two steps: take the money, then alter the record so its absence is not visible. The retroactive edit is that second step. Without the ability to change entries after the fact, most schemes cannot stay hidden.
What makes an audit trail trustworthy?
It should record the before value, the after value, who changed it, and when, and it must be immutable, meaning the person making the change cannot edit or delete the log itself. An audit log that ordinary users can disable or clear provides little protection.
How do I stop staff from altering records?
Restrict deletion, reversal, and large-adjustment permissions to a small senior group, require documented reasons for adjustments, protect the audit log from being disabled, and review change reports regularly. These reduce exposure but still live inside the system being manipulated.
How can I be certain my ledger is accurate?
Compare it against a record your staff cannot edit: your bank. The money that reached your account is fixed, so comparing deposited amounts against what the ledger reports collected reveals any retroactive edit that covered a discrepancy, because the edit changed the ledger but not the deposit.
Zeldent compares your ledger against your actual bank deposits every day and re-checks any previously reconciled entry that changes, so a retroactive edit does not stay hidden. It is the independent record your staff cannot alter. Book a demo to see what your audit trail is not showing you.
