A reference of how the field values imported from Spectrum's AP module match up with fields in Trimble Pay as part of the import process.
| Spectrum Field Name | Trimble Pay Field Name |
|---|---|
| Company_Code | Pulled from the database |
| Vendor_Code | Pulled from the database |
| Invoice_Number | formatted_invoice_number |
| Invoice_Type_Code | I |
| Approval_Status | A |
| GL_Date | The configured accounting date |
| Invoice_Date | invoice_submission_date |
| Invoice_Amount | The gross invoice amount including retainage and the items completed and stored this period |
| Contract_Number | Pulled from the database |
| AP_GL_Account | Comes from the Default A/P Trade G/L Account field in |
| Images | The link to the image file |
| Image_File | The file extension |
| Image_Description | The readable name of the document |
| GL_Account | Comes from the GL account assigned to the subcontract |
| Amount | The amount for the given phase code, including retainage |
| Job | Job Number |
| Job_Number | Pulled from the database |
| Phase_Code | The phase code for the accounting line |
| Cost_Type | The cost type for the accounting line |
Spectrum Invoice Export Status
A reference of how statuses in Trimble Pay affect Spectrum actions as part of the export process.
| Invoice Status in Trimble Pay | Action required in Spectrum |
|---|---|
| Pending | None |
| Approved | Export the invoice. Note: If the auto-import integration setting is enabled, Trimble Pay exports it automatically. |
| Declined | None |
| Unapproved | Manually delete the invoice in Spectrum. Important: If an invoice gets un-approved in Trimble Pay after being exported to Spectrum, you must delete the invoice from Spectrum. If you don't delete it, you will encounter a problem during the next export attempt when Trimble Pay detects a duplicate invoice number and prevents the re-approved invoice from being exported to Spectrum. |