Hypercore Inc

Hypercore Help Center

Stay updated on the status of all your company's support tickets.

Hypercore Support Request

Customer portal

Using Additional Info (Dynamic Properties) and Data Tables in Hypercore

Hypercore allows users to enhance system data using 

. This guide explains the difference between hardcoded fields and customizable fields ("Additional Info"), how to create them, and when to use a dynamic property versus a data table.

Dynamic properties (also called "Additional Info") allow users to store custom data for any entity in Hypercore—such as loans, clients, funding sources, equity, and more.

Navigate to any entity (e.g., a loan or client)

Find the “Info” tab on the right panel

 (e.g., Client, Product, Purpose, Loan Amount) cannot be modified

All fields, whether hardcoded or dynamic can be hidden (by clicking on the eye symbol when hovering to its right) or reordered (by drag and dropping the left side of the field).

 – uses Google Maps API for full addresses

 – links to another entity (like a Client, Loan, or Funding Entity) or data table (if present) in Hypercore

Data tables are structured sets of information. They’re ideal for storing:

Lists (e.g., contacts, legal reps, assets)

Time-based records (e.g., monthly revenue, inspections)

There are 2 ways you can create a new data table:

From within an entity (loan, client, funding source, etc.)

Select the Table Name and Category Name (Optional)

Select Entity Type (Loan, Client, Funding Entity, etc.)

A version history is available for each row

 when the data is organizational but not tied to one specific loan/client.  

4. Dynamic Properties + Data Tables in Reporting

Dynamic fields and data tables can be embedded into:

This can be relevant for a variety of uses such as additional banking data for invoice statements, geographic information on a portfolio dashboard, creating a portfolio loantape, etc. 

Our import/bulk actions functionality supports uploading data into Hypercore, whether it is additional information or a data table.

From the Bulk Actions module, you can select 

Once inside the import functionality, you can either upload via file (CSV preferred) or manually enter  the data.
 

Reach out to the Hypercore Customer Success team for support or ideas on how to structure your data most effectively: 

Data Tables and Dynamic (Custom) Properties

Bulk Import in Hypercore enables you to process large volumes of data in a single step, either by uploading a CSV/TSV file or by entering rows manually. This feature is especially useful for onboarding, migrating from another system, reconciling reports, or updating information at scale.

 – Use a prepared CSV/TSV/TXT file with one record per row.

 – Enter multiple rows directly in the in-app table.
 

 – Upload loans in bulk; generally used for onboarding. Most complex and large bulk item.

 – Upload new loan terms in bulk.  
⚠️ 

Automatically replaces previous terms; cannot be undone.

 – Transition multiple loans at once from 

 – Upload individual fees per loan, allowing multiple fees per loan entry.

 – Update or bulk load metadata about loans.

 – Upload Fair Market Value (FMV) and methodology for each loan.

 – Upload commitments and expected deployments by date for each loan. 

 – Upload Original Issue Discount (OID) components in bulk.

Upload transactions linked to a funding source.

 – Upload cashflow transactions linked to a funding source.

 – Upload FMV valuations for funding sources.

 Create or update a list of clients in bulk.

 Upload data for custom entity tables (Loan, Client, etc.).

 – Upload equity positions related to loans or clients.

 – Upload valuations for equity positions.

– Override system-calculated OID values (like: OID rate, OID cost etc) for loans.

– Set a baseline snapshot of a loan's aging values for a specific date (used for reporting and analysis).

 – Override Hypercore’s loan schedule calculations. The last row must include 

, which Hypercore uses to calculate future schedules.

Override Hypercore’s funding source schedule calculations. The last row must include 

  Override system-calculated OID values (like: OID rate, OID cost, etc) for funding sources.

 feature demonstrates the standard process used for all bulk imports in Hypercore. While this example focuses on client records, the same steps apply to loans, fees, transactions, funding sources, and other bulk data types.

 From the left-hand navigation bar, click the 

 is included → the existing client will be 

 from the top of the page, fill it out in Excel, and upload it back into the system. (Available for: 

 format. Each row should represent one client. 

 → align your file’s columns with Hypercore fields.

 → preview the data, clean up errors, or remove bad rows.

📘 For another detailed walkthrough, please see the guide on uploading Transactions 

After uploading a file or entering data manually, you’ll arrive at the 

. This step ensures accuracy before the import is finalized.

Validation messages for any mismatches with expected repayment schedules

: If you identify an error after execution, you can revert the entire import batch from the Import screen, or revert an individual record by opening it and clicking Revert in the sidebar.

: Download a file with full details for external review or archiving.

: Clients → Loans → Fees → Transactions.

: Spot-check sample records to confirm data accuracy.

 uploads, since they overwrite existing terms.

Bulk Actions & Imports

 feature in Hypercore allows lenders to efficiently upload multiple transactions at once, either from a CSV file or through manual entry. This is especially useful for importing bank statements, aligning with expected repayment reports, or entering historical data.

This is the most common workflow for importing data in bulk.

Mark the row in your CSV that contains column headers.

Match the CSV columns to platform fields:
 

The platform automatically validates input:

Required fields are highlighted in red if missing.

Dates and numbers must be in valid formats.

Note: Entering both total amount and components simultaneously will trigger an error.

Callout: The recommended approach is to fill in the individual components to avoid mismatches.

Instead of uploading a CSV, you can enter transactions directly into the table.

This method is helpful for entering a small batch of transactions.

After uploading a file or entering transactions manually, you'll be taken to the 

 screen. This screen allows you to review and confirm the imported data before it's finalized.

 is automatically split across components (e.g., principal, interest, fees, compounding) based on the loan’s repayment strategy.

Hypercore validates the imported repayments by comparing them against the 

 defined in each loan’s settings (e.g., fees → principal → interest) to:

Automatically allocate amounts when only a total is provided.

Highlight mismatches between imported and expected repayments.

This ensures that the transactions are aligned with the original amortization logic of the loan.

If there's a mismatch (e.g., the imported transaction differs from the expected schedule), the system will display a warning. You can:

 the warning if the difference is intentional.

After confirming your transactions, you can either:

: allows team members to review and approve.

After uploading and previewing your data, you’ll be directed to the 

 page. This step lets you confirm, export, or save transactions before finalizing them.

: Download a file with full transaction details for external review or archiving.

If a mistake is identified after execution, you can:

This provides flexibility to correct errors without manual cleanup.

Importing Transactions

 is a document that summarizes detailed financial activity, helping you present accurate information to clients, investors, and stakeholders. In Hypercore, statements can include loan details, funding sources, interest breakdowns, and other financial data, making them essential for tracking performance and communicating updates.

 – Regular updates to borrowers or investors

 – Payoff calculations and settlement documentation

 – Billing for interest, fees, or other charges 

 – Statements summarizing positions or allocations

 – Historical loan activity for reporting purposes

- Breakdown of accrued interest and all fees within a chosen period 

You can generate statements for the following entities:

Navigate to the loan or funding entity you want to generate a statement for

 (loan, funding entity, or funding source).

 The statement can be downloaded, saved, or shared with your customer.

You can also generate multiple statements at once:

 A statement will be created for each selected entity 

 with predefined templates for common use cases. If you’d like access to the gallery, or if you require a new type of statement tailored to your needs, please contact our support team at 

Data Management