A practical guide to completing Box 24G: Days or Units accurately and consistently.

From our workflow: Days or Units may be a small entry, but it affects the rest of the claim. We compare it with the source record and then confirm that the surrounding fields tell the same story.

Report the number of units, visits, miles, items, or days represented by the service line.

For Days or Units, 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

For Days or Units, 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.

Do not change Days or Units simply to clear an edit. The value should come from finalized documentation, the current code set, and the charge record, and the correction should be made in the source record when possible.

How to enter it consistently

  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.

Mistakes worth catching early

  • Defaulting every line to one.
  • Entering minutes instead of timed-code units.
  • Conflicting with documentation.

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

Last check before sending

  • Determine the unit definition.
  • Calculate from documentation.
  • Check code and payer rules.
  • Confirm the charge reflects the units.
  • 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.

Using software without skipping review

A dependable program can reuse stable records and flag inconsistent entries for Days or Units. It should not silently guess at information that is absent or uncertain.

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.

Official references

These primary sources support the field or transaction guidance on this page. Receiver-specific rules still take precedence.