Transactions

entries.create

Manually create a receipt entry from preserved evidence when extraction needs correction. Requires the submission revision, exact minor-unit amounts and an idempotency key.

POST/api/v1/accounting/entries.create

Permissions

accounting:readaccounting:write

Who can call it

admin, finance

Retries

Idempotency key required, with expectedRevision

MCP

accounting_create_record

Fields

  • submissionIdstring (ID)Required

    The ID of an upload, returned by uploads.prepare or uploads.inline.

  • expectedRevisionintegerRequired

    The record's current revision, from the last time you read it. If someone changed the record since, the request is refused with a conflict so you can reload and check before trying again.

    at most 9007199254740991 · greater than 0

  • merchantstringRequired

    1–500 characters

  • datestringRequired

    A date, as YYYY-MM-DD.

  • currencystringRequired

    Three-letter currency code, such as CAD or USD.

  • amountMinorstringRequired

    An amount in cents (the currency's smallest unit), written as a whole-number string such as "1250" for $12.50.

    Whole number written as a string

  • taxMinorstringRequired

    An amount in cents (the currency's smallest unit), written as a whole-number string such as "1250" for $12.50.

    Whole number written as a string

  • taxKnownboolean
  • categoryIdstring (ID)

    The ID of a category, from categories.list.

  • paymentAccountIdstring (ID)

    The card or account the purchase was paid with, from accounts.list.

  • typeenumRequired
    expenseincomeincome_refundrefundtransferfee
  • notesstring

    Notes kept with the record.

    at most 10000 characters · Default ""

  • sourceFactIndexinteger

    0 to 19

  • statusenum

    Only include records with this status.

    reviewed
  • duplicateDecisionenum
    keep_separate
  • tripIdstring (ID)

    The ID of the related record.

  • tripRoleenum
    lodgingholdroom_chargemealtransportother
  • idempotencyKeystringRequired

    Any unique text you generate once per intended change, so a retried request only happens once. Send it as the Idempotency-Key header instead if you prefer; if you send both they must match.

    8–200 characters

Example

curl https://app.getoatmilk.com/api/v1/accounting/entries.create \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "submissionId": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
  "expectedRevision": 3,
  "merchant": "example",
  "date": "2026-09-30",
  "currency": "CAD",
  "amountMinor": "1250",
  "taxMinor": "1250",
  "type": "expense"
}'
Response
{
  "data": { … }
}

Try it

Try it

Checks your input with this action’s real schema and answers like the API, with synthetic data. No key needed, and nothing changes.

POST/api/v1/accounting/entries.create
curl https://app.getoatmilk.com/api/v1/accounting/entries.create \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "submissionId": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
  "expectedRevision": 3,
  "merchant": "example",
  "date": "2026-09-30",
  "currency": "CAD",
  "amountMinor": "1250",
  "taxMinor": "1250",
  "type": "expense"
}'

More in Transactions.