Home / Research / E-billing

How often do e-billing status feeds disagree with the vendor portal?

A reconciliation study protocol for comparing e-billing status feeds with vendor portals, including field definitions, sampling, and disagreement coding.

Legal Billing Assistant Editorial Team · Published

Editorial illustration representing How often do e-billing status feeds disagree with the vendor portal?
Table of contents

Method note: this brief proposes a source-led review approach. It does not claim that private client or firm data has been collected.

Question and scope

This protocol asks how often the firm's e-billing status feed disagrees with the vendor portal for the same invoice at the same point in time. The unit is an invoice-day observation, because a status can agree on Monday and disagree on Wednesday. The purpose is to quantify reconciliation effort and identify the fields that drift most. The result does not assign fault to the vendor or the firm.

Scope the study to one vendor or a defined set of vendors and to invoices submitted during the window. Include invoices that are pending, accepted, rejected, adjusted, and paid. Exclude invoices that were never submitted through the portal. State the observation times so a later analyst can reproduce the comparison. Record the observer and the access method so a later audit can repeat the same observation.

Defining a status feed and a portal

The status feed is the automated or manual data set the firm uses to track invoice state internally. The portal is the vendor's authoritative interface for submission and payment status. Define which system is authoritative for each field before comparing. The portal usually controls submission acceptance, while the firm's accounting system controls cash application. Name the system owner who can confirm the authoritative field for each status.

Record the exact field names and allowed values in both systems. A comparison between free-text notes is not a status comparison. If the firm maps portal values into internal codes, retain the mapping table and its version. The mapping is often where a disagreement originates, so it belongs in the evidence. Keep the mapping version with the study so a later comparison uses the same definitions.

Observation design

Observe the same invoice at a consistent time each business day for the study window. A daily observation captures movement without requiring continuous access to the portal. If daily observation is not possible, choose a fixed interval and state it. Random observation times make the disagreement rate harder to interpret. Keep the mapping table under version control because a silent change can create a false disagreement, and record who approved the last change.

Record the portal status, the feed status, the last update time in each system, and the invoice amount. Include a note when the portal is unavailable or the feed has not refreshed. Those cases are not disagreements, but they affect the denominator. Keep an observation log with the date, time, and observer. Record the refresh interval for each system beside the field definition, and note the source of that interval.

Sampling

If the invoice population is large, sample by vendor, submission month, and status category. Include a minimum number from each status so the study does not overrepresent pending invoices. Draw the sample before examining disagreements. A sample selected because it looks suspicious will overstate the problem. Use the same clock and time zone for both systems so a timestamp difference is not coded as a status change.

For each sampled invoice, follow it through the entire observation window rather than observing it once. A single snapshot cannot show whether a disagreement is transient or persistent. Report both the share of invoices with at least one disagreement and the share of invoice-days with a disagreement. The two measures answer different questions. Note any planned maintenance window in the observation log before the comparison begins.

Coding disagreements

Code a disagreement when the two systems report different states for the same invoice at the same observation time. Distinguish a value mismatch from a timing lag. A timing lag exists when the portal changed after the feed's last refresh and the feed is expected to catch up. A value mismatch exists when both systems have processed the same event but report different states. Record the selection method and the number of invoices drawn from each stratum.

Add codes for missing data, unmapped status, and duplicate invoice records. Missing data is not a disagreement, but it affects the ability to reconcile. Keep the codes small, define each one with an example, and have a second observer code a sample. Resolve differences by returning to the portal and the feed timestamp, and state the observation window beside the result.

Analysis and reporting

Report the disagreement rate by field, vendor, and status category. Include the median duration of a disagreement and the share that resolved within one business day. A high rate of short lags is operationally different from a low rate of persistent mismatches. The report should separate the two before recommending a fix. Include the count of invoices behind each rate so a small sample is visible.

Show the share of invoices that required manual reconciliation and the estimated time per reconciliation. Do not invent a labor rate; use the firm's actual observed time if available and label it as an estimate. Compare the rate across vendors only when the submission volume and status mix are similar. The comparison should be transparent about those conditions.

Limits and sources of error

Portal availability and refresh schedules can create apparent disagreements that are really timing artifacts. The observation log should record outages and known maintenance windows. A feed that refreshes hourly will look different from one that refreshes daily. Report the refresh interval beside the rate. Include the number of observations with missing data beside the disagreement rate, and separate missing data from a true mismatch.

The study observes status, not the reason for the status. A disagreement may reflect a vendor error, a mapping problem, or an internal update that was never saved. The protocol can locate the field and the timing, but a separate review is needed to assign cause. Do not infer cause from the disagreement alone. Report the share of mismatches that remain unexplained after the cause review.

Retention and privacy

Store the observation log and the mapping table in a controlled location. Remove client names and matter numbers from the analysis file when they are not needed. If invoice amounts are included, aggregate them before sharing outside the billing team. Follow the firm's records policy for the retention period. Record the refresh interval and the outage history in the limitations section.

Do not capture portal screenshots that contain unrelated client data. Crop or redact to the invoice under review. Limit access to the study team and the billing manager. The purpose is a data quality study, not a broader collection of client information. Keep a separate cause review for a sample of persistent mismatches if the team needs that detail, and label it as a separate follow-up.

Applying the result

If one field drives most disagreements, fix the mapping or the refresh schedule before adding more manual checks. If one vendor drives the rate, review the submission integration and the vendor's status definitions. If timing lags dominate, adjust the daily reconciliation time rather than escalating individual invoices. The fix should follow the measured pattern. Name the access owner and the review interval in the study file.

Test the change on the same sample design and compare the rate with the baseline. A reduction in persistent mismatches is more valuable than a reduction in short lags, because persistent mismatches are the ones that mislead the team. Report the result to the billing manager and the vendor contact. Use a redaction rule for screenshots that includes cropping unrelated invoices.

Review cadence

Repeat the study after any change to the portal, the feed, or the billing system. Also repeat it quarterly during the first year of a new integration. Keep the field definitions and the mapping version with the result. A comparison across versions is only valid when the definitions are stable. Record the portal and feed version with each result so a future comparison is valid.

Review the findings with the team that performs daily reconciliation and ask which mismatch caused the most rework. Their experience can explain a pattern the data only describes. Set one process change and a follow-up date. The cadence should be tied to system changes and observed risk, not to a calendar alone. Ask the reconciliation team which mismatch created the most manual work and include that note.

Reporting the result to the vendor contact

Share the field-level result with the vendor contact only after the firm has confirmed the mapping and the observation method. A disagreement rate without the field definition can sound like an accusation rather than a data quality request. Include one example invoice and the exact timestamps for both systems. The vendor needs enough detail to reproduce the issue.

Ask the vendor whether the portal changed its status definitions during the window and record the answer. If the cause is on the firm side, keep the conversation internal and fix the mapping before the next review. A joint review is useful when both sides can see the same evidence. It is not a substitute for the firm's own reconciliation control.

Authoritative sources

These public references inform the operating questions in this article. They do not replace legal, ethics, privacy, financial, or client-specific advice.

  1. Legal Electronic Data Exchange Standard
  2. NIST Privacy Framework
  3. NIST Cybersecurity Framework
  4. U.S. Government Accountability Office Green Book
  5. Federal Trade Commission data security guidance
  6. U.S. Department of Health and Human Services HIPAA Security Rule

Put the guidance to work

Choose one recurring billing workflow, identify its authoritative source records, and name the owner who reviews exceptions. We can help turn that boundary into a focused support role.

Discuss your workflow