How Kini reads vacancies from Abacus Umantis and files applications into it.
Abacus Umantis splits a vacancy into titled text blocks and keeps applicants and applications as separate records. Five things Kini does with that structure, from reading a published vacancy to filing the finished application.
Externally published vacancies, in the languages you choose
Kini imports the vacancies the end customer has published for external candidates in Abacus Umantis, in the content languages set for that customer, German (Switzerland) unless configured otherwise. A language version is imported only where the vacancy is marked as published on the external website and has text in that language, so internal postings stay out of Kini.
Job text in sections, not one long block
Abacus Umantis holds a vacancy's text in up to eight titled text blocks. Kini sorts them, mainly by their headings, into introduction, tasks, profile, benefits and contact, puts them in that order and keeps each as its own section next to the full description. A vacancy without text blocks falls back to its short description.
Employer, location and contact person taken from the vacancy's links
A vacancy linked to a branch office takes the branch name as its employer name, and where the vacancy names no place of work, city, street and postcode come from that branch. The HR manager linked to the vacancy, or otherwise its manager, becomes the job's contact person, with name, business email address and direct phone number.
Applicant and application filed the way Abacus Umantis expects
Kini first creates the candidate in Abacus Umantis as a person of the applicant type, with salutation, name, email, mobile number, address and, where the channel provides them, birth date, LinkedIn and XING profiles and photo. It then creates the application linked to that person and to the position, with CV, cover letter and further documents attached.
Every application's source, in the customer's own terms
Kini writes the channel an application came from into its source text, with channel names that can be mapped per end customer. Where the end customer wants Kini applications under an entry from their own list of application sources, Kini also sets that entry as the source of information, so they appear under a value the customer already uses.
Every field. Every entity.Exactly where it belongs.
Three kinds of record pass between Abacus Umantis and Kini. Published vacancies come in as jobs, and each application from a connected channel goes back as an applicant record plus an application linked to it. The key fields use the attribute names of the Umantis ATS API.
Jobs
Applicants
Applications
Abacus Umantis keeps applicants and applications as separate records, so Kini creates the applicant as a person first and then the application, linked to that person and to the position.
Operations like GET, POST, PATCH are documented per endpoint in the . The primary source for field definitions. Kini adds mapping and fallback logic on top.
End-to-end GDPR consent
Every application that flows through Kini carries a consent flag, mirrored on the target system's side and traceable in audits.
Native-language custom fields
Locations, departments and sources are mapped correctly even when they use German naming conventions or regional variants, whether your customers sit in DACH or operate internationally.
Application flows for a wide range of job boards
Stepstone, Indeed, Jobrapido and regional boards each have their own required fields, screening patterns and encoding rules. Kini's mapping engine is trained for those: out of the box, not as a custom project.
Operated by the Kini team
Kini runs the connection for you, including monitoring and alerts. If a vendor changes an API or a mapping breaks, our team fixes it before it reaches your funnel. Operated from Germany.
Frequently asked questions about the Abacus Umantis integration.
What Abacus Umantis is, which records Kini exchanges with it, and how applications are filed on the Abacus Umantis side.
Abacus Umantis is the HR suite of Abacus Umantis AG in St. Gallen, a wholly owned subsidiary of Abacus Research AG. Umantis belonged to the Haufe Group from 2012 to 2023. Kini connects to its applicant management. The Abacus Human Resources software has its own applicant management and is a separate product with its own Kini page.
Both reach the applicant management of Abacus Umantis, through different interfaces. This integration works through the Umantis ATS API, the interface Abacus Umantis documents for connecting its applicant management to other applications. Kini's Umantis integration files applications through the Umantis SOAP import instead and is described on a page of its own.
Vacancies come in with title, job text in sections, place of work, salary range, start date, work schedule, reference number and contact person. Applications go out: Kini creates the applicant as a person and then the application linked to it, with CV, cover letter, further documents, the source and answers to a channel's own screening questions as remarks.
No. Abacus Umantis remains the end customer's system of record, where vacancies are written and published and where applications are reviewed. Kini reads the published vacancies so they can be distributed to further channels, files the applications those channels bring back, and runs that connection as a managed service on your behalf.
Access to the Umantis ATS API. Abacus Umantis documents that the API has to be activated in the customer's own settings, with its terms of use accepted, before anything can use it. Requests from partners for access to specific parts of the API are accepted or rejected there, and access can be changed or withdrawn at any time.
Not for applications Kini files. The Umantis ATS API lets the system that creates an application decide whether Abacus Umantis sends its welcome email to the applicant. Kini creates every application with that option switched off, so the welcome email is not sent for applications that reach Abacus Umantis through Kini.
As text. Where a channel asks its own screening questions, Kini writes each question with its answer into the remarks field of the application, together with any note the candidate added. They are not filed as Abacus Umantis application questions, which the Umantis ATS API supports per position as free text, single choice and multiple choice.
Abacus Umantis refuses the application, and Kini records the refusal as an expected outcome with its reason rather than as a failed sync. Where a fallback position is set up for the end customer, Kini files the application to that position instead, so the candidate still reaches Abacus Umantis.
On Kini's side, application data is processed in Frankfurt, within the EU, and a data processing agreement is available. Abacus Umantis states on its own site that it hosts in Switzerland and Germany. Kini hands each application to Abacus Umantis itself, so nobody on your team has to download, store or forward applicant files.
Trusted by recruiting teamsacross europe.
From enterprise HR platforms to lean recruiting boutiques. Teams use Kini to connect their tools without involving engineering. Here's what they say.
"Kini syncs candidates from Perspective straight into our customers' ATS. That saves us manual transfers and around four hours a week."
"Kini gets enterprise customers on SAP SuccessFactors live much faster. Fewer technical hurdles in sales, around 20% more conversion."
"With Kini, we sync candidates straight into our customers' ATS through 65+ integrations. We don't need an extra full-time hire for it."
