Federation with Teampay
Federation allows you to create separate, distinct instances of Teampay, which are centrally administered. Your Teampay instances can mirror how your organization is structured, subsidiary or entity-wise, allowing spend to be correctly attributed, managed, and reported on, per the needs of the greater organization.
Federation includes:
- Separate accounting, more accurate reporting
- Separate roles, rules, holding accounts, funding sources (macro + micro approval policies)
- Centralized User directory: Cross-subsidiary switching
- Different base currencies (EUR, GBP, CAD, AUD, INR, ILS, PHP, PLN, SGD, CHF and more to come)
- … all while maintaining an easy to navigate, common end-user experience.
Configuring Federation
* Indicates this step is required for each subsidiary
Prior to configuration, provide Teampay with the following requirements:
- Submission of User Assignment List
- A list of user emails and their corresponding subsidiary/entity.
- A list of users that need request/approval in multiple instances. A sample csv template can be found here. (By default, federated users are given access to the specified instance.
- The indication of the currency each subsidiary will be configured in.
1) Connect Bank Account*
- Once the subsidiaries are created (your CSM or the Support team can advise on timeline), an admin can switch into each subsidiary by heading to the web app > settings > switch organizations
2. Once in the subsidiary, head to settings > bank accounts, and connect a bank account via Plaid or ACH.
See Subsidiary Funding below for more information on funding mechanics
2) Connect your ERP*
-
Head to settings > organization settings > connect accounting
-
Connect to your accounting system, taking care to select the subsidiary/entity and accounts that are relevant to the subsidiary you are in.
-
Review Settings
-
Check your dimensions to ensure they’re relevant to each subsidiary (ex. Are all your GL accounts relevant for your operations in France?)
-
Configure Approval Policy
-
Configure your approval policy for each subsidiary. This can be identical or independent of your primary sub’s policy. Some examples of ways to configure this are:
-
Managerial hierarchy via HRIS upload
-
User profile/request parameter based (ex. Department = Customer Success, then assign to Chuck Norris)
-
If your federation package consists of an assisted federation onboarding, Teampay will guide you through the implementation
Subsidiary Funding
Subsidiaries are currently fundable via our debit-based model. Teampay connects to your bank account, and withdraws funds for a holding account within our platform, used to fund your organization’s purchase requests.
Currently, all subsidiaries need to be connected to a USD-based bank account, regardless of the local denomination to be used.
Teampay does not charge foreign exchange fees for subsidiaries utilizing a different currency. The FX fee is determined by the spot rate, which we pull via a 3rd party FX API partner.
Comments
0 comments
Please sign in to leave a comment.