Offered workflow scope is confirmed in implementation. Public examples are fictional; specific integrations and production data handling are evaluated separately.
How the workflow works
01
Associate remittance and payment evidence
Retain the applicable trace references, payer and payee context, posting batch, and deposit evidence. A remittance is not itself proof of a bank deposit.
02
Investigate the difference
Separate missing deposits, unposted remittances, offsets, duplicate entries, unsupported adjustments, and reversals. Preserve original and replacement events.
03
Approve the supported resolution
The authorized financial owner reviews corrections and the basis for adjustments. Keep patient-balance effects and remaining dependencies visible before closing the case.
The evidence stays with the case
Associate remittance and payment evidence
Retain the applicable trace references, payer and payee context, posting batch, and deposit evidence. A remittance is not itself proof of a bank deposit.
Example Reassociation: Evidence: Remittance reference / trace / bank match; Next action: Named owner review · Demo data
Investigate the difference
Separate missing deposits, unposted remittances, offsets, duplicate entries, unsupported adjustments, and reversals. Preserve original and replacement events.
Example Reconciliation exception: Evidence: Difference identified / owner / source references; Next action: Named owner review · Demo data
Approve the supported resolution
The authorized financial owner reviews corrections and the basis for adjustments. Keep patient-balance effects and remaining dependencies visible before closing the case.
Example Financial review: Evidence: Reviewed basis / ledger effect / reconciled result; Next action: Named owner review · Demo data
Inspect a fictional workflow
Try the workflow · fictional demo case
A remittance arrived; the deposit remains unmatched
Fictional payment exception: automated posting completed, but the bank match and a later reversal need financial review.
Select a check to reveal the finding and next action. Nothing is sent to a payer.
0 of 3 checks reviewed. A named person still approves the next action.
This fictional example illustrates an offered Marsa workflow. We do not connect this public example to a payer or present it as a customer result. We measure demo starts and completions using fixed labels; no input text is collected.
Explore the offered workflows with fictional examples. These public walkthroughs prepare example outputs locally; they do not access records, connect to a payer, or submit anything.
Authorization and concurrent review
✓Authorization requirement checks and payer routing
✓Packet preparation and evidence checks
✓Initiation, attachments, and submission after approval
✓Status follow-up and additional-information responses
✓Renewals, concurrent review, and unit reconciliation
Fictional case · no patient information
A fictional IOP renewal has an amendment, a quantity question, and one missing supporting item.
Your implementation scope confirms the required payer workflows, systems, integrations, and operating responsibilities. A named human approves payer submissions.
A named authorized human approves payer-facing work. Qualified people retain clinical, coding, financial, contractual, and privacy decisions. No payer submission happens automatically.
Can I send patient information for the evaluation?
No. Use demo-safe, de-identified worksheet facts. Do not send charts, denial letters, or patient identities.
See the workflow on a demo case
Twenty minutes, your payer questions, and a visible human-review checkpoint.