متابعة الذمم المدينة
يدير متابعة الفواتير المستحقة: يحدّد أي حسابات تحتاج متابعة ومتى، ويكتب رسائل متابعة بنبرة مناسبة مبنية على عمر العلاقة وحجم المبلغ، ويصعّد للإنسان عند الحاجة. يقصّر مدة التحصيل ويحسّن التدفّق النقدي بدون ما يضرّ العلاقات.
المتطلبات تصف قدرات يحتاجها النمط في بيئتك، مو الموردين اللي لازم تشتريهم. أي نظام يملأ متطلباً يحقّقه — وهذا اللي يخلّي الكتالوج قابلاً للنقل عبر الذيل الطويل من أدوات الشركات الصغيرة والمتوسطة.
ar_registerOpen invoices with their aging, customer, and terms.
- AR module of the accounting system
- billing system with invoice records
- ERP receivables ledger
customer_relationship_contextInformation that should affect collection approach: is this customer in active expansion, has there been a service issue, are they a strategic relationship.
- CRM with account state
- customer success platform with account health
- structured account flags maintained by the team
collection_template_libraryApproved language for each stage of follow-up: friendly reminder, firmer follow-up, final notice. Tone matters; templates encode it.
- templates maintained by AR or finance leadership
- library inside the AR tool
- approved drafts from prior collection cycles
customer_communication_channelHow follow-up messages reach customers. Usually email; sometimes portal notifications.
- email send from the AR team mailbox
- customer portal notification
- billing system with built-in notifications
internal_alert_routeWhere account owners (account managers, customer success, sales) get notified when an AR issue might affect the relationship.
- chat alert to the account owner
- task created on the account record
- weekly digest to commercial leadership
human_call_queueWhen email isn't enough — high-value invoices, persistent delinquency, customer issues — the pattern surfaces accounts for human calls with full context.
- call queue for the AR specialist
- task list in the CRM for the account owner
- weekly review with prioritized accounts
payment_event_feedbackWhen invoices get paid, the pattern needs to know to stop the follow-up sequence and learn from what worked.
- payment events from the AR module
- feed from the bank reconciliation pattern E19 if also live
- payment processor event stream
- 01Daily, scan the AR register for invoices needing follow-up: approaching due, just overdue, escalating overdue
ar_register - 02For each candidate, fetch customer relationship context to decide whether to proceed and how
customer_relationship_contextقرار Skip if account has active hold flag or commercial team has paused collections. - 03Determine appropriate stage and pull the matching template
collection_template_library - 04Generate personalized message with invoice details and customer context
- 05Send through the customer communication channel
customer_communication_channel - 06If the account is high-value or delinquent past threshold, alert internal account owner
internal_alert_route - 07If the case warrants a call, queue with full context for the AR specialist or account owner
human_call_queueقرار Threshold based on amount, age, and customer criticality. - 08Watch for payment events and stop follow-up when received
payment_event_feedback
مخرجات منظّمة ينتجها هذا النمط. أنماط ثانية وأنظمة العملاء تقدر تشترك فيها، وهكذا يتركّب الكتالوج مع الوقت.
dso_signalDays sales outstanding trend, the headline AR metric this pattern moves.
- finance dashboards
- controller monthly review
- executive cash flow reviews
collection_effectiveness_signalPer-stage and per-template effectiveness, used to tune the approach.
- AR team workflows
- template library refinement
customer_payment_pattern_signalPer-customer payment behavior over time, useful for credit risk decisions and account planning.
- credit and risk management
- sales when planning expansion
- B5 churn-risk pattern if live