Subpoena Responses: RevTrack AI only

• No outside service. Bank statements in Subpoena Responses are now read by RevTrack AI ©, which runs on the PC or on a server inside the agency's network. Nothing from a statement is sent outside it, and no API key is used.
• The screen works on PostgreSQL. Subpoena Responses opens, records who imported each statement, and keeps responding while a statement is read; Cancel stops at once.

Supported environment for this release: unchanged from 2026.1.1.

Software Updates: the Python release you can install

• Python runtime currency. The Python runtime is now judged against the newest release that has a Windows installer. A newer source-only security release is named in the compliance evidence with what it means, instead of reading as an update that cannot be applied.
• Stage window. Building with a release that has no Windows installer now explains why and what to use instead.

Supported environment for this release: unchanged from 2026.1.1.

Email Templates: a History tab

• Every change logged. The Email Template editor now has a History tab, as Document Templates do: who changed which setting, when, and from what to what. New, Copy and Delete are listed too.

Supported environment for this release: unchanged from 2026.1.1.

Payment Schedule: both parts of a Square payment

• Partial paid to agency, check to client pending. When a Square payment credits the agency costs and queues a check to the client for the rest, the installment row now says so, with the check's amount, state and date.

Supported environment for this release: unchanged from 2026.1.1.

AutoPay through Square: the right installment

• Fixed: a paid installment could be charged again. When Run AutoPay Now sent a payment through Square, it could pick a plan row the schedule already showed as paid. It now reads the same schedule the Payment Schedule grid shows and charges the next unpaid installment.

Supported environment for this release: unchanged from 2026.1.1.

Sign-in log and Email Templates

• One Enter, one sign-in. Pressing Enter on the sign-in screen no longer records a second, empty attempt, and no longer uses two lockout attempts at once.
• No typed text kept for unknown names. When the name entered at sign-in is not a user, the failed attempt is recorded without it, so a password typed in the wrong box is never stored.
• Email Templates. A template list and editor in the same style as Document Templates, with search, a client filter, a summary of each template and a new Copy.

Supported environment for this release: unchanged from 2026.1.1.

One-time payments

• One-time plans. A one-time payment plan now charges the amount entered when it was set up, not the whole balance. Plans set up earlier correct themselves the next time they are opened.
• 1 Time Payment. A new button under Compose Email takes a single payment on the accounts picked, for the amounts entered, with the same checks and payment routes as Run AutoPay Now. No payment plan is needed, and nothing is paid on an account that was not picked.

Supported environment for this release: unchanged from 2026.1.1.

Email template delete requests

• Supervisors ask. A Supervisor's Delete files a request with a reason; the template stays in use until an administrator decides. Administrators see the requests at sign-in and review each one with the template in front of them.
• Pick clients. Client Code and Exclude Clients use the same client list as Document Templates.
• Payment plans. Recon Bills Corrections holds any account on an open payment plan.

Supported environment for this release: unchanged from 2026.1.1.

Email Templates

• Client codes from a list. Choose... beside Client Code and Exclude Clients ticks codes from the full list; a template can be scoped to several client codes.
• Delete for administrators. Refused while something still uses the template; the deleted template is archived and the delete logged.

Supported environment for this release: unchanged from 2026.1.1.

Email templates: agency flags only

• On send, add flags. The two flag lists offer the agency's flags only, not the client's.

Supported environment for this release: unchanged from 2026.1.1.

Templates write fields on generating

• Fields to write. A document template can put values into fields when it generates -- a Custom Account Data key, a custom tab field or a debtor column -- with merge tokens such as {{TODAY}} in the value. Set under After generating in the template editor.

Supported environment for this release: unchanged from 2026.1.1.

Letters read the Resp Prty tab

• Fix. Values on a debtor custom tab (Resp Prty and the like) now reach the letter merge for the debtor the letter is addressed to; a required RP1_* token no longer stops a letter whose tab is filled in.

Supported environment for this release: unchanged from 2026.1.1.

Document Templates: Delete

• Delete a used template. A template that has produced letters can now be deleted: its document goes and it leaves every list; a name-only record stays so the letter history still reads. Templates a series or Auto Pilot still uses are refused, with Retire offered.

Supported environment for this release: unchanged from 2026.1.1.

Document Templates: deleting a used template

• Fix. A template that has produced letters cannot be deleted (the letter history points at it); the screen now says so and offers Retire, instead of appearing to do nothing.

Supported environment for this release: unchanged from 2026.1.1.

"Also saves to" picker readable

• Fix. The field picker now has its own light styling inside the builder.

Supported environment for this release: unchanged from 2026.1.1.

"Also saves to" picker

• Fix. Clicking a form line's "Also saves to" cell now opens the field picker.

Supported environment for this release: unchanged from 2026.1.1.

Auto Pilots: one at a time

• Open / New Auto Pilot. From the library, the builder opens on that one Auto Pilot with no side list; the library is the list. The full builder remains under "Full builder...".

Supported environment for this release: unchanged from 2026.1.1.

Returned mail marks the right address

• The address on the letter. A returned-mail scan now marks bad the address the letter was actually sent to -- the co-debtor's when the generator addressed it there -- not the account's primary by default. New letters carry the addressed debtor in their QR code; letters already in the mail are resolved by the generator's own addressing rules.

Supported environment for this release: unchanged from 2026.1.1.

Auto Pilots library; form prompts reach custom tabs

• Auto Pilots library. Admin > Auto Pilots opens a library in the Document Templates style: search, filters, a table of every Auto Pilot with a plain-words summary, and Open, Copy, Disable and Delete from the list.
• Custom tab fields. Prompt for Form Fields can save an answer to any custom tab field.
• Several fields per prompt. An "Also saves to" column puts one answer into more than one field.

Supported environment for this release: unchanged from 2026.1.1.

Working a held lane

• Route for: a held lane. The route selector lists each lane held off the route; pick one to work exactly its stops and its accounts with no stop, then move debtors on to their working lane.

Supported environment for this release: unchanged from 2026.1.1.

Lanes held off the route; mail returns cancel queued letters

• Hold Off Route. A lane can be held off the route for pre-collection work: it keeps its collector (letters carry their name) but its debtors' stops show on no one's route until they are moved to a working lane or the lane is released.
• Returned mail. Scanning or marking a mail return now cancels every letter still queued for that debtor, with a note naming each.

Supported environment for this release: unchanged from 2026.1.1.

Assign Collectors: tick boxes that work

• Assign Collectors. Collectors are ticked and unticked with real tick boxes, and Save keeps exactly the ticked users. When a collector comes off a lane, RevTrack offers to move their open stops on that lane to the lane's new owner so they stay on a route.
• AG Recon Import. The confirmation now says whether recon postings are on or off.

Supported environment for this release: unchanged from 2026.1.1.

GEARs: employer record in the account family

• GEARs. New Yes / No conditions find accounts where no debtor in the account's family has an employer record -- the client's E records, the Employers tab, or both.

Supported environment for this release: unchanged from 2026.1.1.

Recon-difference alert

• Recon alert. Opening an account whose balance (agency costs left out) differs from the client's recon balance by more than $100 shows a one-time notice to check for a pending offset payment -- once per collector, per account, per day.

Supported environment for this release: unchanged from 2026.1.1.

Logs row on the Admin Dashboard; export to Excel or text

• Logs. A LOGS row on the Admin Dashboard opens each log an IRS Safeguards review asks for -- sign-ins and failures, access-control changes, privileged use, record access, emails sent, bank-number reveals, log reviews, backups and software releases -- for any period.
• Export. Any or all of the logs for a period to an Excel workbook (a summary sheet and a sheet per log) or to text files (tab-delimited or CSV). Every row in the period is written, and every export is itself recorded with a fingerprint of each file.

Supported environment for this release: unchanged from 2026.1.1.

Recon Bills corrections: exact landing only

• Recon Bills Corrections. Every account that differs from the client's recon balance is checked; a set of recon rows is offered only when reversing it lands the account exactly on the client's figure. Accounts cancelled by the office (bankruptcy, recall) are out of scope; the rest go on a "Needs a look" tab untouched.

Supported environment for this release: unchanged from 2026.1.1.

Documents across every debtor on the account

• Documents. An account shared by two debtors shows all of its documents whichever debtor it is opened under; a co-debtor's file is shown in italics and says so on hover. The tab count and the email composer's attachments follow the same rule.
• Backfill Last Recon Date now also replays the per-account recon balance by bucket from the recon folder.

Supported environment for this release: unchanged from 2026.1.1.

Recon Bills corrections

• Importers › Recon Bills Corrections. Finds the negative recon postings that double-counted a reversed or suspended payment, shows each account against the client's last recon balance, and backs out the ticked rows in one batch with a note on the account. A book comparison report groups every account by what explains its difference from the client.

Supported environment for this release: unchanged from 2026.1.1.

Daily Transactions window: minimize and maximize

• Daily Transactions, GEARs, WorkNumber Imports. The windows now carry minimize and maximize buttons on their title bars.

Supported environment for this release: unchanged from 2026.1.1.

AG recon reports instead of posting; recon balance by account; paid-in-full sweep

• AG recon posting is off by default. Interest and fee differences on the recon file are listed on the pending report rather than posted; a switch under Agency Settings › AGO Importers turns posting back on. The last recon date, the client flags, the absence rule and the re-placement run as before.
• Recon balance by account. Click LAST RECON or RECON BALANCE on the collector screen to see the client's last reported balance for each of the debtor's accounts, by bucket, beside ours.
• Paid-in-full sweep (report only). Each recon run lists the debtors whose every account is paid to zero, as a workbook in the Reports folder; no status is changed yet.

Supported environment for this release: unchanged from 2026.1.1.

Route "No stop" view: the slow query fixed

• No stop. The query behind the Route tab's No stop view is rewritten so the database can use its indexes; the same rows come back in well under a second instead of tens of seconds, and status changes on the route are quick again. One new index is created automatically on the first start.

Supported environment for this release: unchanged from 2026.1.1.

Client-flag drop rule checked every time

• Drop rule. A client flag that retires an agency flag is checked against the flags the record carries on every recon, maintenance and placement file, not only when it first arrives.

Supported environment for this release: unchanged from 2026.1.1.

Email templates: flags on send; inserts in emails

• Flags on send. A template can add debtor flags and account flags when it is sent.
• Insert Builder in an email. A built insert reads as an aligned text block instead of showing its table markers.

Supported environment for this release: unchanged from 2026.1.1.

Daily Transactions: families, Review all, OFFSET

• A debtor's accounts together. Rows in each section sit by debtor, striped by debtor, with the count on the first row.
• Cancelled accounts (recall) as a section of its own.
• Review all on the payment-plan and cancelled bands.
• OFFSET payments in bold on the transaction line.

Supported environment for this release: unchanged from 2026.1.1.

Clutch: Assigned Date

• Assigned Date. The Agency Placed Date row is renamed and shows the days since the date beside it: 08-31-2025 (416).

Supported environment for this release: unchanged from 2026.1.1.

Route "No stop": closed-status debtors left out

• No stop. A debtor with any account whose status is marked Removes From Route is left out of the view whole.

Supported environment for this release: unchanged from 2026.1.1.

Route "No stop": payment plans left out

• No stop. Accounts on an active payment plan no longer appear in the route's No stop view.

Supported environment for this release: unchanged from 2026.1.1.

GEARs: Agency Placed Date

• Agency Placed Date. The date from the placement file's name, as a GEARs condition (equals, before, after, blank) and as an output column.

Supported environment for this release: unchanged from 2026.1.1.

Auto Pilot Builder: re-apply a flag

• Re-apply even if present (add if not). A third Action on the Set Debtor Flag / Token and Set Account Flag / Token steps: a flag already there is taken off and put back, a missing one added.

Supported environment for this release: unchanged from 2026.1.1.

Clutch: Agency Placed Date

• Agency Placed Date. A bold Clutch row with the date the account was placed with the agency, taken from the placement file's name.

Supported environment for this release: unchanged from 2026.1.1.

Flag actions: re-apply even if present

• Re-apply even if present (apply if not). A tick on the Add account flag and Add debtor flag actions: a flag already there is taken off and put back, so it is applied today and the client told again; a missing one is added.

Supported environment for this release: unchanged from 2026.1.1.

WorkNumber review: the debtor's lane

• Lane on the review screen. Each candidate debtor and the selected debtor show the lane they currently sit on.

Supported environment for this release: unchanged from 2026.1.1.

Strategies: branch on a debtor's flags

• Has agency / client debtor flag, has agency / client account flag. Every defined debtor flag and account flag is a yes/no field for strategy conditions and flow questions, by side, so a placement flow can send an existing debtor's new account down a branch of its own. Family-scoped flags read the whole family.

Supported environment for this release: unchanged from 2026.1.1.

Sidecar route: the "No stop" view

• No stop. A view on the Route tab listing the accounts on the collector's lanes that have no open route stop and whose status is not closed, so nothing on a lane goes unseen.
• Closed statuses. The "Removes From Route" column under Admin, Case Status Types is the closed mark and is now headed so.

Supported environment for this release: unchanged from 2026.1.1.

Route ASAP with a mini note

• Route ASAP. The strategy actions "Route to lane" and "Route stop (lane owner)" can write the stop with no date, so the account sits at the top of the collector's route.
• Mini note. A short note on the stop, shown in the route viewer beside the date and stop code.

Supported environment for this release: unchanged from 2026.1.1.

Where the placed accounts went

• On screen after a placement loads. Every account loaded, with the strategy path it took, the END it reached and the actions run, with a count per path at the top.
• In the New Placements report. The same columns on the records sheet and a per-path count on the Summary sheet.

Supported environment for this release: unchanged from 2026.1.1.

Strategy Flows

• Strategies drawn as a flow chart. A new Strategy Flows screen draws the main account flow (what every placed account walks) and the side strategies collectors run, as question, action, wait and END boxes. Every branch must reach an END before a flow can be switched on.
• Built on the existing engine. Switching a flow on writes the strategies it draws; nothing changes in how strategies run. The strategies already in place can be drawn as flows in one click.
• Test on an account. The path an account would take lights up, with the reason at each question.

Supported environment for this release: unchanged from 2026.1.1.

WorkNumber review: Employer + fee only

• Add the employer record and the fee, nothing else. A fourth option on the review screen writes the employer record and posts the verification fee without a stop, letters, lane move, flags or the Auto Pilot.

Supported environment for this release: unchanged from 2026.1.1.

Family-wide debtor flags in GEARs

• A flag can apply to the whole family. A debtor flag definition can be marked as applying to every member of the debtor's family; a GEARs "has flag" or "does not have flag" condition on it then reads every family member, so a flag on one scopes them all.

Supported environment for this release: unchanged from 2026.1.1.

WorkNumber review: Copy debtor #

• Copy the debtor number. A button on the review screen copies the selected debtor's number to the clipboard.

Supported environment for this release: unchanged from 2026.1.1.

WorkNumber review: Reject + fee

• Reject a match and still charge the search. The review screen has a third option beside Accept and Reject: reject the employer match and post the POE Verification Fee to the account picked, with nothing else written. The queue row and an agency note record the account and the amount.

Supported environment for this release: unchanged from 2026.1.1.

WorkNumber accept cancels queued letters

• Queued letters are cancelled on accept. Accepting an employer match now takes every letter still waiting to print on any of the debtor's accounts off the queue, before the demand series is assigned, and records which ones in a note on the debtor.

Supported environment for this release: unchanged from 2026.1.1.

PDF form templates

• A court's own form as a template. A document template can now be a fillable PDF, such as a court's form. Each field holds the merge fields that print in that blank, and the generated form keeps the court's exact layout, flattened so it prints exactly as the court issued it.
• Forms inside a Word template. A Word template can bring in a PDF form, as many copies as the court asks for, with a line of its own; a two-sided template starts each copy on a new sheet.
• Edit the form in your PDF reader. The template screen opens the stored form in Edge or Acrobat to type the merge fields into its blanks, and takes a PDF form from disk.
• Attached as a PDF. A template that prints as a PDF is attached to the account as a PDF and opened there; there is no Word file to edit.

Supported environment for this release: unchanged from 2026.1.1.

Initial letter series by client code

• Initial Letter Series on each client code. The series a new account on a client code starts with is named for what it does, and a series that has been turned off is shown and kept rather than lost the next time the client code is saved.
• Strategies. A new action, Start letter series based on client code, starts the client code's own series on the account, so one strategy serves every client code. A debtor already in the series, an account running another series and a suppressed debtor are left as they are, and the collector's Stop stops it.
• Auto Pilot. Start Letter Series can take its series from the account's client code.
• Placement. Honours a strategy's "Don't start a letter series", skips a series that has been turned off, no longer ends a debtor's running series to start another, and on a joint account runs the owner's strategy whichever debtor the file lists first.
• Stopping a strategy. Stop the remaining actions stops the letter series the strategy started, and removes only that series' unprinted letters; other letters on the account stay.

Supported environment for this release: unchanged from 2026.1.1.

Account tab colors

• A color for each account tab. Agency Settings has a new Account Tab Colors section: give any tab on the account screen its own color, such as a green Payment History tab, as a light tint or solid, and see it closed and open before you save.
• The same for everyone. The colors are an agency setting, so every user sees the same tabs; other workstations pick up a change within five minutes.
• Warnings stay on top. The Bankruptcy tab is always red and Client Changes turns amber while a change waits, whatever colors are set.

Supported environment for this release: unchanged from 2026.1.1.

Security: sign-in, sessions and payment records

• Windows sign-in cannot be borrowed. Where an agency uses Windows sign-in, RevTrack now asks Windows itself which account is running the program, instead of trusting settings a user can change before starting it, and where the database is also reached with Windows sign-in it checks that both name the same person.
• Account changes take effect at once. Deactivating, locking, deleting or renaming a user, resetting their password, or removing the role they are working in, now closes that user's open session within 30 seconds, with a message saying why, and the Session & Security Log records it.
• No card or bank numbers in payment error records. When an AutoPay or card payment run fails, the picture kept for review masks the card, bank account and routing numbers (at most the last four digits show), and so does the text recorded on the account. When a number cannot be masked, no picture is kept.

Supported environment for this release: unchanged from 2026.1.1.

Auto Pilots

• See the note before it is saved. A step that asks the collector to review account fields now also shows the note it will add, and the collector can change it before saving. Left as it is, the same note is saved as before.
• Bulk runs skip debtors with no account. When an Auto Pilot runs on a list of debtors, a debtor with no account of their own is now skipped before anything runs and listed in the result, instead of stopping the run with a message to dismiss for each one.

Supported environment for this release: unchanged from 2026.1.1.

Account screen: Payment History

• Adjustments on one line. An adjustment posted to several buckets at once now shows as a single line with its total, marked MULT, with each bucket’s share on the tooltip — the same way payments, charges and reallocations already show.

Supported environment for this release: unchanged from 2026.1.1.

Letters & emails: last payment amount

• The whole payment, across every account. The last payment amount inserts now find the debtor’s last payment date across all of the debtor’s accounts and add up everything paid that day — every part of each payment, on every account. Before, a letter could show just one part of a payment.
• The true last payment date. Dates are read correctly whatever format they were stored in, and reversals and internal bookkeeping entries are no longer counted as payments.

Supported environment for this release: unchanged from 2026.1.1.

Letters & emails: document templates

• Edit in Word tells you where things stand. While a template’s document is open in Word, the Document tab says whether Word has saved it yet. Clicking Save before anything has been saved in Word now stops and says so, instead of keeping the old document. The working copy RevTrack opens in Word has a name of its own, so it no longer clashes with a document of the same name you already have open.
• Required fields with a space in the name. A required field such as Interest Rate is now checked as one field. Before, it was read as two fields that do not exist, and every letter from that template stopped even when the account had the value.

Supported environment for this release: unchanged from 2026.1.1.

Account screen: the document insert for each custom field

• Hover a field’s name. On the Custom Account Data tab, resting the pointer on a field’s name shows the insert to type in a Word template to print it — for example {{DEFENDANT_1}}, the city, state and ZIP parts of an address field, or {{UD:KEY}} for a UD field placed on the tab — and where the field’s value comes from.
• Which templates use it. The same tooltip lists the active document templates that use the field — in the text, as a show-only-if test, as a lookup key or as a required field — and the retired ones separately, or says that no template uses it yet.
• No account data. The tooltip names fields and templates only; it never shows a value from the account.

Supported environment for this release: unchanged from 2026.1.1.

Letters & emails: vendor letters (ready, not turned on)

• Vendor letter settings. A new Admin tile, Vendor Letters, describes the file a letter vendor receives: the vendor and the agency’s vendor number, the next file number (it goes up by one for every file), the file name, the header line and the positions every letter’s line carries — each position fixed text, blank, a merge field or one of the file’s own values — and rules for Template Codes. A preview shows the exact text of a file for a template and some accounts, on screen only.
• Template Code and a Vendor tab on every document template. A template can be marked as a vendor letter and given its Template Code and the fields that follow the standard positions. The tab shows the whole line’s layout, copies it (field names only) for the vendor, and shows the line one account would produce.
• Nothing is sent yet. Sending to a vendor is not turned on in this release: every letter, marked or not, queues and prints in the office exactly as before, and no file is written.

Supported environment for this release: unchanged from 2026.1.1.

Letters & emails: Insert Builder

• UD fields by page. In the Insert Builder's field picker, choose the UD page, then the field on it. Each account's value is read from that page's current record, so a field that appears on two pages prints the one you chose.
• Merge Field Dictionary. A UD field's description now names the page it comes from.

Supported environment for this release: unchanged from 2026.1.1.

Letters & emails: Insert Builder

• A rebuilt Insert Builder. Each column's field is picked from every field on the system — the account-list fields and every merge field a template can use, searchable — and a Pulls from column says where each value comes from. A merge field is read for each account as it would print in a letter for that account.
• Fixed text. A column can print the same words on every row, e.g. a creditor name.
• Text size and shrink to fit. A table can take the letter's own text size or a set size, and long values can shrink to stay on one line in their column.
• Test and see it in Word. Type an account number to preview the insert with that debtor's accounts, or open it in Word — alone, or inside a template where it is used — before saving. Nothing is sent or recorded.
• Duplicate, find, and where it is used. Start a variant from an existing insert; the screen names the templates that use each insert and asks before closing with unsaved changes.
• Merge Field Dictionary. 44 fields that were listed under “Other” with no description (the bucket balances, the date offsets, the second-debtor and last-activity fields) now have both.

Supported environment for this release: unchanged from 2026.1.1.

Compliance (IRS Safeguards SCSEM)

• An audit summary after “Run all system checks”. The results window now opens on a plain-language summary: for every check, one line on what RevTrack looked at and one on what it found, grouped as Failed, Needs attention and Passed. It can be copied or saved on its own for the assessor. The full output of each check (facts and evidence) is unchanged, one tab over and on the control.
• Warn is recorded. A check that needs attention now writes Warn to the control’s Status, as a pass writes Pass and a failure Fail. A status set by hand is still never overwritten.
• Last check column. The SCSEM Audit screen shows the result of each control’s own check the last time it ran, beside the Status, so a finding set by hand and the check’s latest result can be seen together.

Supported environment for this release: unchanged from 2026.1.1.

Daily Transactions

• The day is the day it posted to your system. The screen now keys on the same Posted Date the Payment History shows, not the client’s own date, so an entry the client dated earlier is listed on the day you took it in.
• NSF filter. Activity → NSF / NSFFee shows the accounts with an NSF entry or an NSFFee charge, and those accounts sit under Reversals / NSF.
• Two more things left out by default. The daily AGFee / Int accrual charges, and pairs of entries that cancel each other on the same day. Each has a button to bring them back.

Supported environment for this release: unchanged from 2026.1.1.

ZIP Subs

• The debtor’s copy. The Zip Subs step also queues one letter to the debtor: a cover letter of your choosing with a copy of each subpoena behind it in the same file, every copy on its own page with the taxpayer identification numbers masked. The cover can list the banks and their count.

Supported environment for this release: unchanged from 2026.1.1.

Daily Transactions

• NSF charges filter. The Activity dropdown can show only the accounts with a charge to the NSF bucket, for whoever works the NSFs across all accounts.

Supported environment for this release: unchanged from 2026.1.1.

ZIP Subs

• A subpoena to each bank in the debtor’s zip, from one button. The new Zip Subs Auto Pilot reads the debtor’s zip code, finds the banks the banks-by-zip library lists for it, looks each bank’s address up in the bank library, and queues one subpoena per bank with the bank filled in. A bank already queued is not queued twice; a bank the library does not know is reported. The step is also available in the Auto Pilot builder.
• A queued letter can carry fields of its own. Values that belong to one letter rather than the account (here, the bank) ride on the queue row and merge when the letter prints.

Supported environment for this release: unchanged from 2026.1.1.

Daily Transactions

• One table, header always in view. The sections are bands in a single table whose column header stays at the top as you scroll. Thousands of accounts appear at once, and ticking one no longer rebuilds the list.
• The day, and only the day. The screen shows what posted on the day selected. The unreviewed accounts of the previous 30 days are a button in the band, + earlier unreviewed, off until pressed.
• Find an account. Type any part of an account or debtor number in the band to narrow the list.
• Receiver offsets left out. Receiver cash and receiver creditor cash entries that cancel each other on an account are hidden, like Reconbill and Replacements, with a button to show them.

Supported environment for this release: unchanged from 2026.1.1.

Daily Transactions

• No more “Not Responding”. The screen reads the ledger through a new index instead of scanning all of it, fetches only the entries it shows, and does the reading on a background thread: the window opens at once, says loading, and stays responsive while the day arrives. Changing the day, Refresh, Reconbill and Replacements all work the same way. What is shown for each account is unchanged.
• A ledger entry whose posted date is not a real date no longer breaks the screen.

Supported environment for this release: unchanged from 2026.1.1.

Debtor screen

• An N typed in the Gear Shift’s day box opens the note again. After a note is committed the cursor lands in Next stop in; typing N or n there now goes straight back to the note editor instead of being swallowed, so another note can be entered before the next stop is set. Same for Sub stop in. The days in the box are kept.

Supported environment for this release: unchanged from 2026.1.1.

Flags

• A client flag that comes back can retire one of yours. Each client flag definition (debtor level and account level) has a new setting, When it comes back, drop. When that client flag arrives on a reconciliation, maintenance or placement file and the debtor or account carries the agency flag named there, the agency flag is removed, with a Flag History row and a note saying why — for example, the client’s echo of a KEEP coming back retires the KEEP that asked for it. Only the arrival triggers it; a file that still carries the flag the next day changes nothing.

Supported environment for this release: unchanged from 2026.1.1.

Flags

• Send a flag to the client again from the debtor screen. Right-click a flag pill and choose Send … to the client again: the debtor goes on the next maintenance file with that flag’s client tag, and a note on the account records it. For when the client’s copy did not take the first time.

Supported environment for this release: unchanged from 2026.1.1.

Client flags

• The maintenance file adds; the reconciliation file syncs. A client flag on the daily maintenance file’s debtor record is added (with a note); the reconciliation file, which carries every current flag, is what also removes the ones the client has dropped.

Supported environment for this release: unchanged from 2026.1.1.

Maintenance import

• The maintenance file’s client flags are read. The debtor record’s flag list in the daily maintenance file now reaches the debtor’s client flags, where before it was read into a field nothing used.

Supported environment for this release: unchanged from 2026.1.1.

Reconciliation and maintenance imports

• Client flags are synced from each reconciliation file. For every debtor on the file, the client’s flag list becomes the debtor’s client flags: flags the file carries are added, flags it no longer carries are removed, and each changed debtor gets a note saying which. Debtors not on the file are left alone. (2026.1.27 only added.)
• A note on every imported payment. When the maintenance file posts a payment, the account gets a one-line note — “PYMT applied by FT to account … $amount” — dated the day of the import, shown in italics on a light green.

Supported environment for this release: unchanged from 2026.1.1.

Reconciliation

• The client’s flags reach the debtor again. The daily reconciliation import now merges the flags the client sends on each account (position 17 of the file) into the debtor’s client flags, with a Flag History row per code. A one-off action merges them from a file already processed.
• Placement Import Options opens with “Skip accounts already in the system” unticked; the pre-placement notes loader opens with “Stage unmatched rows” ticked.

Supported environment for this release: unchanged from 2026.1.1.

Administration

• Post a Balance Adjustment. An administrator can correct an account’s balance by posting a charge or a credit to any bucket, up or down, with a reason. The screen previews the result with the program’s own balance engine before anything is written, posts one transaction (never an edit), recomputes the account, notes it on the debtor, and can reverse an adjustment later by posting its opposite. A credit does not touch a payment plan unless asked to.
• Load History is back. The account tab listing every imported file that touched the account.

Supported environment for this release: unchanged from 2026.1.1.

Payment History

• Payment reversals, NSFs and credits collapse to one line per posting, like payments do, with the per-bucket split on the tooltip.
• Reallocations (REAPP) group across tendered dates. One posting is one line however many original payments it touched; the tendered date is left blank when they differ.
• The monthly interest-and-fee charges are hidden by default. A charge made only of AGFee, Int and FwdFee stays out of the way of the real payments; a new checkbox, Show AGFee, Int and FwdFee charges, brings them back. They still count in the Net, and the summary says how many are hidden.

Supported environment for this release: unchanged from 2026.1.1.

Payment History

• Suspended payments show as one line per posting. A suspended payment that arrived as one row per bucket now collapses to a single line per cheque, like payments and charges already did: the bucket reads MULT, the amount is the total, and the per-bucket split is on the MULT cell’s tooltip. A posting is the same posted dates, type, memo, cheque number and account.

Supported environment for this release: unchanged from 2026.1.1.

Strategies

• The active-strategy question is asked on any account of the debtor. Opening any of a debtor’s accounts now asks about a strategy running on another one, naming that account: “Account 5 on this debtor has an active strategy … it is still set to … do you want to stop that strategy?” Yes stops it where it lives.

Supported environment for this release: unchanged from 2026.1.1.

Strategies

• A strategy runs as a flow. Every action now has a Day: Day 0 is the moment the strategy fires, Day 45 is forty-five days later. A strategy can start a letter series on placement and move the account to a collector’s route stop weeks later. Each firing is recorded as a run on the account; steps whose day has come are run at the first sign-in of that day, or from the new Run due steps now button.
• A stop rule. A strategy ends after its last action, or after a set number of days. A strategy whose actions are all Day 0 behaves exactly as before.
• The collector is asked. Opening an account that is in an active strategy asks whether to stop its remaining actions, listing what is still to come, including the unprinted letters of the series it started. Yes skips the rest, stops that series on that account and writes a note; No is remembered for the rest of the sign-in.
• Letter series by client code. The Assign letter series action has a table of client code → series, so one strategy can carry the whole office’s series choices. A client with no row gets the fixed series, or its default series when none is picked.
• Runs. The Strategies screen reads each strategy as its flow, shows run counts, and opens a Runs screen: every run by strategy, status and account, with its steps, their results and who stopped it.
• With two active series on one client code, the default is now always the oldest, rather than whichever the database happened to return.

Supported environment for this release: unchanged from 2026.1.1.

Document Templates

• A letter series can be created while adding a template to one. “Add to a letter series…” now has a New series… button that creates the series and selects it, so a template can become the first step of a brand-new series without visiting Letter Series first. The template’s client code is prefilled.

Supported environment for this release: unchanged from 2026.1.1.

Document Templates

• A new look. The library and the editor now carry the program’s own palette: a navy header band with the template’s name, flat tabs, and the settings grouped into white cards with short titles. Type shows as a tinted pill in the library, and buttons are coloured by what they do. Nothing moved and nothing was renamed; the fields are where they were.
• A History tab. Every save records who changed which setting, when, from what to what — the document included (size before and after), along with retire, restore, copy and delete. The history of a deleted template is kept.
• The previous Document Templates screen, and the crash fixes it had accumulated, are removed from the program; the new screens have replaced it entirely.

Supported environment for this release: unchanged from 2026.1.1.

Document Templates — rebuilt

• A library and an editor. Admin › Document Templates now opens a table of every template — name, type, clients, users, letter series, document, last change — with search and filters. Nothing on it is editable; selecting a row shows a read-only summary, and a template is opened on purpose, in an editor with Save and Cancel and a check for unsaved changes. The editor has four tabs: Definition, Document, After generating, and Series & usage.
• The stored document is the only copy. A template that had been opened in Word kept a working file on disk, and that file — not the database — was what printed and what Save stored. Printing now reads the stored document only; Edit in Word writes a scratch copy and Save reads it back and stores it. Until Save, letters keep printing from the stored document; after it, every queued letter of that template prints the new one. On first open the program adopts, once, any working file that was newer than its stored document, so nothing goes back to an older copy.
• Every replaced document is kept. The Document tab lists each previous version with who replaced it and when, and can restore one. Copying over an existing template keeps its old document there too.
• Templates can be limited to named users. A restricted template is hidden from everyone else in Generate Document and Queue Letter. Letter series, Auto Pilots and strategies are unaffected.
• Flags on generating, any number. Agency debtor flags and account flags are offered in two lists side by side; tick as many of either as the document should put on. “Next stop after generating” is a tick box plus the days instead of “0 = none”, and “Run strategy” lists strategies by name.
• Retire instead of delete. A retired template leaves every pick list and keeps its history, its series steps and its documents; it can be brought back. Delete refuses while anything still points at a template and says what does.

Supported environment for this release: unchanged from 2026.1.1.

Document Templates

• The field pickers no longer crash the program. The “pick fields” dropdowns in the template editor could bring RevTrack down with an access violation when they were rebuilt — most recently from the Rescan button after editing a document in Word. The dropdown has been rebuilt on a different footing that creates and destroys nothing on a rebuild. It looks and behaves as before.
• The note under “Stop letter if blank” now says what happens. When the stop list names a field the document no longer contains, the note said such a stop never fires. It does fire: the letter stops whenever the account has no value for that field, whether or not the document prints it. The note now says so, so an entry that is no longer wanted can be removed.

Supported environment for this release: unchanged from 2026.1.1.

Client reporting

• A flag the client is told about re-announces itself whenever it is applied; the per-flag switch and the importer settings from 2026.1.16 are withdrawn. Applying any flag that has a client tag — by hand, by an importer, by a strategy or an Auto Pilot, whether the debtor already had it or not — now puts that debtor on the next maintenance file with the tag, once per day. Nothing has to be set up. The “tell the client again” tick and the WorkNumber importer settings added in 2026.1.16 are removed; the importer applies the same markers it always did.
• Debtors already carrying a flag the client never received can be sent in one step. Admin › Debtor Flags has a Send to client again… button: select the flag, and every debtor carrying it goes on the next maintenance file with its tag, whether or not anything about them has changed. It says how many before it does anything, and pressing it twice is harmless.
• A new payment plan tells the client KEEP again. Every payment plan has put the keep flag on the debtor since 2026.1 began, but a plan set up for a debtor who already had the flag told the client nothing. It now re-announces, the same as any other flag.

WorkNumber importer

• Accepting a match updates the debtor’s address from the file. The employee address in a WorkNumber file was kept on the employer record and only replaced the debtor’s own address when that address had been marked bad. It now replaces it on every accept where the file’s address is complete and differs; the old address is kept in the address history and a note records the change. Because the client receives a debtor’s address on the maintenance file, the new address reaches the client on the next run.

Document Templates

• Uploading a new Word document to a template now replaces it. A template that had ever been opened with Edit in Word kept a live working file, and Save read that file back over an uploaded document, so the upload was silently discarded and letters kept printing the old version. The upload is now what is stored and the working file is updated to match. The Save line also now reports what was stored (“document stored, 48,213 bytes”, “document unchanged” or “settings only”), and the file label says whether the working file on disk is the same as the saved document.

Auto Pilot Builder

• The client-code list no longer crowds out the steps. An action scoped to many client codes listed every one of them in the builder, pushing the steps down to a single visible row. The list is now one line with a count; the full list is on its tooltip and under Choose….

Supported environment for this release: unchanged from 2026.1.1.

Client reporting

• A flag can now re-announce itself to the client. A debtor goes on the maintenance file only when something about them changed, so putting a flag on a debtor who already has it told the client nothing — there was no way to make an already-set flag count as an event again. Any flag with a client tag can now be marked tell the client again every time this flag is applied in Admin › Debtor Flags, and applying it — by hand, by an importer or by a strategy — puts that debtor on the next maintenance file whether or not anything changed. It is set per flag, so only the ones the client acts on behave this way, and each re-announcement is recorded in the flag history.

WorkNumber importer

• The markers an accept applies are configurable. Accepting a match stamped a debtor flag, an account flag and a work status, all three built into the program and applied all-or-nothing. They are now three settings under Agency Settings › WorkNumber Importer, each a list, with the previous values as the defaults — so nothing changes until they are edited. An agency can add its own flags to the list, which combined with the change above is how a hit can report itself to the client every time.

Supported environment for this release: unchanged from 2026.1.1.

Letters

• securityA letter could carry the wrong person’s contact details. The collector merged onto a letter — name, direct dial, email, signature — was taken from whichever route stop on the account came up first, and a sub stop (asking a second person to help with one debtor) is a route stop. So a sub stop silently took the letter over from the account’s own collector. An undated stop also lost to a dated one, which made it more likely, not less. The collector on a letter is now the lane owner, always, resolved the same way every other screen resolves it. Licensees should re-queue any letter held for a missing collector field, and review letters sent while a sub stop was open.
• A collector’s profile could be on file and not found. The profile lookup compared usernames letter-for-letter, despite documenting the opposite, so a lane written in capitals never matched the account it named. Fixed; the comparison ignores case as it always claimed to.
• A held letter now says whose profile to open. It used to say to fill the missing fields in on the account, where they are not — these come from one user’s profile. The message names that user and where to edit them, or says the account has no lane owner to take them from.

Imports

• A placement address that is a returned-mail marker now stops the letters. Where a client sends a marker instead of an address because mail has already come back to them, RevTrack stores it and wrote to it. A placement carrying that marker now marks the address bad on import, writes a note, and holds every letter to that debtor until the address is corrected — the behaviour a returned envelope already produced. The marker is configurable and must be the whole address line, so ordinary addresses that merely begin with the same letters are unaffected.

Supported environment for this release: unchanged from 2026.1.1.

Accounts

• Daily Transactions is no longer on an administrator’s menu bar. The screen assembles a posted day plus thirty days of carried unreviewed accounts before it draws anything, and it does that work on the interface’s own thread — so the window sits unresponsive while it runs, which reads as a freeze. Administrators, who open it occasionally, no longer have the entry. Supervisors, collectors and auditors keep it, because the screen is their daily review. The screen itself is unchanged and the wait is unchanged; moving that work into the background is a separate piece of work.

Supported environment for this release: unchanged from 2026.1.1.

Database

• securityA column could be added, lost, and then never added again. RevTrack adds missing columns as it needs them. Two separate layers remembered having added one — and both recorded it before it was certain. A column added inside a screen’s own transaction is undone when that screen closes without committing, so the column vanished while both layers still believed it was there, and no later attempt would re-add it for the rest of the session. The screen that first hit this worked once per session and then failed on every open and every save. Both layers now commit the change and confirm it against the database before recording it, so a change that did not take is retried rather than assumed. This applies everywhere RevTrack adds a column, not only where it was found.

Document templates

• A template that cannot be saved now says so. Saves were failing against the missing column and the error went nowhere, so the screen looked as though it had saved. It now states plainly that nothing was changed and names the reason. Licensees should re-check any template edited recently — an edit that reported nothing may not have been stored.

Supported environment for this release: unchanged from 2026.1.1.

Document templates

• The “Stop letter if blank” list kept only what its dropdown could show. That dropdown lists the fields the document itself contains, and picking from it replaced the whole setting — so any entry it could not represent was dropped the moment a box was ticked. Editing a field out of the document, or using a lookup tag, was enough. The entries the dropdown cannot show are now carried through untouched and named beneath the field, and the editor and the letter generator read the setting by the same rule, which they had not since the generator's rule was corrected. Licensees who have edited a template since should check the stop list on it.
• A failure to open Document Templates now says so. The screen had no error handling, so anything that went wrong opening it produced no message at all — the click simply did nothing. Failures are now reported with the reason and written to the log, and the window is released when it closes instead of being kept for the life of the session.
• “New Template” starts empty. It cleared the name, client code, description and type but left the stop list, recipient-address pattern, batch report fields and conditional tokens from whichever template was open — and saved them onto the new one.

Imports

• A folder of your own for not-loaded and unmatched files. These files hold the original source lines of the rows that did not load, so they hold the same protected data the import did, and they were going to places fixed in the program — one to a set folder, the other beside the file it came from. Agency Settings now has a single setting for both, alongside the import and archive folders rather than with the reports. Leaving it blank keeps exactly what each did before.

Supported environment for this release: unchanged from 2026.1.1.

Imports

• securityThe two import run reports were being written to the folder the client files arrive in. The New Placements and Maint Transactions workbooks named a fixed folder that had been renamed, and fell back to the folder the imported files came from — the agency’s inbound data folder — silently, with nothing in the log an operator would have reason to read. Both now go to the configured Report Directory, which is created and checked for write access first, and still fall back rather than being lost if it cannot be used. Licensees should check that folder and move or delete any reports already written there.

Accounts

• The Gear Shift shows a case-event change at once. Adding, editing, completing or dismissing a case event updated the Case Events tab and its count but not the upcoming-events list in the Gear Shift, which stayed as it was until the account was reloaded. Both now update together, through a single hook that any future way of changing an event inherits.

Accounts and roles

• A username ending in “Dev” is reserved. That ending marks a vendor maintenance account. Only a vendor account may create or rename to such a name, and the account must carry the Developer role, so the ending stays a reliable sign of what the account is. The New User screen says so while the name is typed. Enforced where usernames are set rather than in the screen, so every route is covered.
• Vendor accounts no longer appear in staff lists. The signed-in strip, the sub-stop user, the share-a-report list and the payment-plan approver list all showed the vendor’s maintenance account alongside the office. All four now read one definition that leaves it out. Administration is unchanged: users, roles, the access log and the account review still show every account, so one with full rights stays visible to the people responsible for it.

Supported environment for this release: unchanged from 2026.1.1.

Imports

• The file name each importer accepts is now a setting. Client files arrive named after the identifier that client uses for the agency, and RevTrack decided what to read from that name — with the first licensee’s identifier built into the program. A second agency’s files would have been passed over, and a passed-over file is reported as nothing to import rather than as an error. The identifier is now a single field, Client Reference Name, under Agency Settings › Agency Identity, and each importer’s accepted prefix is written against it. A file whose name carries a different identifier is refused, which is what a Safeguards review asks the program to insist on.
• A new Developer-only section sets the prefixes. Agency Settings › AGO Importers gives one line per importer — placement, placement notes, maintenance, maintenance notes, recall and reconciliation — each showing the name it resolves to as it is typed, with a test that takes a file name and says which importer would read it or that none would. These follow the client’s file format rather than agency policy, so they are not offered to administrators: a prefix that does not match what the client sends does not raise an error, it skips every file.
• A skipped file now says which name was expected. The import log and the skipped-file report name the prefix the importer wanted instead of reporting only that the name did not match. File names carry no taxpayer data, so the expected and actual names can both be shown.

Supported environment for this release: unchanged from 2026.1.1.

Security

• securityThe inactivity sign-out could be held open for the rest of a session. RevTrack holds the inactivity sign-out while an import or a nightly-strategy sweep is running, so that long work is not discarded part-finished. One sweep raised that hold and then released it under the wrong name, inside a guard that discarded the error silently, so the hold stayed up: from the first sweep of a session onward the sign-out woke, saw work in progress, restarted its clock and did nothing. A workstation left signed in stayed signed in. Three changes close it — the sweep releases the hold it took; any hold expires after sixty minutes, is recorded in the audit log when it does, and cannot outlast the control again; and an independent watchdog checks the time since the last keystroke, click or scroll every thirty seconds and ends the session itself, whatever the main timer is doing. The hold still works as designed: an import running when the limit falls due finishes first.
• The check reads the program for it (APP-35). The inactivity-lock check no longer confirms only the setting and the timer. It reads the program's own text and fails if any hold is released under a name that does not exist, if holds and releases do not balance, or if the expiry or the watchdog is missing — the three faults that would allow this defect back. Its evidence names what limits a hold, for the reviewer. Licensees should re-run “Run all” after this release so the recorded result reads the new program text.

Supported environment for this release: unchanged from 2026.1.1.

Compliance reviews

• The weekly database-log summary is read on the screen (DB-18). The Database Server Log review shows the week's summary in the program — the newest file in the agency's folder, period and items to look at on top — with the notes and Record review beneath it. The summary carries names, counts and addresses and never a data value, so it can be read in place; Open remains for printing.

Supported environment for this release: unchanged from 2026.1.1.

Compliance reviews

• Reviews open at sign-in. The sign-in notice now opens the review itself — "Review now" or a double-click on the row — instead of pointing to a menu, and for the reviewing roles the first review opens on its own. A review the control does not accept (recorded by an administrator, or the weekly database-log review without its summary) no longer silences the notice; the row says why it was not counted. The weekly summary folder is shared by every workstation once anyone has chosen it.
• Web App test cases are not applicable. RevTrack is a desktop program; the Web App sheet's last remaining check (WEBAPP-14) is now treated like the rest of that sheet and left out of "Run all". Input validation in the desktop program remains the vendor's practice under APP-47 and APP-67.

Supported environment for this release: unchanged from 2026.1.1.

Compliance checks (IRS Publication 1075 / SCSEM)

• Separation of duties on the database (DB-22) counts from the signed assignment. A review of the database server's log recorded before the agency's signed separation-of-duties assignment took effect is reported but no longer counted against the control, as the application-side check (APP-10) already does. An administrator's review recorded after that date still fails it.

Supported environment for this release: unchanged from 2026.1.1.

Compliance checks (IRS Publication 1075 / SCSEM)

• Automatic FTI archive (DB-05). A new Agency Settings entry names the agency's FTI archive folder. With it set, RevTrack moves every file under the import folder older than 30 days into the archive — by year, keeping the folder layout — when an administrator signs in, and on demand from DB-05 ("Archive old files now", which shows what would move and asks first). Each move is recorded in the Session & Security Log by file name; the last run is shown on DB-05. The archive must be outside the import folder and restricted; an original that cannot be removed is never left copied.
• Run all system checks has a results window. Counts as tiles, a verdict line, every Fail and Warn with its full output, the passes collapsed, and Copy summary / Save report / Open control. This also corrects a defect in 2026.1.3 that stopped the run before any summary was shown and left APP-55 without its check; a check that cannot produce a result is now one Error row rather than the end of the run.

Supported environment for this release: unchanged from 2026.1.1.

Compliance checks (IRS Publication 1075 / SCSEM)

• FIPS 140 encryption check (APP-51) reaches a verdict. The check no longer ends in "verify with the administrator". It reads the connection's cipher, the workstation's Windows FIPS policy and the administrator's yearly attestation of the encryption modules on the database path (recorded under DB-25), and passes when all three stand; when one is missing it says which. The guide's APP-51 entry says the same.

Supported environment for this release: unchanged from 2026.1.1.

Compliance checks (IRS Publication 1075 / SCSEM)

• Encryption-in-transit checks read correctly with Windows sign-in. With Windows sign-in to the database (2026.1.1), the database withholds a session's encryption record from the application role, and four checks took the missing record for an unencrypted session. The checks now read the record as the signed-in person, or ask the connection library directly, and their evidence says which way the record was read. The sessions themselves were encrypted throughout; this corrects the reading, not the connection.

Supported environment for this release: unchanged from 2026.1.1.

Compliance checks (IRS Publication 1075 / SCSEM)

• Both IRS workbooks filled. SCSEM Audit › Fill IRS workbook now offers the Application SCSEM, the Database SCSEM, or both into one folder. Each remembers its own blank workbook, a blank of the wrong kind is refused by name, and each fill is recorded in the Session & Security Log.

Supported environment for this release: unchanged from 2026.1.1.

The first numbered release. It names the program as deployed on this date and brings together the changes of the last two weeks. From here on, every release gets the next number.

Sign-in and security

• securityWindows sign-in to the database. RevTrack now connects to the database as the person signed in to Windows, under a database login of their own, with nothing typed and nothing stored. The shared database password that every user had to type is retired once every workstation has moved over. The database server’s log then names the person who made each change, not just the program. Set up by the agency’s IT with a script RevTrack supplies; the rollout is in two phases so nobody is locked out on the way.
• Who may apply updates. Staging a new runtime and “Update & Restart” are now available only to RevTrack, LLC’s own sign-in. Administrators still see the versions, re-check, back up and see where each workstation stands.
• The version is visible. The sign-in screen, the use notice and About show the RevTrack version, and every workstation reports the version it runs.

Compliance checks (IRS Publication 1075 / SCSEM)

• Unusual-access notice can be cleared. The sign-in notice that lists an unusual day of record access (DB-27) now records the weekly log review from the notice itself, with a line for each day’s explanation, by the people allowed to record that review. A review recorded later the same day now covers that day.
• Database checks under Windows sign-in. The account, lockout, expiry, privilege and logging checks understand each person’s own database login: they are confirmed by the agency’s Windows group rather than one by one, must hold nothing of their own, and are flagged when they do.
• Idle connections. The session-termination check now warns when the database server has no idle timeout of its own, since connections under other people’s logins cannot be seen from RevTrack.

Reports and imports

• New Placements report corrected. The report written after a placement import showed the same debtor number on every account, the assessment number in the Placed column and no balance. Each account now shows its own debtor number(s), its placement date and its balance. The imported data itself was always correct.

Starting RevTrack

• Faster start. On each workstation RevTrack now writes a “RevTrack” shortcut on the Desktop and in the Start Menu that starts the copy on that computer directly, skipping the minute the old shortcut spent loading across the network. Start RevTrack once from the old shortcut after this release, then use the new one.
• Startup profile. Each launch writes a timing profile the administrator can read, now including the time before RevTrack’s own window appears.

Supported environment for this release: Windows 10 or 11 workstations (64-bit); Windows Server or Linux database host running PostgreSQL 16 or later; Microsoft Word on workstations that generate documents; Microsoft 365 with Graph API access for email. Each component on a release its publisher still supports.