Payment promises and payment schedules
Review a detected promise or approve a negotiated schedule without treating it as received payment.
Updated
In short
A payment promise remains a customer statement, not proof of collection. When a reply proposes several installments, Billabex structures the schedule and opens an approval task. After human confirmation, amounts are allocated across the relevant invoices and follow-ups wait for each due date without marking the payments as received.
Expected result
The promise or approved schedule reflects the customer commitment and adjusts follow-ups without recording a false payment.
Before you start
- Review the message where the customer explicitly commits.
- Compare date, amount, and currency with account documents.
Procedure
- Open the situation summary and find the active promise or schedule task.
- Check the source message, dates, amounts, and currency proposed.
- For several installments, review the displayed allocation across the relevant invoices.
- Approve only when it matches the agreement; otherwise reject it or request a correction.
- Review forecast and, after each due date, wait for synchronized payment before deciding it was honored.
What Billabex does
Billabex keeps the promise as context. A negotiated schedule takes effect only after human approval; installments are allocated across invoices in order, and each due date pauses the corresponding follow-ups. No commitment settles an invoice before real payment arrives.
If the result is not what you expected
- A vague date or inconsistent total must be clarified before approval.
- Rejecting a proposal stores no schedule and keeps the task available for follow-up.
- When payment arrives, wait for synchronization instead of editing the commitment manually.