Skip to content
HRMSPayHRMSPay

Integrations

Pay any bank. Post to any ERP.

Send an approved payroll to your bank as the file it expects, and keep the ERP you already run in step: SAP, Oracle, Microsoft Dynamics, IFS or any other system with an API.

Book a demoSee pricing
my-workspace.hrmspay.com/dashboard/integrations

PAY-2026-12-133-1

December 2026 · KCB Bank

Paid, some failed
Payments20
Total1,980,630.89
Pay on25 Dec 2026
Failed1 · Account closed
H1102934857   01  20261225 000020 198063089
D01109876543200 11 011 000000031384115 Daniel Mutua
D01192837465    01 091 000000010580379 Grace Wanjiku
T000020000000198063089

Posted by Daniel Mutua · approved by Grace Njeri

What you get

  • Your bank’s file

    Kenya bulk EFT as CSV or fixed width, or a layout you design column by column.

  • Paid and failed

    Record what the bank paid, then pay the failed ones again once their details are fixed.

  • One poster, one approver

    The person who approved the payroll can’t post it to the bank.

  • Any ERP

    SAP, Oracle, Microsoft Dynamics, IFS or your own system: connect over its API with the fields mapped, not coded.

  • Journals and results out

    Payroll journals with your GL codes, and each person’s results, sent when payroll is approved.

  • Changes in, checked

    New hires and changes from the ERP arrive for review before they touch a record, and failed calls are retried, not lost.

It all works together

Payroll

Payroll that checks itself before anyone is paid.

Explore

Pay rules & formulas

Your pay rules, not ours.

Explore

Statutory compliance

Statutory deductions done right, wherever you pay people.

Explore

Close every month knowing the payroll is right.

See HRMSPay run a month for an organisation like yours, with your pay cycles, your countries and your ERP.

Book a demoSee pricing
  • Statutory rules for your country
  • Your data moved in with you
  • A parallel run before you go live