Skip to main content

Collections

The Collections module is intended for receivables and payables follow-up: outstanding balances, statements, reminders, and dunning notices.

Important Availability Note​

In the current live demo tenant used for this documentation pass, the Collections route returned a “not found or no access” page. That means this module appears to be feature-, edition-, or permission-dependent in practice.

For that reason, the workflow below reflects the intended functional model of ZeyOS, but not a currently accessible live demo screen.

No live screenshot is included for this article because the module could not be opened in the demo tenant.

What This Module Is For​

Use Collections when payment follow-up must become a structured process rather than an informal reminder outside the system.

Typical Functional Areas​

Collections is designed around several sub-areas:

  • Receivables for outstanding customer-side amounts
  • Payables for supplier-side liabilities that still need settlement context
  • Statements for account overviews
  • Reminders for early payment follow-up
  • Dunning notices for escalated collection communication

Typical Workflow​

  1. Start from open invoices or other outstanding items.
  2. Review overdue balances by account and due date.
  3. Generate a statement if the customer or supplier needs a consolidated overview.
  4. Send a reminder.
  5. Escalate to a dunning notice if required.
  6. Close the process once payment is received or the item is otherwise resolved.

Where Users Usually Need More Clarity​

Collections is often confused with:

  • Payments, which record actual money movement
  • Invoicing, which creates the receivable in the first place
  • Procurement, which creates supplier-side liabilities

The clean separation is:

  • Invoicing / Procurement create the underlying transactions
  • Payments settle them
  • Collections manages overdue follow-up when settlement has not happened on time

Best Practices​

  • Treat collections as a controlled escalation workflow.
  • Align reminder and dunning rules with finance policy.
  • Train users to distinguish clearly between “open”, “paid”, and “overdue but not yet escalated”.