Upcoming Changes to Transaction Export – Proof Help Center
Proof has updated its transaction export feature by adding new fields previously visible only in the UI (such as risk score, order_of_progress, title_underwriter, lender, and closing_date), introducing entirely new export-only columns (like sender_name, org_name, sender_email, and number_of_seals), and cleaning up duplicate or renamed columns to improve consistency and functionality, while some key columns remain unchanged; users are advised to review these changes and update any scripts or reports accordingly.
These changes are now live. The updated column list is reflected in Transaction Export: Columns and How-To.
The short answer: We're improving the transaction export feature to add new fields, create consistency between the UI and the export, and clean up duplicate or renamed columns. Review the changes below and update any scripts, integrations, or reports that reference the affected columns.
For the current full list of export columns, see Export Transactions. The following columns are not changing and will continue to work as-is: detailed_status, customer_email, source, external_id, scheduled_at, scheduled_at_timezone, completed_at, last_updated_at, archived_at, and cost_center.
New fields are being added to the export
The following fields are already visible in the Proof UI but were missing from the export. They will be added:
- risk: The risk score shown in the UI (for organizations with Proof Defend).
- order_of_progress: Closing Operations status. Relevant for title and lender accounts; visible today in the Open Orders tab.
- title_underwriter: Title underwriter name. Previously available in lender org exports only — now also added to title org exports.
- lender: The lender's brand name (defaults to org name if no brand is set). Title org exports only — lender orgs do not receive this field.
- closing_date: The closing date shown in the lender and title UI. Previously missing from the export.
Entirely new export columns
The following fields do not currently exist in the UI — they are net-new additions to the export only (available to Business and title accounts unless noted):
- sender_name — Name of the user who sent the transaction
- org_name — The organization's name. Previously only the org ID (
account_id) was exported — this is a new, separate field - sender_email — Email address of the user who sent the transaction
- number_of_seals — Total number of notary seals applied
- number_of_recipients — Total number of recipients on the transaction
- number_of_meetings — Total number of meetings associated with the transaction
- number_of_odn_meetings — Number of on-demand notary (ODN) meetings
- number_of_ihn_meetings — Number of in-house notary (IHN) meetings
- number_of_witnesses — Number of witnesses on the transaction
Title and lender field changes
These changes introduce some asymmetry between title and lender org exports.
Previously, only lender orgs had the following four fields in their export: title_agency_id, title_agency, title_underwriter_id, and title_underwriter. Title orgs now receive those same four fields, following the principle that everything visible in the UI should be in the export.
Title orgs also receive two net-new fields: lender_id and lender. Lender orgs do not get equivalent lender fields. This means title orgs now have both title and lender fields in their export, while lender orgs continue to have only title fields.
| Field | Title org export | Lender org export |
|---|---|---|
title_agency_id | New | Existing |
title_agency | New | Existing |
title_underwriter_id | New | Existing |
title_underwriter | New | Existing |
lender_id | New | Not included |
lender | New | Not included |
Renamed columns
| Old name | New name | Notes |
|---|---|---|
expires_at | closing_date | Real estate accounts only. Non-real estate accounts retain expires_at. |
name | transaction_name | More descriptive column name |
customer_name | first_recipient | Standardizes naming across Business, title, and lender accounts |
Removed columns
The following column is being removed to reduce duplication:
- transaction_type — This is a legacy field. The
typecolumn (which reflects the current transaction config) will remain and is the recommended column going forward.
If your workflow currently references the transaction_type, name, customer_name, or expires_at (real estate accounts) columns, update your scripts or integrations to use the new column names.
Summary Checklist
- 5 fields newly added to close the gap between the UI and the export.
- 9 net-new export-only columns added.
- 3 columns renamed — update any scripts or integrations that reference them.
- 1 column removed (
transaction_type) — usetypegoing forward.
Questions? Contact Proof Support for help.
Related
Proof Q3 2026 Product Roadmap
The Proof Q3 2026 Product Roadmap highlights recent launches including Verified Business for trusted organizational profiles, Document Template Application for reusable document tag sets, Risk Decision Summary providing AI-generated risk assessments, and VC Issuance & Presentation API for cryptographically-signed identity verification, with upcoming integration into the Rippling platform to embed identity verification within HR workflows.
2026-03-02 Proof Release Notes – Proof Help Center
On March 2, 2026, Proof released an opt-in, phased rollout of real-time deepfake detection for notary meetings, alerting notaries during live signing sessions to potential deepfake attempts to help Defend customers across all industries reduce fraud losses, with limited availability initially and full general availability expected by the end of March.
2025-09-22 Proof Release Notes
The 2025-09-22 Proof release introduces enhanced Identity tab and report features with failure reasons and downloadable reports, enables Sign Ahead for eSigning before notary meetings on eligible documents, restricts domain users from self-managing transactions via Command Center, and improves video reliability by adding a second WebRTC provider for outage protection and scalability, all generally available to relevant users and organizations.
Upload a Document During a Meeting – Proof Help Center
During a notary meeting, recipients with personal accounts can upload or replace documents on a computer, mobile browser, or the Notarize app when prompted by their notary, who may request this to correct errors or add needed files, with instructions provided for each device type and the ability to rotate or replace documents as necessary.
2025-07-14 Proof Release Notes
The July 14, 2025 Proof release introduces new reporting features for Business and Title Pro plans, expands credible witness call eligibility to Virginia notaries, enhances identity verification processes for clearer outcomes, corrects the selfie retake flow for identity-verified witnesses, updates the Command Center page header, and adds transaction type data to exports.
Why Lenders Are Doubling Down on eMortgage Tech and What It Means for Title Agents
Lenders are rapidly adopting eMortgage technology to reduce closing costs, save time, enhance fraud prevention, and ensure compliance, compelling title agents to adapt to digital workflows like eClose and RON to remain competitive in the evolving mortgage industry.