Members can use this kit when planning or executing a Workday Financial Management implementation that connects to multiple banking institutions.

Before using this tool, complete these actions:

• Confirm licensing for the appropriate Workday Bank Connectivity SKU.
• If the customer is still MSA, the Innovation Service Opt-In is required to start the Kyriba database provisioning and enable the delivered connectors.

Review these core architectural designs, configuration standards, and security policies before establishing your integration landscape:

• Solution Architecture: Workday Bank Connectivity is powered by Kyriba, which operates as a subprocessor for managing global bank integrations.
• Golden Database Assets: Kyriba maintains a comprehensive list of supported banks, countries, and payment profiles within a Golden Database. This database establishes standardized mappings and naming conventions to enable repeatable asset reuse and eliminate 1-off custom scripts per project.
• Integration Standards: Joint standard documentation specifies address-field usage per country and covers extended fields. Using standardized bank naming conventions and external mapping identifiers unlocks predictable integration reuse across environments.
• Multi-Tenant Complexity: Aligning reference data between a Workday tenant and a Kyriba tenant is highly technical, especially when multiple Workday tenants connect to a single Kyriba tenant. Document which Workday tenant owns specific mapping entries to prevent data collisions. 
• Sandbox Operating Expectations: Workday uses a multitenant unit and end-to-end (E2E) testing model, whereas Kyriba operates on a Production-first model. Aligning these different environment strategies early maps risk and test flows correctly to prevent Sandbox misunderstandings.
• User Interface Access and Security: The system operates similarly to a service bureau, meaning members generally don't require direct access to the Kyriba user interface (UI) for routine operations. Exceptions apply for specific tasks such as Electronic Banking Internet Communication Standard (EBICS) signing. When UI access is necessary, configurations must enforce single sign-on (SSO), multifactor authentication, and limited access profiles to reduce operational risk.
• Troubleshooting Boundaries: Many support cases stem from mapping and setup configurations rather than technical connector defects. During platform failures, explicit incident retry guidelines dictate whether to resend payments or wait, preventing duplicate file transmissions.
• Support and Escalation Architecture: In resell scenarios, Workday owns the service-level agreements (SLAs), and Workday Support coordinates directly with Kyriba Support. Members escalate all issues through Workday rather than using a separate Kyriba escalation path. Workday Support manages file transmission, mapping, and scheduling between Workday and Kyriba. For issues regarding Treasury Management Functions within Kyriba, members must engage Kyriba or their designated Kyriba implementation partner.
• Value Added Services Engagement: If members require a new bank logo setup or subsequent configuration changes within Kyriba after the initial deployment, the Kyriba Value Added Services team engages directly to deploy the updates. Contact workday@kyriba.com for information regarding these services.
• Proven Outcomes: Implementation data from previous deployments demonstrates significant efficiency gains:
  • Custom integration maintenance is eliminated through native connectors.
  • The solution fully automates manual payment file corrections.
  • Bank file transmission fees decrease significantly.
  • The solution reduces new bank Onboarding effort.

Review these technical deployment guidelines, testing recommendations, and baseline timelines intended for services personnel and partners:

• Standard Project Timelines: Establish baseline expectations early in the sales cycle. Core bank connectivity typically requires 4–6 weeks. Complete implementation requires 8–12 weeks for bank reporting and an additional 8–12 weeks for payment origination.
• Testing Lifecycles: Project teams spend most deployment hours during E2E testing validation cycles with banking institutions, not during the underlying technical build or integration-mapping phase. Set expectations early that introducing new banks or complex debt scenarios requires extensive validation time.
• Bank-Specific Testing Quirks: Certain financial institutions exhibit specific behaviors during the testing phases. Example: Certain banks don’t provide payment acknowledgments within test environments, which create a temporary verification gap before go-live.
• Onboarding Coordination: Bank Onboarding is a joint process involving the customer, Workday, the bank, and Kyriba consulting. Workday services personnel confirm core readiness on the Workday side, while Kyriba defines the connectivity method and security models, including encryption and certificates. The customer remains responsible for coordinating and scheduling Onboarding meetings with the bank.
• Kyriba Database Playbooks: For customers migrating to a new Kyriba database or connecting an existing Kyriba instance, Kyriba services or implementation partners must execute specific Kyriba-side scripts and steps.
• High-Volume Configuration: For deployments with exceptionally high transaction volumes, configure the scheduled settlement run with a holiday calendar feature to streamline settlement runs.
• Support Transition Handoff: The initial post-go-live support window for payments spans 2–3 days of close observation before completing a tightly scripted handoff to Workday Platinum Support.

To prepare your tenant for a successful deployment and go-live cycle, follow these sequence steps:

1. Download and complete the standardized configuration workbook.
2. Align project definitions with the Workday and Kyriba Shared Terminology Glossary to ensure all teams use a shared language.
3. Agree on all bank names, account identifiers, and mapping keys across Workday, Kyriba, and the financial institutions before finalizing configuration.
4. Validate your core configurations against the supported banks, countries, and payment profiles listed in the Golden Database.
5. Establish at least 1 successful complete Production payment cycle for each connected bank.
6. Create a comprehensive runbook defining which team acts as the 1st line of support for specific error types, including Workday, Kyriba, the implementation partner, or the bank.