AvantGuard - Sage Intacct (Company Configuration) icon

AvantGuard - Sage Intacct (Company Configuration)

AvantGuard - Sage Intacct (Company Configuration)

Actions43

Overview

This node allows users to create a new exchange rate type configuration within a company's settings. Exchange rate types are identifiers or categories used to specify different sets of currency exchange rates, which can be useful for financial applications that need to handle multiple exchange rate scenarios (e.g., spot rates, average rates, or custom rates).

Typical use cases include:

  • Defining a new exchange rate type for internal accounting or reporting.
  • Setting up a default exchange rate type that the system should use automatically.
  • Managing multiple exchange rate types for different business units or purposes.

For example, a company might create an exchange rate type named "GBP-Rate" to represent the official exchange rate for British Pounds used in their financial reports.

Properties

Name Meaning
Name Name or unique identifier for the exchange rate type. Example: "GBP-Rate".
Additional Body Fields Optional additional fields to customize the exchange rate type:
- Key System-assigned unique key for the exchange rate type.
- Id Unique identifier for the exchange rate type.
- Href URL endpoint for the exchange rate type resource.
- Is Default Boolean flag indicating if this exchange rate type should be set as the default. Setting true will unset others.
- Audit JSON object containing audit information such as creation and modification timestamps and user IDs.

Output

The node outputs JSON data representing the newly created exchange rate type object as returned by the API. This typically includes all properties sent in the request along with any additional metadata assigned by the backend system.

There is no binary output from this node.

Dependencies

  • Requires an API key credential for authentication to the AvantGuard Sage Intacct Company Configuration API.
  • The base URL for the API must be configured in the node credentials.
  • The node sends HTTP requests with JSON payloads to the /ia/api/v1 endpoint.

Troubleshooting

  • Missing Required Property: If the "Name" property is not provided, the node will likely throw an error because it is required.
  • Authentication Errors: Ensure the API key credential is valid and has permissions to create exchange rate types.
  • Invalid Field Values: Providing invalid values in additional body fields (e.g., malformed JSON in Audit) may cause request failures.
  • Default Flag Conflicts: Setting Is Default to true will override the current default; ensure this is intentional to avoid unexpected changes.

Links and References

Discussion