This selects whether the switch sends accounting records to its configured 802.1X accounting servers strictly by priority order or spread across them via load balancing. Unlike the authentication case where load balancing spreads login load, load-balancing accounting records across multiple servers means a single session's start, interim, and stop records could in principle land on different accounting servers, which matters if downstream billing or usage reports expect a session's full record set on one system. For example, a service provider billing on session duration would likely want this set to priority(1) with one accounting server so a session's start and stop records reach the same database.