From a read-only look at the FieldRoutes account on 2026-11-02 and its official manuals. Each line ends with its evidence: Observed in the account, Documented in a manual, or not tested. Capture numbers link to the screen below. All of FieldRoutes across the 20 blocks
In FieldRoutes, this block is everything that happens to money after an invoice exists: recording and charging payments, AutoPay, stored cards and bank accounts, credits and prepayments, receivables aging, collections, payment batches, convenience payment plans, failed payments, and processor payouts (disbursements). Most of it sits in the Billing menu (nine pages). The rest is spread over the Customer Card (Billing and Invoices tabs, the Add Payment forms), office preferences, Trigger Rules, Customer Communication settings, mobile defaults, access permissions, and a set of Office reports. The research has 40 screenshots whose main block is payments: all nine Billing pages, including the later loaded states, the five Add Payment method forms, one opened failed card payment, and the payment-related Office reports. Another 57 screenshots from other blocks also matter here. All of it is read-only. No charge, payment, posting, refund, reversal, write-off, collections submission, statement, export, stored-card change or saved report was executed. So this page describes controls and the existing records the account showed. It does not describe tested money flows.
Each capture is a saved screen state from the FieldRoutes account on 2026-11-02. A screen shows what controls exist; it does not prove what happens when they are used.

Add Payment opens a payment entry panel with five payment methods as tabs: Cash, Check, Card, ACH and Coupon/Credit, and asks to select one. Captures 024-028 show each method. No payment was recorded.

The Cash payment form has Payment Amount, Confirm Amount and customer payment notes, with Record Cash / Record Payment. Distribution Details limit where the money goes (customer, subscription, which invoice to apply to first), and Payment Flags mark it as an office, collection or collections-agency payment. Nothing was recorded.

The Check payment form is like Cash but adds a Check Number field, with Record Check. It has the same distribution (customer, subscription, apply-to-first invoice) and payment-flag options. Nothing was recorded.

The Card payment form offers Use Card On File (crossed out, no card stored), Single Use Card (selected) and Existing Transaction. It shows amount, confirm amount, the billing name/address and an embedded payment processor card-entry area, then Charge Single Card, plus the usual distribution and payment flags. The embedded card-entry area is blank in the capture, so usable card entry is unverified; no charge was made.

The ACH payment form offers Use Account On File and Existing Transaction (selected). For an existing transaction it asks for amount, confirm amount, date, transaction ID and notes, with Record Existing, plus distribution and payment flags. Nothing was recorded.

The Coupon/Credit form records a non-cash credit: amount, confirm amount, Coupon Code, Description and notes, with Record Coupon. Besides the usual distribution options and payment flags it adds a Write Off flag. Nothing was recorded.

The Billing area opens on AutoPay Balances: customers on card or bank (ACH) AutoPay who still owe money, so the office can see who should be charged. It lists the Billing submenu (AutoPay Balances, Accounts Receivable, Accounts With Credits, Collections, Payment History, Payment Batches, Convenience Payments, Manage Stored Cards, Disbursements), filters for account status, AutoPay type, card status (successful, soft/hard decline, invalid/missing), property type and minimum balance, and Batch Charge and Update Actions buttons. The table is empty under these filters; nothing was charged.

Adds the advanced AutoPay Balances criteria: balance age bands, paper-statement preference, has-email, maximum-monthly flag, collection stage (not sent/pending/sent) and include/exclude customer flags, plus saved-report controls (name, user/office scope, default, save). Table columns cover subscription, card status, attempts, age, preference, monthly, due and charging amounts. Result is empty; no charge or action was run.

Accounts Receivable is the aging list of who owes money. It shows filters (as-of date, account status, AutoPay type and status, property type, balance range), a populated table of about 30 accounts with AutoPay, max monthly, age, total due and statement/SMS/voice communication status columns, and Total Owed / Current / Over 30 / 60 / 90 day summary cards. The summary cards are seen fully in 537; advanced options are in 512.

Accounts With Credits lists customers holding credit or prepayment balances. This first capture shows the filters but the result area had not loaded. Superseded by 504.

Collections is the review list of overdue accounts for follow-up or sending to a collection agency. This first capture shows the filter header but the result area had not loaded. Superseded by 505 and 506.

Payment History (Payment Reports) lists recorded payment transactions with method tabs, status and origin filters and summary totals. This first capture shows the empty table and the disbursement-column tooltip, but not a settled loaded state. Superseded by 508 (loaded, current day) and 509 (prior month).

Payment Batches is where office staff enter checks and cash in a batch and post them. This first capture shows only the page heading with Payment Batches and Prepayments tabs; the entry form had not loaded. Superseded by 507.

Lists upcoming scheduled advance payments for customers on a convenience payment plan (spreading service cost into regular charges). Shows a future date range, payment-method status filter, included subscriptions, Refresh, Export to Excel and Send Message, with columns for charge date, charge amount, subscriptions and method status. No rows match the shown period; nothing was sent or exported.

Helps the office maintain stored payment cards: filters for expiry (already expired, this month, next three months), unused period, customer status and office, with columns for cardholder, card, token, expiry, last successful transaction, AutoPay card, Bill-To, bank update and date refreshed. The table is empty under the filters; no card was changed.

Shows payouts from the payment processor to the company bank account, for reconciliation. It has a date range, office selector, Refresh and Export to CSV; for the selected two days it says No data to display.

An audit log of who did what in billing and accounts receivable. Filters cover date, office, user type (office staff, sales rep, technician), employee, customer, screen location (billing menu, customer tabs, admin, reporting), object (AutoPay, AR, collections, payment batches, stored cards, invoices, trigger rules and more) and a long list of actions (exported, charged a batch, wrote off a balance, changed AutoPay, refunded a payment, edited trigger rules and many others), plus an option to include IP address (default No). It has saved-report presets (name, User or Office scope, Global disabled, default flag), Export to Excel and a searchable table; the page says it is limited to 25,000 logs. No log rows were inspected and nothing was exported.

Lists customers flagged as having paid a year in full whose prepaid period is running out, so the office can follow up. Columns: customer, subscription, phone number, remaining prepayment and recurring price, with search, Refresh and Export to CSV. The table shows zero entries.

Finds stored credit cards that expire between a start and end month, filtered by customer status (any, active, frozen) and office. Besides Refresh and Export to CSV it has Send Messages to contact these customers (not used). The result area is blank.

Finds customers whose stored payment method failed. Filters: customer ID, card last four digits, balance at or above an amount, and method type (all, credit card, ACH), with Refresh and Export to CSV. The result area is blank.

Meant to list frozen (inactive) customers who still have stored payment accounts. Only Refresh and Export to CSV show; the body is blank with no result message. The later recapture 491 is still blank, so the result remains unknown.

Summarises payments received for a date, grouped by service type by default with up to two sub-groups (choices include billing frequency, city, county, customer source, division, GL account, invoice, month, office, payment date, payment type, region, sales rep, service bundle, technician, year, zip). Filters: coupons include/exclude/only, payment as-of date, service plans, disbursement, service bundles and Advanced Filters (not opened). Columns split collections into applied payments before tax, tax, unapplied, coupons, cash, checks, Visa/Mastercard, Amex, ACH and total collected. It has saved-report presets and Export to Excel; the detail table was still loading when captured.

Shows collections for a date range, with an option to include $0 collected (default No), Refresh and Export to CSV. The result area is blank, so it is not clear from the screen how collections are attributed.

Lists initial (first) services that have not been paid, for a start/end date range, with Refresh and Export to CSV. The result area is blank.

Communication settings editor for 'SalesRoutes and Customer Portal Auto Payment Message', opened unchanged and cancelled. Plain authorization text shown above the automatic-payment initials in SalesRoutes and the portal; a standard text is used if blank. No payment mandate was created. The filename only gives the group number.

Prepayments finds customers to offer paying ahead for a service plan. Filters: Service Plan (required; the list offers no plans), Property Type (All/Residential/Commercial) and Overdue Balances (exclude, include, or exclude 7+ to 180+ days overdue), with Save filter and Search. The customer table (Customer ID, name, subscriptions, Mail, Email) is empty.

One of the 19 data-quality checks in the Audit report, selected on its own: it lists customers with a stored card who are not on AutoPay. The panel shows 0 customers for customers entered on the captured day, so no result table or columns appear. It shares the Audit date range, Refresh and Export to CSV; nothing was corrected or exported.

A second visit to this report. Only the title, Refresh and Export to CSV appear; the body is still blank with no result message, so it is not known whether any customers match.

Lists customers holding money in their favour. Filters: as-of date, account status, AutoPay, payment-method status, property type, credit type (credits, prepayments, both), paper/email preference, max monthly, collection stage and flags. Columns separate the responsible customer from the originating customer and office, plus total credit and statement/SMS/voice columns. Loaded result: zero rows and zero total credit under these filters; no refund or allocation.

The collection accounts list loaded with 30 overdue accounts: balance, age, earliest due date, days overdue, contact and location, account status, collection stage, subscriptions on hold, AutoPay and payment status and last payment. Basic filters are as-of date, account status, balance age, payment due and days overdue. Every one of the 30 row checkboxes is already checked (only the select-all box is not), so an Actions command would likely apply to all listed accounts; the Actions button was not opened.

Adds the advanced collection criteria: AutoPay type and status, property type, paper/email preference, max monthly, include/exclude collection stage (not sent, pending, sent), minimum balance, On Hold and customer flags, over the same 30-row loaded list, where all 30 rows are checked. Stage cells show 'Not Set' while the filter says 'Not Sent'. Nothing was sent to collections.

The batch payment entry screen for office-received payments. It shows batch date range and selector, Close Batch, Import Lockbox Batch, customer and invoice lookup, method (cash/check), amount and confirm amount, notes, allocation limits (customer, subscription, invoice), a Collections Agency Payment checkbox, Add, running totals and Finalize & Post Payments. Below, Recorded Payments lists one existing card payment in the open batch with method totals. Nothing was added or posted.

Payment Reports loaded for the current day with method tabs (all, card, ACH, cash, check, coupon) and filters: transaction date (defined as when the transaction was created in FieldRoutes Payments), office/collection payment flags, payment status (success, failed, disputes, ACH returned), card type, coupon, method, office, reversed payments, disbursement, payment origin (manual, portal, batch, trigger, collections, API, import, convenience payment), agency payments, write-offs and flags. Summary totals (successful, by method, collected, gateway fees, net) and the table show zero rows for the day.

The same report for the previous month shows one failed card payment, while the successful count, collected totals, gateway fees and net collected stay at zero. The Disbursement column header carries a ? help icon; its tooltip text (N/A, blank, Pending and payout values) is in the saved UI text, not visible in the image.

Despite the 'attempt' filename, this is the actual opened detail of an existing failed card payment inside the Customer Card. It shows 'This payment failed', amount, transaction date, API origin, FieldRoutes Payments gateway, a system recording actor, the status detail 'The referenced resource does not exist', blank authorization and transaction references, AVS/CVV Not Available, empty Applied To and disabled allocation controls. Unpaid invoices are listed in the sidebar; nothing was changed.

The Actions menu on the failed payment detail offers Update Payment, Email Receipt and Print. Only the menu was opened; no update, retry, receipt or print happened.

Shows the AR configuration choices: balance age, payment due and days overdue filters, paper/email preference, max monthly, Group By Bill To or Invoice, Determine Aging By account balance or individual invoice balances, Aging Start Date invoice date or due date, Convenience Payments invoices (exclude, include, only), collection stage and flags. The populated 30-row table and aging summary sit below; defaults are Bill To, Account Balance and Invoice Date.

The AR bulk Actions menu offers Send Message, Print Statements, Snail Mail Statements (paid postal mailing) and Email Statements for selected accounts. Only the menu was opened; nothing was sent or printed.

Accounts Receivable after dismissing a notification banner, with the 30-row list and the five aging summary cards (Total Owed, Current, Over 30, Over 60, Over 90 Days). The detail supplement shows all five totals clearly above the bottom dock.

Collections after dismissing a notification banner, with the loaded account list and the five aging summary cards. The detail supplement shows all five totals clearly.
AutoPay collection (configured; not executed). An account is enrolled in Card or ACH AutoPay, at customer level or per subscription (Documented: subscription AutoPay overrides the customer default). AutoPay Balances then lists enrolled accounts with a balance at or above a minimum (0.05 shown). Columns show billing customer, subscription, card status, attempts, age, preference, monthly cap, due, charging and action. Staff can start Batch Charge or Update Actions; neither was opened, so the confirmation flow, number of customers per batch and authorization are unknown. In the captured filter state the table was empty with a 0.00 total. That shows nothing about all enrolled accounts. Official guidance says rules automatically submit designated AutoPay invoices for ACH or card payment, and grouping can reduce repeated manual work (Documented, public blog). An Auto Payment trigger type also exists, with account status, balance age (bucket or custom range), AutoPay type, minimum (required) and maximum balance, property type and flag filters (Observed 234-trigger-auto-payment). The subscription tooltip says that if Next Billing is in the past, charging happens within 24 hours (Observed, not tested). 040-billing, 041-autopay-advanced
Soft declines and retries (configured; not executed). Billing Preferences has Retry Soft Declines, Soft Decline Payment Hold Days (default or 0-10 days) and Soft Decline Threshold (1-20, currently 3, the default). Beyond the threshold a soft decline becomes a hard decline. This rule excludes listed legacy merchant integrations. The report filters show decline states, but retry algorithms and processor codes are not established. 220-office-billing-preferences-editor
Recording a payment on the Customer Card (forms observed; nothing recorded). Customer Card > Invoices > + Add Payment opens five method tabs.
Every form has Distribution Details (limit to customer, limit to subscription, which invoice to apply to first) and Payment Flags (office, collection, collections agency). 023-customer-add-payment, 024-payment-cash, 025-payment-check, 026-payment-card, 027-payment-ach, 028-payment-credit. The invoice detail also has + Add Payment and a Charges / Payments / Balance summary 441-existing-invoice-detail.
Payment Batches (controls observed; nothing posted). Staff choose or open a batch (date range plus batch selector), look up a customer or search by invoice, and pick a method. The entry form offers only Cash and Check. They enter Amount and Confirm Amount, notes, allocation limits (Any Customers / Any Subscriptions / Any Invoices) and an optional Collections Agency Payment checkbox, then click Add. Running totals (Cash, Check, Total) show staged entries. Finalize & Post Payments posts them, and Close Batch ends the batch. Import Lockbox Batch is a separate import entry. Below the form, Recorded Payments shows history: one existing card payment in a batch still marked Open, with method totals (Cash, Checks, CC, ACH, Coupons, Total). So history can hold methods the entry form does not offer. The date filter (10/02-11/02/2026) did not match the record's dates, which were earlier: the current batch and the record's Date Open are 7/6/26, and its Date Paid is 7/23/26 (CC(1), $0.30). So the filter's date basis is unknown. A green dot on the record is unlabeled. Transaction atomicity, validation and reconciliation are untested. 507-payment-batches-revisited
A failed payment (existing record, opened). Payment History for the current day loaded zero rows. Setting the range to the previous month showed one failed card payment. The Successful count, collected totals, gateway fees and net collected all stayed at zero, and the row's fee and net cells were blank. Opening the row opens the Card Payment detail inside the Customer Card, which checks out the card. The detail says "This payment failed". It shows the amount and date (10/5/2026 1:41 PM), Payment Origin API, Gateway FieldRoutes Payments, a system recording actor and Status Detail "The referenced resource does not exist". That is the displayed text, not a diagnosed cause. Transaction ID and Authorization Code were blank, AVS and CVV were "Not Available", Applied To was empty, and the flags and distribution selectors were disabled. Actions offers Update Payment, Email Receipt and Print; only the menu was opened. Two unpaid recurring-billing invoices showed in the sidebar, and the failed payment was not applied to them. The card was then closed and the checkout release verified. 509-payment-history-prior-month, 510-payment-history-detail-attempt, 511-failed-payment-actions
Receivables review and statements (observed; nothing sent). Accounts Receivable loaded about 30 rows with payer identity, AutoPay, max monthly, age, total due and communication columns (Send SMS, Send Voice, Email Statement, Print Statement). Some cells already read Undeliverable, Sending or Printing. The research did not trigger these, and they do not prove delivery or printing. Summary cards show Total Owed, Current, Over 30, Over 60 and Over 90 Days: $6,442.00 owed, split $1,749.00 current, $1,250.00 over 30, $2,485.00 over 60 and $958.00 over 90 days. The four buckets add up to the total. Collections showed the same five figures over its 30 rows. That is a display check only. The Actions menu offers Send Message, Print Statements, Snail Mail Statements and Email Statements. The menu label itself says nothing about cost; the only price seen is the Account Statement Tear Sheet tooltip: snail-mail statements with a tear sheet include a return envelope and "an additional charge $0.20 per statement". None was clicked, so selection scope, preference enforcement, queueing and cost are untested. 042-accounts-receivable, 537-receivables-totals-clear, 513-receivables-actions. Billing Letter Templates insert conditional text into statements based on minimum and maximum days past due and invalid payment method (No / Yes / Any). Each template holds up to 2000 characters, with placeholders for billing name, last service date, balance age and days overdue (Observed; priority between overlapping templates untested) 204-billing-letter-templates, 205-billing-letter-template-editor.
Collections (observed; no agency step). Collections loaded about 30 rows with balance, age, earliest due date, days overdue, contact and location, account status, collection stage, subscriptions on hold, AutoPay and payment status, and last payment. Rows have selection checkboxes. In all three loaded views every one of the 30 row checkboxes was already checked (only the select-all box in the header was not), so an Actions command would likely apply to every listed account; that is a reading of the screen, not tested. The research did not set these checks, and they are not a result. The Actions button was not opened. The row states were uniform: all 30 rows had stage Not Set, 0 subscriptions on hold, AutoPay None, payment status Invalid/Missing and a blank Last Payment; 29 accounts were Active and one Frozen. Being on the list, or a row's age, does not mean the debt was sent to a collector, held, frozen or contacted. Stage can be set by hand on the Billing tab or by a trigger action (Set Collections Stage: Not Sent / Pending / Sent). Payments can carry Collection Payment and Collections Agency Payment flags, and Payment History can filter Collections Agency Payments. 505-collections-revisited, 506-collections-advanced, 538-collections-totals-clear
Automation on receivables (configured; nothing saved or fired). An AR trigger filters by balance age or days past due (with a required day count), minimum and maximum balance, customer status, multi-unit, property type, flags, divisions, collections stages, paper preference and convenience-payment invoices. Its actions are Add Flags, Create Invoices, Freeze Customers, Place Subscription On Hold, Send Email / SMS / Snail Mail / Voice, Set Collections Stage and Webhook. Scope differs by action. Create Invoices (a fixed or percentage value plus a service type, for example a late fee) applies the filters per invoice. Communication, flags, collections stage and freeze use the responsible customer's balance and aging date instead. Freeze Customers also freezes subscriptions on other accounts that customer is financially responsible for. The ACH Return and Chargeback trigger types work only with FieldRoutes Payments and give no notice for other processors. The Trigger Rules manual warns that backdating an AR fee rule can charge invoices that were overdue then but are paid now. It says blank filters mean "all", and that Subscription Hold removes due work and pauses recurring billing. It also describes freeze and payment-profile deletion in a way that conflicts with a separate removal action, which needs vendor clarification (Documented). 230-trigger-rule-editor, 231-trigger-rule-action-editor, 249-trigger-action-freeze, 235-trigger-ach-return, 236-trigger-chargeback
Failed ACH (configured). ACH Auto Returns can be "no system response" or Automatic Reversal. Per the tooltip, Automatic Reversal restores the unpaid balance when an ACH payment fails, for FieldRoutes Payments only. 220-office-billing-preferences-editor
Convenience Payments (documented; no enrolled plan seen). The Billing tab has + Convenience Payments. The Service Plan editor has Include in Convenience Payments, and Frequency Options has a Convenience Payments type, for example a Monthly/30 Days label. The manual says the plan builds up advance AutoPay funding for eligible subscriptions, and those subscriptions must be paid up before enrollment. It does not work with Renewal Billing or consolidated invoices. Included subscriptions drop out of ordinary AutoPay reports and triggers, and one-time add-ons bill separately. Recovery after a decline can collect several overdue charges together. Changing the payer or removing the payment source requires first removing or reassigning the plan or subscription. Mobile collection warnings can be overridden, so they do not prevent payment. The manual also says excluding these invoices affects statements. The Convenience Payments report (Billing) lists upcoming charge date, charge amount, subscriptions and payment-method status for a future window (11/03-12/04/2026); it had zero rows. AR has its own Convenience Payments Invoices control: Do Not Include (default), Include in Total, Only Show. AR triggers can exclude these invoices or include only them. 047-convenience-payments, 512-receivables-advanced-filters, 137-settings-service-plan-form, 169-settings-frequency-options
Prepayment offers (configured; nothing sent). Customers > Prepayments finds customers to offer a plan prepayment. It needs a Service Plan, but the plan list was empty, and it has Property Type and Overdue Balances filters (exclude, include, or exclude 7+ to 180+ days overdue). Its table (Customer ID, name, subscriptions, Mail, Email) was empty. Prepayment Discounts define the offer discount; the field shows no percent or currency unit. Prepayment Letter Templates carry a portal prepayment link and an upsell link. The Customer Communication groups 11-14 hold pre-pay email and postal templates for new and renewing plans, and the welcome SMS and voice templates have optional prepayment wording. The portal can show plan details plus 30/60/90/180-day prepay options. The Prepayments report tracks offers sent: value, discount, tax, payments collected and accepted base and upsell offers. Expiring Paid In Full lists customers whose prepaid year is ending. All observed with empty results. 460-customer-prepayments, 335-prepayment-discounts, 336-prepayment-discount-editor, 292-communication-section-11-editor, 087-report-prepayments, 078-report-expiring-paid-in-full
Field collection (configured; not run on a device). Mobile Service defaults include:
Mobile Sales defaults include Require Valid CC/ACH for APay and Require Payment Method for Scheduling (a valid payment method for the initial appointment). The mobile permission Override Payment & Agreement Schedule Requirements bypasses those prerequisites. The Tech Collections report shows payments collected by technicians at appointments. 183-mobile-service-default-editor, 100-report-tech-collections
Payouts and reconciliation (documented; not reconciled). Disbursements shows processor payouts for a date range and office. The captured two days said "No data to display". Payment History's disbursement column has four tooltip states: N/A for cash, check or coupon; blank for card or ACH not reported through the merchant portal; Pending for a new transaction awaiting payout; and a payout value, meaning the payout that contains the payment. The 2026 Payrix release guide describes a 9:30 PM ET settlement cutoff, separate fee and non-fee presentation, finalized / finalizing / delayed statuses, complete row loading and continued non-Payrix compatibility. These are vendor release claims, not checked for this account. 049-disbursements, 509-payment-history-prior-month
Stored-card upkeep (observed; empty). Manage Stored Cards filters by expiry, unused period and customer status. The table was empty, and selecting rows is not a cleanup action. Expiring Credit Cards finds cards expiring between two months and has Send Messages. Failed Payment Methods finds customers whose stored method failed. Frozen Customers w/ Payment Accounts was blank twice and stays unknown. The dashboard card Frozen w/ Stored Acct warns that some gateways charge per stored account. The Audit check "Customers with cards on file but not on auto pay" showed 0 for the captured day. Customer Communication's Portal Payment Method on Account setting aims to keep at least one method on file. 048-manage-stored-cards, 079-report-expiring-cards, 082-report-failed-payment-methods, 491-frozen-payment-accounts-revisited, 402-dashboard-metric-help-14, 476-audit-cards-without-autopay
Linked properties (documented). Each linked site keeps its own card, billing and invoices. A payment to one property does not settle the others. A master portal account can pay for child properties, but child accounts cannot see each other. Merge is permanent. (Properties manual)
| Filter | Options |
|---|---|
| Acct. Status | All / Active / Frozen (customer lifecycle, not payment outcome) |
| AutoPay (AR, Credits, Collections) | Any AutoPay Status / Not on AutoPay / Card AutoPay / ACH AutoPay / Card or ACH AutoPay |
| AutoPay (AutoPay Balances) | Any AutoPay Type / Card AutoPay / ACH AutoPay (no "not enrolled" option) |
| Status / Payment Method Status | Any AutoPay State or N/A; Successful; Soft Decline; Hard Decline; Soft or Hard Decline; Invalid/Missing |
| Prop. Type | All Properties / Residential Only / Commercial Only |
| As Of Date | Blank date input (AR, Credits, Collections); calculation basis, default and time zone unspecified |
| Balance Age | Any; 7+, 10+, 15+, 30+, 60+, 90+, 180+ Days Old; 0-3, 0-14, 15-29, 0-29, 30-59, 60-89, 90-119, 120-149, 150-179 days; Custom Age Range (child fields not opened) |
| Payment Due | Separate blank Payment Due Date (AR, Collections) |
| Days Overdue | Any; same bands as Balance Age; Custom Range |
| Pref. Paper / Has Email | All / Yes / No |
| Max Monthly | N/A / Yes / No |
| Incl. / Excl. Collections | Multi-select Not Sent / Pending / Sent |
| Incl. / Excl. Flags | Customer flag multi-select (AND/OR not tested) |
| Control | Options / meaning |
|---|---|
| Method tabs | Toggle Menu; All / Card / ACH / Cash / Check / Coupon |
| Transaction Date Range | Creation date in FieldRoutes Payments (shown 11/02-11/02/2026, then 10/01-10/31/2026) |
| Office Payment / Collection Payment | Either / Yes / No |
| Payment Statuses | All; Success; Failed; In Dispute; Disputed - Won; Disputed - Lost; Disputed - Closed; ACH Returned |
| Last 4 #s | Masked-method lookup |
| Card Types | Mastercard / Other (this account's list, not all supported cards) |
| Coupon Codes | Multi-select, empty |
| Payment Methods | Coupon / Cash / Check / Card / ACH (all selected) |
| Offices | Current office |
| Reversed Payments | Include Reversed Payments (default) / Exclude Reversed Payments |
| Disbursement | Any or None; narrows to payments in a chosen payout |
| Payment Origins | Manual; Customer Portal; Batch Process; Trigger; Collections; API; Import; Convenience Payment |
| Collections Agency Payments / Write Offs | Either / Yes / No |
| Include / Exclude Flags | Customer flags |
| Summary | Successful, Coupons, Cash, Check, Card, ACH, Total Collected, Gateway Fees, Net Collected |
| Columns | Customer ID, Customer, Transaction Date, Payment Method, Type, Status, Payment Amount, Fees, Net, Recorded By, Disbursement |
| Method | Fields and buttons |
|---|---|
| Cash | Payment Amount, Confirm Amount, customer payment notes; Record Cash / Record Payment |
| Check | As Cash plus Check Number; Record Check |
| Card | Use Card On File / Single Use Card / Existing Transaction; amount, confirm amount, billing name and address, embedded card entry; Charge Single Card |
| ACH | Use Account On File / Existing Transaction; amount, confirm amount, date, transaction ID, notes; Record Existing |
| Coupon / Credit | Amount, confirm amount, Coupon Code, Description, notes; Record Coupon; Write Off flag |
| All | Distribution Details (customer, subscription, apply-to-first invoice); Payment Flags (office, collection, collections agency); Cancel Payment (not clicked) |
| Control | Options / meaning |
|---|---|
| Default Net Billing Days | Office payment terms default |
| Customer Portal Max Payment Limit | Separate Residential and Commercial caps |
| Customer Portal Plan Display | Hide / details only / details plus 30/60/90/180-day prepay |
| Customer Portal Display Renewals | Hide / always / day window |
| Technician Tip | Portal tipping; only with FieldRoutes Payments |
| ACH Auto Returns | No system response / Automatic Reversal (restores unpaid balance; FieldRoutes Payments only) |
| PO Expiration Auto Freeze | No / freeze subscription (stops future services until reactivated) |
| Convenience Payments Receipts | Receipt delivery policy |
| Retry Soft Declines / Soft Decline Payment Hold Days | Toggle; default or 0-10 days |
| Soft Decline Threshold | 1-20, currently 3 (default); then hard decline; excludes listed legacy merchant integrations |
| Month Closing / Close Month | Closes an accounting period; not run |
| Report | Controls |
|---|---|
| AR Oversight | Saved-report controls (Show Saved Filters); Date; Offices; User Types; Employees; Customer ID; Locations; Objects; Actions; Include IP Address (default No); Refresh; Clear Filters; Export to Excel; limited to 25,000 logs. Columns: Date Created, Location/Object, Action Taken, Change, Customer ID, Related IDs, Office, Employee |
| Payments by Service Type | Saved-report controls (Show Saved Filters); Date; Group By (default Service Type) plus two sub-groups. The Group By list: Billing Frequency, City, County, Customer ID, Customer Name, Customer Source, Division, GL Account, Invoice, Invoice Type, Map Page, Month, Office, PO Number, Payment Date, Payment Type, Region, Sales Rep, Service Bundle, Service Category, Service Type, Service Type ID, State, Subscription Source, Technician, Year, Zip; Coupons (Include / Exclude / Only Coupons); As of Date (field Payment as of Date); Service Plans; Disbursement; Service Bundles; Advanced Filters; Refresh; Clear Filters; Export to Excel. Columns: Applied Payments before Tax, Tax Collected, Total Unapplied, Coupons, Cash, Checks, Visa/Master/Etc, Amex, ACH, Total Collected |
| Expiring Credit Cards | Start / End month; Customer Status (any / active / frozen); Offices; Refresh; Export to CSV; Send Messages |
| Failed Payment Methods | Customer ID; Last Four; Balance >=; Payment Method (all / credit card / ACH); Refresh; Export to CSV |
| Frozen Customers w/ Payment Accounts | Refresh; Export to CSV |
| Expiring Paid In Full | Refresh; Export to CSV; search; columns customer, subscription, phone, remaining prepayment, recurring price |
| Prepayments | Date Created; Expiration Date; Service Plans; Offices; Hide Filters; Refresh; Export to CSV; search |
| Sales Collections | Start / End Date; Include $0 Collected (default No); Refresh; Export to CSV |
| Tech Collections | Start / End Date; Include $0 Collected; Exclude Initial Appointments; Incl. $0 invoice/customer balances; Refresh; Export to CSV; Appointment Breakdown |
| Unpaid Initial | Start / End Date; Refresh; Export to CSV |
| Audit (two panels for this block) | Customers with cards on file but not on auto pay; Locked Periods Audit Log |
| Customers > Prepayments | Clear filters; Service Plan (required); Property Type (All / Residential Only / Commercial Only); Overdue Balances (required: Exclude Overdue Balances, Include Overdue Balances, Exclude 7+ / 10+ / 15+ / 30+ / 60+ / 90+ / 180+ Days Overdue); Save filter; Search |
| Sales Tax | Cash Hybrid method: revenue and tax count when cash is applied to an invoice, prepayments count only once invoiced, late payments count when received, coupon payments are excluded (cash, check, card and ACH are included). Points to Billing by Service Type or Payments by Service Type for accrual or cash views |
| Billing by Service Type (Invoicing and billing terms) | Payment as of Date; Revenue / Production value; Write Offs; collections summary |
AR Oversight's Objects filter covers AutoPay, AR, collections, payment batches, stored cards, invoices, trigger rules and more. Its Actions list includes exported, charged a batch, wrote off a balance, changed AutoPay, refunded a payment and edited trigger rules. These are audit filter names, not proof that each workflow was used. A vendor review says AR Oversight monitors more than 200 AR-related events; it is an audit log, not an aged-debt ledger 064-report-ar-oversight.
Read in the research (Documented):
Indexed in the official catalog, body not read:
Public vendor pages used for corroboration: Payment Processing product page (grouped payments, AutoPay, collection tools, portal payments, status reporting; not proof of this account's processor or fees), FieldRoutes Customers' Adjustments to the Economy (AutoPay rules, Convenience Payments), PestWorld 2022 announcement (disbursement data inside Operations Suite), 2024 Year in Review (AR Oversight tracks more than 200 AR events; prepayments for future Service Plan costs).
Research reports: billing findings, billing control inventory, assessment: billing, payments and accounting, assessment: automation, manual findings, dashboard financial metrics, Customer Search billing filters.
The original research reports are kept unchanged in the archive. These are the sections that speak about this block: