Expenses

Expenses already paid, entered many at a time. Each is its own journal entry.

List expenses entered as already paid

GET /expenses

Sends Vortex-Entity.

Newest first. Requires ledger:read. reversed is true once the expense's journal entry was reversed.

Parameters

NameInTypeAbout
start_datequerystring (date)
end_datequerystring (date)
limitqueryinteger
starting_afterquerystring

Answers

  • 200 object. A page of expenses.
  • 4XX Problem. An error. `code` is stable and safe to branch on; `detail` says in plain English what
  • 5XX Problem. An error. `code` is stable and safe to branch on; `detail` says in plain English what

Enter already-paid expenses in a batch

POST /expenses

Sends Vortex-Entity and Idempotency-Key.

Records up to 100 expenses that were already paid. Each one becomes its own journal entry: the expense account is debited and the bank, cash or credit card account it was paid from is credited. They are recorded together or not at all: if any row is wrong the response is 422 invalid_expenses, with one entry in errors per problem (its path names the row and field), and nothing is saved. Requires journal:write. With an Idempotency-Key, each row gets its own key derived from it, so sending the same batch again records nothing twice.

account_id must be an active expense, cost of goods sold, other expense or asset account (not a bank, receivables, payables or inventory account). paid_from_account_id must be an active bank or cash account, or a credit card account. An expense paid to a vendor flagged for a 1099 counts in the vendor 1099 report; card payments are shown apart there, as for bills.

Body

FieldTypeAbout
expenses requiredlist of object

Answers

  • 201 object. The entries recorded, in the order sent.
  • 4XX Problem. An error. `code` is stable and safe to branch on; `detail` says in plain English what
  • 5XX Problem. An error. `code` is stable and safe to branch on; `detail` says in plain English what