The absence of a written collections policy does not mean a team is operating without policy. It means each team member is operating with their own implicit policy, built from their own judgment about what is appropriate in each situation. That produces inconsistency: the same customer, at the same payment stage, treated differently depending on who handles the account that week.
Inconsistency is expensive. It creates customer confusion when they receive different types of messages from different contacts. It creates gaps where invoices do not receive follow-up because the implicit policy of the person handling them was to wait longer. It makes it impossible to improve the collections process systematically, because there is no documented baseline to improve from.
Writing a collections policy is not a large project. The core decisions can usually be documented in two or three pages. The following sections describe the decisions that matter most.
Segmentation: Not All Customers Get the Same Treatment
The first decision is how to segment your customer base for collections treatment. Not all customers should be handled identically. A long-term customer with a strong payment history and a significant ongoing commercial relationship warrants different escalation thresholds than a new customer with one invoice and no track record.
Most finance teams settle on two or three segments. A common approach is to define a strategic segment (customers with annual billing above a defined threshold, or with contractual relationships that the business regards as high-priority), a standard segment (the bulk of customers), and a new or unproven segment (customers with less than 12 months of payment history). The policy then defines different escalation timelines and tone approaches for each segment.
The segmentation decision is worth explicit discussion because it is the point where finance and sales or account management need to agree. Finance may want to escalate a strategic customer at day 45. Sales may have made a commitment that the relationship manager will handle any collections conversation personally. Documenting that agreement in the policy prevents the AR team from inadvertently stepping on a sales relationship by sending an automated escalation to a customer the account manager considers their direct relationship.
Escalation Timelines: When Does What Happen?
The escalation timeline section of the policy answers the question: at what number of days past due does each type of action occur? The standard framework includes an invoice confirmation contact (often before the due date, particularly for large invoices), a first reminder (typically 3 to 7 days past due), a second reminder (typically 15 to 21 days past due), an escalation to a direct call or escalated message (typically 30 to 45 days), and a formal demand or third-party referral threshold (typically 60 to 90 days).
The specific timelines should reflect your actual customer base and payment terms. A business with net-30 terms serving customers that routinely pay in 45 days should not set their third-party referral threshold at 60 days from due date. That threshold would result in constant escalation on accounts that are slow but reliable payers. The escalation timeline needs to be calibrated to the reality of how your customers actually behave, not to a theoretical payment cycle.
The policy should also address invoice amount thresholds. Many teams apply a different escalation path for invoices above a defined amount (for example, invoices above 500,000 yen) because the cost of the relationship friction from escalation is lower relative to the amount at risk.
Channel Selection: Which Channel at Which Stage?
The policy should specify which communication channels are used at each escalation stage. Email is standard for early reminders because it is low-friction and creates a written record. Phone calls become appropriate at later stages or for high-value invoices where a direct conversation produces faster resolution. Some customer segments respond better to specific channels, and the policy can capture those preferences where they are known.
A channel selection policy also helps with capacity planning. If the team commits to phone contact at day 30 for all invoices above 300,000 yen, that creates a predictable workload for the team to plan around. Without that specification, the decision is made ad hoc and the workload is unpredictable.
We are not suggesting that channel choice should be rigid. Customer behavior data often reveals that a particular customer responds well to SMS and ignores email. The policy sets defaults; individual customer knowledge allows for adjustment. The point is that the default should be explicit, not implicit.
The Dispute Handling Pathway
The policy needs a specific section on dispute handling because disputed invoices require a different process from overdue invoices. When a customer raises a dispute, the collections escalation clock should typically pause. Escalating a collection action on an invoice the customer has formally disputed damages the relationship and rarely accelerates resolution.
The dispute handling pathway should specify: who receives the dispute notification, what information needs to be gathered to investigate, what the target resolution timeline is, and at what point an unresolved dispute gets escalated to management. The policy should also define what constitutes a formal dispute versus a payment query. Customers sometimes use questions about an invoice ("can you resend the invoice with a different PO number?") as an informal delay tactic. The policy can help the team distinguish between substantive disputes that should pause the collections cycle and non-substantive queries that should not.
Third-Party Referral: The Decision Criteria
Most finance teams have a point at which a sufficiently overdue invoice gets referred to a collections agency or to legal counsel for demand. That point is rarely documented precisely. The policy should specify the criteria: is it age alone (90 days past due regardless of amount), amount and age combined (60 days past due for invoices above 1,000,000 yen), or a judgment call that requires management sign-off?
Clarity on third-party referral criteria matters because the decision has commercial consequences. Referring a customer who would have paid without escalation to a collections agency damages the relationship and incurs a fee. Not referring a customer who has no intention of paying delays the recovery and reduces the probability of collecting. The policy should reflect the risk tolerance and customer relationship priorities of the business, not just default to the most aggressive option available.
Review and Update Cadence
A collections policy that is written once and never reviewed becomes outdated. Customer mix changes, payment behavior patterns shift, regulatory requirements evolve. The policy should specify a review cadence, at minimum annual, and assign a responsible owner. The review should assess whether escalation timelines are calibrated to current customer behavior, whether the segmentation criteria still reflect the current customer base, and whether the dispute handling process is working.
The goal of having a written policy is not compliance for its own sake. It is to ensure that the collections process is consistent, predictable, and improvable. A policy that the team refers to and that is updated when reality changes is useful. A policy that is filed and forgotten is not.
