Claims submission: how to avoid stress on submission day

Every month, hospital billing teams have one date that carries disproportionate pressure: the day claims are closed and submitted to payers. It is when accumulated pending items, XML errors and outdated tables take their toll all at once.

The problem is not the technical complexity of the process. It is that most hospitals still treat health plan claims submission as a monthly correction event, when it should be a continuous checking routine. The result is overtime, rework and claims submitted with inconsistencies that will turn into denials weeks later.

This article explains what hospital claims submission is, why submission day is so problematic and how to reorganize the process so that the close is a confirmation, not a race.

What hospital claims submission is

Health plan claims submission is the process by which the hospital organizes, audits and sends to health plans all the care records for the period: procedures performed, medications administered, materials used, daily rates and fees. Based on this submission, the payer reviews the claims and processes payment.

The technical standard that governs this exchange of information is TISS (Troca de Informação em Saúde Suplementar, or Supplementary Health Information Exchange), defined by the ANS (Brazil’s National Supplementary Health Agency). TISS determines the XML file format, the required fields, the accepted procedure codes and the submission rules for each type of form. Each payer has its own contractual deadlines and specifications within this standard, which multiplies the complexity for hospitals that serve multiple health plans.

Missing submission deadlines can result in untimely-filing denials (refusal of payment because the claim was sent after the contractual deadline, regardless of its technical quality). That is why calendar control is an inseparable part of billing management.

Why submission day concentrates so many problems

The chaos of the monthly close rarely has a single cause. It is the result of several dysfunctions that build up over the month and all show up at once on submission day.

The first is postponed auditing. When claim review is left to the last days of the month, the accumulated volume makes a careful review of each batch unfeasible. The billing specialist has to choose between submitting with possible inconsistencies or delaying the batch and risking an untimely‑filing denial.

The second is manual XML editing. When the file generated by the hospital system shows validation errors on the payer’s portal, the makeshift fix is to open the XML in a text editor and correct it by hand. This practice solves the immediate submission problem, but it creates a discrepancy between what was sent to the health plan and what is recorded in the hospital’s system, compromising future audits and financial reconciliation.

The third is outdated tables. The Brasíndice and SIMPRO tables, which set reference prices for medications and materials, are updated periodically. When the hospital system is not synchronized with the versions in force at the time of billing, the amounts submitted differ from what the payer expects, leading to price discrepancy denials that could have been avoided entirely.

The fourth is the multiplicity of contract rules. Each payer defines its own billing criteria, deadlines, required fields and authorization formats. A hospital that serves ten different health plans manages ten sets of rules at the same time, with no guarantee that the system is applying each one correctly to every claim.

The most common XML submission errors

XML submission validation errors have well-mapped origins. Knowing them makes it possible to act preventively, before they turn into denials.

Missing required fields

The TISS 4 standard defines a series of fields that must be filled in on each type of form. If any of them is missing, the file cannot be validated on the payer’s portal. The most frequently forgotten are: the ICD code on the admission form, the prior authorization number for elective procedures and the procedure date in the fee fields.

Incorrect or outdated TUSS codes

The TUSS code identifies each procedure, test or material billed. Using a discontinued code, applying the wrong code to a similar procedure or failing to update the table after ANS revisions are frequent causes of automatic rejection. The payer does not pay for the procedure described in free text: it pays for the code.

Price table discrepancies

When the unit price of a billed item differs from the table in force under the contract with the payer, the claim is denied or audited. The most common cause is the use of outdated versions of the Brasíndice or SIMPRO tables at the time of billing.

Missing prior authorization. Procedures that require prior authorization from the payer and are submitted without the corresponding number are automatically rejected. Tracking the status of each authorization, by payer and by type of procedure, is an essential part of hospital billing management.

How to spread the workload and reach submission day calmly

The solution to monthly close stress is not on submission day: it is in how the whole month is managed. Three process changes make a practical difference:

Continuous auditing throughout the month

Concurrent auditing (carried out during the hospital stay, before discharge) identifies discrepancies while it is still possible to correct them without affecting the submission deadline. When auditing is done in real time, the monthly close is just the consolidation of work already done, not the discovery of accumulated problems.

Automatic validation of tables and contracts

Tools that automatically cross-check the items charged against the price tables in force and each payer’s contract rules eliminate the need for exhaustive manual reviews. The claim leaves the system already validated against what each health plan accepts.

Cleaning up the XML at the source

The XML file should leave the hospital system ready to send, with no need for manual intervention. This requires the system to be correctly configured for each payer’s rules and any validation errors to be flagged before the batch is closed, not at the moment of submission to the health plan’s portal.

When these three elements work, submission day becomes just the formal moment of transmitting a batch that has already been audited and validated.

Stress-free billing starts with the routine, not the deadline

Monthly close stress is a symptom of a process that accumulates problems instead of solving them continuously. When checking is spread throughout the month and the XML is generated and validated at the source, submission day stops being a race against the deadline and becomes the final step of a process that is already in order.

Rivio uses artificial intelligence to manage the entire hospital revenue cycle, increasing revenue and operational efficiency. From auditing to payment, our technology analyzes clinical records, cross-checks information against hospital claims, identifies and corrects denials, sends the XML file and manages denial appeals, all automatically.

With Rivio, hospitals and clinics leave the bureaucracy to AI and can focus on what really matters: caring for the health of the Brazilian population.

FAQ — frequently asked questions about hospital claims submission

What is health plan claims submission?

It is the process of organizing, auditing and sending to health plans all the care records for the period, including procedures, materials, medications, daily rates and fees, so that payment can be processed. Submission follows the TISS standard, defined by the ANS, and each payer has specific deadlines and contract rules.

Why do errors occur in the billing XML file?

The most frequent causes are: missing required TISS fields, outdated or incorrect procedure codes, discrepancies between the amounts billed and the price tables in force, and a missing prior authorization number for procedures that require one. Most of these errors originate in process failures that could be identified before submission day.

How can denials be reduced in claims submission?

The most effective strategy is to spread auditing throughout the month, automatically validate the items charged against each payer’s tables and contracts, and make sure the XML is generated and validated at the source, with no need for manual editing. Automated checklists that block the submission of claims with technical or administrative inconsistencies also significantly reduce the denial rate.

What is the advantage of automating claims submission to state health plans?

State and regional health plans often have very specific contract rules that differ from the national tables and change frequently. Automation ensures that these particularities are applied correctly to every claim without depending on the team’s memory or manual updates, reducing the risk of denials for breach of contract rules.

How can overtime be avoided on billing day?

By spreading the audit workload throughout the month and using tools that check data continuously. When the monthly close is just the consolidation of work already done over the period, the volume of pending items on submission day is minimal and the time needed for transmission is predictable.