Agda PS: Integration

Modified on Wed, 8 Oct at 1:10 PM

Agda PS: Integration 
 
Overview 

With this integration you will connect Simployer One to your Agda PS account via SFTP and can then do the following: 

  • Scheduled or manual sync of employee data such as personal information, employment data, compensation data and more from Simployer to Agda PS.

Available in: Sweden

Agda PS requirements 


  1. SFTP server access 
    You must request a dedicated SFTP account from Agda PS support. Agda PS will provide the credentials to enable Simployer One to deliver the XML file(s). 

  1. Agda import job setup 
    Agda PS must configure an import job to automatically process these XML files from your SFTP file area. 

Note: When configuring the integration, you can choose to send the files to either folder Test\Importfiler or Prod\Importfiler on your Agda PS SFTP area. You can use this during the setup process together with Agda. 

Note: There may be setup and ongoing service fees from Agda PS for file processing. 


How Agda PS File Transfer Works 

When your integration runs, Simployer One automatically creates employee files in Agda PS XML Person Export format and sends them to your Agda PS SFTP import area. 


Multiple Organizations 

If you have multiple organizations in Simployer One, you'll get one file for each organization. This makes it easier to import data into Agda PS separately and for Agda PS to understand which organization should go to which Adga PS company. 

File Names 

Files are named to help you identify them: 

[Organization ID]-[Organization Name]-employees-[Date and Time].xml 

Example: 1-Acme_Corp-employees-20250103-143022.xml 

File Location 

Files are delivered to the folder you chose during setup. 

 

Set up in Simployer

The integration is activated from Settings → IntegrationsSelect payroll systemAdd integration

 

 

  • In the API Integrations section, select Agda PS

  • Click Next to start the configuration wizard

  • Enter all the details needed for the connection

  • Optionally: set up a specific scope (which employees to include in the sync) and/or a scheduled sync from Simployer to Agda PS

 

Settings

You can choose how the integration sync for employees is executed. The options available are as follows:

  • Manual sync

    • The data is manually synced to Agda PS by the user

    • This can be valuable if you have the scheduled sync turned off and want to control when data is synced to Agda PS. Either during the implementation phase or during times when an update is not wanted due to process and payroll timing

    • Manual syncs can be performed even when a scheduled sync is configured. This may be necessary if there have been a significant number of changes in Simployer after a scheduled sync has been executed

  • Scheduled sync

    • The sync runs on a schedule that you can define

    • Options include the day(s) of the week and the time of day for the sync to be executed

 

Note : Currently the sync is queued and it starts shortly after 06:00 CET.


Scope

  • The edit scope settings allows for more granularity on what employee will be part of the automatic or manually triggered employee export. This is useful if you know that not all of the employees should be exported to Agda PS.

  • The scope selection follows the standard scope selection that exists in Simployer.

     


Employee data

Overview

Employee data is synchronized from Simployer to Agda PS. This means that if data is updated in Adgda PS on "data fields" and then the sync from Simployer is done the data in Agda PS will be overwritten.

 

When the sync is executed it will compare the data in Simployer for the "data fields" to see if there is a difference between the values for those fields in Agda PS. If there is no change, the user will not be updated. If there is a change present, the data will be updated.

 

Some fields are currently hardcoded, see below for more information.


Data fields

Personal Information

Simployer One

Agda PS XML Field

Notes

Person.employeeNumber 

ANST_NR 

Required - Long integer (1-999999999999) 

Person.nationalIdList[0].nationalId 

PERSNR 

Required - Swedish SSN format 

Person.firstName 

FORNAMN 

Required 

Person.lastName 

EFTERNAMN 

Required 

Person.gender 

KON 

MALE→"M", FEMALE→"K", other→"" 

Person.email 

EMAILADRESS 

 

Person.birthdate 

FODELSEDATUM 

yyyy-MM-dd format 

Person.nationalIdList[0].country 

MEDBORGARSKAP 

From nationalId, not address 

Employee.organizationId

FTG_NR 

If organizationId missing, hard-coded to “1”


Address Information

Simployer One

Agda PS XML Field

Notes

Person.address.streetAddress1 

ADRESS 

Home address only 

Person.address.postalCode 

POSTNR 

 

Person.address.city 

ORT 

 

Person.address.country 

LAND 

 

Person.phoneNumber 

TELEFON 

Mobile address entry 

(hard-coded) 

ADRESSTYP 

"Hemadress" for address, "Mobiltelefon" for phone 

(hard-coded) 

GALLANDE 

true for home address, false for mobile 

Section omitted when: No address data AND no phone number present


Position Information

Simployer One

Agda PS XML Field

Notes

Employee.jobTitle 

BEFATTNING 

Section omitted if empty or null 

(hard-coded) 

BEFATTNINGSSTATUS 

Hard-coded: "H" 


Employment Information

Simployer One

Agda PS XML Field

Notes

Employee.hireDate 

ANSTALLNINGSDATUM 

Required for active employees 

Employment.endDate 

AVGANGSDATUM 

Only if person inactive OR no ongoing employment 

Employment.employmentType 

ANSTALLNINGSFORM 

permanent_employment→"Tillsvidareanställning", probation_employment→"Provanställning", hourly_employment→"Timanställning", fixed_employment→"Vikariat", consultant→"Konsult" 

Employment.startDate 

TILLTRADE 

Per employment period 

Employment.endDate 

TILLTRADETOM 

Per employment period 


Working Time

Simployer One

Agda PS XML Field

Notes

Employment.rate 

SYSSELSATTNINGSGRAD 

From mainEmploymentId employment only. Section omitted if no mainEmploymentId OR main employment not found 


Bank Account

Simployer One

Agda PS XML Field

Notes

Person.bankAccount.clearing 

CLEARINGNUMMER 

Section omitted if no bank account data 

Person.bankAccount.accountNumber 

BANKKONTONUMMER 

 

(hard-coded) 

UTBETALNINGSTYP 

Hard-coded: "Löneutbetalning" 

(hard-coded) 

UTBETALNINGSSATT 

Hard-coded: "Bankkonto" 


Organization

Simployer One

Agda PS XML Field

Notes

Group.groupName 

AVDELNING 

 


Salary Components

Simployer One

Agda PS XML Field

Notes

Payroll.payoutPeriod 

LONEART 

MONTHLY→"70", HOURLY→"10" 

Compensation.compensationAmount 

BELOPP 

For MONTHLY salary (amount) 

Compensation.compensationAmount 

PRIS 

For HOURLY salary (price) 

Payroll.payrollEffectiveDate 

DATUM_IN 

Start date (as XML attribute) 

(calculated) 

DATUM_UT 

End date (day before next payroll starts) 

(type-specific) 

FASTAARTER_TYP 

"A" for MONTHLY, "P" for HOURLY 

 

Limitations 
  • Absence data is not synchronized. 
  • Only employee information is transferred—no leave, absence, or time reporting data. 
  • No real-time updates; the integration operates via batch file transfer up to once per day or on manual trigger. 
  • Only employees with valid Swedish personal numbers and employee numbers are processed. 
  • Recently terminated employees are included only for 30 days after end date. 


Troubleshooting & questions 

  • For technical questions around XML output from Simployer One, contact the Simployer support. 
  • For inquiries about setting up Agda PS import jobs and SFTP access, contact Agda PS support. 

 

Example XML output 
If needed, you can request a sample of the XML file output from the Simployer Integration Team for review.  
 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article