> ## Documentation Index
> Fetch the complete documentation index at: https://developer.tryfinch.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Recordkeeper

> Finch Recordkeeper connects payroll to a retirement plan's recordkeeper, syncing contribution and election data directly instead of manual file exchanges.

<Note>
  **Finch Recordkeeper is in Private Beta.** Contact us [here](https://www.tryfinch.com/product/recordkeeper/contact-us) to learn more. This page will expand as the product grows — endpoint paths and data availability may change before general availability.
</Note>

Finch Recordkeeper automates the flow of contribution and election data between payroll and an employer's retirement plan recordkeeper, so payroll providers, TPAs, and plan sponsors don't have to manage that exchange by hand.

The `recordkeeper` Connect scope covered on this page is the entry point to that automation: it captures which recordkeeper administers the plan, and the Plan ID, directly during Finch Connect authorization.

Unlike Finch's other products, Recordkeeper doesn't yet expose a read API — the scope adds an additional step to the Connect flow rather than a queryable endpoint.

## What you can do with the recordkeeper scope

* **Request the `recordkeeper` scope** when creating a Connect session (`POST /connect/sessions`) to add a Recordkeeper step to the Connect flow.
* **Prefill known values** — if you already know the employer's Plan ID and recordkeeper, pass them at session creation and the step renders prefilled and editable, so the end user confirms or corrects them instead of starting from a blank form.
* **Collect a recordkeeper selection** from a supported list and a Plan ID, both required before the end user can continue.

## How the recordkeeper step works

When a Connect session requests the `recordkeeper` scope, Finch Connect inserts a Recordkeeper step between the permissions screen and provider sign-in. The end user selects their recordkeeper and enters their Plan ID; both values are submitted with the authorization request and stored against the connection.

## Supported recordkeepers

* Empower
* Transamerica
* Fidelity

## Common use cases

* **Payroll providers** — offer recordkeeper connectivity as a native feature instead of building and maintaining one-off integrations per recordkeeper.
* **Third-party administrators and advisors** — automate the payroll-to-recordkeeper workflow you currently run by hand, without manual files or reconciliation.
* **Plan sponsors** — connect payroll and the retirement plan once, so contribution and election data stay in sync going forward.

## Recordkeeper scope and permissions

Recordkeeper is its own Finch product scope, `recordkeeper`, separate from Organization and Payroll.

## Next steps

<CardGroup cols={1}>
  <Card title="Request access" icon="clipboard" href="https://www.tryfinch.com/product/recordkeeper/contact-us">
    Contact us here to join the Private Beta.
  </Card>
</CardGroup>