Actions43
- Location Groups Actions
- Locations Actions
- Roles Actions
- User Groups Actions
- Users Actions
- Affiliate Entity Groups Actions
- Attachments Actions
- Classes Actions
- Contacts Actions
- Department Groups Actions
- Departments Actions
- Document Sequences Actions
- Earning Types Actions
- Email Templates Actions
- Employee Types Actions
- Employees Actions
- Entities Actions
- Exchange Rate Lines Actions
- Exchange Rate Types Actions
- Exchange Rates Actions
- Attachment Folders Actions
- Get Next Value Actions
Overview
The "Create Company Config Entity" operation in the Entities resource allows users to create a new company configuration entity within the AvantGuard Sage Intacct system. This node is useful for automating the setup of company entities with detailed configurations such as tax IDs, contacts, fiscal periods, and accounting settings.
Typical use cases include:
- Automating the onboarding process of new companies into the accounting system.
- Synchronizing company data from external systems into Sage Intacct.
- Setting up complex company structures with inter-entity relationships and tax configurations programmatically.
For example, a finance team could use this node to create multiple entities with their respective tax IDs, fiscal months, and contact information without manual entry, ensuring consistency and saving time.
Properties
| Name | Meaning |
|---|---|
| Id | Unique identifier of the entity (max 20 characters). Immutable after creation. |
| Name | Name of the entity. |
| Federal Id | Federal tax ID used if the company issues separate 1099 forms per US entity. |
| Additional Body Fields | Optional additional fields including: - Key: System-assigned unique key. - Href: URL endpoint. - Start Date / End Date: Operational period. - First Fiscal Month / First Tax Month: Starting months. - Week Start: Week start day. - Contacts: JSON object with detailed contact info. - Texts: JSON with invoice/report texts. - Is Root: Boolean indicating working entity status. - Business Days / Weekends: JSON arrays defining work and weekend days. - Tax Id: State or VAT tax ID. - Default Country For Addresses: Country code for addresses. - Business Id: Company's business registration number. - Open Books Start Date: Date from which books are open. - Operating Country: Country where entity operates. - Legal Contact: JSON with legal contact details. - Is Partial Exempt / Is Default Partial Exempt: Booleans for VAT exemption settings. - Accounting Type: 'Entity' or 'Fund'. - Statutory Reporting Period Date: Max lock date for GL approval. - Customer / Vendor: JSON objects linking customer/vendor. - Unrecoverable Tax Account: JSON for tax account. - Enable Inter Entity Relationships: Boolean to enable different accounts by target entity. - Inter Entity Payable/Receivable GL Account: JSON for related accounts. - Manager: JSON with employee managing the entity. - Tax Solution: JSON describing tax solution used. - Is Limited Entity: Boolean indicating limited entity status. - Status: 'Active' or 'Inactive'. - Audit: JSON with creation/modification metadata. |
Output
The node outputs the response from the API call that creates the company config entity. The output is structured as JSON containing the created entity's details, reflecting all submitted properties and any server-generated fields such as timestamps or keys.
If binary data were involved (not indicated here), it would represent files or attachments related to the entity, but this operation deals solely with JSON data.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard Sage Intacct API.
- The base URL for the API must be configured in the credentials.
- The node uses HTTP headers to accept and send JSON content.
- No other external dependencies are indicated.
Troubleshooting
- Missing Required Fields: Errors may occur if mandatory fields like
id,name, orfederalIdare missing. Ensure these are provided. - Invalid Field Formats: Dates should be in ISO format (YYYY-MM-DD). JSON fields must be valid JSON strings.
- API Authentication Errors: Verify that the API key credential is correctly set up and has necessary permissions.
- Status Errors: Setting the status to inactive might cause the entity to be hidden or unusable; ensure correct status is selected.
- Inter-Entity Relationship Issues: If enabling inter-entity relationships, ensure related GL accounts are properly specified.
- Country Codes and Options: Use valid country codes and options as listed; invalid values may cause rejection.