Integration · Payroll
Otto HR payroll, in the modelevery completed pay run, filled in on its own.
Payroll is the largest line in most forecasts and the easiest to understate. Otto HR is the payroll Replafin connects to: paste a read-only key and each completed pay run lands on the payroll line with its gross total and headcount, so the actuals are what was really paid and the hiring plan projects forward from the real number.
What Replafin reads
The lines Otto HR fills
We read completed pay runs and their totals; we never build, approve, run or cancel a payroll.
- Staff
- Kind
- Payroll
- Connects by
- Paste a read-only key
- Time to connect
- about 2 minutes
How to connect
- 01In Otto HR open Settings → API Keys and click New key.
- 02Pick the HR scope and name it "Replafin". Copy the key: it starts with ottohr_hr_ and is shown once.
- 03Paste it here. We check it against your workspace and read the completed pay runs.
- 04Past pay runs load in a minute, and each new run lands on the payroll line once it is completed.
Free. The key reads gross pay per run; the employer's share of SGK and benefits is not in that read, so add it by hand or leave the rule to estimate it.
What happens next
What the forecast does with Otto HR
Completed pay runs fill the payroll actual for each month, dated to the period they pay for. The roles you plan to hire sit on top with their start dates, so next month's payroll in the forecast is this month's real run plus the hires that begin, and runway reflects both. The employer's share of SGK and benefits is not in Otto's read, so the loaded-cost rule adds it, or you type it.
Live connections refresh themselves when they are more than six hours old. Every row a sync writes lands on the changes log, and anything it cannot categorise with confidence waits for you in Review. The cash flow forecast guide shows how the months ahead are built from these actuals.
Questions
Otto HR, answered
Where do I get the key?
In Otto HR, Settings → API Keys → New key, with the HR scope. The key starts with ottohr_hr_ and is shown once; paste it into the connect dialog. Portal keys cannot read pay runs. Otto rate-limits keys at sixty requests a minute, which a sync never approaches.
Why Otto HR and not Gusto or Rippling?
Replafin connects to one payroll, and Otto HR is it: it prepares the bordro and the run is the record, so the payroll line reads a completed run, not a spreadsheet of it. If your payroll lives elsewhere, export the run as a CSV with one row per person and import it; the picker knows the layout.
Does Replafin write anything back?
No. Every connection is read-only by construction: restricted keys, read scopes or a Plaid link that cannot move money. Replafin reads balances, transactions and reports; it never posts, edits or deletes anything in the source.
How often does it sync?
Live connections refresh themselves when they are more than six hours old, and you can refresh on demand. Every row the sync writes lands on the changes log, and anything it cannot categorise with confidence waits for you in Review instead of being guessed.
Which plan includes integrations?
All of them. Connectors are part of the workspace on every plan; nothing about the bank, books or payroll links is gated by tier.
Other sources: QuickBooks Online, Xero, Stripe, Mercury, Brex, Your bank, via Plaid, CSV or XLSX.
Connect Otto HR.Forecast from real numbers.
Open the workspace, connect the source in minutes, and the model opens on the balances you actually have. Plans from $200 a month.