1. "Invalid Account Number"

   • The GL account used in the transaction does not exist in Intacct.

   • Fix: Verify that the account exists in the chart of accounts and is active.

2. "Account is Inactive or Restricted"

   • The GL account may be inactive or restricted to certain transaction types.

   • Fix: Check the account settings in Intacct and ensure it is active and assigned to the appropriate category.

3. "Period is Closed"

   • The posting period for the transaction date is already closed.

   • Fix: Either reopen the period (if permitted) or adjust the transaction date to an open period.

4. "Currency Mismatch"

   • The currency used in the transaction does not match the currency of the GL account.

   • Fix: Ensure the correct currency is being used and exchange rates are properly set.

5. "Location/Department Required"

   • Intacct may require a location or department code for GL entries.

   • Fix: Ensure that all required dimensions (e.g., location, department, project) are populated.

6. Vendor Not Found"

   • The vendor associated with the expense does not exist in Intacct.

   • Fix: Confirm that the vendor exists and is active in the vendor list.

7. "Duplicate Invoice Number"

   • An invoice with the same number already exists.

   • Fix: Change the invoice number or check if the transaction was already posted.

8. "Approval Required"

   • The invoice requires approval before posting.

   • Fix: Check the approval workflow in Intacct and get the necessary approvals.

9. "GL Account Not Set for AP"

   • The AP account is missing from the vendor setup or transaction.

   • Fix: Ensure the AP GL account is correctly assigned.

10. "Missing Tax Configuration"

• Tax settings are required but are missing or incorrect.

• Fix: Verify that tax configurations are set up properly for the expense category.

11. "Entity Restrictions Prevent Posting"

• Multi-entity environments may have restrictions preventing certain transactions.

• Fix: Ensure that the entity permissions allow posting for the given company or department.

12. "Project or Customer Not Linked"

• Expenses might be linked to projects or customers that are not mapped correctly in Intacct.

• Fix: Verify that the project or customer exists and is correctly linked.

13. "Invalid Dimensions"

• Dimensions (e.g., department, class, project) may be required but are missing.

• Fix: Ensure all necessary fields are completed.

14. "Out of Balance Transaction"

• Debits and credits do not match.

• Fix: Review the entry to ensure proper balancing

Posting expense to Account Payable Entry in Intacct getting this error

Open

Request Fail!
*Select a payment date that occurs after the bill creation date, then try again. [Support ID: ]

*Currently, we cannot create the transaction
'20250318183528'. Check the transaction for errors or inconsistencies, then try again.

*The entire transaction in this operation has been rolled back due to an error.

Possible Causes:

1. Payment Date is Earlier Than the Bill Date

   • Sage Intacct does not allow a payment to be processed before the bill was created.

   • Example:

     • Bill Creation Date: March 20, 2025

     • Payment Date: March 18, 2025 ❌ (Invalid, because it's before the bill date)

2. Incorrect Date Format in Import or API Call

   • If you're importing data or using an API, the date format might be incorrect, causing Sage Intacct to interpret it wrongly.

3. System Setting Restriction on Backdated Payments

   • Your Sage Intacct account might have settings that restrict payments before the bill date.

How to Fix It:

✅ 1. Ensure the Payment Date is After the Bill Date

• Open Accounts Payable > Bills

• Locate the bill you are trying to pay and note the "Bill Date".

• When making a payment, select a Payment Date that is later than the Bill Date.

• Example:

  • Bill Date: March 20, 2025

  • Valid Payment Date: March 21, 2025 ✅ (Any date after the bill date)

•  

  • Make sure the "payment_date" is AFTER the "bill_no" creation date.

✅ 3. Modify System Settings (If Needed)

• If you need to allow backdated payments, check with your Sage Intacct administrator:

  • Go to: Company > Setup > AP Configuration

Check if any restrictions are in place for backdated payments

Posting to GL getting the following error in Intacct GL: “You are attempting to Post a transactions with a date within the current Period”

Open

The error message “You are attempting to Post a transaction with a date within the current Period” in Sage Intacct GL usually indicates that there are restrictions set for posting transactions within the current accounting period.

Possible Causes and Solutions:

1. Posting Restriction for Current Period

   • Some organizations configure Sage Intacct to restrict posting to the current period to prevent accidental entries.

   • Fix:

     • Go to General Ledger → Setup → Books and check if there are restrictions on posting for the current period.

     • If necessary, update the settings to allow posting.

2. Role-Based Permissions

   • Your user role may not have permission to post to the current period.

   • Fix:

     • Go to Company → Admin → Roles and verify whether your role has permission to post to the current period.

     • Request an administrator to update your permissions if needed.

3. Accounting Period is in “Soft Close” Mode

   • If the period is soft closed, Sage Intacct may block postings.

   • Fix:

     • Navigate to General Ledger → Setup → Accounting Periods and check the status.

     • If it’s in a restricted mode, consider reopening it (if permitted).

4. Transaction Date Falls Outside Allowed Range

   • Some configurations limit posting to a specific date range within an open period.

   • Fix:

     • Verify the allowed date range for postings in General Ledger settings.

     • If necessary, adjust the transaction date to fit within the approved range.

5. System-Wide Posting Restriction

   • Certain company-wide settings may restrict posting for all modules (GL, AP, AR).

   • Fix:

     • Check Company → Setup → Posting Preferences and adjust restrictions.

Next Steps

• If you're an admin, verify and adjust the GL settings and role permissions.

• If you lack admin access, consult your finance team or Intacct administrator to modify settings.

While Posting Timesheets or Expenses gets this failed message: *The Task '913' does not exist or the employee '004215' is not assigned to this task or its project.

Open

The error "The task does not exist or the employee is not assigned to this task or project" in Sage Intacct typically occurs in Project Accounting or Time and Expense modules when attempting to log time, expenses, or transactions related to tasks or projects.

Common Causes

1. Invalid Task or Project ID: The task or project referenced does not exist in the system.

2. Employee Not Assigned:

   • The employee is not associated with the task or project.

3. Inactive Task or Project: The task or project is inactive or closed.

4. Permissions Issue: The employee lacks the necessary permissions to access the task or project.

5. Missing Project/Task Associations:

   • Tasks are not properly linked to the project.

   • Employees are not assigned to the task.

Steps to Resolve

1. Verify the Task and Project ID:

   • Go to Projects > Tasks and ensure the task exists and matches the ID used.

   • Check that the Task ID and Project ID are spelled correctly.

2. Check Employee Assignment:

   • Navigate to Projects > Projects List.

   • Open the relevant project and check the Assigned Employees tab.

   • Ensure the employee in question is assigned to the project and the specific task.

3. Ensure the Task/Project is Active:

   • Verify that both the Project and Task are marked as Active.

   • Go to Projects > Projects List or Tasks List.

   • Reactivate the project/task if it has been inadvertently closed.

4. Assign the Employee to the Task:

   • Go to Projects > Tasks.

   • Edit the task and assign the employee under the Task Assignments or Resources section.

5. Check Permissions:

   • Navigate to Company > Admin > Roles.

   • Review the permissions for the role assigned to the employee.

   • Ensure the employee has access to the Project Accounting and Tasks modules.

6. Revalidate the Transaction or Entry:

   • After making the above corrections, re-enter the time, expense, or transaction

While posting to Intacct GL

*GL balancing account on line item 3 is not valid.

[Support ID:q03030303300IQ-UXwWOQAAABc]
Select a valid GL balancing account, and try again.

*Currently, we cannot create the transaction 'DB1226-V0000'.
Check the transaction for errors or inconsistencies, then try again.

*The entire transaction in this operation has been rolled back due to an error.

Open

It looks like the error is related to an invalid GL balancing account on line item 3, which is preventing the creation of the transaction 'DB1226-V0000'.

Steps to Fix the Issue:

1. Verify the GL Balancing Account:

   • Check the GL balancing account assigned to line item 3.

   • Ensure it exists and is active in your financial system.

   • Confirm that it is mapped correctly in the GL setup.

2. Validate Account Configuration:

   • Confirm that the balancing account is set up for the correct entity, cost center, or company code.

   • If the account has been recently changed or deactivated, update it with a valid one.

3. Review the Transaction Details:

   • Open 'DB1226-V0000' and inspect all fields for missing or incorrect values.

   • Ensure the GL accounts, amounts, and categories are correctly assigned.

4. Check System Configuration:

   • If the issue persists, verify the financial system’s balancing rules and whether any validation rules are preventing the transaction.

   • Some systems require specific GL accounts for certain transaction types.

5. Retry After Correction:

   • Once the invalid GL account is corrected, attempt to resubmit the transaction.

6.  

While posting to Expense
*The account number '3322' requires a BILLFLAG
[Support ID: 33030303034b- Ta9DtgAAAAk]
Enter a valid BILLFLAG on line item 1, in transaction 'DB1012-V0000', and try again.

*Currently, we cannot create the transaction 'DB1012-V0000'.
Check the transaction for errors or inconsistencies, then try again.

*The entire transaction in this operation has been rolled back due to an error.

Open

The error message indicates that while posting an expense transaction, the account number '3322' requires a BILLFLAG, which is missing in line item 1 of transaction 'DB1012-V0000'. Because of this issue, the transaction could not be created, and the entire operation was rolled back.

Steps to Resolve the Issue:

1. Check Account Setup:

   • Verify in your Chart of Accounts whether account '3322' is configured to require a BILLFLAG.

   • If this requirement is incorrect, adjust the account settings.

2. Review the Expense Entry:

   • Open transaction 'DB1012-V0000' and navigate to line item 1.

   • Check whether the BILLFLAG field is present and populated.

   • If missing, enter a valid BILLFLAG as required.

3. Validate Data Entry Rules:

   • Ensure that all required fields in the expense report are properly filled.

   • Look for any inconsistencies in the vendor details, GL account assignments, and tax configurations.

4. Retry the Posting:

   • Once the BILLFLAG is added, attempt to repost the transaction.

   • If the error persists, check for any other errors or missing fields in the transaction.

5. Audit the Logs:

   • If the issue is unclear, check system logs or audit trails to understand why the BILLFLAG is being enforced.

6. Escalate if Needed:

   • If the problem persists and no configuration issues are found, escalate the issue to your DATABASICS admin or support team with the provided Support ID.

While Posting to GL
Request completed partially. ## out of #### records have been processed.
Please refresh data and re-submit the request.
*Line 1: The task you selected is not associated with the project you selected. When you select a task dimension, that task must be associated with the project dimension that you selected at the linelevel. The task you selected is 32-323. Go back and select another task.

[Support ID: 39393939- Bed4QQAAAAs]

*Could not create glbatch record

*Could not create GLBatch record.

*The entire transaction in this operation has been rolled back due to an error.

Open

This error suggests that the GL posting process was only partially completed due to issues with task-to-project mapping and an inability to create the GL batch record.

Steps to Resolve:

1. Check the Task and Project Association:

   • The error message states that the selected task (32-323) is not linked to the chosen project.

   • Verify in your project setup that this task is associated with the selected project.

2. Refresh Data and Retry:

   • As suggested by the system, refresh your data before re-submitting.

   • Ensure that no stale data is being referenced from a previous attempt.

3. Check GL Batch Creation Issue:

   • If the system cannot create the GL batch record, there may be:

     • Missing configurations in the GL batch setup.

     • Data inconsistencies preventing the batch from forming correctly.

   • Look for error logs related to GL batch processing.

4. Verify Transaction Rollback Cause:

   • Since the entire transaction was rolled back, check if there are any related dependencies (e.g., missing accounts, invalid periods, or unposted prior transactions).

   • Run system diagnostics or review error logs to find specific causes.

5. Check Support ID for Logs:

   • Use the Support ID: 39393939- Bed4QQAAAAs to trace the issue in your system logs or support portal.

6. Re-submit After Corrections:

   • Once the task and project association is corrected, and GL batch creation is verified, try re-posting the data.

If the issue persists, contacting your technical support team with the Support ID may provide additional insights.

*Match the site currency on line item 1 to the base currency in transaction '2####098', and try again.
*Currently, we cannot create the transaction '224#####98'.
Check the transaction for errors or inconsistencies,
then try again.

*The entire transaction in this operation has been
rolled back due to an error.

Open

Entity currency is different than the allowed report currency that is getting imported to Intacct Expense.

1. Site Currency vs. Base Currency Mismatch

   • The currency used in line item 1 does not match the base currency of the transaction.

   • Fix: Ensure that the currency of the line item matches the base currency of the transaction. You can check this in Intacct’s Currency Setup and adjust accordingly.

2. Currency Exchange Rate Issues

   • If your system has currency conversion enabled, ensure that the correct exchange rates are applied.

   • Fix: Verify that the currency rates are set up correctly in Intacct under Company > Currency Rates.

3. Transaction Rejection

   • The error message indicates that Intacct has rolled back the entire transaction, meaning it wasn't recorded due to inconsistencies.

   • Fix: Review all fields in the transaction, especially currency, amounts, and line items.

4. Permissions or Configuration Settings

   • Some permissions or settings may prevent the creation of the transaction.

   • Fix: Ensure that the user performing the transaction has the required permissions.

5. Validation Rules or Required Fields

   • There may be custom validation rules that enforce currency matching.

   • Fix: Check any custom rules applied to currency transactions.

1. Check the currency setup under Company > Base Currency and ensure it matches the site currency for the transaction.

2. Re-enter the transaction, ensuring that each line item matches the base currency.

3. Run an error report in Intacct Logs to see if any other validation errors exist.