Record expenses and review balances

Expenses and the payment ledger are separate. An expense is an outflow entered by the business. A payment row is a calculated balance derived from an order. Neither endpoint performs a transfer or bank reconciliation.

Save an expense

Send a description, category, positive amount, and date to POST /expenses. Use a consistent date representation, preferably YYYY-MM-DD; the API only checks for a non-empty date string.

curl -X POST "$SIMAMIA_API/expenses" \
  -H "Authorization: Bearer $SIMAMIA_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"description":"Shop rent","category":"Rent","amount":650000,"date":"2026-10-11","method":"Bank transfer"}'

Review costs and amounts due

Fetch expenses and payment balances separately:

curl "$SIMAMIA_API/expenses?page=1&page_size=100" \
  -H "Authorization: Bearer $SIMAMIA_TOKEN"
 
curl "$SIMAMIA_API/payments" \
  -H "Authorization: Bearer $SIMAMIA_TOKEN"

Compute totals in a trusted reporting layer. Expenses can be paginated and need aggregation across pages when there are more than 100 records. The payments endpoint currently returns all balances in one response.

Reconciliation cautions

• Do not assume paid means a provider verified payment. It is an order field edited by an authenticated client.
• Do not treat the payment ledger as an immutable accounting journal.
• The API does not provide date range filters or expense summary endpoints.
• Editing or deleting records changes reports immediately; no audit log or soft-delete history is implemented.