A synthetic receivables day

Illustrative amounts in PHP. This page saves no data and sends no reminders.

Try a receivables workflow

Everything here is synthetic and resets when you reload. No messages, bank transactions or ledger records are created.

Cebu Logistics

Outstanding: ₱5,300.00 / Paused dispute: ₱1,300.00 / Chaseable: ₱4,000.00

Next action: confirm a receipt date with accounts payable. Review the paused dispute separately.

1. Reconcile the opening book

Import 100 invoices and historical receipts. Review matched, duplicate and problem rows before committing. A reused invoice number needs a customer or source reference.

2. Work one customer at a time

Cebu Logistics owes ₱5,300. ₱1,300 is paused for a dispute; ₱4,000 remains chaseable. One contact owner sees the reply, task and next call together.

3. Apply one receipt

A ₱1,000 receipt applies ₱600 and ₱300 to two invoices. ₱100 stays unapplied with its source reference. The review lists both balance changes before posting.

4. Decide with cash evidence

Recorded bank cash, dated commitments and scheduled obligations form the conservative projection. Expected receipts can be included or shifted 15 days late; overdue unconfirmed amounts stay separate.

Build a workspace from scratch Choose another demo path

Sample outcomes are examples, not measured savings or a forecast of customer payment. Live sending and purchase availability depend on deployment configuration.