A practical guide to completing Box 27: Accept Assignment accurately and consistently.

From our workflow: When reviewing Accept Assignment, we look at both the field itself and the related patient, insured, provider, and service-line data. Payers evaluate the claim as a connected record.

Indicate whether the provider accepts assignment when the payer uses this field.

For Accept Assignment, we also check the related patient, insured, provider, diagnosis, and service-line data. A field can pass a format edit and still be inconsistent with the claim around it.

General rule: Payer-specific instructions, contracts, program manuals, and current coding guidance can add to or override general form guidance. Verify requirements before submission.

Why this deserves a careful check

The payer does not read Accept Assignment in isolation. We compare it with the surrounding claim data before deciding the entry is ready.

If Accept Assignment fails an edit, verify the source and the payer rule before changing it. A guessed value can move the problem from rejection to denial.

A practical entry routine

  1. Identify the person, organization, date, code, or identifier the field is asking for.
  2. Locate the source document: insurance card, eligibility response, clinical note, authorization, provider enrollment record, fee schedule, or payer remittance.
  3. Enter the value using the form’s structure and the payer’s required format.
  4. Compare it with related fields and service lines for consistency.
  5. Save evidence of the source and the final submitted claim.

What commonly goes wrong

  • Assuming the answer is the same for every payer.
  • Treating assignment as the same as network participation.
  • Contradicting enrollment.

We do not treat the last paid claim as the source for Accept Assignment. It may contain information that was valid then and is no longer valid now.

A quick check before submission

  • Review payer and program rules.
  • Match provider status.
  • Train staff on the meaning.
  • Do not use the field to express unrelated payment preferences.
  • Compare the completed claim with the clinical and billing record.
  • Confirm the receiving address or electronic route.
  • Keep a secure copy and proof of submission.

What software can check

For Accept Assignment, software should catch missing values and obvious conflicts while leaving coverage, coding, and documentation decisions to the user and current payer rules.

Apply this in software: For a workflow that keeps claim data reusable and reviewable, see the CMS-1500 paper and electronic filing options. Software can enforce format and consistency, but the source record and payer instructions still control the claim.
Privacy reminder: Use fictional data for training and printer tests. Claims contain protected information and should be stored, transmitted, printed, and destroyed through approved secure processes.

Written and reviewed by

1500Software Development Team

Covers the software, printing, validation, export, and troubleshooting steps described on this page.

1500Software Claims Review Team

Reviews field placement, provider roles, source records, and practical correction steps.

Reviewed July 26, 2026. Always follow the receiving payer’s current instructions and companion guide.

Source material

Use these references for the national standard, then compare them with the current payer or clearinghouse guide.