Warning! Construction underway! Amatino is in an 'alpha' state. Not all features are operational. See roadmap

Primary
Account
Entity
Transaction
Derived
Balance
Ledger
Performance
Position
Recursive Balance
Recursive Ledger
Tree
Ancillary
Custom Unit
Object
Global Unit
Global Unit List
Ledger Row
Session
Side
Tx Version List
Tree Node
Type
User

Entry

Entries compose Transactions. An individual entry allocates some value to an Account as either one of the fundamental Sides: a debit or a credit. All together, those debits and credits will add up to zero, satisfying the fundamental double-entry accounting equality.

When consuming the Amatino API, operations involving Entries always occur as part of a Transaction request. For example, when creating a Transaction, you will specify a JSON Array of Entry objects under the entries key. You will never send or recieve an Entry object on its own to or from the Amatino API.

The Entry Object

Amatino expects the following object structure when creating and updating Entries, and will provide the same object back to you when asked to retrieve them. Note that you never directly interact with an Entry object on its own, instead they are used as part of Transactions requests.

Root Type

JSON Array

Object Structure

description The integer identifier of the Account to which this Entry is allocated.
key "account_id"
example 42
type JSON Number
description A description of this Entry. If an empty string is specified, Amatino will use the parent Transaction description to describe this Entry.
key Description
example "Juicy dividend on a big ol' pile of diversified stocks"
type JSON String
description Either debit or credit.
key "side"
example "debit"
source /constants/sides
type JSON String
max value Somewhere north of one quadrillion (Your mileage may vary at that magnitude!)
description The absolute value of this Entry, denominated in the parent Transaction unit or custom unit.
key "amount"
example "23125.95"
type JSON String