To connect Vendor Bills with Purchase Orders, it is necessary to set both orderDoc and orderLine on line-items level (showing only relevant parts of the export config):

{
 "export_configs": [
 {
 "payload": {
 "method_name": "upsert",
 "method_args": [
 {
 "tranId": "@{document_id}",
 "itemList": {
 "_ns_type": "VendorBillItemList",
 "item": {
 "$FOR_EACH_SCHEMA_ID$": {
 "schema_id": "line_item",
 "mapping": {
 // …
 "_ns_type": "VendorBillItem",
 "orderDoc": "@{item_po_match}", // PO internal ID
 "orderLine": "@{item_po_item_line_match}" // Relevant line-item number from PO (itemList.item.line)
 // …
 }
 }
 }
 }
 // …
 }
 ]
 }
 }
 ]
}

Note that the combination of Purchase Order and line item no. can appear only once in the payload. In case it appears twice on the invoice then it's necessary to group the line items before exporting.

You can leverage JSON Templating to introduce conditions into the configuration. For example, in this example, we are changing document (NS) type based on the detected document type:

{
 "_ns_type": {
 "$DATAPOINT_MAPPING$": {
 "schema_id": "document_type",
 "mapping": {
 "tax_credit": "VendorCredit",
 "tax_invoice": "VendorBill"
 }
 }
 }
}

Similarly, for line items and so on:

{
 "_ns_type": {
 "$DATAPOINT_MAPPING$": {
 "schema_id": "document_type",
 "mapping": {
 "tax_credit": "VendorCreditItemList",
 "tax_invoice": "VendorBillItemList"
 }
 }
 }
}

Consider implementing this $DATAPOINT_MAPPING$ condition higher in the configuration tree and duplicating the whole sections to avoid too complex conditional configurations.

Custom fields on header level are usually prefixed by custbody_:

{
 "customFieldList": {
 "_ns_type": "CustomFieldList",
 "customField": [
 {
 "value": "@{amount_total}",
 "_ns_type": "StringCustomFieldRef",
 "scriptId": "custbody_captured_total_amount"
 }
 // …
 ]
 }
}

Custom fields can also be added conditionally using special $IF_SCHEMA_ID$ syntax:

{
 "customFieldList": {
 "_ns_type": "CustomFieldList",
 "customField": [
 {
 "$IF_SCHEMA_ID$": {
 "mapping": {
 "value": "@{amount_total}",
 "_ns_type": "StringCustomFieldRef",
 "scriptId": "custbody_captured_total_amount"
 },
 "schema_id": "amount_total"
 }
 }
 // …
 ]
 }
}

Line item custom fields are usually prefixed by custcol_. They also must be nested in the item list:

{
 "itemList": {
 "item": {
 "customFieldList": {
 "_ns_type": "CustomFieldList",
 "customField": [
 {
 "value": "@{ns_custcol_some_field}",
 "_ns_type": "StringCustomFieldRef",
 "scriptId": "custcol_some_field"
 }
 // …
 ]
 }
 }
 }
}

Custom fields are represented by the type CustomFieldRef, which is an abstract type. The table below contains a list of concrete custom field types that extend the CustomFieldRef type:

For more information, please visit this link.

You can reference earlier export stages by accessing pipeline_context variable. In the following example, we use pipeline_context for attaching file uploaded to the NetSuite File Cabinet. Note that the configuration uses original_file_name variable from the Get document information serverless function.

original_file_name serverless function

from txscript import TxScript

def rossum_hook_request_handler(payload):
 t = TxScript.from_payload(payload)

 # Original file name:
 t.field.original_file_name = payload.get("document").get("original_file_name")

 return t.hook_response()

{
 "export_configs": [
 {
 "payload": [
 {
 // … upsert VendorBill here as usual
 },
 {
 "method_name": "add",
 "method_args": [
 {
 "name": "@{original_file_name}",
 "folder": {
 "type": "folder",
 "_ns_type": "RecordRef",
 "internalId": "123456"
 },
 "content": {
 "$GET_DOCUMENT_CONTENT$": {}
 },
 "_ns_type": "File",
 "attachFrom": "_web",
 "description": "VendorBill processed by Rossum"
 }
 ]
 },
 {
 "method_name": "attach",
 "method_args": [
 {
 "_ns_type": "AttachBasicReference",
 "attachTo": {
 "type": "vendorBill",
 "_ns_type": "RecordRef",
 "internalId": "{pipeline_context[0].internal_id}"
 },
 "attachedRecord": {
 "type": "file",
 "_ns_type": "RecordRef",
 "internalId": "{pipeline_context[1].internal_id}"
 }
 }
 ]
 }
 ]
 }
 ]
}

Notice also the highlighted $GET_DOCUMENT_CONTENT$ which returns the content of the original file.

Vendor credits can be linked to vendor bills via applyList configuration. Note that the credits can be applied only "Open" vendor bills and always to VB line 0. In this example, we apply the whole credit note value to the specified vendor bill:

{
 "applyList": {
 "$IF_DATAPOINT_VALUE$": {
 "schema_id": "ns_status_match",
 "value": "Open",
 "mapping": {
 "apply": {
 "doc": "@{ns_internalId_match}",
 "line": "0",
 "apply": true,
 "amount": "@{amount_total_normalized}",
 "_ns_type": "VendorCreditApply"
 },
 "_ns_type": "VendorCreditApplyList"
 }
 }
 }
}