Tax integration field map fields

  • Release version: Australia
  • Updated July 29, 2026
  • 1 minute to read

    • Field descriptions for the Tax integration field mappings [sn_spend_intg_tax_field_map] table, which defines the outbound and inbound mappings that transform invoice data between APO and a tax engine.

    Tax integration field map fields

    The Tax integration field mappings [sn_spend_intg_tax_field_map] table drives the transformation of invoice data between APO and the tax engine. Mappings are maintained as configuration rather than script. The following table describes the fields.

    Table 1. Tax integration field map fields
    Field Description
    Type Direction of the mapping. Set to outbound for the request that is sent from APO to the tax engine, or inbound for the response that is returned from the tax engine.
    Transaction type Transaction type that the mapping applies to, such as invoice tax verification.
    Source table Table that the source data is read from.
    Source field Field that the value is read from on the source table.
    Target field Field that the value is written to in the target payload.
    Target entity Entity in the target payload that the target field belongs to.
    Target tax engine Tax engine that the mapping applies to, such as Vertex.
    Mapping type Vertex's tax response is converted back as JSON format into internal staging record.
    Version Version of the mapping set.
    Order Order in which the mapping is applied.
    Active Status of the mapping. The transformation uses active mappings only and excludes inactive mappings and mappings for a different tax engine.