Release InformationThe April 2026 release brings powerful updates across:
|
Key Highlights
- Consistent Revenue Reporting - Standardized usage charge handling and Order Date (Booked Date)–based ARR/MRR for accurate and aligned metrics
- Accurate Financial Operations - Line-level tax support, subscription journal reversals, and improved NetSuite integration
- Flexible Integration Management - Custom field mappings and enhanced dashboard for faster error resolution
- Simplified Usage Billing - No-code meter configuration with simulation to validate billing logic
- Enhanced Customer Operations – Improved subscription updates and credit approval workflows
- Stronger Audit & Observability – Field-level audit logs and structured webhook logging for better traceability
- Improved Payments Experience – Enhanced gateway UI with HMAC-based webhook authentication for increased security
- Unified Payments Platform – Ordway Payments to manage payments, refunds, payouts, and reconciliation
- Developer-Friendly APIs – Standardized error responses and support for aggregation and advanced queries
Analytics
Enhanced ARR and MRR reporting to deliver greater consistency and flexibility in revenue analysis.
Standardized “Include Usage Charges” Filter Across ARR & MRR Reports
ENHANCEMENT
| We’ve enhanced ARR and MRR reporting to introduce a mandatory and consistent “Include Usage Charges” filter across all relevant reports and analytics. |
What’s New
A standardized filter — “MRR/ARR By Month: Include Usage Based Charges (Yes/No)” — is now available and required across ARR and MRR reports.
Previously, this option was only available in select reports such as MRR Movements. With this enhancement, the same filter has been extended and enforced across all ARR and MRR reporting surfaces for consistency.
Key Highlights
- Mandatory filter: The Include Usage Based Charges (Yes/No) field is now a required selection when generating ARR/MRR reports
- Consistent experience: Uniform availability of this filter across all ARR and MRR reports
- Explicit control: Users must explicitly choose whether to include or exclude usage-based charges
Aligned metrics: Ensures ARR and MRR values are calculated consistently across reports
For more details, refer to Recurring Revenue Reporting Framework (ARR & MRR) – Ordway Support Portal
MRR/ARR Reporting Based on Order Date (Booked Date)
ENHANCEMENT
| This enhancement introduces the ability to calculate MRR/ARR using the Order Date (Booked Date), allowing finance and revenue teams to reflect bookings earlier in reporting cycles. |
This enables businesses to align reporting with when deals are closed, supporting investor and management reporting needs.
Feature Highlights
- New selectable metric: Order Date / Booked Date
- Available in:
- MRR Reporting
- MRR Movement Analysis
- Supports reporting aligned with contract booking timelines
For more details, refer to Recurring Revenue Reporting Framework (ARR & MRR) – Ordway Support Portal
Finance
Delivered multiple enhancements across finance, integrations, and reporting to improve accuracy, consistency, and operational efficiency.
NetSuite Line-Level Tax Support
ENHANCEMENT
Introduced support for applying taxes at the line level in NetSuite integrations. |
What’s Changed
- Added a new setting to enable line-level tax in NetSuite configuration
- Tax codes are now passed at the invoice/credit line level during sync
- If a matching tax code with rate does not exist, it is automatically created using configured tax agency and tax account
- NetSuite automatically derives and applies the tax rate based on the associated tax code
Impact
- Improves accuracy of tax reporting
- Aligns with NetSuite’s native tax handling
- Eliminates extra tax line items and simplifies reconciliation
For more details, refer to NetSuite Line-Level Tax Integration – Ordway Support Portal
Integration Field Mapping Enhancements
ENHANCEMENT
| Added support to create new field mappings directly within the Integration Settings. |
What’s Changed
- Introduced an “Add” button in the Integration Field Mapping section
- Enables users to create custom mappings between Ordway and external systems (Example: QuickBooks, Xero, NetSuite)
Impact
- Eliminates dependency on predefined mappings
- Provides greater flexibility in integration configuration
- Simplifies setup and customization of field mappings
Integration Dashboard Enhancements
ENHANCEMENT
| Enhanced the Integration Dashboard to improve visibility and resolution of sync failures across integrations. |
What’s Changed
-
Real-time Sync Actions
- Introduced Resync Now for immediate retry of selected records
- Eliminates dependency on delayed jobs for faster processing
-
Improved UI Performance
- Actions like Mark as Resolved now refresh only impacted records instead of the entire page
Impact
- Faster resolution of integration failures
- Improved efficiency in managing large volumes of sync errors
Events and Meters: Simple Mode and Simulation
ENHANCEMENT
| Enhancements to Events and Meters introduce a simplified meter creation experience, especially for non-technical users, along with simulation capabilities to validate metering logic before billing. |
What’s Changed
-
Simple Mode for Meter Creation (Preview)
- Create meters using a no-code interface
- Select event type, apply filters, and choose aggregation (SUM, MAX, MIN, AVG, COUNT)
- Option to convert configurations into SQL for advanced use cases
-
Meter Simulation Capability
- Test meter logic using sample or existing events
- Validate results before applying to billing
- Simulation runs in isolation and does not impact production data
Impact
- Reduces dependency on SQL for defining billable metrics
- Enables faster validation of metering logic
- Improves accuracy and confidence in usage-based billing
For more details, refer to Create and Test Event Meters Using Simple Mode
Subscription Journal Entry Reversal
ENHANCEMENT
| Subscription updates now support period-aware journal handling when billing or service dates are modified. |
When such changes occur, the system evaluates the financial period of the existing Journal Entry:
- Closed period: the original Journal Entry is reversed and a new entry is created for the updated subscription
- Open period: the existing Journal Entry is updated (deleted and recreated)
This ensures accurate accounting, prevents duplicate Journal Entries, and supports consistent financial adjustments for date-based subscription changes.
Unified Import & Export Framework
ENHANCEMENT
Export and import templates are now standardized across all modules, ensuring a consistent data structure. Billing Runs exports have been updated from a single-sheet format to a structured multi-sheet format (Invoices, Line Items, Contacts, etc.), aligning with Invoice exports.
What’s Changed
- Key data is organized across sheets (Invoices, Line Items, Contacts)
- Standardized column structure across modules
- Common fields like Invoice ID, Customer, Date, Due Date, and Description are consistently mapped
Impact
Reduces manual effort, enables reuse of export files for import, and improves data consistency and usability across modules.
Platform
Introduced new capabilities and enhancements across customer management, logging, analytics, and auditability to improve operational efficiency, control, and transparency.
Audit Events for Commerce Modules
ENHANCEMENT
| Audit Events now support field-level change tracking across key Commerce modules. |
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, Finance and Product modules, this enhancement now extends coverage to Commerce related models.
This update strengthens audit transparency, improves compliance readiness, and enables more granular operational oversight.
For more details, refer to Audit Logs
Approval Process for Credits
ENHANCEMENT
| An Approval Process for Credits has now been introduced, enabling controlled and auditable approval workflows for credit transactions. |
System-generated log messages have also been enhanced to deliver clearer and more meaningful descriptions of each approval step.
For more details, refer to Approval Histories
Standardized API Error Response Format
ENHANCEMENT
| Introduced a standardized error response structure across all API endpoints to ensure consistency and improve developer experience. |
What’s Changed
- Unified error response format across APIs.
- All errors now follow a consistent structure with status, source, and details.
- Error messages are standardized within a structured details object.
- API responses now align with documented formats.
Impact
- Simplifies error handling for API clients.
- Eliminates the need for endpoint-specific parsing logic.
- Improves reliability and consistency across integrations.
- Ensures documentation accurately reflects API behavior.
Improved Webhook Logging & Traceability
ENHANCEMENT
| Enhanced the Custom Webhook framework to provide more efficient and structured logging for better observability. |
What’s Changed
- Introduced structured, info-level logging with key identifiers (Company ID, User ID, Integration Log UUID, Object details, Event Type).
- Removed large payload logging to reduce noise and improve performance.
- Standardized log format with timestamp and transaction identifier.
- Updated S3 file naming to integration_log_id + retry_count for retry tracking.
Impact
- Improved traceability and debugging efficiency.
- Reduced log volume and storage overhead.
- Better visibility into webhook retries and execution.
- Enhanced overall observability of webhook processing.
Commerce & Payments
Introduced enhancements across payments, gateway configuration, security, and cash application to improve efficiency, accuracy, and user experience.
Enhanced Payments Gateway UI
ENHANCEMENT
| The Enhanced Payments Gateway UI is now the default experience for payment gateway configuration, offering a more structured and intuitive interface. |
What’s Changed
The Enhanced UI is now enabled by default for:
- Ordway Payments
- Adyen Gateway
- Stripe Gateway
All new companies will be onboarded with the Enhanced UI enabled by default
Impact
- Provides a consistent and improved configuration experience
- Simplifies onboarding with no manual setup required
- Aligns gateway configuration across supported payment providers
HMAC Authentication for Adyen Webhooks
ENHANCEMENT
| Introduced HMAC-based authentication for webhooks from Adyen to enhance security and ensure message integrity |
As part of this update, webhook processing for Ordway Payments has been unified, covering events such as Payments, Refunds, and Reports.
Key Changes
- Support for HMAC validation of incoming webhooks
- Continued support for No Auth (for backward compatibility)
- Improved security for Adyen Gateway
For more details, refer to Adyen Payments – Ordway Support Portal
Ordway Payments
NEW FEATURE
| Ordway Payments is a fully integrated payment processing solution that enables businesses to manage the complete payment lifecycle—from customer payments to payouts, refunds, disputes, and reconciliation—within a single platform |
Key Features
- Unified Customer Dashboard: View balances, payments, payouts, refunds, and disputes in one place
- Payments Management: Access detailed views of all customer payments
- Refunds Management: Track and manage refunds with full visibility
- Payouts Management: Monitor payouts and settlement details
- Disputes Management: Review and manage disputes efficiently
-
Cash Application
- Automatically match incoming payments (ACH, wires, checks) to invoices
- Improve accounts receivable accuracy and efficiency
For more details, refer to Ordway Payments – Ordway Support Portal
Default Billing Address Selection for Adyen Gateway
ENHANCEMENT
When adding a payment method using the Adyen Gateway, the Billing Address option now defaults to Default from Billing Contact. |
What’s Changed
-
The default selection for Billing Address is updated from:
- Enter Manually
- Default from Billing Contact or Shipping Contact
Impact
- Helps reduce interchange fees by ensuring accurate billing address usages.
- Reduces payment rejections due to missing or incorrect address details.
- Minimizes payment disputes by improving data consistency
API Updates
Enhancements focused on improving performance, scalability, and cross-environment portability—enabling more efficient revenue data access and seamless migration of report configurations.
Company Settings API (GET / PUT)
NEW FEATURE
| You can now retrieve and update Company Settings via API, enabling centralized and programmatic configuration management. |
Get Settings
GET/ api/v1/settings
- Retrieve all or specific company settings
- Supports query parameters:
GET / api/v1/Settings?auto_pay,auto_renew
Get Finance Settings
GET/ api/v1/settings/finance
- Returns Finance and Default GL Account settings
Update Settings
PUT/api /v1/settings
- Update one or more company settings in a single request
For more details, refer to Company and Finance Settings (API) – Ordway Support Portal
Aggregation Query Support in GET API
NEW FEATURE
| Enhances GET APIs to support aggregation, grouping, and filtering, enabling analytical queries directly via API without post-processing. |
Parameters
- aggregateby → Apply functions (sum, count, avg, min, max)
- groupby → Group results by fields
- filterby → Filter records (returns normal list if used alone)
Benefit: Enables direct API-level analytics with better performance and flexibility.
For more details, refer to Aggregation and Advanced Querying – Ordway Support Portal
Comments
0 comments
Please sign in to leave a comment.