Skip to main content
Once a company connects an accounting platform such as QuickBooks, NetSuite or Xero, Slash prepares an accounting entry for every transaction once it settles, and for every bill it sends to the platform. The accounting API lets you code those entries, sync them to the platform, and set up rules so most of them code themselves.

Dimensions and values

Find what to code entries with.

Code and sync entries

Code, approve and sync entries.

Automate coding

Code entries with rules and AI.

Key concepts

  • Connection. The legal entity’s link to its accounting system: a platform Slash syncs with, such as QuickBooks, Xero or NetSuite, or a CSV export. Dimensions, entries and rules belong to a connection. Where an endpoint takes an optional connectionId, it’s required (connection_id_required) only when the legal entity has more than one connection. When a list needs it, send it with every page, not only the first. Endpoints that address an entry or rule by id find its connection themselves.
  • Dimension. A field an entry is coded with, such as the GL account, vendor, class or department. Each dimension has a list of values that come from the platform.
  • Entry. What Slash will post to the platform for one transaction or bill. Its line items carry the coding.

Get started

1

Check the connection

Call List accounting connections. An empty list means the legal entity hasn’t connected accounting yet, and the other accounting endpoints return not_found.
2

Look up what entries are coded with

List accounting dimensions shows the fields the platform expects. See Dimensions and values.
3

Read entries

List accounting entries with status=in_review to get the entries waiting for review. To find the entry for a specific transaction, pass transactionId, or read the transaction’s accountingEntryId.

Entry status

Accounting entry lifecycleAccounting entry lifecycle