How to map Acrobat Sign data fields back to Microsoft SharePoint lists

Re-keying tax IDs, addresses, and contract values from signed PDFs into SharePoint invites errors. Mapping Acrobat Sign fields to SharePoint lists lets signer-entered values update list columns after completion.

1. Prepare document form fields

In your Acrobat Sign template, give every input a precise, unique name — for example Txt_CustomerTaxID, Txt_CompanyAddress, Num_ContractValue. Avoid generic labels like “Text1”.

2. Align SharePoint list columns

Create list columns with matching types (single line of text, number, date). Keep internal names predictable so admins can map without guesswork.

3. Configure Acrobat Sign ↔ SharePoint mapping

1. Open your SharePoint / Acrobat Sign integration settings for the site or tenant (wording varies by package version).
2. Create a mapping definition for Agreement → List (inbound).
3. Map each Sign field name to the target SharePoint column.
4. Test with a single agreement in a non-production list before enabling for HR or vendor libraries.

Acrobat Sign field          →  SharePoint column
Txt_CustomerTaxID           →  Client_Tax_Identifier
Txt_CompanyAddress          →  Company_Address
Num_ContractValue           →  Contract_Value

For file archiving of the signed PDF itself, use Power Automate. For intranet embeds, see SharePoint embed guide.

Sign integration manuals