> ## Documentation Index
> Fetch the complete documentation index at: https://developers.pleo.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Migrate to the Accounting Entries API
> How to migrate from the legacy Expenses API to the Accounting Entries API for custom workflows.
export const WhatComesNext = ({children, href}) =>
;
This guide is for partners who used the [Expenses API](/reference/pleo-deprecated/expenses/get-an-expense-for-a-company) to build custom expense-related workflows — for example syncing expenses to project management software, building dashboards, or generating reports. If you were building an accounting export integration, see [Migrate to the Export API](/deprecation/legacy-expense-api/migration-guide-expenses-api-to-export-api) instead.
## New to the Accounting Entries API?
What an Accounting Entry is and how the API is structured.
Required scope: `accounting-entries:read`.
How to generate standalone API keys for authenticating your integration.
End-to-end guide for authenticating with standalone API keys.
How to make API calls using standalone API keys in Postman.
## Getting Started
You'll need API credentials with at least the [`accounting-entries:read`](/reference/accounting-entries/scopes) scope. Once authenticated, the two main endpoints you'll use are:
Search Accounting Entries
Get an Accounting Entry by ID
## Key Differences
* Field names and structure have changed. See [Field Mapping](#field-mapping) below.
* The Accounting Entries API uses cursor-based pagination.
## Field Mapping
The table below maps fields from the `Expense` model to their equivalents in the `AccountingEntry` model.
* `—` : field is not available in the AccountingEntry model
* `*` : data is the same but represented differently. See the [Accounting Entries API reference](/reference/accounting-entries) for details.
| `Expense` field | `AccountingEntry` equivalent |
| :---------------------------- | :---------------------------------- |
| id | id |
| employeeId | employeeId |
| employeeCode | — |
| departmentId | teamId |
| performedAt | performedAt |
| amountOriginal | transactionValue |
| amountSettled | totalBillValue **\*** |
| note | note |
| type | family **\*** |
| accountId | accountId |
| taxCodeId | taxCodeId |
| createdAt | createdAt |
| updatedAt | updatedAt |
| deletedAt | deletedAt |
| tagIds\[].id | tags\[].tagId |
| tagIds\[].tagGroupId | tags\[].tagGroupId |
| receiptIds\[] | receiptIds\[] |
| settledExpenseIds\[] | — |
| status | status **\*** |
| supplier.CIF | supplier.cif |
| supplier.documentNumber | supplier.documentNumber |
| cardTransaction.state | — |
| cardTransaction.authorizedAt | — |
| cardTransaction.settledAt | settledAt |
| cardTransaction.reversedAt | — |
| cardTransaction.merchant.id | — |
| cardTransaction.merchant.name | — |
| lines\[].amountSettled | splitItems\[].totalBillValue **\*** |
| lines\[].accountId | splitItems\[].accountId |
| lines\[].taxCodeId | splitItems\[].taxCodeId |
| lines\[].tagIds\[] | splitItems\[].tags\[].tagId |
| lines\[].accountCode | splitItems\[].accountCode |
Accounting Entries API Overview
## New Fields in AccountingEntryV1
The following fields are available in `AccountingEntryV1` with no equivalent in the Expense API.
| Field | Description |
| :----------------- | :------------------------------------------------------------------- |
| companyId | Company the entry belongs to |
| accountCode | Account code for the entry |
| bookkeepingDate | Date used for accounting records |
| subFamily | Finer-grained classification within `family` |
| exportStatus | Export state of the entry (separate from `status`) |
| reviewStatus | Review state of the entry |
| attendees | People associated with the entry (e.g. attendees of a business meal) |
| foreignExtensionId | Auto-generated ID used when this API interacts with other Pleo APIs |
## Other Use Cases
For use cases beyond what's described in this guide, please fill in [this form](https://forms.gle/5CHPcM15qH9umGoTA) to let us know.