Third-Party to FinancialForce Application Integrations

You can create and update resources in PSA directly from the worker information stored in your third-party HCM application using the PSA Resource API.

The feature enables you to:

• Securely integrate between your third-party HCM application and PSA
• Create resources as contact or person account records, as appropriate
• Update existing resources when a record is modified in your third-party HCM application
• Send personal and contact information, as well as employment status and manager details
• Ensure that you allocate resources in PSA based on up-to-date information
• Use the data transformation features in Foundations to transform data received via the API so that it is appropriate for the target field in the subscribing application
• Create up to 15 custom mappings to send additional information from your third-party HCM application to the PSA resource record

The feature uses an off-platform REST API. For more information about the new PSA API, see PSA REST API Developer Reference on FinancialForce Community.

Authentication and authorization are provided by Salesforce. For more information, see the Salesforce Developer API documentation.

You can automatically create and update assignments in PSA that represent a resource's time off using the PSA Assignment API. The API enables you to send information from your third-party HCM application to PSA to provide accurate visibility of your resources' availability.

The feature enables you to:

• Create assignments and schedules to represent a resource's time off
• Create timecards and timecard splits for the dates within a time off request
• Update a time off request to reflect a change in approval status or a change to the dates in the request
• Cancel time off in hours or days and automatically update the related timecards, schedules, schedule exceptions, and assignments, as required
• Specify the project to which a time off assignment relates
• Specify which policies you want to use to create time off details in PSA
• Update existing assignments when a record is modified in your third-party HCM application
• View the overall status of the time off request in PSA
• Use the data transformation features in Foundations to convert data received via the API so that it is appropriate for the target field in PSA

Days and Hours

You can send time off details based on hours or days, to suit your organization’s requirements. PSA records time off as hours in a timecard. If you send a quantity in days, PSA calculates the number of hours this represents based on the hours specified in the resource’s work calendar.

PSA prevents you from entering more than 24 hours for a single date in a timecard.

Schedules and Assignments

If you use the API to record time off for different days in consecutive weeks against the same assignment, PSA creates the following:

• A new schedule for the details in the first week
• A schedule exception for the details in each subsequent week when the time off does not match the days in the schedule

If additional time off is requested against the same assignment in a subsequent request, PSA updates the date of the schedule and creates a schedule exception, if required.

You can create journals in FinancialForce Accounting directly from the information stored in your third-party applications using the Accounting Journal API.

This feature enables you to:

• Securely integrate your third-party application with Accounting
• Create journals and journal line items using data from your third-party application, such as payroll data
• Automatically derive the period of a journal, based on the date and company provided
• Specify the general ledger account to which you want to add your line items
• Send details for up to four analysis dimensions
• Create up to five custom mappings to send additional information from your third-party application to journal line items
• Automatically add a custom description to all journals created via the API to help identify third-party data
• Specify how Accounting splits journals, based on maximum line limits, and designate a general ledger account to use as a suspense account
• Specify the custom description to add to all balancing lines automatically created via the API
• Review the journal and journal line items in Accounting before posting the journal
• Use the data transformation features in Foundations to convert data received via the API so that it is appropriate for the target field in Accounting

Journals created through the API are of type Manual Journal.

Splitting Journals

When you send data that exceeds the Manual Journal Line Limit in Document Line Volume Settings, Accounting automatically enters a balancing line and creates the remaining data as a separate journal.

The Manual Journal Line Limit can only be updated by FinancialForce. To do this, contact Customer Support.

Example 1

If the Manual Journal Line Limit is 250 and you send data that equates to 400 journal line items, Accounting does the following:

• Creates one journal containing lines 1-249
• Creates a balancing line in that journal, which is associated with the suspense account specified in FDN Accounting Messaging Settings, to ensure the Journal Total is zero
• Creates a second journal that contains lines 250-400
• Creates a balancing line in the second journal, if required, to ensure the Journal Total is zero

Example 2

If the Manual Journal Line Limit is 250 and you send data that equates to 250 journal line items, Accounting creates only one journal.