Finicity

Finicity provides access to borrower bank account and transaction data in JSON format. Depending on your integration, Finicity JSON data may be obtained through borrower-initiated flows, backend processes, or batch data retrieval.

Ocrolus does not require a specific Finicity integration pattern. As long as the Finicity JSON files are generated by Finicity and belong to the same data pull, they can be ingested into Ocrolus for processing.

Uploading Finicity JSON to Ocrolus

Finicity provides bank data across multiple JSON files that together represent a complete data bundle. To ingest Finicity data into Ocrolus, perform the following steps:

1. Create a new Book to house the Finicity data.
2. Upload the required Finicity JSON files (accounts, transactions, customers, and institutions) to the Book using the Upload Aggregator JSON endpoint.
3. Once the Finicity JSON data is successfully ingested, borrower bank data can be accessed using Ocrolus’s Transactions and SMB analytics endpoints.
4. Finicity uploads must include all required JSON files from the same Finicity data pull. Partial uploads are not supported.

📘

Note

• Finicity JSON ingestion is used for analytics enrichment and does not perform reconciliation against PDF bank statements.
• Ensure that all cross-file identifiers (such as account IDs, customer IDs, and institution IDs) resolve correctly across the uploaded files.
• Subscribe to the document.verification_failed webhook event to receive notifications if JSON reconciliation fails. To learn more, see the Webhook page.

Rejection reasons

While parsing the document, a document may be successfully uploaded but later rejected during processing. Common rejection reasons include:

• Finicity JSON Parse Error: The uploaded Finicity JSON file could not be parsed due to invalid or malformed data.
• Finicity Customer Not Found: The accounts.customerId does not match any customer.id in the customers JSON.
• Finicity Institution Not Found: The accounts.institutionId does not match any institution.id in the institutions JSON.
• Finicity Account Not Found: The transactions.accountId does not exist in the accounts JSON.
• Finicity Insufficient Transaction Data: The uploaded Finicity transactions JSON does not contain sufficient data to generate periods for the account.