1. Ensure that Shopperations Order ID is activated and visible in the Org Settings
2. Set the name for the Shopperations ID field, if needed (Tactic ID is typical).
3. Review Shopperations upload template to understand required and optional Shopperations fields and map to internal systems’ fields that represent them.
4. Document field mapping exercise results.
5. Create or obtain a report from each system with real data
6. Transform internal reports to match Shopperations template, if multiple systems are in play, can combine into one file or load to Shopperations separately.
Check to see if there is a single reporting source for both invoices and deductions that can be used. This will simplify the process and save on setup time!
Field Mapping Table:
Invoice System | Deduction System | |
Shopperations Field Name | Field Name (or formula to be used) | Field Name (or formula to be used) |
Invoice Number (required) | ||
Order ID (required) | ||
Invoice Date (required) | ||
Invoice Amount (required) | ||
Fiscal Year (required) | ||
Beneficiary | ||
Type | ||
Status | ||
Vendor Number | ||
GL Code | ||
Description | ||
Budget ID | ||
Budget Description | ||
User ID | ||
Doc.number | ||
PO# |
Fields used to define uniqueness:
- invoice number
- Invoice date
- order id
- budget id
- doc.number
- description
- type
Upload File Formatting - Fields & Data Types
Invoice Number (required) | Order ID (required) | Invoice Date (required) | Invoice Amount (required) | Fiscal Year (required) |
Field Type = text | Field Type = text | Field Type = date mm/dd/yyyy must include 4 digit year |
Field Type = number |
Field Type = number must include 4 digit year |
Beneficiary | Type | Status | Vendor Number | GL Code | Description | Budget ID | Budget Description | User ID | Doc.number | PO# |
Field Type = text | Field Type = text | Field Type = text | Field Type = text | Field Type = text | Field Type = text | Field Type = text | Field Type = text | Field Type = text | Field Type = text | Field Type = text |