Mark an accounting entry ready to sync
Approve an entry for syncing. Nothing is sent to the accounting platform until the entry is synced. If anything required is missing, such as a line without an account, returns entry_not_ready listing what to fix.
Authorizations
User API key authentication. Create a key under Settings → API keys in the Slash dashboard (https://app.slash.com/global-settings/api-keys) and send the x-legal-entity header naming the legal entity to act on with every request. Keys scoped to a legal entity are rejected with 403 user_api_key_required.
Headers
The legal entity to act on. Required on every request; a user API key can act on any legal entity its user has access to.
^le_[a-zA-Z0-9]+$Path Parameters
Entry id with the accounting_entry_ prefix.
Response
The entry, now ready_to_sync.
The accounting record for one settled transaction (or group of related transactions) or one bill. An entry is created automatically when its source settles, coded with dimensions on its line items, and then synced to the connected platform. status tracks that lifecycle.
Entry id with the accounting_entry_ prefix.
"accounting_entry_2rj4l7hmrrrcv"
The accounting connection the entry belongs to.
"accounting_connection_2rj4l7hmrrrcv"
What the entry represents on the platform. expense_card and expense_card_refund come from card transactions; bank_transfer, bank_deposit, and expense from account transactions; journal_entry from transactions posted as journals; bill is the accounts-payable bill and bill_payment the transaction that settles one. unknown entries have not yet been classified.
unknown, expense, bank_transfer, bank_deposit, journal_entry, expense_card, expense_card_refund, bill_payment, bill in_review until a user or rule marks it ready; ready_to_sync when coding is complete; pending_sync and syncing while a sync is queued or in flight; synced once the platform holds it; failed when the platform rejected it (see lastSyncError); archived when excluded from the books.
in_review, ready_to_sync, pending_sync, syncing, synced, archived, failed When status last changed.
"2026-09-19T14:05:22.000Z"
Accounting date as YYYY-MM-DD: the settlement date of the source transaction or the invoice date of the bill.
"2026-09-18"
Net amount in minor units. Negative for money leaving the account (expenses, bill payments) and positive for money arriving. On a bill's entry it is the bill's total, which is positive.
What the entry was created from.
Every transaction the entry covers. Usually one; internal transfers and card repayments combine two.
Ordered fixed lines first, then editable lines by splitIndex.
For bill entries, the dimension keys coded per line item. Dimensions not listed take the same value on every line. Empty for transaction entries.
Dimension keys the platform records once per entry rather than per line item. Every line item carries the same value for these, and a split cannot code them differently across its lines.
Dimension keys the platform does not accept for this entry type. Any value set on them is dropped at sync time.
Raw values of entry level custom fields, keyed by the field's fieldKey from GET /v2/accounting/dimensions.
"2026-09-18T20:11:02.000Z"
"2026-09-19T14:05:22.000Z"
Memo sent to the platform.
"AWS hosting, September"
The platform's id for the synced record. Present once status is synced.
"1234"
A link to the record in the platform, when the platform provides one.
"https://app.qbo.intuit.com/app/expense?txnId=1234"
Why the most recent sync attempt failed. Present while status is failed.