ComputerEase AP Vendor Bills Data Mapping

  • Updated

Important Note: The ServiceTrade Accounting Connector (STAC) requires a Premium or Enterprise ServiceTrade Subscription and is a paid add-on. Please contact your ServiceTrade Salesperson or your Account Manager if you want to learn more about STAC.

 

This article covers what comes out of the box with your ComputerEase STAC Connector for AP Vendor Bills data mapping.

Note: Any requests for this STAC Recipe to do anything not described below will require additional scoping and potentially additional hours to create a custom STAC.

AP Vendor Bills Data Mapping Chart

ComputerEase Field Data Type Description ServiceTrade Data Mapping
<vennum> string External ID Custom Field on the Vendor
<name> string Required if <vennum> is blank Vendor.name
<address1> string    
<address2> string    
<address3> string    
<deptnum> string If you are using multiple AR departments, this would be the department you want for this invoice. If blank, it would be the default dept. Single Entity Mapping
Example: Dept. mapped to ST Invoice Office
<invdate> date   shipmentReceipt.dateReceived
<duedate> date   Single Entity Mapping
<ponum> string PO Number POLineItem.PurchaseOrder.number
<invnum> string   shipmentReceipt.reference
<desc> string   Single Entity Mapping
<amount> double    
<onhold> boolean This is a custom field and must be requested for use.  
<distribution>   Note: See the distribution sub-fields in the table below.  
<jobnum> string   - SalesOrder.externalId (ST Job #)
OR job_computerease_id
<phasenum> string This is a custom field and must be requested for use.  
<catnum> string This is a custom field and must be requested for use.  
<ctnum> integer
If <ctnum> is used, <ctcode> is ignored
  
<ctcode> string
If <ctnum> is used, <ctcode> is ignored
  
<glaccount> string  

Double Entity Mapping.

- If more than 2 entities, this will require additional scoping and potentially additional hours to create a custom STAC.
<date> date   dateReceived
<qty> double   quantity
<notes> string   Single Entity Mapping.
- If more than one entity, this is will require additional scoping and potentially additional hours to create a custom STAC.

 

Distribution Sub-Fields (Required if distributions are used)

ComputerEase
Distribution Sub-Fields		 Data Type Description ServiceTrade Data Mapping
<amount> double    
<jobnum> simple    
<phasenum> string    
<catnum> string    
<ctnum> integer
If <ctnum> is used, <ctcode> is ignored
  
<ctcode> string    
<glaccount> string    
<directpaynum> string    
<equipnum> string    
<equipcode> string    
<equiporder> string    
<desc> string    
<date> date    
<qty> double    
<hours> double    
<secondparty> string    
<poitemid> integer    
<podistid> integer    
<poqtyreceived> decimal    
<poqtyinvoiced> decimal    
<posalestaxinvoiced> decimal    
<subrfcnum> string    
<subitemnum> integer    
<subbillqty> integer    

 

Glossary

  • Single Entity Mapping: We can tie this to a single ServiceTrade data point.
  • Double Entity Mapping: We can determine this value based on up to two ServiceTrade data points.

Was this article helpful?

/

Comments

0 comments

Please sign in to leave a comment.