Workday
Joiners and leavers, without a ticket.
People
Finly + Lattice
People · Two-way sync · Live since 2025 · About 10 minutes to connect
What it does
Finly takes its approval chain straight from Lattice's reporting lines, so an expense goes to the manager who actually manages. Departments and locations ride along, and nothing about reviews or goals is ever read.
What syncs
What moves, and which way.
Both directions, on every sync.Nothing here is a nightly batch —a record that changes at 14:02 is in the ledger before you look at it.
Lattice → Finly
- Employees and their work email
- Direct and dotted reporting lines
- Departments and their leads
- Locations and their currency
- Start date and status
- Manager changes, as they happen
Finly → Lattice
- Card and account status, per employee
- Department spend, back on the team
- Reimbursement totals per period
Connected
What it looks like once it is on.
The org chart, doing real work.
A new starter in Lattice arrives with a card limit, an approver and a cost centre already set, and a leaver's spend stops the same hour.Nobody maintains a second list of who works here.
Before you start
What you need, and what it will not do.
You need a Lattice account with people-admin rights and a Finly plan on Core or above.Finly reads the directory, not the record:name, work email, manager, entity and cost centre come across, and nothing that looks like salary, health or performance data ever does.
Two things it deliberately will not do.It will not create or deactivate anyone in Lattice —the people system stays the source of truth and Finly follows it.And it will not close a leaver's account by itself:it freezes the card the same hour and puts the account in a queue for a human, because an automatic close on a bad feed is a locked-out employee.
Related
Others in people systems.
Get started
Stop closing the month in arrears.
Book a 30-minute demo and we'll run your own last month through a sandbox, so you can see the close before you commit to anything.