How to integrate Acumatica with Corfix

This article will summarize how you can integrate Acumatica with your Corfix account.

Acumatica Integration

This guide explains how the Acumatica Integration works when connected to Corfix. The integration is built and maintained by Heuristyc and runs directly inside the customer’s Acumatica environment.

For detailed setup instructions, please also refer to:

• Heuristyc Documentation Guide

• Heuristyc Product Licensing Guide

• Mappings

Setup

To enable the integration:

1. Follow the steps outlined in the Heuristyc Documentation guide.

2. Ensure the user performing the setup has the following Acumatica permissions:

   • Client License Settings – Delete

   • Purchased Products – Delete

Licensing Information

• CustomerID: CORFIX

• Repository Name: hcpkheuristyc

• Access Key: Provided by Heuristyc

• Secret Key: Provided by Heuristyc

Customization Files

Heuristyc provides customization files that enable:

• Licensing

• Integration

Integration Items

The integration syncs the following data between Corfix and Acumatica:

Projects

• Sync Direction: Bi-directional

• Caveat: Project numbers in Acumatica are generated using its number sequencer.

  • Project numbers created in Corfix will not sync into Acumatica.

  • If a project syncs to Acumatica, the Acumatica project number will be sent back into Corfix.

Workers / Employees

• Sync Direction: Bi-directional

• Caveat: Employee IDs in Acumatica are generated using its number sequencer.

  • Employee numbers created in Corfix will not sync into Acumatica.

  • If an employee syncs to Acumatica, the Acumatica employee number will be sent back into Corfix.

Project Notes / Activity Notes

• Sync Direction: One-way (Corfix → Acumatica)

• Requirements:

  • The project must first exist in one system and be synced across.

  • The Acumatica project must contain a task to attach the note to.

• Updates: Notes will be updated in Acumatica when changes are made in Corfix.

Timecards / Employee Time Activities

• Sync Direction: One-way (Corfix → Acumatica)

• Requirements:

  • The project and worker must first exist in one system and be synced across.

  • The Acumatica project must contain a task to attach the time activity to.

• Limitations:

  • Time entries only sync once and do not update after initial sync.

Forms / Project Attachments

• Sync Direction: One-way (Corfix → Acumatica)

• Requirements:

  • The project must first exist in one system and be synced across.

• Behavior:

  • Files will be added to the project in Acumatica.

  • The filename will include the form’s template name and the date it was created.

• Limitations:

  • Attachments only sync once and do not update after initial sync.

Mappings