How to Track a Medicare Enrollment Application With the MAC

Identify the MAC and transaction before chasing a status update

The MAC processes Medicare enrollment applications for providers, group practices, and non-DMEPOS suppliers.

CMS advises applicants to work with the MAC and to use it for enrollment-status questions.

PECOS provides a submission path and application information, but the MAC may request additional documentation.

Start the tracker with the provider or supplier, NPI, PTAN when one already exists, state or jurisdiction, MAC, transaction type, group relationship if relevant, and PECOS tracking information. A practice can have several open Medicare transactions at once—an individual enrollment, group update, reassignment, or location change—and a phone note that says “Medicare application pending” is not specific enough. If the MAC has a contractor portal or case reference, link it to the same row. This basic context prevents staff from following up on the wrong application or misreading an update on one relationship as completion of another.

Use PECOS to confirm the application actually reached a submitted state

Development requests can stall an otherwise complete application if ownership of the response is unclear.

Approval letters and effective dates belong in the permanent enrollment file.

A status tracker should answer “what is the next action?” in one glance. If it only stores dates, it is an archive, not a control.

Verify submission status in PECOS after the filing. A saved draft, signature request, incomplete application, and submitted transaction are operationally different states. Save the confirmation page or transaction reference and the submission date. If an electronic signature was required, confirm that the authorized signer completed it. The tracker should show who owns the next action only after the system indicates the case has actually moved forward. This catches a common problem in which staff start counting “processing days” from the date they finished data entry even though the application did not leave the office until days later.

Log development requests as deadlines, not as ordinary correspondence

Treat a development request like a mini-project with a due date. Record the date received, response deadline, every item requested, person responsible for each item, date sent, transmission method, and proof. Answer the contractor’s request from current source documents and keep the exact response packet. If one item is unclear, contact the MAC early rather than sending an improvised answer near the deadline. Multiple coordinators should not respond independently from separate inboxes. A centralized development log prevents duplicate uploads and inconsistent explanations that can create more questions instead of resolving the first request.

Ask the MAC narrow questions that produce operationally useful answers

Calling the MAC repeatedly without recording reference numbers or outcomes. The safe response is to stop the handoff until the source evidence and submitted answer tell the same story.

Letting requests sit in one employee’s inbox. If one field changed, review the related identifiers, addresses, dates, and relationships instead of patching only the item mentioned in a portal message.

Treating a “submitted” status as approval. The problem is not merely cosmetic: a mismatch can change which transaction is reviewed or where the request is routed.

Updating the billing system before the effective date and relationship are confirmed. This tends to surface later, when billing or scheduling discovers that a supposedly completed file still has an unresolved dependency.

When contacting the MAC, ask questions tied to a specific case and operational decision. Useful examples are whether the contractor has received a particular development response, whether a transaction is waiting on additional information, whether a reassignment is included in the case, or what status appears for a specific location. Avoid asking only “is the provider active?” when the practice actually needs to know whether the practitioner is active under a certain group for a specific period. Record representative name when provided, call date, reference number, and the exact scope of the answer. A narrow note is safer than a broad paraphrase.

Separate approval, effective date, reassignment, and location readiness

Pecos tracking number: Store it with the transaction rather than in a personal downloads folder or one coordinator’s inbox.

Mac contact details: Tie the document to the specific field or decision it supports.

Development request copies: Record where it came from and when someone verified it.

Response package: Preserve the prior version when an effective-date sequence could matter in a later review.

Final determination letter: Keep the current version and enough history to show when it changed.

Do not collapse every milestone into “approved.” The practitioner enrollment may be approved while a reassignment to the group is still incomplete. A group update may be processed while a location issue remains. The effective date relevant to billing can differ from the date the office received an approval message. Capture each status and date separately, then give billing a concise activation note that identifies provider, group, location, and effective period. This avoids the recurring failure in which the credentialing team sends an approval email and the revenue-cycle team assumes every Medicare relationship in the file is now ready.

Close the case only after the disposition evidence is saved and handed off

Close the tracker row with durable evidence: final PECOS/MAC disposition, approval or confirmation letter where available, PTAN information if issued, effective date, reassignment outcome, and any conditions or unresolved follow-up. Store the final record with the source documents and update the maintenance calendar if the transaction changes future revalidation or location work. A completed case should be understandable months later without access to one employee’s email. That standard also makes later claim research faster because billing can see what Medicare relationship existed on a historical date of service.

Operational checklist

• Create one tracking row for each application with the PECOS tracking reference.
• Record the MAC, submission date, current status, and next follow-up date.
• Route every development request to a named owner the same day.
• Answer with the requested source documents rather than a narrative that introduces new inconsistencies.
• Save the approval/denial/return correspondence.
• Hand the final effective date to billing and payer-operations staff through a controlled activation step.

Sources reviewed