RemotePass posts your payroll costs into SAP S/4HANA through SAP's own APIs, already coded with the cost centers and projects synced from SuccessFactors. The numbers your finance team sees in SAP are the numbers on our invoice, entered once, by the system, with SAP's own checks applied. Where the API route is not available in your SAP landscape, the same coded output is delivered as a reconciliation report every payroll cycle for your finance team to post.
How It Works
1. Connection Your SAP team provides RemotePass with API access to S/4HANA: an OAuth 2.0 client or a technical user, over an encrypted connection. This works for S/4HANA Cloud, where the standard APIs are available by default, and for on-premise or private cloud installations, where your SAP team exposes the same standard APIs through SAP Gateway or Integration Suite.
2. Your finance master data, read from SAP RemotePass reads your company codes, GL accounts, cost centres, projects and the vendors you created for RemotePass directly from S/4HANA. Mapping is done against your live SAP IDs; nothing is typed by hand, and a code that is retired in SAP is flagged in RemotePass before anything is posted.
3. GL account mapping Under Integrations → SAP S/4HANA → Settings → GL Account Mapping, map each RemotePass cost component to your GL account, per company code:
Base salary
Allowances
Employer social contributions
Health insurance premiums
End-of-service accruals
RemotePass service fee
Adjustments and FX differences
4. Posting When a RemotePass invoice is paid, RemotePass creates a supplier invoice in S/4HANA, one per company code, with one line per cost component coded by GL account, cost centre and project, in your invoice currency. Each line carries the worker's cost center. SAP applies the payable account from your vendor master.
5. Confirmation The SAP document number is stored on the RemotePass invoice. Each invoice shows its status, Posted, Parked or Failed, with SAP's own message when something needs attention, and can be re-sent after the fix.
Is the API route available to you?
Most S/4HANA installations can use it. During implementation we review your SAP landscape with your finance and SAP teams and configure the route that fits your structure:
S/4HANA Cloud: the standard APIs are available; your SAP administrator creates the communication user and we connect.
S/4HANA on-premise or private cloud: your SAP basis team exposes the standard supplier-invoice and master-data APIs and issues credentials; we connect the same way.
API access is not possible in your landscape: the reconciliation report below carries exactly the same coding, and your finance team posts it. Nothing about the data changes; only the last step does.
Reconciliation report
For every payroll cycle, RemotePass generates a reconciliation report with one line per worker and cost component: amount, currency, company code, cost centre, project and mapped GL account. Totals reconcile to the invoice. It is available for download in the platform and can be delivered on schedule. Finance teams using the API route keep it as the audit companion to the postings; teams without API access use it to post.
Supported Data
Data | Direction | Purpose |
Company codes, GL accounts, cost centres, projects | S/4HANA → RemotePass | Mapping against live IDs; validation before posting |
Supplier record (RemotePass) | S/4HANA → RemotePass | Posting reference and payable account |
Supplier invoice with coded lines | RemotePass → S/4HANA | Cost allocation and payable in one document; post or park |
Credit memo | RemotePass → S/4HANA | Corrections and refunds |
Reconciliation report | RemotePass → Finance | Audit companion, or posting source where APIs are not available |
Multi-Entity Setup
If you invoice several company codes or currencies, mapping, posting options and reports are maintained per company code, with one RemotePass entity per company code. Company codes, currencies and vendor records are confirmed during implementation planning.
Prerequisites
Cost centres and projects maintained in SuccessFactors and synced to RemotePass
API access to S/4HANA provided by your SAP team, and the vendors RemotePass will post to, created in your vendor master.
GL account mapping completed by your finance team
An SAP cost center assigned to every worker in RemotePass.
Frequently Asked Questions
What if our SAP team cannot expose the APIs?
You receive the reconciliation report every payroll cycle with the same GL, cost centre and project coding, and your finance team posts it. The data is identical; only the last step is manual.
Do you post journal entries?
Payroll costs from an EOR provider are posted as supplier invoices with coded lines, which creates the payable and the cost allocation in one document.
Does RemotePass change anything in SuccessFactors or S/4HANA master data? No. RemotePass reads master data and creates finance documents; it never edits employee records, cost centres or GL accounts.
To read more about how integration works, see How does SAP S/4HANA Finance Integration Work?