--- title: "Insurance Claims Automation for Clinics | Vascue" description: "Vascue Claims turns each visit into a coded, checked, ready-to-file insurance claim, then tracks it until the money is in the bank. Staff keep the final submit." image: "https://www.vascue.io/images/og/claims.jpg" canonical: "https://www.vascue.io/claims" --- Insurance claims # Claims that prepare themselves. Your team just checks and submits. Vascue Claims turns each visit into a coded, checked, ready-to-file claim, then follows it past “submitted” until the money is actually in the bank. Staff keep every decision that matters. The retyping, chasing, and reconciling go away. [See it live](https://wa.me/85293027422?text=Hi%20Vascue,%20I%20would%20like%20to%20book%20a%20demo)[Read the FAQ](/claims/faq) 1. 01Intake & verify 2. 02Review 3. 03Claim ready 4. 04Pack & file 5. 05Track 6. 06Reconcile ![The Vascue Claims dashboard: drafts to verify, claims needing review, claims ready to file, and payments needing attention.](/images/claims/dashboard.webp) Your whole billing day on one screen: what to verify, what to file, what to chase. From referral to reconciled ## About a minute of human time per claim. The work between a patient's visit and an insurer's payment is mostly repetition. Vascue does the repetition and leaves your team the judgement calls. ![A pre-authorisation draft with the collected details on the left and an in-person identity checklist on the right.](/images/claims/identity-check.webp) Intake arrives as a draft. A human verifies identity before anything leaves the clinic. 01Intake & verify ### Nothing leaves the clinic unverified. Pre-authorisation drafts arrive with the referral already attached. A person confirms the patient's identity before anything is sent, and the product makes that check unavoidable rather than optional. ![The claims review queue: counts for what needs review and what is ready to file, above claims listed with their insurer, service date, and amount.](/images/claims/review-queue-rows.webp) One queue, pre-sorted: what needs you, what is blocked, what is ready to go. 02Review ### Claims assemble themselves and queue up pre-checked. Each claim is built from the visit record and sorted by what it needs from you: review it, fix it, or file it. Reviewing is the whole job. ![A claim marked ready to file, with all checks passed, the diagnosis code, and the billed services totalled.](/images/claims/claim-ready.webp) A finished claim your team only has to approve. 03Claim ready ### Coded, checked, totalled. Diagnosis and procedure codes, validation, and totals are done before a human looks at the claim. What is left is an approve button, or a rejection with a reason attached. ![The payments ledger showing claimed, remittance, and banked amounts with a status and next action per claim.](/images/claims/payments-ledger.webp) Every claim followed until the money is in the bank, not just until it is sent. 04Track ### Tracked past “submitted”. Filed is not paid. Every claim stays open, awaiting, overdue, or short-paid, until the money actually arrives, with the next action already queued for whoever owns it. ![A reconciliation view comparing the claimed amount, the remittance advised, and the bank receipt, with the shortfall highlighted.](/images/claims/reconcile.webp) Claimed vs. advised vs. banked. The shortfall is caught, quantified, and queued. 05Reconcile ### Short-pays caught, not silently eaten. Claimed, advised, and banked are compared for you. When an insurer pays below the claim, the gap is quantified and queued to chase or to bill on, so nothing is written off by accident. Built for real money ## Your billing assistant that never clocks out. It prepares every claim, watches every deadline, and chases every short-pay. Your team checks and submits. ![An audit trail listing created, remittance recorded, paid, and bank receipt recorded, each with actor and timestamp.](/images/claims/audit-trail.webp) ### Human-verified by design Nothing files itself. Every action, every actor, timestamped, in an audit trail your compliance reviewer will like. ![Three pre-authorisations with their sessions used and expiry date: one approved, one expiring tomorrow, one expired.](/images/claims/preauth-expiry.webp) ### Nothing expires quietly Authorisations and filing deadlines are watched for you, down to the session and the day. ![An authorisation card showing sessions approved, sessions remaining, and the total authorised.](/images/claims/burndown.webp) ### Sessions to payments, one place Approved sessions burn down as you file. The count updates itself, so the next claim is never a surprise. ![Illustration of one claim document linked to four channels: an API node, a browser portal, an envelope, and a paper folder.](/images/claims/channels.webp) ### Any insurer, any channel Each insurer is configured per clinic, whether it takes an API, a portal, an email, or a hand-filed pack. No custom project per carrier. What it will not do ## Automation with a person on every decision that matters. - Nothing is submitted without a named person approving it. - No clinical decisions, no coverage decisions, no promised reimbursement. - Patient data stays in your controlled workspace; this page shows synthetic demo data only. ### Who it fits Clinics, hospital departments, and billing teams with repetitive, document-heavy insurance work: physiotherapy, rehab, imaging, allied health, and cross-border billing facilitators serving several clinics. Physiotherapy clinics on Cliniko are the first design-partner path; neither is a requirement. ### Where it sits Alongside your practice-management system, your insurers' existing channels, and, if you use it, the Vascue WhatsApp front desk that collects the referral in the first place. [Claims FAQ](/claims/faq)[Security & privacy](/security)[Why the human click still matters](/blog/human-in-the-loop-insurance-portal-automation) Common questions ## Straight answers about claims automation. [Read the full claims FAQ](/claims/faq) What does Vascue Claims automate? It prepares each claim from the visit record: diagnosis and procedure codes, validation checks, totals, the submission pack, tracking after submission, and reconciliation against the insurer's remittance and the bank receipt. Your team reviews and approves; nothing is submitted without a named person. Does it submit claims on its own? No. Every submission needs a named approver inside Vascue, and portal submissions are attended: a member of staff confirms what is on the insurer's screen before anything is sent. Which insurers and submission channels does it support? Each insurer is configured per clinic on the channel it actually accepts: API, provider portal, email pack, or a hand-filed pack. Channels are confirmed with the insurer during onboarding rather than assumed. Does it work with my practice-management system? Cliniko is the first native integration and the source of the visit record. Other systems and approved document inputs are set up per clinic during onboarding. Where does patient data go? It stays in your clinic's controlled Vascue workspace. Direct identifiers are masked before any content reaches a language model, and Vascue is ISO 27001 certified. The screens on this page show synthetic demo data only. Is it available today? Yes, through a design-partner programme for clinics, hospital departments, and billing teams with repetitive, document-heavy insurance work. Book a walkthrough to see the full workflow on one of your own claim types. Further reading ## Deeper reading on claims automation - ![Insurance Portal Automation: Why the Human Click Still Matters](/images/blog/human-in-the-loop-insurance-portal-automation.png) Healthcare AI ### Insurance Portal Automation: Why the Human Click Still Matters An attended browser workflow can remove re-keying while keeping clinic staff in control of the payer portal, final review, and submission action. 7 min read [Learn more](/blog/human-in-the-loop-insurance-portal-automation) - ![Insurance Claim Status and Denial Terms Explained for Clinic Billing Teams](/images/blog/insurance-claim-status-and-denial-terms-explained.png) Revenue Cycle ### Insurance Claim Status and Denial Terms Explained for Clinic Billing Teams What claim statuses such as awaiting insurer concurrence, query raised, shortfall, run-out and PR 31 actually mean, and what a clinic billing team should do next for each. 8 min read [Learn more](/blog/insurance-claim-status-and-denial-terms-explained) - ![Billing, Payments and Insurance Claims for a Small Allied Health Clinic in Australia: The Simple Setup](/images/blog/small-allied-health-clinic-billing-payments-claims-setup-australia.png) Revenue Cycle ### Billing, Payments and Insurance Claims for a Small Allied Health Clinic in Australia: The Simple Setup The four billing rails a small Australian allied health clinic needs (card, private health, Medicare and DVA, NDIS and workers comp), what HICAPS, Tyro Health, Square and Stripe charge, and how to route all of it through the PMS. 9 min read [Learn more](/blog/small-allied-health-clinic-billing-payments-claims-setup-australia) [All articles →](/blog#claims) ## This page is the overview. The rest we show live. Bring one real claim type and one insurer. We'll walk the whole loop on it, from intake to reconciled, and tell you honestly where a pilot would start. [Book a walkthrough](https://wa.me/85293027422?text=Hi%20Vascue,%20I%20would%20like%20to%20book%20a%20demo) Screens are from the current Vascue Claims build, seeded with synthetic demo data. Names, insurers, and amounts are illustrative; currency follows the deployment. Last updated 20 August 2026 · [Markdown version](/claims.md) for AI agents