Your software
Tebra (Kareo) billing services
Tebra billing services from Remitwright put a dedicated biller inside the practice management system that used to be called Kareo.
See where claims are getting stuck. No patient data needed.
Tebra describes itself as built on the strength of Kareo and PatientPop, and its help center states that Kareo and PatientPop are now Tebra, so the screens are the ones your team knows. The biller is a user you create on the Biller web role and works your account: charges, claim processing reports, ERA posting, the ERA Errors tab, denials and patient balances. The work stays in Tebra; a person joins it. See the full list of billing software we work in, by type.
Independent: Remitwright is not affiliated with or endorsed by Tebra. Tebra (Kareo) is a trademark of its owner, named here to describe the system we work in.
Last reviewed by the Remitwright billing team. Editorial policy
- EHR and practice management
Every day
What your biller does in Tebra (Kareo) every day
- Enter charges for every signed visit, matched against the schedule, with the rendering provider, place of service, codes and modifiers the payer expects; an unsigned visit goes back to the provider with its date on it
- Work the claim processing reports Tebra routes to the practice: its own validation report, the clearinghouse acknowledgements and rejections, and the payer's responses, then fix the registration or payer setup that keeps producing the same rejection
- Check claim status on anything a payer has not acknowledged, and resubmit with the clearinghouse acceptance on file where a claim went missing between Tebra and the payer
- Post ERAs from Encounters, Clearinghouse Reports, Electronic Remittance tab, checking the auto-populated lines on the Apply tab of the New Payment from ERA window before the payment is saved
- Clear the ERA Errors tab: a remittance line Tebra could not match to a claim, or one with duplicate or unbundled data, is applied by hand on the Apply tab until nothing is left unapplied, or taken back to the payer with a question
- Work the denials, reversals and underpayments that ERA posting flags, by payer and age bucket, with the CARC and RARC and a dated note left on the claim for each action
- Keep the insurance and payer settings current, so the payer-specific rules Tebra applies before submission catch your payers' habits and not only the common errors
- Verify eligibility ahead of the schedule for patients whose coverage changed, and leave the copay and deductible position where the front desk can see it
- Review patient collections status before statements go out on the cycle you choose, so a patient is billed only for the balance the remittance leaves
- Read the payout report and the claim and collections status views and build the one-page weekly report, with each number defined once so it means the same thing every week
Access
Access and security
Your data, your systems
Patient data stays in your systems. Your biller works inside your own software, clearinghouse and payer portals and never exports, downloads or stores claim files, remittances or patient lists on Remitwright devices or systems.
- BAA signed before any access
- A user you create and can remove
- MFA on every login that supports it
- No claim files or patient lists exported
In Tebra (Kareo)
- Tebra has six web user roles: System Admin, Provider, Clinical Assistant, Office Staff, Biller and Business Manager. Your biller is created on the Biller role, which Tebra gives charge entry, claim status, patient collections status, the payout report and the practice and insurance settings, without clinical permissions such as managing clinical information or viewing notes
- Your System Admin stays the owner of access. Tebra's user management guidance makes understanding each user's level of access the System Admin's job, points to the HIPAA minimum necessary standard, and notes that a billing user without clinical or admin permissions cannot open modules such as Clinical
- We work in your practice account as a user you create, not through a multi-practice billing account of ours, so every claim, note and payment the biller touches stays in your data
- The BAA is signed first and the user is created second; multi-factor authentication is on for the login wherever the account offers it, and you can disable the user whenever you decide to
- Claims leave through Tebra's own connection and reports are read inside Tebra; claim files, remittances and patient lists are not exported into systems of our own
Where the biller steps in
What Tebra (Kareo) does not do, and the biller does
Auto-posting places what it can match. A remittance for a claim billed in another system or through a payer portal, or a claim with duplicate or unbundled lines, opens on the ERA Errors tab, and a person applies it by hand
Payer-specific rules catch what they have been given. A Medicaid managed care plan's taxonomy requirement or a behavioral health plan's telehealth modifier that is not yet in those rules is learned from the first rejection, written into your payer notes and checked before each release
An underpayment only shows when someone compares the allowed amount on the ERA with your contracted rate for that code; the biller keeps those rates loaded and runs the comparison line by line
Appeals with records attached, peer-to-peer requests and payer portal reconsiderations are done outside Tebra and logged on the claim afterwards
The Biller role does not include Billing Analytics, which Tebra gives to the System Admin and Business Manager roles. If you want those charts in the weekly report, your System Admin grants the permission or shares the views
Questions
Questions about billing in Tebra (Kareo)
Our account still says Kareo. Is that the same thing?
Which Tebra user role does your biller need?
Where do rejections and remittances show up in Tebra?
How are remittances posted?
Do you set up a billing-company account in Tebra?
Do we have to change our Tebra subscription to bring you in?
Can you take over from an in-house biller who is leaving?
What do you report, and from where?
Next step
See where claims are getting stuck. No patient data needed.
Three quick questions. No patient data. A billing specialist reads every request and replies in writing, with notes on how the work would run inside Tebra (Kareo).
- Three questions, about two minutes
- No patient data, no software to buy
- A written reply from a biller, not a sales deck
You answer three questions
A billing specialist reads them
A written reply by email
Prefer email? sales@remitwright.com
Request received
Thanks. Your review request is in.
Reference . Quote it if you write to us about this request.
- A billing specialist reads your answers and replies by email.
- If a look at real claims makes sense, we agree read-only access under a BAA first.
- You get a written summary of what is worth working and what it would take. No commitment.
While you wait: see the sample weekly report or read how switching works. You can also download the sample weekly report (PDF).