Review the source and the amount type
Review a Supio Case Ledger with a fictional bill-and-credit example, duplicate checks and a source trail that keeps balances separate from payoff terms.
Supio describes Case Ledger as a way to organize medical-bill charges, adjustments, payments and balances by facility. Its published controls include links to source documents, editable entries, duplicate visibility, and manual merge or unmerge actions. These are vendor descriptions, not results from a VerifyMD product test. Use the controls demonstrated in your own account to answer two questions: did the document information transfer correctly, and does the chosen total answer the question your team is asking?
Prepare one account before reviewing the total
Start with one hospital or billing entity, account and service-date range. A facility name alone may not identify the obligation: a hospital and a separately billing physician can appear in the same treatment packet. Decide whether you are checking original charges, adjustments, posted payments or a stated outstanding balance. Use the itemized bill versus balance statement guide when the team is comparing documents that answer different questions.
Prepare a small, approved evaluation packet with the original files and a simple expected-result sheet. For a demonstration, use fictional information. Mark the source date, covered account and location of each amount. Keep an unreadable or unexplained entry open. Do not ask a reviewer to approve a whole ledger merely because several spot checks were correct. The following example is an arithmetic exercise, not a damages calculation or a model of any particular provider account.
A fictional ledger: one bill, a duplicate, a credit and a payment
Fictional example: a single account has a $1,000 bill, a second copy of that same bill, a separate $200 adjustment and a posted $400 insurer payment. For this exercise, the reviewer has confirmed that all three financial events cover the same account and period, and that the second bill is an exact duplicate. With no other entries in the fictional packet, the remaining amount is $400: $1,000 minus $200 minus $400. The duplicate copy adds no new charge.
Swipe across the table to see every column. Keyboard users can focus the table and use the arrow keys.
| Packet entry | Treatment in this exercise | Effect on the calculation |
|---|---|---|
| Original bill A | Retain once after confirming account and service scope | +$1,000 |
| Second copy of bill A | Keep the source copy; exclude its repeated charge | +$0 |
| Adjustment record B | Apply the separate documented reduction once | -$200 |
| Payment record C | Apply the separately posted payment once | -$400 |
| Calculated remainder | Limited to the stated fictional packet | $400 |
The $400 is the result of the stated exercise. In a live file, a newer statement, another service period, pending payment or unapplied credit can change the question. Compare the calculated figure with an appropriately dated account statement and preserve any difference. A matching sum does not establish an agreed payoff, the validity of a claimed lien or permission to distribute funds. The national balance, lien and payoff guide explains those separate records.
Decide whether a row is duplicated, revised or separate
A repeated amount is a reason to inspect, not a sufficient duplicate rule. Two providers may each bill $250 on the same date. A corrected statement may replace an earlier amount without adding a second charge. A lien notice may repeat a bill amount while asserting a different kind of information. Keep the documents and their roles distinct. Ask your reviewer to record why an entry was retained, excluded or linked to an earlier version.
Test the review decisions with a small fictional packet before applying a workflow broadly. Include one exact duplicate, one similar-looking but separate service and one correction. Compare the displayed total before and after each reviewed change. When a decision is reversed, check that the reviewer can still identify the sources and explain the restored amount. This is a proposed acceptance exercise, not a claim that Supio fails any of these cases.
Swipe across the table to see every column. Keyboard users can focus the table and use the arrow keys.
| Pattern | Evidence to compare | Decision to preserve |
|---|---|---|
| Exact duplicate | Same source content, billing entity, account and line details | Which copy is excluded and why |
| Similar amount, different service | Provider, service date, code or description and account scope | Why both entries remain |
| Revised statement | Earlier and later documents plus explanation of the change | Replacement or adjustment relationship; no double counting |
| Same amount in a lien notice | Document purpose and underlying obligation references | Separate legal-review question; no automatic removal |
| Unexplained credit or payment | Date, reference and account application in the source | Unresolved item with a named owner |
Assign a missing-evidence question before another call
Not every exception requires a provider call. If a payment is visible in the source but absent from the proposed ledger, review the extraction or entry first. If the file contains contradictory statements, identify their account scope and dates. If the task genuinely needs current account information that the file does not supply, assign a defined provider question. Avoid paying for a new contact merely to resolve a document-labeling problem.
Write the next task so its completion is observable: obtain the missing statement for the identified account, clarify the coverage of a dated amount, or ask the appropriate reviewer to resolve a duplicate decision. Keep the owner and expected evidence beside the exception. A call attempt is not an account answer, and a promised statement is not a received file.
Keep a review trail with the exported result
Before sharing or exporting a reviewed result, save the source references, inclusion decisions, unresolved items and review date in the firm's approved process. If an export omits that context, retain a companion review note. Record which documents were available at the time. A later upload should prompt review of the affected entries, rather than silently converting an earlier qualified total into a current answer.
Keep the decision vocabulary precise: copied correctly, excluded as duplicate, account scope unresolved, or current statement requested. An entry can be transcribed accurately while its meaning still needs attention. Staff responsible for accounting and counsel should decide the uses and legal significance of the result within the matter.
Evaluate the work your firm actually needs
Use the Supio pricing scope worksheet to ask which analysis, communications and integration work a quote includes. Evaluate the ledger against your actual review process rather than a vendor speed claim. VerifyMD's medical balance verification service addresses a narrower provider-contact task when the firm needs a reported amount and supporting evidence. It does not replace a comprehensive financial ledger, determine a legal obligation or promise a native Supio connection. Live provider calls require agreed setup, permissions and explicit owner activation.
Explore provider follow-up and source review for your firm. Live calls require agreed setup and activation.
Book a demo