Retry a failed accounting posting
POST
Retries an event that could not be posted to the ledger, after you fix the cause (for example adding a missing account mapping or reopening a period). Safe to repeat: it never posts the same event twice.
How to use it
- Find a PENDING exception with List failed accounting postings and read its reasonCode.
- Fix the cause first, e.g. Update posting rules for UNMAPPED_EVENT_TYPE or Reopen an accounting period for PERIOD_CLOSED.
- Call retry: POSTED marks it RESOLVED with the journal entry ID; FAILED keeps it PENDING with the new reason.
- Safe to repeat: an event already in the ledger is never posted twice.
BearerAuthheader
AuthorizationBearer <JWT>id*stringID of the record (UUID).
Format
uuidX-TenantID*stringYour merchant's tenant code — the value typed in the Domain field on the iotoms login screen. See Concepts.
OK
*/*- response
status*stringOutcome of the call: SUCCESS when the request was processed; otherwise an error status.
message*stringShort human-readable message describing the outcome, e.g. which record was saved or why the call failed.
data?The result of the retry and the posting exception as it stands afterwards.
Example Request
curl -X POST 'https://beta.iotoms.com/api/v1/accounting/posting-exceptions/497f6eca-6276-4993-bfeb-53cbbbba6f08/retry' \ -H 'X-TenantID: your-tenant-code'Example Response
{ "status": "string", "message": "string", "data": { "outcome": "POSTED", "entryId": "09a8b554-45ca-4bab-a638-265db4b3e828", "exception": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "sourceSystem": "string", "externalId": "string", "eventType": "string", "reasonCode": "string", "reasonDetail": "string", "status": "PENDING", "effectiveAt": "2019-08-24", "amounts": { "property1": 0, "property2": 0 }, "memo": "string", "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z", "resolvedAt": "2019-08-24T14:15:22Z", "resolvedEntryId": "e05c7998-6fd9-42d8-a16b-15fdd5bb9807" } }}