Embedded benefits for accounting platforms

Embedded benefits for accounting platforms means an accounting, payroll, or tax product offers employee benefits through its own interface instead of pointing customers to an outside benefits vendor. The modules – Meal, Voucher, Mobility, Internet – arrive through an API from a benefits infrastructure that brings the tax logic, the receipt review, and payroll-ready reporting files with it. The extension is not an arbitrary one: benefits and accounting work on the same objects – receipts, per-employee monthly values, postings, and records with a retention period. For the category itself, start with what are embedded benefits.

Four artifacts you already process

Artifact	What the benefit produces	Where it lands in your platform
Receipt	an employee's till receipt or invoice, per working day, reviewed and valued	receipt processing and archive
Monthly value	per employee: the tax-free portion, the taxable benefit in kind, and the flat-rate tax on it	payroll run and payroll account
Posting	benefit expense and flat-rate tax plus solidarity surcharge, both employer cost	coding and period close
Record	the written agreement that the benefit sits on top of salary; for Internet, the employee's statement of their own cost	documentation held with the payroll account

One difference from HRIS and EOR platforms matters here: you are not the employer. An employer of record carries the employer role, and with it the benefit obligation, inside its own product (embedded benefits for EOR platforms); in your model, case-by-case tax responsibility stays with your customer. What your platform contributes is auditability – the values, the receipts, and the files that carry your customer through a wage tax audit. The payroll-side view of the same problem sits in embedded benefits for payroll.

Receipt capture is not receipt review

Pulling amount, date, and merchant out of a receipt does not make it reviewable for tax purposes. The German meal allowance attaches to one main meal per working day, usually lunch, and only to working days without travel. In the first three months of a travel assignment, those days may not be valued at the official benefit-in-kind value (R 8.1 (7) no. 4 (a) LStR; BMF circular of January 5, 2015, BStBl I 2015, 119). Add duplicate submissions, undated receipts, and line items that are not a meal.

The second half is arithmetic. Each receipt splits into a tax-free employer top-up of up to €3.10 and a benefit in kind valued at €4.57, which carries 25% flat-rate tax – paid by the employer and therefore contribution-free (§ 40 (2) sentence 1 no. 1 EStG, § 1 SvEV). How the daily cap of €7.67 divides depends on the receipt:

Receipt amount	Benefit in kind	Tax-free
€2.50	€2.50	€0
€7.67	€4.57	€3.10
€9.67	€2.57	€5.10
€12.24 and above	€0	€7.67

If the employee contributes at least the benefit-in-kind value of €4.57, there is no taxable benefit and no flat-rate tax. None of that sits in the receipt; it sits in the rule, and the rule is reset every year. In 2025 the benefit-in-kind value was €4.40 and the daily cap €7.50. Build receipt review yourself and you maintain those values, and their legal sources, indefinitely.

What reaches payroll each month

Module	2026 frame	Wage tax, social contributions, condition
Meal	up to €7.67 per working day, €115.05 per month at 15 working days	25% flat-rate tax on the benefit in kind, paid by the employer and therefore contribution-free; working days without travel only (§ 40 (2) sentence 1 no. 1 EStG, § 2 SvEV)
Voucher and Benefit Card	€50 per calendar month, €600 per year	tax- and contribution-free within the threshold, no carry-over; on top of salary (§ 8 (2) sentence 11, § 8 (4) EStG)
Mobility (public transport)	no cap, up to the cost of the ticket	tax- and contribution-free, on top of salary; reduces the employee's commuting deduction (§ 3 no. 15 EStG)
Internet	up to €50 per month, €600 per year	25% flat-rate tax paid by the employer, therefore contribution-free; net for the employee but not tax-free in the legal sense; keep the employee's cost statement (§ 40 (2) sentence 1 no. 5 EStG)
Health	up to €600 per year	tax- and contribution-free, on top of salary (§ 3 no. 34 EStG)

Two mechanics slip in practice. The €50 voucher limit is a cliff, not an allowance: at €50.01 the whole amount becomes taxable, and an unused month expires. And the flat-rate tax is employer cost, not an employee deduction – it is declared and remitted, plus the solidarity surcharge and church tax where applicable. Treat it as a net deduction and the error surfaces in an audit, not in the ledger.

Three retention clocks, not one

Record	Period	Legal basis
Accounting records, e.g. the purchase invoice behind a benefit in kind	8 years	§ 257 (1) no. 4 in conjunction with (4) HGB, § 147 (3) sentence 1 AO
Payroll accounts and their attachments	6 years	§ 41 (1) sentence 9 EStG
Books, inventories, annual financial statements	10 years	§ 257 (1) no. 1 in conjunction with (4) HGB

The eight years are recent: the Fourth Bureaucracy Relief Act shortened the period for accounting records from ten years to eight, effective January 1, 2025. The blanket phrase "ten years under § 257 HGB" still appears in guides and help articles, and for accounting records it has been wrong since 2025.

What a wage tax audit asks for

Your customer faces the audit; your platform is where the documents live. Four things have to be producible per employee and month: the reviewed meal receipts, a payroll account that shows the tax-free portion and the taxable benefit in kind separately, evidence that the benefit was granted on top of salary and not through a parallel salary reduction, and the flat-rate tax declaration. For Internet, add the employee's own cost statement. All of it is cheap to log as the transaction happens and expensive to reconstruct two years later – the argument for keeping benefits inside the system that already keeps the records.

Build it or embed it

Task	Build it yourself	With benefits infrastructure
Receipt review	check every receipt against working days, one main meal, and duplicates	individual receipt review at the provider, automated plus a manual re-check
Tax logic	track benefit-in-kind values, thresholds, and the on-top requirement every year	encoded in the module and maintained
Payroll reporting	produce per-employee monthly values in a payroll-ready format	monthly wage tax reporting files
Archiving	run three retention clocks and keep receipts readable	receipts reviewed and archived at the provider
Support	answer your customers' tax questions yourself	1st level enablement, 2nd level with the provider

One point deserves precision, because it tends to get widened. Hrmony assumes tax liability for the receipts reviewed under its individual receipt check, and it does so for the Meal module. For the other modules, case-by-case tax responsibility stays with the employer – your customer. How that split works in detail sits in embedded benefits: compliance and tax liability.

The commercial fit

Accounting and payroll platforms usually bill per client or per employee, so a benefit module drops into an existing shape: a wholesale price per activated module and employee, your own retail price, and the difference stays with you as recurring margin. The revenue scales with the employees inside your client accounts, not with the number of accounts – a figure your platform already holds. The second effect is retention: a benefit is used monthly and often daily, so switching accounting products takes something away from employees who rely on it.

What an integration hangs on

Four questions are worth settling early. First, the client model: the employer carrying the benefit obligations has to map cleanly to one client or company ID, including customers with several sites. Second, mid-month joiners and leavers, because the €50 threshold applies per calendar month and does not carry over. Third, how monthly values reach payroll – your own payroll component, an export in a common format, or a handoff to your customer's tax adviser. Fourth, who owns which support level.

Which modules are available through the API, and how an integration is set up, is on the Hrmony Embedded page.