The audit letter arrives. You export the answer.
Audit builds your defense file while the work happens, not after the letter lands. Every claim keeps its documentation attached from day one, so a two-hundred-claim request becomes an afternoon, not three weeks of archaeology.
Nothing in the left-hand column is missing. It is just scattered.
| When | Without the archive | With it |
|---|---|---|
| Day 1 | The letter arrives. Two hundred claims, thirty days, documentation required per claim. | The letter arrives. You paste the claim list into a new case. |
| Day 2 to 5 | Someone starts pulling hardcopies, signature logs and prior auths from paper files and three systems. | The package assembles from the archive. What is missing is listed, per claim, as a short worklist. |
| Day 6 to 20 | The pharmacy still has to open every morning. Progress happens in the gaps between prescriptions. | The worklist is worked. Most of it is documents that were never uploaded, not documents that never existed. |
| Day 21 to 29 | Assembly, photocopying, reconciliation against the letter, and a check that nothing is missing. | Nothing. It has been ready since day six. |
| Day 30 | Sent, with a reasonable fear that something was missed. | Sent. The record of what was sent, and when, is itself in the archive. |
Audits are only painful because the evidence is scattered.
The PBM wants two hundred claims with hardcopies, signature logs, prior auths and purchase invoices, inside a deadline, while the pharmacy still has to open every morning. None of that material is missing. It is just spread across paper files, fax confirmations and three different systems, and reassembling it under pressure is what eats the three weeks.
Evidence you can edit is not evidence. It is a claim.
Append-only at the grant level
The application role holds no UPDATE and no DELETE permission on the archive. Not a policy that says we do not edit it. A permission that means we cannot, including us, including under pressure.
Written before interpretation
The exact bytes are stored before any code reads them, with the time, the principal, the source address and a content hash. What you can produce is what arrived, not what we decided it meant.
Assembled before the question
Documentation binds to its claim on the day it happens. Evidence gathered after a letter arrives invites an argument about when it was gathered. Evidence that predates the question ends one.
Audit, in practice.
Evidence that files itself
Every event is archived exactly as it arrived, immutably, and every document binds to its claim on the day it happens. The defense file exists before anyone asks for it.
Response packages on demand
Paste the claim list from the letter. Get back an organized package, documentation attached per claim, ready to send.
Problems found before the auditor finds them
Continuous checks against what audits actually test. A missing signature is a task this week, not a recoupment next quarter.
Every audit run as a case
Deadlines, correspondence, evidence and owner in one workspace. Nothing rides on one person remembering a date.
A record that stands up
The archive cannot be edited after the fact, by anyone, including us. Evidence assembled from records that predate the audit question is evidence that ends arguments.
Already connected? Audit was a switch, not a project.
Every product runs on the same event spine. Turning one on starts it working on data that is already flowing, which is why there is no second onboarding and no second integration bill.
See Audit on your own data.
Thirty minutes. We connect one facility read-only, replay your recent events, and show you what Audit finds. Your numbers, not a demo dataset, and credentials you can revoke when we are done.