payment-collection — process narrative

Payment & Invoice Collection

15 Flow(s) · 0 Task creation(s) · 4 Apex class(es) · 0 trigger(s) on related SObjects.

Invoice issuance → payment request → authorisation (DD or card via Asperato) → collection. Handles reminders and cancellations.

Focus SObjects: Invoice__c, asp04__Payment__c, PaymentRequest__c, asp04__Authorisation__c

Flows involved

Flow	Trigger	Creates Tasks	Updates Objects
Asperato Payment After Insert Flow	asp04__Payment__c (Create)	—	—
Asperato Payment After Update Flow	asp04__Payment__c (Update)	—	—
DD Payment Authorisation for Client	Flow	—	—
Initiate Payment Authorisation Screen Flow	Flow	—	—
Initiate Payment Request Screen Flow	Flow	—	—
Invoice After Update Create Asperato Payment Record	Invoice__c (Update)	—	—
Invoice Before Update Populate Invoice Sent Date	Invoice__c (Update)	—	—
Invoice Cancellation Approval Flow	Invoice__c (Update)	—	—
Invoice Sent Reminder Email	AutoLaunchedFlow	taskSubject	—
Issue Invoice Screen Flow	Flow	—	—
Pause Payment Request Screen Flow	Flow	—	—
Payment Request After Save Create Draft Invoice	PaymentRequest__c (CreateAndUpdate)	—	—
Process Immediate Payment	AutoLaunchedFlow	—	—
Re-Issue Invoice Screen Flow	Flow	—	—
Reinstated Payment Request Screen Flow	Flow	—	—

Tasks created by this process

None matched.

Apex classes matching this process

Class Name
InvoiceBatch
InvoiceNumberGenerator
sendRecurringPaymentInvoice
ShowRecentInvoicesController

Apex triggers on focus SObjects

None (or all are in managed packages).

End-to-end storyboard (Mermaid)

Notes & caveats

This narrative is assembled heuristically from the process registry patterns. It will pick up most of the process but may miss Flows/Tasks/Apex that don’t match the naming conventions. Dig into the individual Flow/trigger docs for the authoritative view.