Q: My company isn’t using SAP or a TMS. Can we still use FinLync?
A: Yes. FinLync apps are currently available for use with SAP. More ERPs are coming soon, sign up to be notified when Oracle apps become available. We also offer the option to connect directly to our multi-bank API aggregator, BankLync, which exposes a RESTful API allowing integration across any ERP or TMS. Request a demo for more information.
Q: What is required of the corporate when a bank changes or upgrades their API?
A: FinLync handles the maintenance of bank API connections and we remain in ongoing communication with our global banking partners even after individual projects conclude. As a result, we are made aware of upcoming updates. In turn, we ensure our quarterly/monthly releases are timed to capture these changes accordingly. Product release updates are performed via simple transport uploads in SAP.
Q: Are you a competitor to legacy TMS systems?
A: Depending on your unique needs, FinLync can sit alongside a legacy TMS or can be a standalone tool.
Q: What bank APIs does FinLync currently connect to? What if one of my banks is not already offered? What happens if one or more of my banks does not offer APIs?
A: FinLync is constantly adding new bank API connections. View a list of what banks are live or are in progress via the FinLync API Catalog (coming September 2021). If your bank is not listed, or if you’re not sure if your bank offers APIs, simply submit a request and we’ll reply within 48 business hours.
Q: My bank has an API. Why shouldn’t I just connect directly to it?
A: Connecting to 1 single bank API is an arduous task, much less multiple APIs at multiple banks. Read more about this topic on our Multi-Bank API Connectivity page.
Q: What does support look like after I go-live with FinLync apps?
A: FinLync clients have a dedicated Client Success Executive as their point person for any issues that arise after go-live as well as a dedicated support desk to handle any functional issues that arise.
Q: What does it mean that your apps are ERP-native?
A: Native apps are a type of software that installs directly into an existing software system so you can perform specific tasks. In our personal lives, nearly everyone already uses native apps on their smartphones – iPhone apps are iOS-native apps, and Android apps are Android-native. But apps aren’t limited to just phones, they can install into all kinds of software systems, like your company’s ERP. FinLync offers treasury apps that are ERP-native.
Q: What SAP versions are supported?
A: FinLync works seamlessly with most versions of SAP, including all ECC 6.0 versions as far back as EHP4 and all S/4HANA versions.
Q: How does FinLync work with upgrades from ECC to S4?
A: The FinLync suite of apps is built for simplicity from the ground up. FinLync code is the same code in both S4 and ECC systems so no migration is required and apps function as expected following the system upgrade. For green-field S4 implementations, the same transports used in your ECC system can be installed in S4, and you are ready to go.
Q: How does FinLync work when you have multiple instances of SAP?
A: FinLync code is deployed in all instances of SAP and relevant setup is done for relevant companies and accounts in that system. Each system takes less than 1 hour. All of these systems are linked to a single front end SAP system via RFC connections. The end result is a centralized view where your organizational operations can be displayed and managed.
Q: What SAP modules are required to use FinLync?
A: No additional SAP modules are required for FinLync applications.