You need to set up the following information in the Job Cost application:
- A cost code format
- Standard cost codes (optional)
- Standard categories (required to import transaction files from Sage Estimating (SQL))
Tip: Sage recommends using the same coding scheme for phases in Sage Estimating (SQL) and cost codes in Job Cost. Although Sage Estimating (SQL) can handle different coding, using the same scheme minimizes data entry in Sage Estimating (SQL). If you want, you can import Job Cost data directly into your Sage Estimating (SQL) standard database. When you set up your standard database, select Sage 300 Construction and Real Estate as the Job cost interface type.
If the two applications have different coding, you will have to set up a job cost phase for each phase in Sage Estimating (SQL). Keep in mind that multiple phases can reference the same Job Cost code.
- The job cost phases you enter in Sage Estimating (SQL) should not exceed the 12-character limit allowed by Job Cost.
- Since Job Cost automatically formats the job cost phase codes imported from Sage Estimating (SQL), you should set the job cost phase suffix to zero in Estimating.
- If you are using a free form format (15 characters) for job cost phases, Sage Estimating (SQL) treats any phase with any segment consisting of all zeros as a group phase.
- Standard categories in Job Cost make it possible to create cost codes on the fly when importing estimate transactions with non-existent job cost codes.