March 2026 Ordway Platform Release Notes

Enhancing reporting flexibility, financial accuracy, and overall system performance.

Key Highlights

Analytics

Enhancements focused on increasing reporting flexibility and portability—enabling teams to build fully customizable dashboards and seamlessly migrate report configurations across companies and environments. 

Customizable Dashboards NEW FEATURE

You can build tailored dashboards using drag-and-drop widgets including charts, tables, KPI cards, and custom metrics.

Widgets can be resized, reordered, and configured with metric selection, time range, grouping, and formatting options. Layout and settings are saved explicitly using the Save action.

You can create, duplicate, delete, and manage multiple dashboards. Dashboards are private by default and support configurable View and Edit permissions.

Global filters (Example: Date Range, Customer) refresh compatible widgets instantly. Table widgets support CSV export with applied filters and permission controls.

For more details, see Custom Dashboard Builder – Ordway Support Portal

Grouping Support in Report Downloads and Scheduled Exports ENHANCEMENT

When grouping is enabled in the report view, the downloaded or scheduled file will reflect the same grouping structure shown on screen.

This enhancement applies to both manual downloads and scheduled report exports (email delivery). Users can select the export format during download or while scheduling the report.

Supported Formats 

Excel (XLS/XLSX) only. Grouping will not be applied when CSV or PNG formats are selected.

Grouping will not be applied when unsupported formats are selected.

Benefits

Ensures consistency between reports and exports, reduces manual data rework, and improves usability for grouped reporting.

Export Enhancements: Export History Includes Scheduled Reports ENHANCEMENT

The Export History page under Analytics → Reports now includes both manual report exports and scheduled report runs.

This enhancement improves visibility into report activity, reduces navigation overhead, and simplifies monitoring of exports and scheduled reports.

Availability: The Export History page is available for all users with access to Analytics reports.

For more details, see Export History – Ordway Support Portal

Accurate MRR for Paused & Resumed Subscriptions ENHANCEMENT

• Paused subscriptions are excluded from MRR during the pause period
• MRR is automatically included again when subscriptions resume

This ensures MRR consistently reflects active, billable revenue across analytics, exports, and reports.

For more details, see MRR by Customer and Subscription – Ordway Support Portal

Finance

Enhancements focused on improving billing accuracy, automating usage-based revenue workflows, and strengthening financial control and audit integrity. 

Exchange Rate Stability for Subscription Changes ENHANCEMENT

This behavior applies consistently for Subscriptions, regardless of:

• Separate invoice setting (enabled or disabled)
• Whether an exchange rate is explicitly passed in the request
• Create, update, change, or other mid-cycle actions

During amendments or updates, the current exchange rate remains unchanged. A new exchange rate is applied only upon renewal.

This enhancement ensures billing consistency and prevents unintended exchange rate fluctuations during subscription lifecycle changes.

Event Enhancement: Included Units and Support Prepayments ENHANCEMENT

Previously, support for prepayments in usage-based plans was available only through the UI when adding usage lines. With this enhancement, included units and prepayments can now be defined programmatically for event-based usage contracts.

This enables seamless automation of event-driven billing scenarios while ensuring parity between UI and API workflows.

For more details, see Configure Included Units and Prepayments for Usage-Based Charges – Ordway Support Portal

Smarter Journal Entry Updates for Edited Transactions ENHANCEMENT

Earlier, editing a transaction resulted in deleting and recreating the entire Journal Entry. Now, the system updates only the impacted JE lines—preserving the original Journal Entry record.

This enhancement maintains better audit continuity while reducing unnecessary record churn.

The logic supports complex scenarios where a single transaction generates multiple JEs (e.g., Invoice, Payment, Subscription, FX Adjustment, Parent–Child).

For journal entries affected due to source transaction changes, the Source and User will be recorded as SYSTEM.

All GL integrations with journal sync enabled have been thoroughly evaluated and validated to ensure seamless synchronization

Update Credit Records via Workflows ENHANCEMENT

Previously, the Credit object in workflows only supported two actions: Create Record and Reverse Record. With this enhancement, a new Update Record action has been added.

This allows users to modify existing Credit records directly through workflows by selecting the fields that need to be updated (such as date, notes, or other editable fields). When the workflow runs, the specified field values will be updated automatically.

This update addresses a functional gap specific to Credit workflows and enables greater automation when managing credit-related processes.

Journal Entry Import Without Changing Doc Numbering Rule ENHANCEMENT

Previously, importing Journal Entries automatically changed the Doc Numbering configuration to Manual, which unintentionally affected other processes such as automatic Journal Entries (auto JE) and JE runs.

With this update, the system retains the existing Doc Numbering rule during import. Users must still provide a Journal Entry ID in the import file, but the configuration will no longer switch to Manual.

This change ensures that manual Journal Entries can still be created and updated, and both manual and system-generated Journal Entries can be updated when a valid Journal Entry ID exists, without impacting other automated processes.

Incorrect Invoice Amount Sent to GL Systems ENHANCEMENT

This occurred when a subscription had a flat fee for the first tier and no usage was recorded during the billing period. Although Ordway correctly generated the invoice with the flat fee amount, the integration incorrectly sent the invoice total as $0 to downstream GL systems.

With this fix, invoices now sync with the correct total amount, ensuring accurate financial reporting in connected GL systems.

Platform

Platform enhancements focus on improving search intelligence, data consistency, audit transparency, and workflow performance, delivering more predictable behavior, stronger governance, and streamlined system operations.

Fuzzy & Partial Search (API) ENHANCEMENT

Fuzzy search intelligently matches spelling variations and common letter swaps to return the closest results. Partial search lets you search using just the beginning of a name, while wildcard search adds flexibility by placing * before, after, or within a term.

This capability is currently available via API only and applies to text-type fields across multiple modules.

How this helps: faster lookups, fewer failed searches, and more resilient integrations.

For more details, see Search Mechanisms – Ordway Support Portal

Predictable NEQ filters ENHANCEMENT

NEQ filters support comparisons against null or unset values and explicitly exclude empty or whitespace strings—ensuring predictable results and reducing integration errors.

For more details, see NEQ (Not Equal) Filters - Usage and Empty Value Handling – Ordway Support Portal 

Sync Default Value to Custom Field ENHANCEMENT

What’s New

When you add a new custom field with a default value, you now have the option to enable a Sync Existing Records toggle.

How It Works

• New records will always receive the default value automatically.
• Existing records are updated only if the field is empty.
• Records that already contain a value remain unchanged. 

The sync runs once as a background job to avoid heavy processing on large datasets.

Field support

• Fully supported for text fields
• No impact on formula, inherited, file upload, or multi-select fields

For more details, see Manage Custom Fields

Audit Events for Finance Modules ENHANCEMENT

You can configure audit tracking for up to 10 fields per company (up to 20 fields in higher environments).

For tracked fields, audit logs now display both the previous value and the new value, providing precise visibility into what changed.

Previously available for Platform, Customer, Contact, and Product modules, this enhancement now extends coverage to Finance entities including Credits and other finance-related models.

This update strengthens audit transparency, improves compliance readiness, and enables more granular operational oversight.

For more details, see Audit Logs

SETUP Section Audit Events ENHANCEMENT

You can track field level changes and view detailed before-and-after values directly within audit logs. This builds on the existing audit framework and expands monitoring capabilities to configuration-level updates.

With this enhancement, organizations gain improved visibility into system configuration changes—ensuring better governance, accountability, and change tracking across both operational and financial modules.

Improved Workflow Filtering Using Native FK Relationships ENHANCEMENT

Previously, invoice line processing relied on custom fields to establish relationships for filtering, even though native FK fields (such as invoice_id) already exist in the invoice_lines table. With this update, filtering now directly uses these built-in FK relationships.

This change simplifies query structures, improves indexing efficiency, and enhances overall performance and maintainability.

The same enhancement has been extended to:

• Credit Lines
• Journal Entry Lines
• Revenue Schedule Lines

By standardizing filtering logic across these entities, workflows are now more streamlined, performant, and aligned with the underlying data model.

Sample Screenshot

Plans: Approval Workflow Support ENHANCEMENT

With this enhancement, any changes made to a Plan can go through an approval process before becoming effective. Plans marked for approval will remain in a pending state until reviewed and approved by the designated approver.

What’s New

• Approval process support for Plans
• Plan changes can enter an Approval Pending state
• Approved changes are reflected only after review
• Clear visibility into approval status within the Plan

This ensures better governance over pricing and plan configuration changes, reducing the risk of unintended updates.

Commerce & Payments 

Improvements across quoting, payments, and integrations that simplify deal workflows, enhance payment transparency, and reduce manual effort.

Usage Events Now Visible on Customer Portal ENHANCEMENT

By default, the portal displays: ID, Date, Quantity, Description, Unit of Measure, Status, Invoiced status, Subscription Line ID, Subscription ID, and Charge ID.

If you need to display additional fields (for example, Amount), you can configure them using Custom Fields.

Navigate to Customize → Usages to add either:

• A Text Field
• An Inherited Field, or
• A Formula Field.

Once created, enable the field for display on the Customer Portal and save your changes. The new field will appear on the portal after refresh.

This enhancement provides greater flexibility and transparency for usage-based billing customers.

For more details, see Customer Portal Setup – Ordway Support Portal

Stripe L2/L3 V2.0 Support (Visa CEDP Compliance) ENHANCEMENT

This replaces the legacy enhanced data format with Stripe’s new Payment Line Items–based model for commercial card transactions.

When this feature is enabled, Ordway sends detailed line-item data using Stripe’s latest API structure. Newly created Stripe accounts are automatically mapped to this configuration.

The rollout begins with selected beta customers and will be enabled by default for all companies starting with the March release. The legacy L2/L3 toggle will be deprecated after stabilization.

No action is required for most customers. This update ensures continued eligibility for Visa commercial card interchange optimization under the new CEDP model.

Availability: This feature is turned off by default and can be enabled with the help of the Ordway Customer Success team.

Configure Statement Descriptors Using Custom Fields NEW FEATURE

From Setup → Settings → Payments → Statement Descriptor, select a text-type custom field to define the value that should be sent as the statement descriptor during payment processing. The selected field auto-populates while creating a payment and remains editable before submission.

Once processed, the mapped value is passed directly to Stripe and is reflected in both the Stripe Dashboard and API response.

Currently, text custom fields, Inherited fields and Formula fields are supported. Support for additional custom field types will be introduced in a future update.

For more details, see Statement Descriptor – Ordway Support Portal

Stripe Integration: Sync Combined Stripe Fees to Ordway ENHANCEMENT

Previously, when Stripe applied more than one fee (for example, a processing fee and a currency conversion fee), Ordway synced only a single fee value instead of the combined total.

With this fix, Ordway now aggregates all Stripe fees related to a payment before syncing. The total fee amount is then converted to the payment currency and recorded correctly in Ordway.

This ensures that Stripe processing fees and additional charges (such as currency conversion fees) are accurately reflected in Ordway.

As a result, financial reporting between Stripe and Ordway will now remain consistent, eliminating the need for manual reconciliation.

For more details, see Connect and Manage Stripe Gateways in Ordway – Ordway Support Portal

Payments Gateway Experience Improvements UPCOMING CHANGE

No action is required for customers already using the new experience. If you are currently on the legacy experience, it will automatically transition in April.

We recommend reviewing the updated workflow ahead of the rollout to ensure a smooth transition.

API Updates

Enhancements focused on improving performance, scalability, and cross-environment portability—enabling more efficient revenue data access and seamless migration of report configurations.

Export & Import Report Definition APIs NEW FEATURE

What’s New

You can now:

• Export an existing report’s definition from a source company.
• Import the exported report definition into:
  • The same company
  • A different company
  • A different environment.

API Endpoints

• Export Report
• Import Report 

This enhancement provides greater flexibility for report migration, backup, replication, and cross-environment deployment.

API for Revenue Schedule Line level NEW FEATURE

This enhancement enables direct retrieval of revenue schedule line items without fetching entire parent schedules, significantly improving performance for high-volume accounts. Customers can now query only the data they need, reducing response times and minimizing system load during reconciliation and reporting workflows.

The API supports advanced filtering across both revenue schedule and line-level attributes, including customer, product, charge type, financial period, posting status, revenue amounts, and custom fields. Flexible range operators (gt, gte, lt, lte, eq) allow for precise data retrieval.

For more information, see List Revenue Schedule Lines | Ordway