Skip to main content

Money S3

The Money S3 connection allows agents and workflows to work with selected accounting and ERP data from Money S3. It is typically used for reading directories, orders, and invoices or for creating selected documents according to the settings of the customer installation.

Prerequisites​

Money S3 is not a standard purely cloud service. Before connecting, the customer's Money S3 environment must be prepared:

  • active Money S3 API module,
  • installed and available S3Api service,
  • configured API domain or local API endpoint,
  • created API key with Client ID and Client Secret,
  • Money S3 user assigned to the API key if using Client Credentials mode,
  • configured XML import queue for processing entries.

Without a properly set up queue, entries may be accepted into the queue but will never actually be created in the accounting system.

Quick Connection​

  1. In the Connections section, click on Add Connection.
  2. Select Money S3.
  3. Enter the Money S3 API domain or endpoint.
  4. Insert the Client ID, Client Secret, and other required information according to your Money S3 settings.
  5. Name the connection and save it.

What the Connection Can Do​

  • Read selected accounting and business data, such as directories, orders, or issued invoices.
  • Create selected documents if the connection has the necessary permissions.
  • Support automation over ERP data, such as order verification, customer synchronization, or document preparation.

Important Principles​

  • Money S3 API uses GraphQL over HTTP.
  • Entries are asynchronous. A successful response means the request has been accepted into the queue, not a guarantee that the document has already been created in Money S3.
  • When writing, save the operation identifier to verify the processing result later.
  • Errors may occur during later queue processing, for example, due to number series, accounting configuration, VAT, or validation rules.

Security and Permissions​

Use a separate API key for Siesta AI and assign it only the necessary permissions. Production and testing Money S3 environments should have separate accesses. Regularly rotate the Client Secret and recreate the connection if there is suspicion of a leak.

The Money S3 connection is suitable for automating invoices, orders, synchronizing business partners, and auditable workflows over ERP data. For accounting entries, we recommend using a clear approval step or control workflow.

Technical Notes​

  • Implementation: Money S3 is documented as a configured accounting/API integration; exact implementation depends on the customer setup.
  • Authentication/scopes: depends on the Money S3/API credentials and the accounting permissions assigned to the integration account.
  • Functions: expected functions depend on the configured API surface, such as reading accounting documents, contacts, invoices, orders, or creating/updating records where enabled.
  • Write behavior: accounting writes can have financial and audit impact. Use read-only credentials by default and require confirmation for any mutation.