Embedded payroll infrastructure · EU + APAC
ledra

The ledger of record for global payroll.

Government-sourced country packs, a native gross-to-net engine, and an evidence chain on every write — behind one API. Your platform ships payroll; a new country is a config flag. Ledra computes it and proves it. It never holds your funds.

ledrapay.com Pronounced LED·ra Run. Prove. Lodge.
01The name

Named after the thing it is.

Ledra comes from ledger — the book of record. A payroll system does one job that outranks every other: it has to be the trusted account of what was calculated, under which rule, and whether it was right. Ledra writes that record on every action and makes it the identity, not a footnote.

It reads as one clean word, not a borrowed one. No dictionary owns it, and no negative meaning hides in it across the markets you sell to. Short enough to say once and spell back correctly — the test most names fail. The product goes to market as Ledra Pay, at ledrapay.com.

/ ˈlɛd·rə / — like “ledger,” without the -ger.
02Positioning

The payroll layer under your platform.

Ledra is embedded payroll infrastructure. It computes gross-to-net correctly in every jurisdiction through a native engine and government-sourced regulation packs, evidences every write in an immutable chain, and lodges to the authority. It sits underneath other platforms as a neutral layer — your customer stays your customer, your brand stays on the screen.

The gap was never “we ran payroll.”
It was “we ran payroll correctly.”

Most payroll failures are not calculation failures. They are record and proof failures. Ledra closes that gap by treating the evidence as the product, not the receipt.

Ledra does not hold or move funds. It computes, proves, and lodges, and hands payment files back to you. No custody is a feature: less risk to embed, less to license, faster to adopt.
03The loop
/ 01

Run

Gross-to-net through one engine and the country’s government-sourced pack. The API never changes shape between jurisdictions.

/ 02

Prove

Every state-changing write lands in a hash-chained evidence record. “Why was this payslip this number” is one API call.

/ 03

Lodge

Finalised runs submit to the authority through the pack’s rail — STP, RTI, payday filing — or return statutory output files.

04Primitives

What makes it one integration.

Four ideas carry the product. They are also the brand’s proof points — concrete, checkable, and hard to copy.

Jurisdiction is a parameter

Government-sourced regulation packs

Country logic lives in independently versioned, government-sourced packs. Statutory updates ship as pack releases, never silent behaviour changes. Compliance is an API object, not a PDF.

Never a wrong answer

The capability matrix

Engines genuinely differ. Each feature is native or unsupported per binding, and an unsupported call returns a clear 501 with alternatives instead of a quietly wrong number.

One call to the truth

The evidence chain

Actor, reason, inputs digest, pack version, result digest — hash-chained on every write. The auditor’s question has a deterministic answer.

Trust before go-live

Shadow runs

Calculate against the incumbent and return a line-level variance report. Prove the numbers before a single live run. Never lodges, never pays.

05Logo

The mark is a closed book.

Three recorded entries above a double rule — the line accountants draw under a verified, final total. It says exactly what the product does: the entries are written, the run is finalised, the total is proven.

Primary lockup
ledra
Reversed
ledra
Glyph only
Wordmark ledra
06Color

In the black.

The palette is a ledger. Ink and paper carry everything; one disciplined green marks what is computed, evidenced, and correct. Oxblood appears only on a variance or an unsupported capability — a real exception, never decoration.

Ink
#16181D
Text, surfaces, the mark
Paper
#F6F4EF
Ground. Warm, not white
Reconciled Green
#0E6E4E
Accent — proven, native
Oxblood
#9E3B2D
Variance / 501, rare
Slate
#5E6168
Secondary text
Rule
#DAD6CD
Hairlines, dividers
07Type

Engraved headers, a clear hand, ruled figures.

A real ledger has three voices: the engraved heading, the clerk’s legible hand, and the tabular column of figures. The type system keeps all three.

DisplaySchibsted Grotesk
Run. Prove. Lodge.
BodyHanken Grotesk
Every write lands in a hash-chained record. The book always reconciles.
Figures & labelsIBM Plex Mono
net AUD 2,591.85 · pack AU-2026.1 · evd_a90b
0 1 2 3 4 5 6 7 8 9 — tabular, aligned, never ambiguous
08Voice

Say it like a ledger would.

Plain, exact, and quiet. Ledra states what happened and what will happen. It does not sell, soften, or embellish. If a sentence has a marketing adjective in it, cut the adjective.

Declare, don’t pitch

Short declarative sentences. The evidence is the proof; the copy doesn’t need to argue.

“Jurisdiction is a parameter.”
“A powerful engine that revolutionises global payroll.”

Name the real thing

Use the operator’s words — pay runs, packs, lodgement, evidence — not system internals.

“Lodge a finalised run to the authority.”
“Emit downstream event-sourced artifacts.”

Exact over impressive

A pack version, an evidence id, a status carries more trust than a claim.

“Computed under AU-2026.1 · evd_a90b.”
“Best-in-class accuracy, guaranteed.”

Never a wrong answer

When an engine can’t do something, say so plainly and offer the alternative. No faking, no sorry.

“Effective-dating isn’t supported on this pack. Here’s what is.”
“Oops! Something went wrong.”
09Naming architecture

Ledra plus a plain noun.

Surfaces map to the real API, named with ordinary words rather than coined sub-brands. Plain nouns stay neutral, which is the point: a platform embedding Ledra puts its own name in front without fighting a brand system. This is deliberately the opposite of a captive product suite.

Ledra Engine
Native gross-to-net. One calculation core behind every pack.
Ledra Packs
Government-sourced, versioned country rulesets. Jurisdiction as a parameter.
Ledra Runs
The pay-run lifecycle: draft, preview, approve, finalise.
Ledra Shadow
Variance runs against the incumbent. Proof before go-live.
Ledra Lodge
Statutory rails — STP, RTI, payday filing — and output files.
Ledra Evidence
The hash-chained record. The answer to “why this number.”
Ledra Components
White-label SDK surfaces the partner re-skins and embeds.

Named to be embedded, not owned. “Rails” here means statutory lodgement rails, never payment rails — Ledra does not move money.

10Applied — ledrapay.com

The brand, in one screen.

Get sandbox keys →

The ledger of record for global payroll.

Government-sourced country packs, a native engine, and an evidence chain on every write. One API your platform builds on. Ledra computes and proves. It never holds your funds.

Pay run · pr_8f2c · AU-2026.1
draft → previewed → approved → finalised
18 employees · engine-computed
Pack AU-2026.1 · government-sourced
Every write evidencedcev_
Finalisedevd_a90b
▪ Proven · “why this number” in one call