What Happens to the Overpayment After You Close the PTAN?

If you are retiring a PTAN this fall, the open receivables under it are probably the last item on the closing checklist, somewhere below the record custody agreement.

Move them up.

CMS issued Transmittal 13966 on September 17, rescinding and replacing April's Transmittal 13708 under the same CR 14020. It creates a PROVIDER-TERMINATED status at the provider/customer level in HIGLAS, the general ledger the MACs run Medicare accounts receivable on, effective and implemented January 4, 2027.

Every word of it is systems housekeeping. What it changes for a practice that stops billing is how fast its unpaid balances leave the MAC.

What CMS Is Actually Automating

Today the status exists only one level down. The CR's background section says so plainly: PROVIDER-TERMINATED "is only utilized at the transaction level which means that if a provider/customer has been terminated, every AR transaction of that provider/customer will be required to be manually updated."

So a MAC analyst has to touch each receivable, one at a time, and keep watching the terminated entity in case a new one shows up.

From January 4, the status goes on the Customer Status History Form once and cascades to every eligible AR the customer owns, existing and new. CMS is explicit about the point of it:

"This will reduce the chance of misclassified AR transactions which will allow these overpayments to be referred to Treasury earlier, thereby increasing the potential for collections."

The reissue is not cosmetic either. April's version moved its effective date from July 6 to January 4 and gained business requirements 14020.2.1 through 14020.2.6.1, including a restriction that stops a MAC from setting "Default To New Transactions" to "No" while entering the status. Read that as CMS closing the one configuration that would have let a terminated provider's next receivable escape the cascade.