Payment follow-up should never create a second financial truth. The ERP or approved finance system remains the authoritative record for schedules, receipts, balances, and reconciliation; the buyer-operations layer uses that context to organize approved reminders, capture evidence, and route discrepancies to finance. That separation lets teams move routine work forward without telling a buyer that a payment is settled when the system of record says otherwise.
Key takeaways
- Treat the ERP as the source of financial truth and the buyer-operations layer as the coordination surface.
- Separate a buyer’s payment promise, proof of payment, ERP receipt, and reconciliation outcome.
- Make every discrepancy visible with a named finance owner and next action.
- Do not auto-confirm, forgive, reallocate, or alter a balance outside approved finance policy.
The four records that should not be collapsed
| Record | Meaning | Authoritative owner |
|---|---|---|
| Scheduled obligation | What the payment plan calls for | ERP or approved finance system |
| Buyer communication | What was requested, sent, or promised | Approved communication history |
| Payment evidence | What the buyer supplied | Original file or payment channel evidence |
| Reconciliation state | What finance has matched, rejected, or needs to investigate | ERP and finance review |
When these records are merged into “paid” or “unpaid,” the team loses the reason an item needs attention. A buyer may have sent evidence while finance has not matched it; a scheduled payment may be overdue but covered by an approved exception. The status question needs the right source and owner, not a guess.
A controlled follow-up queue
Build a queue with the following decision columns: buyer and unit, due item, authoritative schedule status, last approved communication, evidence received, reconciliation state, exception flag, owner, and next action. Then use a daily sequence:
- Pull only schedule and receipt data approved for operational use.
- Identify items that meet the project’s reminder policy.
- Send approved reminders; retain the message and context with the buyer record.
- Attach submitted evidence without changing the financial state.
- Route unmatched, duplicate, short, late, or disputed items to finance.
- Update buyer-facing status only from an approved source or an authorized finance response.
Human review and exceptions
Finance owns reconciliation, adjustments, credits, refunds, allocation, and any commitment about a balance. Asterisko can keep the buyer context, schedule reference, evidence, messages, and handoff in one operating view. It must escalate when a record conflicts or a decision changes financial obligations. That boundary is especially important where different teams communicate with the buyer and reconcile cash in separate systems.
Where Asterisko fits
The payment operations workflow explains the operating boundaries in more detail. Pair it with the CRM and ERP integration guide to keep source records connected, and with buyer status-question governance to keep communication aligned with finance-approved context.
