# Fill Financial Documents for Account Openings

Feathery maintains a library of 40,000+ financial PDF forms across major financial institutions that allow for automated filling and e-signature. Collect the information in your Feathery workflow and then automatically fill that information into a set of financial PDF forms.

## Getting Started

Navigate to the Feathery form that you want to set up. Click on the **Integrations** tab and navigate to the [Quik integration](https://www.feathery.io/integrations/quik). Follow the configuration guide below, and once configured, click **Connect** to activate your integration and the form filling workflow.

## Authenticate

Open the Quik integration and input your Quik account credentials. If you do not specify account credentials, a test account will be used by default.

<figure><img src="/files/uWcC9S4SDeFiGYHovPxx" alt="" width="375"><figcaption></figcaption></figure>

## Choose Forms to Fill

Specify if you want to choose a static list of Quik PDF forms to fill out or dynamically configure the forms, ordering, and prefill logic. The second option is useful for more complex use cases that have complex mapping rules and need to pull from third-party systems like CRMs.

### Static Form IDs

Specify a list of Quik PDF form IDs that you'd like to connect to your Feathery form workflow. You can also make specific forms conditional by appending `:<FieldId>` to the Quik PDF form ID you specify. Here, `FieldId` refers to a field within your Feathery form. These Quik PDF forms will only be included and filled out if your submission has a value for the field corresponding to `<FieldId>`.

<figure><img src="/files/EiGlvT34yXBrHVzypK7A" alt="" width="375"><figcaption></figcaption></figure>

### Dynamic Form Order and Prefill

In this approach, the included forms, order, grouping, and data prefill configuration are all specified via a data structure stored into a hidden field. This is useful for advanced mappings that might also need to integrate with third-party data sources like a CRM. This hidden field will need to be constructed via [advanced logic](/platform/build-forms/advanced-logic.md).

<figure><img src="/files/zyByMl28LHCql06t0KCe" alt="" width="375"><figcaption></figcaption></figure>

The base format of the hidden field is `[{"forms": [{"id": <Form ID>}]}]`, where `<Form ID>` is the ID of a Quik form to include. Each object in the array corresponds to a bundle of forms that will be filled with separate data. The forms will be filled and displayed in the same order that they're in within the array.

If your Salesforce account is connected and you have a [Salesforce prefill mapping](#salesforce-prefill) specified, you may include a `salesforce_prefill` property in the format `[{"object": <Salesforce Object Type>, "id": <Salesforce Object ID>, "quik_entities": [<Quik Entity>]}]` to specify a list of Salesforce objects to pull from and their corresponding Quik entities to map to.

If you have a [CSV mapping uploaded](#map-feathery-form-fields-to-quik-form-fields-via-csv) between Feathery and Quik fields, you may include a `csv_prefill` property in the format `["1ben", "2ben"]` to specify a list of Quik entities to pull in the corresponding Feathery field data for.

You may also include a `feathery_prefill` property in the format `[{"repeat_index": 0, "quik_entities": ["1ben", "2ben"]}]` . This allows you to [connect Quik mappings](#map-feathery-form-fields-to-quik-form-fields-via-ui) specified directly on the properties of a form field.

## Other Form Fill Settings

You can also configure other miscellaneous settings related to filling out Quik forms such as enabling draft mode, showing Quik field IDs on the generated PDFs, and statically predefining Quik field values to fill out on the generated forms.

## Connect Data to Quik Forms

Aside from specifying which Quik PDF forms to fill out via your Feathery workflow, you'll also need to configure how the data within the forms are filled out. At a high level, there are two main ways you can do this - send data collected from the Feathery workflow directly and/or pull it in from third party systems like a CRM.

### Map Feathery Form Fields to Quik Form Fields via CSV

You can map Feathery fields to Quik fields by uploading a spreadsheet with two columns - `Feathery Field` and `Quik Field`. Each column contains the corresponding IDs for that field type.

<figure><img src="/files/GhqYvOEkWfP0WnddhMaM" alt="" width="563"><figcaption></figcaption></figure>

### Map Feathery Form Fields to Quik Form Fields via UI

You can also map a given form field to a Quik field by mapping it from the Feathery designer. Select the field, go to the `Properties` tab, and under the `Quik Field` section you'll be able to specify the data set and field ID.

<figure><img src="/files/z3yr5NMoPOqL0DYyaciq" alt="" width="563"><figcaption></figcaption></figure>

### Map Data from Third-Party Systems

You can pull in data from third-party systems like a Salesforce CRM. For Salesforce, Feathery streamlines the process of integrating Salesforce with Quik by allowing users to upload a CSV file that defines how fields map between the two systems. This eliminates the need for manual data entry and ensures accuracy in your Salesforce API connectors when creating or updating records.

### Map Static Field Data

Define static data to be filled into specific Quik fields. Each line must include the Quik field ID, the value to fill into the field, and an optional comma-separated list of form IDs that this mapping applies to. Each of these 2-3 values must be separated with a colon. The structure may look something like: `1rep.BDCompany:Feathery Advisors:12,100,23` .

You may also specify the same Quik field multiple times on different lines with different form IDs conditionally applied. For a particular form, the entry more specifically targetted towards that form will apply.

<figure><img src="/files/7MKXxMKLIVSzUVi0Bmis" alt="" width="563"><figcaption></figcaption></figure>

#### CSV Format

* Your CSV file must contain three columns:
  * **Salesforce Object** – The specific Salesforce object (e.g., Account, Contact, Lead).
  * **Salesforce Field** – The field within the Salesforce object
  * **Quik Field** – The corresponding field in Quik that maps to the Salesforce field.
* Each row in the file represents a single mapping between a **Salesforce field** and a **Quik field** for a given Salesforce object.

<figure><img src="/files/h5s4j9bZCBEBrWCWi3lE" alt="" width="375"><figcaption><p>CSV containing Salesforce &#x3C;> Quik field mapping information</p></figcaption></figure>

#### Automatic Field Prepopulation

Once this mapping is specified, the following will occur:

* When leveraging [dynamic form prefill](#dynamic-form-order-and-prefill), you can specify the `salesforce_prefill` property which will automatically leverage this mapping to pull data from Salesforce.
* Feathery will automatically detect and apply the mappings from your CSV when building Salesforce API Connectors. Feathery will pre-populate the mapped fields with the corresponding Feathery field ID:

<figure><img src="/files/9EirHv5DDrN1L33BgJF2" alt="" width="563"><figcaption></figcaption></figure>

### Value Transformation

You can define an optional **Value Map** column in both the Feathery and Salesforce Quik field mapping CSV uploads. When present, it defines a set of transformation rules that are applied to field values before they are mapped to Quik at prefill.

**CSV Format**

Add a `Value Map` column to your existing field mapping CSV:

| Feathery Field     | Quik Field         | Value Map         |
| ------------------ | ------------------ | ----------------- |
| disclosure\_signed | App.DisclosureSign | true->1\|false->0 |
| applicant\_name    | App.ApplicantName  |                   |

Each entry in the Value Map column is a `|`-separated list of `from->to` transformation pairs. For example, `true->1|false->0` will convert the value `true` to `1` and `false` to `0`. If there is no value map defined for a field, or the field's value does not match a mapping rule, the field value will be passed to Quik unchanged.

**Catch-all Transformations**

You can define a `*->to` mapping that applies to any value not matched by another transformation rule in the Value Map. This is useful when you want to standardize unexpected inputs.

How it works:

* Explicit `from->to` rules take precedence. The catch-all only applies when no other rule in the Value Map matches the incoming value.
* Empty values are never transformed by the catch-all. A blank field will be passed to Quik as empty, even if `*->to` is defined.

### Generate Forms

Typically, you would add a button to the final step of your form that will generate the auto populated Quik forms based on the mappings configured previously. Select the button and navigate to the Button **Properties** tab. Choose the action **Fill Quik Documents**.

<figure><img src="/files/KTHSSoKdWpt5EICVTNiq" alt="" width="563"><figcaption></figcaption></figure>

Under the **Sign Method** dropdown, you can pick either `Feathery` or `Quik`. This controls the behavior of the Quik PDF forms after they are filled.

* **Feathery**: Your Quik PDF forms will be e-signable through Feathery or directly downloaded.
* **Quik**: Your Quik PDF forms will be displayed in a custom form viewer in the workflow for easy review. This option also supports a DocuSign integration to seamlessly send the forms for e-signature afterwards.

<figure><img src="/files/RMkOdNidPlr7cE3XlOlE" alt="" width="344"><figcaption></figcaption></figure>

## eSignature Setup

### Feathery eSign

Feathery's [native eSignature solution](/platform/document-autofill-and-signatures/signature-workflows.md) is great for all use cases that don't involve a specific requirement for a different eSignature platform. This can be used seamlessly with the **Feathery** sign method above.

### Docusign

Feathery offers a native Docusign integration through Quik for custodians that require eSignature of completed documents through Docusign.

1. Enable the DocuSign connection in your Quik Forms App. Refer to the relevant [Quik! documentation](https://support.quikforms.com/hc/en-us/articles/360018360051-DocuSign-How-to-Connect-to-an-Account-Admin) for more details.
2. On your [Fill Quik Documents](#generate-forms) button action, click **Enable DocuSign** and include the name of your Docusign connection(s). If a test connection is specified, it will be used on the test Feathery form and the normal connection will be used on the live Feathery form.
3. The Quik integration configuration under the **Integrations** tab offers more extensive customization options for the e-signature process, including custom invite emails, routing patterns, and more.

<figure><img src="/files/V8gI2oKtMxIHYOLOvvzw" alt="" width="375"><figcaption></figcaption></figure>

## Route Completed Documents

Once your forms have been e-signed through Feathery or Docusign, you can automatically route them to an end system. Some examples are included below.

### Salesforce

When Salesforce sync is enabled, you can have Docusigned envelopes automatically be sent back to your Salesforce account, attached to a custom record type, and custom Docusign information populated into the record as well.

<figure><img src="/files/2LhNPoJIGifWPAq77D7y" alt="" width="375"><figcaption></figcaption></figure>

### eFax

Signed documents can be configured to be e-faxed to custom fax numbers depending on the form.

## Feathery Form Templates

Feathery allows you to build Feathery forms from a list of supported Quik forms.

Click the **Create Form** button and choose the **Financial Services Form Library** option.

<figure><img src="/files/t4Ak5s4jQNmVlcKxFj6T" alt="" width="563"><figcaption></figcaption></figure>

In the **Template** dropdown, select a Quik form to use for building your Feathery form:

<figure><img src="/files/ITXI1cwJfxp4B0eZ2mRX" alt="" width="563"><figcaption></figcaption></figure>

Click **Create**, and a Feathery form will be generated that includes all form fields automatically linked to the corresponding Quik! form fields.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.feathery.io/guides/fill-financial-documents-for-account-openings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.