Improved Project Status Functionality in the Integration with Sage Intacct

The posting preferences for the SCM > Sage Intacct integration currently only allow for setting a default "project status" upon creation of a project in Intacct.

Ideally SCM would have some additional functionality (similar to intacct) that would restrict certain types of transactions to take place when a project has reached a certain status.

The SCM statuses would then ideally be mapped to projects statuses in Sage Intacct via the post preferences.

Then, as project statuses are updated in SCM, the project status would also be updated in Sage Intacct via the accounting link.

This would allow for a more seamless closing of jobs between multiple systems. Ideally, this functionality would also be applicable to COs and Prime contracts as well...

I will provide a use case scenario below:

• A project has come to completion (ie. all fieldwork is 100% complete)

  • at this point in time the project status in SCM would be set to "complete"

• The project status change in SCM triggers a project status change in Sage Intacct

  • Now that the project status has been updated in Sage Intacct, our third party integration (Assignar) will no longer see this project available for scheduling

  • Likewise, since the project has reached a certain status in both SCM and Assignar transactions like creating new POs, Subcontracts, etc will be prohibited

• As bills from subcontracts, POs, etc trickle in, they may still be received against the respective existing POs and subcontracts of the completed project

  • once all bills etc have been received, the status may be updated again in Sage Intacct to prevent no further expenses from being created against the project

• Finally, once payment is received by the customer, the project status may be changed to "closed" in Sage Intacct

  • Ideally, this status would be transferred back to SCM - alerting the Account Manager that all expenses against the job have been finalized, that the customer has paid all invoices, and that the job has now reached a final status of "closed"

    • a financial summary of the project would be a very nice thing to include with this alert

  • At this point the project would be archived.

    • Ideally an additional "bucket" of projects in the project home-page would be created to allow for "Active" projects, "Completed" projects, and "Inactive/Closed/Archived" projects