Integrations and export
HRAI sends approved attendance and pay components to Israeli payroll systems through 13 connectors. Each connector states a confidence level, and a file whose critical field is only an assumption is held: generated and reviewable, but not sent until a payroll accountant signs off the mapping. HRAI prepares the inputs; your payroll department keeps calculating pay.
104Company no.32607Year-month4000004471Employee no.9305123457ID no.9בGross10—1122Component30000018250Quantity10+±10000000000Price10+±1000Client3······Filler61Type1Each field carries its own confidence level. For Michpal and Shiklulit (TAMAL) the structure comes from the vendor’s official document; for systems that have not published a specification, the fields are marked as assumptions and the file is held until a payroll accountant signs it off. The one-character gross field holds a Hebrew letter, as the specification defines it.
Last reviewed
For readers outside Israel
Israeli payroll is usually calculated by a payroll department: an in-house team or an external payroll service, working in a local payroll system. HRAI does not replace it. HRAI collects and approves the inputs, attendance, leave, expenses and changes to terms, and delivers them in the format that payroll system imports.
The list
This table is derived from the connector catalog in the code, the same module that generates the files for customers. A new connector appears here by itself, and a confidence level that changes after calibration is updated here.
| System | Confidence | Structure | Delivery |
|---|---|---|---|
| Michpal | Documented | Fixed-width, 62 characters | Sent directly |
| Shiklulit (TAMAL) | Documented | Fixed-width, 126 characters | Sent directly |
| Hilan / Hilan-Tech | Assumed | CSV, structure set per customer | Held until the mapping is signed off |
| Oketz Trio | Inferred | CSV | Sent directly |
| Harmony (Synel) | Assumed | CSV, structure set per customer | Held until the mapping is signed off |
| Merav | Assumed | CSV, structure set per customer | Held until the mapping is signed off |
| Shomrit | Assumed | CSV, structure set per customer | Held until the mapping is signed off |
| Hargal | Assumed | CSV, structure set per customer | Held until the mapping is signed off |
| Hashavim Otzma | Assumed | CSV, structure set per customer | Held until the mapping is signed off |
| Malam Payroll | Assumed | CSV, structure set per customer | Held until the mapping is signed off |
| Hashavshevet | Assumed | CSV | Held until the mapping is signed off |
| Priority | Assumed | CSV, structure set per customer | Held until the mapping is signed off |
| Generic CSV | Documented | CSV | Sent directly |
9 of the 13 connectors are currently in held delivery. That is not a gap, it is the statement: most long-established Israeli payroll systems do not publish their attendance import structure, and it is set per customer with the payroll accountant. “Verified” is reserved for a connector checked against a real accepted import file, and no connector is at that level today.
From attendance to payroll
Six stations. The two amber ones are gates: a file that fails the round trip, or whose mapping is not signed off, does not go out.
How it is checked
The file is generated, then parsed back by a parser derived from the same specification. A byte in the wrong position fails the check and the file is stopped. CSV has no positions to break, so there the readable twin is the check.
Not on the connector, on the field. The connector’s level is set by its weakest field, because one field in the wrong position spoils the whole record.
A critical field at the assumed level means the file is generated and downloadable but not sent to the payroll department. The payroll accountant’s sign-off on the mapping is what releases it.
Every file gets a table: employee, component, code, quantity. The payroll accountant reviews that, not the ASCII.
Why all this is needed: long-established Israeli payroll systems have no test environment. There is no sandbox and no API to run an integration test against, and no way to know a file was accepted other than asking the payroll accountant. So correctness has to come from the structure itself.
For your accountant
The CFO or HR enters an address and chooses which reports: hours, pay, or the payroll file.
One email with a one-time activation link goes out. Until it is clicked, nothing is sent there.
On the chosen day, for the previous month. It can also be sent manually at any time.
What was sent, to whom, how many employees, and a SHA-256 fingerprint of the file, with a backup to download again.
✓ on a number: a gate, where the next step waits for a person’s approval
A pay report requires pay permission for every employee in scope, not just some of them: a partial report sent to the payroll department looks exactly like a full one, and the difference only shows on the payslip. An hours-only report is not a sum of money, so it needs no pay permission, and it has no ID numbers, salaries or bank details in any column.
Not on the list
You submit a request from inside the system and attach what you have: the interface specification your vendor gave you, a historical import file your system already accepted, or the API documentation. We review it and build a dedicated connector, a file in your format or a connection to an external API.
The connector starts in held mode, because every field in the draft is marked as an assumption: it produces a file for review and does not send it to the payroll department until the payroll accountant signs off the mapping. One custom connector per company, at extra cost.
The bottom line
What these numbers do not say: a connector that is not in held delivery is sent directly, and that includes connectors whose structure comes from an official document or from integration documents, not from a real import file that was accepted. That is why the confidence level is shown to the payroll accountant before every export.
Reviews the readable twin and signs off the mapping that releases a held file.
Approves attendance and leave, and locks the month.
Chooses the accountant’s address and gets a receipt for every delivery.
Sets up SFTP delivery where the connector uses it.
Guide: getting attendance to the payroll department without errors →
Frequently asked
To the main Israeli payroll systems, 13 connectors in all: Michpal, Shiklulit (TAMAL), Hilan / Hilan-Tech, Oketz Trio, Harmony (Synel), Merav, Shomrit, Hargal, Hashavim Otzma, Malam Payroll, Hashavshevet, Priority, Generic CSV. The generic CSV is accepted by most payroll departments, and there is a request path for a dedicated connector to a system that is not listed. A system that is not listed is not supported today, and we say so rather than claim to connect to everything.
There are four levels: verified against a real import file that was accepted; documented from the vendor’s official specification; inferred from third-party integration documents; and assumed, our best estimate, labeled as such. We show it because some Israeli payroll vendors do not publish their attendance import structure, which is then set per customer with the payroll accountant.
That is the normal case, not the exception. You upload one historical import file that your payroll system has already accepted, and HRAI aligns the specification with it and updates the confidence level. Alternatively, you attach the interface specification your vendor gave you.
Every fixed-width export makes a round trip: the file is generated and then parsed back by a parser derived from the same specification. A single byte in the wrong position fails the check and the export stops. CSV has no fixed positions, so instead every file, of either kind, gets a readable twin, the same data as a table, which the payroll accountant reviews instead of raw ASCII.
Yes. You set a destination email address, and it must confirm itself through a one-time activation link before anything is sent to it. After that the report goes out monthly, and every delivery leaves a receipt with a SHA-256 fingerprint of the file that was sent and a backup copy you can download and compare.
There is a path for that. You submit a request from inside the system with the interface specification or a sample import file, and we build a dedicated connector, either a file in your format or a connection to an external API. It starts in held mode and produces a file for review, which is not sent to the payroll department until a payroll accountant signs off the mapping. One custom connector per company, at extra cost.
Quantities only for hour components, on purpose. Some payroll systems calculate the payment from the hours themselves, and sending an amount as well would cause a double calculation. Amounts are sent only for components that are amounts by nature, such as expense reimbursements and travel allowance.
Get started
Leave your details and we will get back to you within one business day to set a time for a 30-minute demo on your own processes. If it turns out not to be a fit, we will say so.
About the details you share. Data controller: Career and Content ltd (operator of HR AI), company no. 515523934, [email protected]. You are not legally required to provide them; without a name and email we cannot get back to you, and that is the only consequence. The information is used to respond to your inquiry, kept for up to 24 months, and shared only with our email provider and our sales team. You may review, correct or delete it at any time at the same address — Privacy Policy (Hebrew), English summary.
Essential cookies run the site and cannot be switched off. Everything else is your choice, and you can change it whenever you like. Cookie policy (Hebrew), English summary.