All collection features

Collection files & lawsuit casesevery follow-up on record

Record every follow-up and promised payment date — and if it goes to court, the case too.

One-month free trial before you buy.

Flows ERP
Collection files & lawsuit cases

01

Collection files with progress and next steps

For each overdue contract, open a collection file and add progress entries: the date, the type (call, visit, LINE, demand letter), whether you reached the customer, their attitude, a description, and attachments. Add a plan for the next step, too. If a customer pays and later falls overdue again, open a new file — earlier files are kept.

  • Progress entries with date and type
  • Customer reached & attitude
  • Next-step plans
  • Several files per contract, history kept
Flows ERP

Collection record — TCH Motors

Call logged

Aug 12 · answered, promised to pay

LINE reminder

Aug 15 · ฿180,000 overdue sent

Demand letter

Aug 22 · copy kept on file

Lawsuit filed

Sep 5 · case documents attached

02

Promised payment dates go into the calendar

When a customer promises to pay on a certain date, record it in the collection file. Flows adds the date to the calendar as a reminder, so your staff follow up on that day.

  • Record the promised date
  • Reminder created automatically
  • Shown in the calendar
  • No follow-up forgotten
Flows ERP

Demand letter — TCH Motors

Letter generated from template

฿180,000 overdue · ฿69,820 penalty

Printed & signed

Authorized signatory · Aug 22

Payment promised

Will pay Sep 5 · added to calendar

Kept in the collection archive

Letter copy · call records

Next: lawsuit pack if unpaid within 15 days

03

Lawsuit cases on a timeline

If a case goes to court, add a lawsuit case with the court, filing date, defendant, lawyers, and cause of action. Then record each stage on the case timeline — hearings, first and second instance, judgment, and enforcement.

  • Court, parties & lawyers
  • Several cases per contract
  • Stages on a timeline
  • Documents attached to each stage
Flows ERP

Penalty interest — live balances

ContractOverdueRateAccrued
SC-04143 days late15% p.a.฿69,820
SC-02712 days late12% p.a.฿8,140
SC-0335 days late15% p.a.฿2,050
Waiver logged on SC-027 · −฿5,000 (negotiated)

Accrues daily by each contract's own rules

Per-period history · payable by cheque too

Inside the module

Real screens from Flows ERP — what your team will actually work in.

Collection file with its progress

Collection file with its progress

Each follow-up — a LINE message, a visit — with who recorded it, when, whether the customer was reached, and their attitude.

Lawsuit case records

Lawsuit case records

The court, filing date, defendant, lawyers, cause of action, and litigation progress for each case.

Why Flows

What makes Flows different

Not another generic ERP — a system built around how Thai SMEs actually buy, sell, and collect.

See how onboarding works
  1. Priced per company, not per seat

    One annual price, every module included. Add users freely within your tier — no feature gates, no seat fees.

  2. Three languages with auto-translation

    Thai, English & Chinese UI — and the data your team enters is translated automatically, so everyone reads the same records.

  3. Your documents, exactly your format

    Send us your invoice and receipt templates; our team configures them into Flows. Every document comes out looking like yours.

  4. We walk you live — and stay

    Five-step onboarding at no extra cost, then quarterly system stability reports. We don't disappear after go-live.

Spec sheet

What collection files & lawsuit cases include — in every plan.

Collection files

Several files per contract; earlier files are kept

Progress entries

Date, type, customer reached, attitude, description, attachments

Next steps

Add a plan for what happens next

Promised payments

Promised dates become calendar reminders

Overdue reasons

Record why a customer is overdue

Lawsuit cases

Court, filing date, defendant, lawyers, cause of action

Lawsuit progress

Hearings, first and second instance, judgment, enforcement

Access

Permissions decide who sees collection records; every action logged

Frequently asked questions

What is a collection file in Flows ERP?

A collection file records one round of collection for an overdue contract. It holds every follow-up, such as calls, visits, LINE messages, and demand letters, along with the next steps and any payment date the customer promised.

Can one customer have several collection files?

If a customer pays and later falls overdue again, you simply open a new collection file. Earlier files are kept, so the full history stays visible.

What happens when a customer promises to pay on a certain date?

Record the promised date in the collection file, and Flows adds it to the calendar as a reminder. Your staff are then reminded to follow up on that day.

How are lawsuits recorded?

Add a lawsuit case with the court, filing date, defendant, lawyers, and cause of action. Then record each stage, such as hearings, first and second instance, judgment, and enforcement, on the case timeline.

Can we attach documents, such as a demand letter?

You can attach files to any progress entry or lawsuit stage. All collection documents are also kept together in the collection document archive.

Who can see collection files?

You decide this with permissions, for example so that only the collections team and managers can see them. Everyone else simply won't see the files.

Keep every collection case in order.

Start a free one-month trial, or book a demo with a real overdue case and we'll set up its collection file together.