Run the Payer Claims Lifecycle End to End
When a patient has insurance, the covered part of their bill is not collected from them — it is claimed from their payer. Veona turns that into a clean lifecycle: raise the insured invoice and a claim is drafted for you automatically; batch-submit it to the payer and Veona produces a branded claim bundle; the payer responds with an approval (or a denial, or a request for more information); and finally you post the remittance that records the money actually paid. This page follows one HMO claim end to end. (HMO is a Health Maintenance Organisation — a private insurer; the sibling public scheme is NHIS, the National Health Insurance Scheme. Both work the same way here.)
Who / when: the claims officer (working with the billing-manager permissions for submit and posting), after an insured patient’s invoice has been raised — whenever a covered bill needs to go to a payer and come back reconciled. Key terms: a payer is the insurer; a scheme is the specific cover the patient holds with that payer (with its coverage percentage and claim window); a claim is the covered portion of an invoice submitted for reimbursement; the bundle is the branded document package sent to the payer; remittance is the payer’s record of what they actually paid. We’ll follow Chidi, a claims officer, taking one claim from draft to paid.
- Claims officer — confirm the patient’s payer scheme is set up. Payers and their schemes live on Bill → Payers (each scheme carries its coverage percentage and claim window). The patient’s coverage must exist before an insured invoice can become a claim.
- Claims officer — make sure the insured invoice exists. When an invoice is raised against an HMO scheme, Veona auto-builds a claim in the Drafted state for it — you do not assemble the claim by hand. (If you need the invoice itself, that is Turn Charges Into a Scheme-Priced Invoice, choosing the payer scheme so the lines are priced and the covered portion is identified.)
- Claims officer — open Bill → Claims. The auto-built claim is listed in the Drafted state, keyed to the patient and carrying the covered amount. Open it (click the row) to review the covered lines and the coverage percentage before you send anything.
- Claims officer — select the draft and batch-submit it from Bill → Claims. Submitting sends the claim to the payer through that payer’s configured adapter and produces a branded per-payer claim bundle; the claim moves from Drafted to Submitted.
- Claims officer — download the claim bundle PDF from the claim (the bundle action on Bill → Claims). This is the branded document package that evidences exactly what was submitted; keep it with your records.
- Claims officer — when the payer responds, record their decision on Bill → Claims. The outcome is one of Approved (with the approved amount), Rejected, or Pending-Info (the payer needs more from you). On an approval, the claim advances to Approved carrying the approved amount.
- Claims officer — when the money actually arrives, post the remittance for the claim (on Bill → Remittance, or from the claim). This records what the payer paid against the claim and reconciles it — the covered money is now posted, not just promised.
What happens next
Section titled “What happens next”The claim is closed: submitted with its bundle on file, decided by the payer, and reconciled by the remittance. Any patient-side balance that remains after the payer’s share — a co-pay, or an uncovered line — is collected the ordinary way at the cashier desk; see Take a Payment, Deposit or Refund. A rejected claim, or one the payer cannot cover, may need an invoice correction — a credit note or a void — which is covered in Void, Credit, Estimate and Plan in the Revenue Cycle.