Claims built from the same record as the care
AraSync prepares X12 837P claims from approved service lines, routes them to MN-ITS or Availity, tracks their status and posts 835 remittances back to the lines they paid. Each claim can be previewed before submission, and your billers keep the final say.
Claims that go out clean.
Lines without a current authorization are held before anything is sent. Claims route to MN-ITS or Availity, and remittances post back against the lines they paid.
- Authorization and units checked before the batch
- MN-ITS for MHCP, Availity for managed care
- 999 acknowledgements and 835 payments matched to each line
From service line to remittance
Each step works from the record the one before it left behind
837P claims prepared for review
Claim files are built from visit and service line data, with a preview you can check before anything is submitted.
Claim status
Follow a claim from submission to payment, with 276/277 status inquiries and payer acknowledgments recorded against the batch.
Claims aging
See open claims grouped by age since submission, so follow-up starts with the oldest.
835 remittance posting
Remittances post back line by line, so payments, adjustments and denials land on the service they belong to.
One view of what is billed, pending and paid
The billing dashboard follows each service line along this path, with the revenue pipeline, claims aging and activity by payer, so the billing team starts each day with what needs attention.
- ✓Service lines created from completed, approved documentation
- ✓Service codes with payer rates and modifiers kept in one place
- ✓A denial worklist, with an AI-drafted appeal letter your team can edit before sending
- ✓Lines held for a missing authorization or an eligibility gap stay visible until resolved
-
Visit and note Session times and the approved note land on one service line.
-
Pre-billing check
- Authorization and units left
- Signatures present
- No overlapping times
-
Claim sent MN-ITS for MHCP, Availity for managed care. 837P
-
Status tracked Accepted, pending or denied, by line. 276 / 277
-
Payment posted The remittance posts back to the line it paid. 835
FlaggedA line that fails a check is flagged for your billing team with the reason attached, so it can be fixed before it comes back denied.
-
Sent Claim file submitted 837P
-
Acknowledged The file was received and read 999
-
Status by line Accepted, pending or denied 277
-
Posted Payment or denial lands on the line 835
Each claim goes where the payer takes it
AraSync sends each batch through the channel its payer uses, then records what comes back: the acknowledgment, the status of each line and the remittance.
- ✓MN-ITS: straight Medicaid (MHCP) claims, eligibility and remittances
- ✓Availity: managed care payers such as Medica, UCare, Bridgeview, HealthPartners and Blue Plus
- ✓Authorization checked before a line is billed, where the program requires one
- ✓Claim preview before submission: what you review is what is sent
- ✓Batch submission with error reporting
Checked before it is billed
Configured checks can help flag problems while they are still easy to fix. Billers make the final call.
Approved documentation first
A line whose note is still pending or sent back for revision stays out of the billing run until a supervisor approves it.
Nightly pre-billing scan
Each morning the billing team gets an email listing unbilled lines with possible overlaps, duplicates, authorization or unit gaps, and missing provider or diagnosis details.
Eligibility holds
Eligibility is checked on the first of each month. Lines for a member shown as ineligible are held, and released when a later check restores coverage.
How the compliance checks work · What the billing agent runs
See your billing run end to end
We will take a service line from approved note to 837P preview to posted remittance, using the payers you bill.
Request a demo