Payment Ledger Entry

One line of what a customer or supplier owes and has paid, written by iVendNext when a document is booked. Read it; never write it.

Area: Payments and payment methods · Why it is here: · Fields: 19

Read and write it

Every call runs as your app's own user, with its key in one header, at the retailer's own address. The user reads and writes only what its role allows: your app's user, and the rights the retailer gives it.

Read a list (only name unless you ask for fields):

curl -s "https://⟨site⟩/api/resource/Payment%20Ledger%20Entry?fields=%5B%22*%22%5D&limit_page_length=20" \
  -H "Authorization: token ⟨api key⟩:⟨api secret⟩"

Read one:

curl -s "https://⟨site⟩/api/resource/Payment%20Ledger%20Entry/⟨name⟩" -H "Authorization: token ⟨api key⟩:⟨api secret⟩"

Your app reads it; it does not write it here: iVendNext writes it when a document is booked. All the record calls and their answers: the API reference.

Fields

Read from the product at POS 2.1.0.667 (till app 60147699c): its own fields, the fields iVendNext adds to it, and iVendNext's changes to any of them. Read-only fields are set by iVendNext; a hidden one is not on the form but can be read. Every record also has name (its id, in the address), owner, creation, modified, modified_by and docstatus (0 a draft, 1 submitted, 2 cancelled), all read-only.

All record types · What you can use

This record type in the kit