Overdue Invoice Payment Chase v2
Every morning the open sales invoices in Parasut are scanned for ones past their due date with a balance still outstanding. After the owner approves, each customer gets an SMS reminder. Three days later the same invoices are re-read, and only those still unpaid go to a second approval for a firmer notice. Small businesses lose collectable money simply because nobody has time to run the ladder by hand.
A finished operation: the trigger, the steps and the agents it needs, already modelled and validated against the live connector catalog.
Overdue Invoice Payment Chase v2 is a finished operation across Paraşüt, Netgsm. Built for Turkey. Its trigger, steps and connectors are validated against the live catalog.
How it works
Overdue Invoice Payment Chase v2
- Action Satış faturaları (sayfa 1, vadesi en eski)
- Action Satış faturaları (sayfa 2)
- Transform Vadesi geçmiş ve bakiyesi olanlar
- Approval Birinci hatırlatma onayı
- Condition Onaylandi mi?
- Loop Birinci hatırlatma SMS'i
- Transform Hatırlatma gönderilen fatura numaraları
- Wait 3 gün bekle
- Action Faturaları yeniden oku (sayfa 1)
- Action Faturaları yeniden oku (sayfa 2)
- Transform Hâlâ ödenmeyenler
- Approval İkinci kademe onayı
- Condition Onaylandi mi?
- Loop İkinci bildirim SMS'i
- End Bitti
Apps & agents 2
Parasut
Netgsm
Frequently asked questions
How does "Overdue Invoice Payment Chase v2" work?
It runs these steps automatically: Satış faturaları (sayfa 1, vadesi en eski) → Satış faturaları (sayfa 2) → Vadesi geçmiş ve bakiyesi olanlar → Birinci hatırlatma onayı → Onaylandi mi? → Birinci hatırlatma SMS'i → Hatırlatma gönderilen fatura numaraları → 3 gün bekle → Faturaları yeniden oku (sayfa 1) → Faturaları yeniden oku (sayfa 2) → Hâlâ ödenmeyenler → İkinci kademe onayı → Onaylandi mi? → İkinci bildirim SMS'i → Bitti.
Which apps does it connect to?
Paraşüt, Netgsm. Each one is reached through a versioned connector pack — no extra development needed.
How is the Paraşüt, Netgsm integration modelled?
Each provider is modelled as a versioned connector pack, and the steps that need reasoning fall to first-party agents hosted in the same runtime as the workflows.