Simulators of two external systems

Sage 300 Accounts Payable

Tuntas sends File 1 (the monthly accrual) as an invoice batch. A Finance user posts it here; Tuntas reads posted documents and GL actuals back.

JSON API under /sage/api, HTTP Basic auth (user sage): POST /sage/api/ap/invoice-batches, POST /sage/api/ap/invoice-batches/{id}/post, GET /sage/api/ap/invoice-batches/{id}, GET /sage/api/ap/posted-documents, GET /sage/api/gl/actuals.

CIMB bulk payment portal

Tuntas sends File 2 (the bulk payment file). A Finance user authorises it here; each payee becomes Success or Failed by fixed rules, and File 3 (the result list) can be fetched.

JSON API under /bank/api, HTTP Basic auth (user cimb): POST /bank/api/bulk/batches, POST /bank/api/bulk/batches/{id}/authorise, GET /bank/api/bulk/batches/{id}, GET /bank/api/bulk/batches/{id}/result.

Fixed outcomes: account 12345678901234 → Failed, Account Closed · account ending 0000 → Failed, Invalid Account Number · beneficiary name under 3 letters → Failed, Beneficiary Name Mismatch · anything else → Success with a CIMB… reference.