Overview Architecture Interfaces & Data Why Mercans

The full inventory · Nothing hidden

Exactly what connects — and what doesn't.

The integration reads a set of documented feeds out of Bob and delivers payslips, GL and bank files back out. Below is the full data inventory and the lifecycle every run goes through — the line-by-line scope your team can audit.

4 inbound feeds from Bob

3 outbound deliveries

Every file hash-stamped & auditable

Integration workflow

In from Bob. Through the PAC. Out to Bob, GL and bank.

INBOUND SOURCE

HiBobREST API · JSON

HR data (master + recurring)

/v1/people/search

Time off (leave)

/v1/timeoff/requests/changes

Actual payments (one-time)

/v1/people/actual-payments/search

Timesheet hours

/v1/company/reports/{reportId}/download

REST · mTLS · IP whitelist · Basic authentication

HRBLIZZ PAYROLL · MERCANS PAC

Mercans API integration

Single web-service user · fetch per pay group

↓

On-demand trigger

Run any time · per pay group

↓

Interface files (PAC)

Pending · Invalid · Errored · Processed

↓

Validate & persist (auto)

Audit trail per persisted file

↓

Payroll processing

Validation → calculation

↓

Payroll outputs

Payslips · GL file · Bank file

OUTBOUND DESTINATIONS

HiBobREST API · PDF

Payslip upload — all employees

/v1/docs/people/{id}/folders/{folderId}/upload

GL / ERP systemSFTP · PGP

General ledger file (XML)

Outbound SFTP · Mercans-hosted · PGP encrypted

BankH2H · SFTP · PGP

Bank payment file (XML)

Host-to-host (H2H) SFTP · bank-hosted · PGP

REST · mTLS · IP whitelist · Basic authentication
SFTP / H2H · SSH key auth · IP whitelist · PGP encryption

LEGEND

REST API over HTTPS

JSON inbound from Bob · PDF payslips back to Bob

SFTP / H2H file transfer

XML GL and bank files · PGP encrypted end to end

Cadence

On demand · run per pay group · full data load

Persistence

Automatic · audit trail per file · errored files rejected & resent

The full interface architecture: Mercans reads Bob through documented REST endpoints, validates every record in the PAC, then delivers payslips back to Bob and GL and bank files to your finance systems over encrypted SFTP / H2H.

Interface inventory

Seven interfaces. That's the whole surface area.

INTERFACEWHAT IT CARRIESDIRECTIONENDPOINT / CHANNELCADENCE

INBOUND · FROM HIBOB

HR data (master + recurring) Personal, employment, work, org & recurring pay, incl. joiners, leavers & changes FROM BOB /v1/people/search Per run

Time off (leave) Requests, balances and changes FROM BOB /v1/timeoff/requests/changes Per run

Actual payments (one-time) One-time payments entered in Bob FROM BOB /v1/people/actual-payments/search Per run

Timesheet hours Prior-period hours from a Bob report FROM BOB /v1/company/reports/{reportId}/download Per run

OUTBOUND · FROM MERCANS

Payslips Payslip PDFs to each employee's Bob profile TO BOB /v1/docs/people/{id}/folders/{folderId}/upload Per run

General ledger GL file (XML) to your GL / ERP system OUTBOUND SFTP · PGP Per run

Bank payments Payment file (XML) to your bank OUTBOUND H2H SFTP · PGP Per run

INBOUND · FROM HIBOB

HR data (master + recurring)FROM BOB

Personal, employment, work, org & recurring pay, incl. joiners, leavers & changes

ENDPOINT/v1/people/search

CADENCEPer run

Time off (leave)FROM BOB

Requests, balances and changes

ENDPOINT/v1/timeoff/requests/changes

CADENCEPer run

Actual payments (one-time)FROM BOB

One-time payments entered in Bob

ENDPOINT/v1/people/actual-payments/search

CADENCEPer run

Timesheet hoursFROM BOB

Prior-period hours from a Bob report

ENDPOINT/v1/company/reports/{reportId}/download

CADENCEPer run

OUTBOUND · FROM MERCANS

PayslipsTO BOB

Payslip PDFs to each employee's Bob profile

ENDPOINT/v1/docs/people/{id}/folders/{folderId}/upload

CADENCEPer run

General ledgerOUTBOUND

GL file (XML) to your GL / ERP system

CHANNELSFTP · PGP

CADENCEPer run

Bank paymentsOUTBOUND

Payment file (XML) to your bank

CHANNELH2H SFTP · PGP

CADENCEPer run

If an interface isn't on this list, it isn't in the integration. That's the entire surface area of the connection.

The processing lifecycle

Every run is fetched, stamped, validated — then paid.

FILE STATUSES PENDING REJECTED INVALID PROCESSED

Record-level validation

Before any pay run, every employee record imported from Bob is checked. Errors and anomalies are counted and surfaced per employee — caught and resolved up front, not discovered after payday.

Full interface monitoring

An operations view tracks every run across Statuses, Logs, Inbound and Outbound — each file traceable by hash, with create / processing / import timestamps, an error count, manual re-trigger and reprocessing.

What sits with the clientConfiguring HiBob's HR and time modules, the local legislation rules inside Bob, and mapping your Bob field codes to payroll are the client's side of the line — done once, with Mercans' guidance and User Guide. The connector consumes that configuration; it doesn't define it.

See the inventory mapped to your own Bob fields.

We'll align the feeds, the data dictionary, and the validation rules to your setup.

Book a session →

Up next · 04

Why Mercans

How the routes compare — and the certified, audited platform behind the connector.

→