Map your fields to GETS

Match the fields

1. Open GETS Field Mapping. Find each invoice field in the table’s sections, such as header, seller, payment, delivery and totals.
2. For a GETS field, choose the matching field from your sample payload. For example, if your payload has invoice_data.document_number, match that source path to the invoice’s document identifier rather than entering a sample invoice number as a fixed value.
3. Choose a format if the value needs one. Review the source and destination together before moving to the next field.
4. In the filter menu, select Mandatory → Pending to find required fields that still have no source. A Conditional Mandatory field needs data when its condition applies to the document you will send.
5. Review the completed mappings and continue to Country Field Mapping. Mapped indicates that a field has a mapping; it does not prove that your sample value satisfies every country rule. Run the test before using the integration.

For field definitions and requirements, use the GETS field reference. Select your country and document type there; do not copy a field list from another country or invoice type into this mapping.

If something goes wrong

A required field has no matching source: add it to the invoice data your system supplies, then use a representative sample that contains it. Selecting an unrelated field only hides the omission.

The same field seems to need a different format: inspect the actual value in the sample, choose the matching format, and retest. A successful field match alone is not a validation result.

The mapping looks right but validation fails: compare the reported field and message with the sample value in Test your mapping.

Next, map country fields for this invoice.