Midnight 11.8.0 (8/22/26) Release Notes Follow

Release Timing 

This release will roll out in two phases: Phase 1 on August 22, 2026, and Phase 2 on September 6, 2026. Sandbox sites will also be updated during Phase 1, even if their associated customer is not part of that phase. All customers — including those in Phase 1 — will receive the Phase 2 update, which includes everything from Phase 1 plus any additional improvements made during the following week.

What to Expect in this Release

As part of our ongoing commitment to improving the reliability of your Midnight system, this release delivered improvements in system performance and several bug fixes. We are also including several enhancements—highlighted below.

Now available to all Customers: File Proofing & Approvals in Midnight! (Beta)

Midnight now includes a Print Reach Drive integrated Proofing Module to help you manage customer file approvals without leaving the system. You will find the option to create a new proof using this feature inside the Order > Proofs tab as seen below. 

You can assign reviewers in stages, send automated notifications, and track approvals, rejections, and revision requests—all within a structured workflow tied directly to your estimates and orders. This keeps your proofing process organized, visible, and easy to follow. Click here to learn more. 

Update: Escrow-to-Earmarked Transfers – Completing the Balance & Transfers Feature

We've added support for Escrow-to-Earmarked transfers in the Balances & Transfers feature in Print Reach Central (PRC) and Midnight, completing the phased rollout of enhanced fund management tools.

With this release, all four transfer types are now supported: Escrow-to-Escrow, Earmarked-to-Escrow, Earmarked-to-Earmarked, and Escrow-to-Earmarked — giving you full flexibility to reallocate funds between escrow and earmarked balances, and between orders, as needed.

This release specifically adds the ability to earmark escrow funds directly against an order. Key details:

• Transfer funds from a customer's escrow balance to an earmarked allocation on one of their open orders
• Destination order must belong to the same customer
• Destination can be any open order — it does not need an existing earmarked balance
• Users select the specific escrow/deposit account to transfer from
• Transfer amount cannot exceed the currently available escrow balance

All transfers remain fully audited, generating a confirmation number and creating linked debit and credit transactions to ensure complete traceability. Balances are automatically updated in both PRC and Midnight.

Here is a link to an article on using this feature.

Additional improvements:

• Earmarked-to-Escrow transfers now show eligible orders with earmarked funds across all deposit accounts, not just the one currently selected in the Balance Transfer grid. Each order lists its associated deposit account for clarity, and deposit account name is now a searchable field when selecting an order.
• A new "Include Inactive" checkbox on the customer selector lets you show inactive customers (labeled accordingly) when you need to manage their escrow or earmarked balances; active customers only are shown by default.

Midnight API Rate Limiting Implemented 

Overview

To maintain platform stability and ensure consistent performance for all Midnight customers, API rate limiting has been implemented for the Midnight API.

Why This Change Was Made

We identified API integrations generating significantly higher-than-expected request volumes. In some cases, this activity created enough load on backend database resources to impact overall system performance.

Because multiple customers may share the same infrastructure, excessive API traffic from a single integration can affect response times and performance for other customers. Rate limiting helps prevent these situations and protects the reliability of the platform.

Current Rate Limit

Midnight currently limits API traffic from a single IP address to approximately:

5,000 requests per 5-minute period

Requests exceeding this threshold will receive:

HTTP 429 - Too Many Requests

Rate limit thresholds may be adjusted in the future as we continue to evaluate usage patterns and platform requirements.

What Happens When a Limit Is Reached?

If an application exceeds the allowed request rate, the API will temporarily reject additional requests and return an HTTP 429 response.

Applications should be designed to recognize and handle this response appropriately.

Recommended Best Practices
Customers integrating with the Midnight API should:

• Handle HTTP 429 responses gracefully.
• Implement retry logic when requests are temporarily rejected.
• Use exponential backoff techniques when retrying requests.
• Avoid repeatedly submitting the same request in rapid succession.
• Filter data whenever possible to reduce the number of records being returned.
• Synchronize incremental changes rather than repeatedly retrieving all available data.

Optimization Opportunities
Customers experiencing rate limiting may be able to significantly reduce API traffic by:

• Filtering orders by date ranges.
• Using modified-date fields to retrieve only changed records.
• Limiting result sets to the data actually required.
• Reviewing integration workflows that repeatedly request the same information.

Need Assistance?

If you are encountering rate limiting or believe your integration has a legitimate need for higher API volume, please contact Print Reach Support with details about:

• The endpoints being called
• Request frequency
• Data being retrieved
• Business process being supported

Our team will review the use case and may be able to recommend changes that reduce API traffic while achieving the same business objectives.

Update: Show/Hide Quantity & Rate on Invoices (Quick Invoice)

Building on the Quick Create Invoice enhancements introduced last release, you can now control whether the Quantity and/or Rate columns appear on generated invoices.

Key details:

• Three display options: Show Quantity + Rate (default), Show Quantity only, or Show Amount only (Quantity and Rate both hidden)
• Quantity cannot be hidden while Rate remains visible — a rate without a quantity isn't a supported combination
• Available everywhere invoices are created: Midnight Accounting, Midnight Order (Quick Invoice), and PRC Invoices
• Included as part of your invoice templates — both the default template and any custom templates you've created — so the setting is consistent wherever that template is used
• Can still be changed on an individual invoice afterward via the items pop-up
• Applies consistently across the invoice setup view, the invoice sent to the customer, and the Stimulsoft printable report
• Hiding columns doesn't affect totals, tax, or other calculations — remaining columns hold their position, no layout reflow

New: Feet (ft.) Support for Roll Materials

Midnight now supports Feet as a fully functional Base Unit of Measure for roll-based inventory items, in addition to Inches.

Previously, Feet could be created as a unit of measure, but roll dimensions, calculator formulas, and inventory quantities still operated in inches behind the scenes. With this release, when a roll item's Base Unit of Measure is set to Feet, the system calculates and displays that item's data natively in feet throughout — no manual conversions required.

Key details:

• New system-defined Feet option added to the Base Unit of Measure, Display Unit of Measure, and PO Unit of Measure dropdowns for roll inventory items
• Applies to roll materials used in Print, Wide Format, and Lamination — including the Print Calculator, Wide Format Calculator, Simple Wide Format Calculator, and Lamination Calculator, along with their related templates and the Orders Inventory tab
• Dynamic unit labels (e.g., "Roll Width (ft.)") display throughout so it's always clear which unit is in use
• Press and machine-specific fields (e.g., Max Roll Width, Cylinder, Gripper, Bleed) remain in inches, since these describe equipment specifications rather than material dimensions

Important:

• If you previously created your own "Feet" unit of measure, it is not changed or removed — it will appear with an "x" prefix (e.g., "xFeet") in drop downs to distinguish it from the new system-defined Feet option
• Existing roll inventory items are not automatically converted; you must update an item's Base Unit of Measure to Feet to take advantage of this feature
• Applies to roll materials only — sheet materials and press configuration are not affected

What's Coming Next: Support for Pounds (LB) as a unit of measure for roll materials is planned for an upcoming release, building on this feet-based foundation.

Update: Show on Invoice Extends to Accounting Export and Estimate/Order APIs

Building on the Show on Invoice controls introduced for Standard Services and Postage Affix last release, this release extends those settings to Accounting Export and the Estimate and Order APIs.

Accounting Export:

• Services and Postage marked as not shown on invoice are now excluded from Accounting Export, consistent with how they're already excluded from invoices and invoice-based reports
• Applies across supported accounting export formats, including QuickBooks, QuickBooks Online, Sage, Great Plains, MYOB, Cougar Mountain, and SysPro, among others
• Totals on the Accounting Export search screen remain accurate whether or not items are hidden from invoice
• Both Generic and Custom exports reflect the setting correctly

Estimate and Order APIs (SOAP & REST):

• A new ShowOnInvoice parameter is now available on Estimate and Order API endpoints — including EstimateInsert, EstimateUpdate, OrderNew, OrderVersionNew, OrderVersionDetailInsert, and related list/detail endpoints — for both requests and responses
• If ShowOnInvoice isn't included in a request, it defaults to true, preserving current behavior for existing integrations
• Validation added: Taxable cannot be set to true when ShowOnInvoice is false

New: Invoice Tracking in CRM History

CRM History now tracks invoice emails, giving you clear visibility into which invoices were sent to a customer and when.

Key details:

• A new Invoice column has been added to the CRM History grid, showing a clickable link to the associated invoice
• A CRM Activity record is created automatically whenever an invoice is emailed — via Save and Send / Save Changes and Send from the Invoice screen, the Email icon in the Invoice Viewer, or the Midnight Invoicing report (Stimulsoft)
• When multiple invoices are emailed together (e.g., a multi-invoice Stimulsoft report), one record is created showing the order and the last invoice record. 
• The Activity detail view includes a new single-select Invoice dropdown, consistent with existing Order and Estimate fields
• Activity descriptions clearly identify what was sent (e.g., "Emailed Invoice – [Invoice Number]" or "Emailed Postage Request – [Invoice Number]")

This gives you a reliable, invoice-level audit trail of customer communications, matching the visibility you already have for Orders and Estimates.

New: Issue Visibility on Orders

You can now see logged issues directly from the order, without leaving to check a separate issue report.

Key details:

• A new "Issues" tab has been added to the order's main tab row (after Packages), with the standard green underline indicator when the order has one or more associated issues
• The tab displays a read-only grid of all issues logged against the order: Issue Number, Version, Entered By, Service, Issue Type, Date, Issue Status, and Close Date
• Issue Number is a clickable link that opens the full issue entry screen, where you can view details (including Issue Description and Resolution) and take action
• When you open an order with one or more issues in Pending status, a popup notifies you: "This order has one or more Issues in Pending Status." (Completed and Resolved issues don't trigger the popup)
• A new "Add New Issue" button on the Issues tab lets you create an issue directly from the order — you're returned to the order with the new issue added when finished

Note: issue costs and credits are still tracked only in the issue log and are not automatically added to the order — that remains a manual step.

New: REST API Users Guide

We've published a new REST API Users Guide for developers building integrations with Midnight, complementing the existing SOAP API guide.

Key details:

• Available at api.vsmidnight.com
• Covers usage of the Midnight REST API endpoints

New: Reports for the Midnight Invoicing Module

We've published new stock reports for customers using the Invoicing Module. The following can be found in the Accounting Reports folder: 

• Invoicing: Aging Report
• Invoicing: All Invoices Report
• Invoicing: Customer Invoice History
• Invoicing: Customer Statement
• Invoicing: Deposit Request (Postage) Status Report
• Invoicing: Export by Date Range Report
• Invoicing: GLID Totals Report
• Invoicing: Invoices (Paid) by Sales Rep Report
• Invoicing: Invoices (Paid) Report
• Invoicing: Invoices (Past Due) Report
• Invoicing: Invoices (Unpaid) Report
• Invoicing: To Be Invoiced Report

Coming Soon: Invoicing: Tax Jurisdiction Report

Bug Fixes and Performance Enhancements: 

• Fixed an issue where the print calculator could show negative or incorrect paper quantities when an item's units of measure didn't match the display units.
• Fixed an issue that could cause the Shop Floor screen to time out.
• Fixed an issue where new customer email notifications showed stray HTML code at the bottom of the message.
• Fixed an issue where the Description field was blank when editing an existing purchase order.
• Fixed an issue where the Order Postage tab showed fewer records per page than configured in Global Settings.
• Corrected sorting and formatting of the Data Due Date field.
• Fixed an issue where quotation marks in item descriptions displayed as HTML code (") on purchase orders.
• Fixed an error that could occur when editing and saving a time card entry.
• Fixed an issue where inventory location balances didn't update correctly for items tracked by lot.
• Fixed an issue where the Order Reserved quantity didn't display for some items, which could prevent inventory from deducting correctly when the order closed.
• Fixed an issue where tax could calculate incorrectly on multiple-quantity estimates.
• Fixed an error that occurred when adding a note to a postage account.
• Fixed an issue that caused an error when saving the close date on an order.
• Fixed an issue where a service could appear twice on reports and the daily job board despite appearing once on the order.