This is the maximum number of billing records the node will store awaiting printing, with records created after this maximum is reached being permanently lost. Because overflow records are explicitly lost rather than queued further, this cap directly determines the node's tolerance for a billing-destination outage; an admin whose billing printer or logging device might be offline for extended periods needs this set high enough to survive that outage without losing revenue-bearing call records. For example, if the billing printer is down for an hour during which 250 calls generate billing records but this maximum is set to 200, the 50 records beyond the cap are permanently lost.