WageRun Rails

South African payroll infrastructure with the responsibility attached.

Versioned calculation, input provenance, close evidence and partner operations for approved embedded use cases.

Discuss a Rails design partnership See the contract shape

Infrastructure, not a mystery box

The same run carries its source, rule version and evidence state.

Rails is designed for platforms that need payroll depth without pretending that an API response is approval, submission or statutory acceptance.

Illustrative sandbox responsev1

{
  "run_state": "REVIEW_REQUIRED",
  "country_pack": "ZA-PENDING",
  "input_snapshot": "sha256:…",
  "calculation_authority": false,
  "named_approval": false,
  "external_submission": false
}

Partner operating model

Embed the rail without blurring who is accountable.

Versioned country pack

Sources, effective dates, implementation, corpus results and release approval remain separate evidence.

Tenant-bound operations

Credentials, scopes, usage, support cases and revocation are designed around exact partner and tenant resources.

Responsibility matrix

Embedded platform, employer, bookkeeper, WageRun and any submission partner keep explicit duties.

South Africa first

Country depth earns expansion.

The first production country pack must pass current-source review, a representative signed corpus, independent comparison and qualified approval. Additional African packs follow signed partner demand and the same gate.

SourceCurrent, effective and owned

CorpusRepresentative and signed

ReviewIndependent and qualified

ReleaseSeparate QMS decision

Current availability

Rails has local sandbox and contract foundations. No production keys, hosted OAuth service, contracted SLA or signed design partner is claimed.

Contact partnerships