Why Your Startup's Second Market Reveals a Hidden Receivables Problem

Jan de Vries · 2026-09-18

European expansion exposes whether a startup has a real receivables process or just a collection of habits that worked back home. Winning a customer in a second European market feels like validation. The sales playbook travels, the product is accepted, and suddenly the company looks genuinely international. Then an invoice goes overdue. That moment is a useful operating test. The European Commission's Payment Observatory reported that 52% of European companies faced problems caused by late payments in 2024. It also found that average payment periods exceeded 60 days in both business-to-business and government-to-business transactions. For a startup, the real issue isn't just the delay. It's whether the team can make a clear, timely decision when the customer, contract, and enforcement route all sit in another country. Call it the second-market test: if an overdue invoice can only be handled by the person who remembers the customer, the email thread, and the local convention, the company has expanded faster than its receivables process. ### Standardize the trigger, not every conversation Founders often try to fix this with a universal reminder sequence. That helps with routine admin, but it doesn't resolve the important differences between cases. A missing purchase-order reference is not the same as a dispute over delivery. A customer who has promised a payment date is not in the same position as one who has stopped responding. The useful standard is the decision trigger: what must be true before the case moves from normal follow-up to an exception queue, executive review, or external recovery? A practical trigger can combine invoice age, value, dispute status, the latest customer commitment, and the number of failed contact attempts. The wording of the next message may vary by market and customer. The evidence needed to make the decision should not. ### Make the evidence portable Cross-border escalation becomes slow when the commercial record lives across a founder's inbox, a CRM note, a billing platform, and a shared drive. Before entering a new market, define the minimum case file that another person could understand without oral history. That file should identify the contracting entities, agreed payment terms, invoice and delivery evidence, relevant correspondence, dispute status, and the latest promised payment date. It should also show who owns the next action and when it becomes overdue. The goal is not bureaucracy—it's portability. A local finance colleague, adviser, or recovery partner should be able to see the same chronology and distinguish an administrative error from a genuine credit problem. In Germany, for example, a company may need local execution once an internal process has reached its limit. The operational handoff is much cleaner when the case file is ready before the team starts considering debt collection in Germany. ### Use three clocks One date rarely tells the whole story. A growing company should track three clocks: - The invoice clock: how long the amount has been overdue. - The promise clock: how long since the customer committed to an action or payment date. - The decision clock: how long the case has waited for an owner to choose the next step. The third clock is often the neglected one. Teams can spend weeks sending reasonable reminders while nobody is accountable for deciding whether the case is disputed, at risk, or ready for escalation. Measuring time to decide exposes that hidden delay. These clocks also prevent a familiar reporting error: activity is not progress. Five emails can leave a case in exactly the same state, while one documented customer promise or one escalation decision materially changes it. ### Keep the core process European and the execution local Expansion doesn't require a different operating model for every country. It requires a common model with deliberate local branches. The common layer should define case stages, data fields, and decision triggers that apply everywhere. The local layer should account for market-specific norms, legal requirements, and escalation routes. A startup that masters this balance turns cross-border receivables from a source of chaos into a competitive advantage. It can expand faster, collect more reliably, and keep its team focused on growth instead of chasing overdue invoices.