Transaction Import Template

Transaction Import Template

The Transaction Import Template is the standardized spreadsheet used to create or update transactions inside Lendware. This template ensures your data maps correctly to the system and prevents upload errors. Below is a step-by-step guide on how to complete the template successfully.

Access the contact template here.

Required Fields for Transaction Creation

Each row in the template represents one transaction (loan). To create a transaction in Lendware, the following fields are required:

Transaction-Level Requirements

  • Loan Number (must be present for every row)

Borrower / Associated Contact Requirements

Any borrower or associated contact (borrower, co-borrower, title rep, agent, partner, etc.) must follow the same rules as the Contact import:

  • First Name
  • Last Name
  • At least ONE unique identifier:
    • Email, or
    • Phone Number

If these requirements aren’t met, the contact—and therefore the transaction row—will fail to import.

Deduplication Rules for Associated Contacts

Lendware applies the same deduplication logic in transaction imports as in the Contacts import.

System Deduping Behavior

  • No two contacts may share the same phone number
  • No two contacts may share the same email
  • Every contact must have at least one unique identifier

 

If a contact has both an email and phone number, and even one of those is duplicated, the second contact attempting to be imported will fail and be marked as invalid.

Required Loan Officer Information

Every transaction must be associated with a Loan Officer so our team knows where to place the loan and which user owns it.

Loan Officer Columns

The template includes fields for:

  • Loan Officer First Name
  • Loan Officer Last Name

These must match how the user appears in your Lendware system.

If the Loan Officer Belongs to More Than One Team

Some loan officers are assigned to multiple branches or teams. If this applies:

  • Include the Team Name (the specific team this loan should be imported under).
  • This ensures the transaction imports into the correct team hierarchy and permissions structure for that LO.

Example

Loan Officer: Chris Walker

Teams: “Arizona Branch” and “Corporate Team”

If the loan belongs under Arizona: Team Name: Arizona Branch

If left blank, we will default to the team named after or close to the user’s name.

Contact Blocks Within the Transaction Template

The template contains multiple “contact blocks,” such as:

  • Borrower
  • Co-Borrower
  • Referral Partner
  • Listing Agent / Buyer’s Agent
  • Title / Escrow
  • Brokerage / Transaction Coordinator
  • Other partners depending on your account configuration

For any contact block you choose to complete, all standard contact rules apply:

  • First & Last Name are required
  • Email or phone must be unique
  • Duplicate values will invalidate the row

Blank contact blocks are ignored.

Completing the Drop-Down Fields

There is one required dropdown field:

Property State

  • Use the two-letter state abbreviation (e.g., UT, OR, GA)
  • Only dropdown-approved values will be accepted

This ensures clean reporting and prevents import errors.

Other Transaction Details

All additional transaction fields—status, term, property details, partner info, appraised value, notes, etc.—are optional unless your internal workflow requires them.

Do not delete, rename, or rearrange columns.

Mapping Custom Fields (Optional)

If you use custom transaction fields:

  1. Scroll to the far right of the template
  2. Add a column for each custom field
  3. Use the exact custom field name from your Lendware configuration
  4. Input your data beneath those headers

This ensures successful importing into custom data fields.

File Format Requirements

Lendware accepts:

  • .csv
  • .xlsx

Best practice: Save and upload as a CSV for best results.

Before You Upload: Quick Checklist

  • Loan Number is present for every row

  • Borrower/associated contacts include First Name, Last Name, and a unique email or phone

  • No duplicate emails or phone numbers anywhere in the fill

  • Property State uses approved dropdown values

  • Loan Officer First & Last Name are correct

  • Team Name is included when the LO is on multiple teams

  • Custom field names match your Lendware config

  • File is exported as CSV

  • No template columns were moved, renamed, or removed

    • Related Articles

    • Import Transactions via CSV or XLSX File

      Managing your own Transaction Imports can be completed in a matter of just a few steps and a little bit of organization ahead of time. You can easily import your transactions into Lendware with a CSV or XLSX file. These file types are standard and ...

    • Anatomy of a Transaction

      A Transaction Record contains the core details of a loan—pulled from your LOS or added manually. It helps track loan progress, update statuses, manage contacts, and support communication. Transactions themselves are viewed a little differently from ...

    • Transaction Detail View – A Walkthrough

      The new Transaction Detail View provides a clear and organized way to view and manage your transactions. All information is separated into intuitive tabs, giving you everything at a glance—making it easy to update, track, and stay on top of every ...

    • Using Custom Transaction Fields

      Default fields are great for capturing standardized information to help identify and understand each transaction in your database. But often, you and your team may want to track additional details specific to your process. That’s where Custom ...

    • Create and Save Transaction Filters

      Creating and saving commonly used transaction filters can save time and streamline your team’s processes. Filters help with repeatable tasks, re-targeting, check-ins, and pipeline reporting. In this guide, we’ll show you how to create basic ...