Employee records
Employees from BrightPay, used when a UK payroll question needs the current person.
BrightPay + PaperThread
Connect BrightPay so PaperThread can answer UK payroll questions from the employee and employer records.
How it integrates with BrightPay.
Employer records
Employer context from BrightPay, so the payroll question stays tied to the right employer.
No pay cutoff
The BrightPay API does not expose pay runs, so PaperThread does not flag or invent a pay cutoff from this connection.
Read only
PaperThread reads BrightPay employees and employers. It does not write employee or pay fields back, and bank details are not part of this connection.
How PaperThread puts that
context to work.
Read context
Answer UK payroll questions from BrightPay employees and employers.
Prepare actions
Prepare a follow-up from the employee or employer record.
Route work
Send the next step to the person who owns it.
Update supported items
PaperThread does not write employee or pay fields back to BrightPay. Bank details are not written.
Hand off to a person
Assign a person when BrightPay cannot finish the action.
Common questions, clear answers.
Answers for this connection, including what PaperThread can read and what still needs a person.
It answers UK payroll questions from BrightPay employees and employers. The API does not expose pay runs, so PaperThread does not flag a pay cutoff.
Employees and employers. Pay-run dates and bank details are not part of this connection, and PaperThread does not invent a cutoff.
No. PaperThread does not write employee fields or pay fields back to BrightPay. A change that BrightPay must store stays with a person.
No. BrightPay stays the payroll system. PaperThread uses the employee and employer records to answer questions and keep the case with a person when needed.
PaperThread keeps the case open, assigns a human step, and records what still needs to happen. An unsupported BrightPay action is not marked done.
A workspace admin enters the OAuth access token, organisation id and employer id. The credentials are stored in the credential vault.
Related integrations
Browse all integrations →
HiBob
HRIS people context when a BrightPay question needs the employee record.
Slack
The private DM where a BrightPay question, nudge or approval can be sent.
'%3e%3cpath%20d='M21.1684%20214.263L33.5166%20235.577C36.0825%20240.064%2039.7709%20243.59%2044.1008%20246.154L88.2016%20169.872H0C0%20174.84%201.28293%20179.808%203.8488%20184.295L21.1684%20214.263Z'%20fill='%230066DA'/%3e%3cpath%20d='M140%2080.1282L95.8992%203.84616C91.5693%206.41026%2087.8809%209.9359%2085.315%2014.4231L3.8488%20155.449C1.33012%20159.839%200.00335347%20164.811%200%20169.872H88.2016L140%2080.1282Z'%20fill='%2300AC47'/%3e%3cpath%20d='M235.9%20246.154C240.23%20243.59%20243.919%20240.064%20246.484%20235.577L251.616%20226.763L276.152%20184.295C278.718%20179.808%20280.001%20174.84%20280.001%20169.872H191.793L210.562%20206.731L235.9%20246.154Z'%20fill='%23EA4335'/%3e%3cpath%20d='M139.999%2080.1282L184.1%203.84615C179.77%201.28205%20174.799%200%20169.667%200H110.331C105.2%200%20100.228%201.44231%2095.8984%203.84615L139.999%2080.1282Z'%20fill='%2300832D'/%3e%3cpath%20d='M191.799%20169.872H88.2024L44.1016%20246.154C48.4315%20248.718%2053.4028%20250%2058.5346%20250H221.467C226.599%20250%20231.57%20248.558%20235.9%20246.154L191.799%20169.872Z'%20fill='%232684FC'/%3e%3cpath%20d='M235.418%2084.9359L194.685%2014.4231C192.119%209.9359%20188.431%206.41026%20184.101%203.84616L140%2080.1282L191.798%20169.872H279.84C279.84%20164.904%20278.557%20159.936%20275.991%20155.449L235.418%2084.9359Z'%20fill='%23FFBA00'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_9984_29122'%3e%3crect%20width='280'%20height='250'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e){kind=small}
Google Drive
Approved policy files that sit alongside BrightPay payroll context.
Staffology
Another UK payroll source when the employee is not held in BrightPay.
Connect BrightPay to PaperThread.
Answer UK payroll questions from BrightPay, and keep anything the connection cannot finish with a person.