Troubleshoot revenue or expense posting—Contracts

The following table lists the most common reasons a revenue and/or expense entry may fail to post:

Error Possible solution
Posting date cannot be before contract line begin date

This may occur for one of the following reasons:

  • You chose to specify a posting date instead of using the scheduled posting date, and the specified date is earlier than the contract start date. Change the specified posting date to a date equal to or after the contract line start date, then try posting the revenue and/or expense again.
  • The revenue or expense template start date on the contract line is earlier than the contract line start date. Change the revenue and/or expense template start date to a date equal to or after the contract line start date, then try posting the revenue and/or expense again.
The revenue or expense entry I want to post does not appear in the Preview results.

Check the following:

Error creating glbatch; or

Periods are closed

This may occur when you try to post revenue and/or expenses in a closed period.

Either specify a posting date in an open period or open the applicable period, then try posting the revenue and/or expense again.

Not enough amount in Unbilled, Billed and Paid Deferred Revenue.

This may occur when you try to post a negative scheduled entry associated with a quantity-based revenue template that reduces the positive amount of revenue already recognized to a value below 0.

Verify the associated usage quantity is correct.

Revenue for the following contract lines is associated with a Project or Task Percent Complete revenue template, but no project is associated with the contract line. Use a different recognition method or assign a project to each contract line and then try updating the percent complete revenue again.

Contract <contract ID> line no.<line no>

This may occur when a contract line associated with a project is renewed, but no project was linked to the child contract line. The system can't calculate the revenue as there is no source for percentage of completion values.

Do one of the following:

  • If the contract line is supposed to be linked to a project, see Renew a contract linked to a project.
  • If the contract line is no longer related to a project, edit the contract line and choose a revenue template with a recognition method other than project or task percent complete.
  • If the contract line was not supposed to be renewed, you can delete the child contract line if it is not included in an MEA or if it was not invoiced.

Revenue for the following contract lines is associated with a percent complete revenue template, but there are no source hours available to determine the completion percentage. Update the source hours and then try updating the percent complete revenue again.

This may occur when a contract line is associated with a project and the associated percent complete revenue template is based on hours, for example estimated or budgeted hours. However, there are no timesheets with hours coded to the applicable project or task for the given as of date.

Create or edit the applicable timesheet records and associate them with the applicable project and task.

There are one or more issues with the project or task percent complete revenue you are trying to update. Create a contract group that excludes the following contracts and use that group to preview. Then contact your Sage Intacct support resource for help with resolving the issues: Contract <contract ID> line no.<line no>, Contract <contract ID line no.<line no>.

This occurs when there is an issue with project or task percent complete revenue for one or more contract lines that you can't resolve on your own.

To process revenue for the contracts without errors:

  1. Create a contract dimension group that excludes the problem contracts.
  2. In the Manage Schedules page, use the new contract dimension group in the Contract/Group filter and execute Preview.
  3. Post revenue as applicable.

To resolve the contracts with errors:

  1. Ask your designated support user to contact Support and give them the exact text of the error message.
  2. For each contract with errors, give them the contract ID and contract line numbers.
  3. The support resource will coordinate the resolution.