Field Mapping
GETS Field Mapping
Complete field mapping guide based on GETS Schema-mapping for KSA
Field Mapping Overview
Understanding how GETS transforms data between different invoice formats
Core Concepts
Source-to-GETS Mapping
Transform your native invoice format to GETS standardized fields
GETS-to-Destination Mapping
Convert GETS format to country-specific requirements (UBL, ZATCA, etc.)
Mapping Benefits
Single integration for multiple countries
Automatic compliance validation
Consistent data transformation
Smart Mapping: GETS uses intelligent field mapping that automatically handles data type conversion, currency formatting, date standardization, and country-specific validation rules.
Field Mapping Reference
Complete field mapping based on MappingConstants and GETS schema registry
Document Header Fields
Field Name | GETS Path | Data Type | Required |
---|---|---|---|
Document Type | header.documentType | enum | Required |
Document ID | header.documentNumber | string | Required |
Document Currency | header.currency | string | Required |
Exchange Rate | header.exchangeRate.rate | number | Conditional |
VAT Currency | header.taxCurrency | string | Required |
Issue Date | header.issueDate | date | Required |
Issue Time | header.issueTime | time | Required |
Supply Start Date | header.invoicePeriod.startDate | date | Conditional |
Supply End Date | header.invoicePeriod.endDate | date | Optional |
Due Date | header.dueDate | date | Optional |
Reference Invoice Number | header.referenceId | string | Conditional |
Note Issuance Reason | header.noteIssuanceReason | string | Conditional |