Connect the application, its supporting evidence, and the agreement that follows.
FormKiQ's packaged Financial Application Management Business Solution brings application workflows, document generation, signature integrations, and retail agreement records together in your AWS environment. Teams can manage financing and leasing applications, collect supporting documents, route reviews, generate the resulting agreements, and retain the complete application and agreement file.
Some customers need the application workflow, others need document generation and signing, and many use both. The solution can support those stages together or connect the required stages to existing retail, finance, and lending systems.
Example in FormKiQ · fictional data
One application file, from intake to signed agreement
1. Collect the application
Staff add applicant details and supporting documents. FormKiQ shows what is still missing.
How FormKiQ handles this step
- Applicant entity: Northfield Equipment's reusable business record.
- Application dossier FIN-1042: connects financing details, the applicant, and supporting documents.
- Business Solution application: checks required items and guides staff through submission. Documents retain their own permissions and history.
2. Review and approve
The reviewer checks the evidence and approves, or returns the application with correction comments.
Lending decisions remain with the authorised reviewer or connected lending system.
How FormKiQ handles this step
- Review summary: a document connects the information under review to FIN-1042's supporting evidence.
- FormKiQ workflow: routes the review document and records the reviewer's decision and comments.
- Business Solution application: updates the next action and, on approval, saves the data snapshot used to generate the agreement.
3. Generate the agreement
Staff select an approved template. FormKiQ creates the agreement using the approved application data.
How FormKiQ handles this step
- Inputs: the approved data snapshot from FIN-1042 and an approved Word template.
- Document Generation: produces the selected PDF or DOCX output.
- Application dossier: links the generated agreement to the application and the information used to create it. Signing is the next step.
4. Sign and return
Staff send the agreement through DocuSign. The signed document and signing evidence return to the application file.
How FormKiQ handles this step
- eSignature Integration: sends the selected agreement and recipients to DocuSign.
- Business Solution application: displays the signing status received from the integration.
- Application dossier FIN-1042: links the returned signed document and signing evidence to the applicant, source evidence, and approval.
Agreement connected to FIN-1042
Is this the right fit?
Where FormKiQ fits
Teams that need a packaged application-to-agreement workflow, or generation and signing alongside an existing finance system, with API integration and control of sensitive records.
When to consider another option
Choose a specialist lending platform when the main requirement is a loan ledger, servicing, collections, or credit decisioning. Specialist loan-document content and standalone signing services may also be the more direct fit.
What your solution includes
| Component | Scope |
|---|---|
| Application | Financial Application Management Business Solution, scoped to the stages your operation needs. |
| Configuration | Application types, evidence requirements, review rules, agreement templates, and record access. |
| Selected modules | Document Generation, eSignature Integration, and optional AI processing, search, and integrations. |
| External services | Credit checks, lending decisions, servicing systems, and signature-provider subscriptions as applicable. |
Commercial scope includes the platform license, selected modules, implementation, and support. AWS usage and external services are separate cost components. See edition pricing and Enterprise vendor-managed deployment. A Business Solution evaluation is scoped to these requirements; the Essentials Proof of Value has its own defined scope.
Follow the data and the responsibilities
A customer-managed deployment puts the primary document and metadata resources in your AWS account. Storage location, processing geography, and operational access are separate configuration decisions.
1. Store and organise
Documents, metadata, indexes, and configured logs live in the selected deployment. Define regions, replication, backups, access policies, and key controls for each resource.
2. Process with defined boundaries
Bedrock requests use the deployment's AWS permissions. The selected model and inference profile determine processing geography. A connected signature, credit, or other external service has its own processing boundary.
3. Retain the result and evidence
Keep generated documents, accepted metadata, review decisions, and returned signature evidence with the business file. Assign access, retention, and operational responsibilities.
| Deployment | Account and operations | FormKiQ access |
|---|---|---|
| Customer-managed | Your AWS account and operational policies. | Access only when you grant it for the agreed support purpose. |
| Vendor-managed Enterprise | A dedicated, segregated AWS account operated by FormKiQ. | Defined operational access, policies, and audit records. |
| Hybrid | Customer-managed production, with agreed support in non-production. | Access scoped to the agreed environment and responsibilities. |
For Bedrock, regional and geographic inference options must match your approved boundary; global profiles may route across supported regions worldwide. Review AWS inference routing and FormKiQ security and governance with your deployment requirements.
Financial applications and retail agreements
A retail finance or leasing agreement is the result of a business process. The application, applicant and product information, financial documents, review decisions, generated agreement, signatures, and later correspondence belong to the same file.
This differs from a general contract management process centred on negotiating commercial terms. Financial Application Management starts with an application and its evidence. It supports repeatable review and agreement workflows, while the Contract Management Business Solution addresses the wider contracting lifecycle.
- Financing and leasing applications submitted through a retail or sales channel
- Collection and organisation of supporting documents and application data
- Review, approval, exception handling, and connected external checks
- Agreement generation from approved templates and application information
- Signature workflows and return of executed agreements to the governed file
- Ongoing agreement access, amendments, correspondence, and retention
Packaged application with an extensible platform
Business Solutions provide a packaged route to the workflow. FormKiQ's APIs also connect the application and agreement file to existing systems, so a customer can use the packaged application, integrate particular stages, or extend the solution around its own process.
Document Generation, AI Processing and Analysis, eSignature Integration, search, and integration modules are selected according to the deployment's requirements. Business Solutions are available through the commercial platform; the open-source Core foundation and the packaged solution have different scope.
Coming soon: FormKiQ's own built-in eSignature feature. Current signing workflows use the available eSignature Integration module.
Related capabilities
Generation, AI, and eSignature modules · Contract Management · Records Management · Editions and support
Evidence you can inspect
Customer experience · migration
RGF Staffing Belgium: 20M+ documents
Micha Van Nijen, Integration Architect at RGF Staffing Belgium, describes the move from Alfresco to FormKiQ and its connection to the organisation's applications.
Read the customer snapshot and original accountEngineering case study · import processing
Tracing and removing an import bottleneck
See the measurements, architecture change, and test conditions behind an optimised 100,000-document import run. The article reports Lambda duration for that workload, with a concurrency caveat.
Inspect the performance case study