How it fits your workflow.
Finastra Phoenix is a core banking platform. For a connected account workflow, the distinction between customer relationships and individual deposit or loan accounts is important. Teams should work from the institution's actual product definitions so account status and financial information keep their intended operational meaning.
WORKFLOW FOCUS
Phoenix core account context and customer relationships.
From your stack to your workflow.
01 / Map the outcome
Choose the process you want to improve and the records, events, or actions it depends on.
02 / Define the connection
Review supported capabilities, access permissions, field mapping, and policy requirements with your Paypath team.
03 / Validate before expanding
Agree on a focused workflow, test it with your team, and confirm the results before extending the scope.
A few things to know.
Which record should anchor a Phoenix-related service task?
Use the appropriate account reference alongside the customer relationship. A customer identifier alone may not identify the loan or deposit account being discussed.
Can we keep our existing systems?
The starting point is your current stack. We work with your team to understand where each record lives and how the proposed connection should fit your operating model.