Patient and Claim IDs
Fields for patient name, DOB, payer member ID, provider NPI, original claim number, service dates, and internal account or encounter identifiers to ensure accurate matching in payer systems.
A correctly prepared Re-BPS Form reduces denial cycles, improves claim accuracy, and documents the basis for payment adjustments. It supports auditability required under HIPAA and payer contracts and helps avoid downstream appeals or duplicate billing. Use clear identifiers and attach verifiable supporting records to reduce processing time and administrative cost.
Common submitters include provider billing teams, practice administrators, and authorized third-party billers acting on behalf of clinicians.
Receiving parties include payer adjudication units, clearinghouses, and internal revenue reconciliation teams; roles vary by organization and contract.
An institutional billing manager or authorized designee completes and certifies the form for reprocessing. That person confirms accuracy of corrected codes and attachments and attests to authorization to act on the provider's behalf; signatures must match internal delegation records.
A clinician or supervising provider signs when clinical justification or corrected clinical documentation supports the re-bill request. Their signature affirms clinical accuracy and is required where clinical reason codes change the payment determination.
Fields for patient name, DOB, payer member ID, provider NPI, original claim number, service dates, and internal account or encounter identifiers to ensure accurate matching in payer systems.
Structured fields for original and corrected CPT/HCPCS codes, ICD-10 diagnoses, units billed, billed amounts, and reason codes that explain the nature of the reprocessing request in standardized terms.
Area to list or attach supporting documentation such as corrected medical records, prior authorizations, proof of eligibility, EOBs/RA, or additional clinical notes required by the payer for adjudication.
Signer block for printed name, title, signature (electronic or wet), date, and an attestation confirming accuracy and authorization; include contact information for follow-up.
Preferred submission channel (electronic portal, secure email, or fax), payer contact, and any required supplemental forms or payer-specific fields to accelerate processing.
Fields that capture form version, preparer ID, timestamp, and internal tracking number to support audit trails, appeals, and records retention policies.
| Field | Configuration |
|---|---|
| Required Identifiers | Make patient, provider, and claim fields mandatory. |
| Conditional Fields | Show code-correction fields only when a correction is selected. |
| Attachment Mandates | Require attachments for specific reason codes or monetary thresholds. |
| Approval Routing | Route to billing manager then to provider signer for clinical attestations. |
Choose platforms that support secure attachments, audit trails, and strong signer authentication to meet regulatory needs.
Varies by payer; often 90–180 days from original remittance
Payer-specific; often 180 days to one year for reconsideration
Establish 3–5 business days for intake validation and routing
Allow additional 5–10 business days to gather supporting records
Schedule payer follow-up at 30 and 90 days if no response
Completing fields and collecting attachments before sending.
Payer confirms identifiers and completeness.
Claims team reviews corrections and applies policy.
Payer issues adjusted remittance or denial notice.
A clinic identified a coding error on a bundled service
A hospital disputed DRG assignment after clinical documentation update
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |