Amili Docs
Home
Products
Products
  • Debt.collection
  • Account Receivable
  • Distribution
Go to amili.no
Home
Products
Products
  • Debt.collection
  • Account Receivable
  • Distribution
Go to amili.no
  1. AutoPostings
  • About
  • ARM API
    • Health
      • Check API health
    • ArItems
      • Get one AR item
      • Get a list of AR items
      • Put (update) ar item details
    • Documents
      • Get one document
      • POST (create) a batch of documents
      • POST (create) one document
      • Get a list of documents
    • AutoPostings
      • POST (create) one or more auto postings
        POST
    • GlItems
      • Get one GL item
      • Get a list of GL items
    • Customers
      • Get one customer
      • Delete a customer
      • POST (create) a batch of customers
      • PUT (update) a batch of customers
      • PUT (update) one customer
      • GET a list of customers
      • POST (create) one customer
    • Batches
      • Get one batch
    • PaymentReservations
      • Creates a new payment reservation
    • Files
      • POST (upload) one or more OS files
Home
Products
Products
  • Debt.collection
  • Account Receivable
  • Distribution
Go to amili.no
Home
Products
Products
  • Debt.collection
  • Account Receivable
  • Distribution
Go to amili.no
  1. AutoPostings

POST (create) one or more auto postings

POST
/clients/{clientno}/autopostings/{autopostingmethod}
Performs a set of one or more auto postings. An auto posting is a complex set of debit/credit entries to the GL/AR based on one event.
NOTE:
If at least one posting in an autoposting batch fails, all postings in that batch will be rejected as FAILED. A posting that validates OK but is rejected for being part of a failing batch will be marked with resultType = BATCH-REJECTED in the response body
If at least one posting in an autoposting batch is tagged with the option validateOnly then all transactions in that batch will be treated as validateOnly
Standard/default behavior is to reject a posting if there are warnings. You can force a posting with warnings to be processed by setting suppressWarnings = true on the batch level (metadata) or use the suppressWarnings option on the transaction level

Request

Authorization
JWT Bearer
Add the parameter
Authorization
to Headers
Example:
Authorization: ********************
or
Path Params

Body Params application/jsonRequired

Examples

Responses

🟢200OK
application/json
OK. The request succeeded
Body

🟠400Bad Request
🟠403Forbidden
🟠404Not Found
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST '/clients//autopostings/' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "metadata": {
        "userId": "TestUser",
        "suppressWarnings": false,
        "validateOnly": false
    },
    "postings": [
        {
            "arItemId": "2218-500002-35078-0",
            "dueDate": "2025-07-15",
            "currency": "NOK",
            "currencyAmount": 150,
            "voucherDate": "2025-07-16"
        }
    ]
}'
Response Response Example
200 - Posting(s) performed
{
    "status": "PROCESSED",
    "result": "CREATED",
    "message": "Posting(s) performed",
    "clientNo": 2218,
    "autoPostings": [
        {
            "arItemId": "2218-500002-35078-0",
            "result": "CREATED",
            "resultType": "OK",
            "message": "Posting performed"
        }
    ]
}
Modified at 2025-09-29 16:08:55
Previous
Get a list of documents
Next
Get one GL item
Built with