FieldRoutes in Payments and collections

FieldRoutes calls it: AutoPay, Auto-pay Profile, AutoPay Balances

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.

In short

  • FieldRoutes keeps debt, credit, payment and payout as separate views. They are AutoPay Balances, Accounts Receivable, Accounts With Credits, Collections, Payment History, Payment Batches, Convenience Payments, Manage Stored Cards and Disbursements. Each view has its own filters and its own meaning (Observed, 040-billing).
  • AutoPay enrollment, a stored card or ACH source, a valid profile, a queued charge and a successful transaction are five different facts. AutoPay Balances shows who is ready to be collected, not who paid (Observed, 041-autopay-advanced).
  • Receivables aging is a set of choices, not one formula. You can group by Bill To or by Invoice, age by account balance or by individual invoice balances, and start aging at the invoice date or the due date. The defaults are Bill To, Account Balance and Invoice Date (Observed, 512-receivables-advanced-filters).
  • The payer is a separate concept from the customer. The Billing tab has a Default Bill To for new invoices and subscriptions. The manual says responsibility can sit at the customer, subscription or invoice level, and subscription AutoPay can override the customer default. Automation then acts either on single invoices or on the responsible payer's total balance, depending on the action (Observed and Documented, 453-customer-bill-to-selector, 249-trigger-action-freeze).
  • Several money rules depend on the processor. ACH Return and Chargeback triggers, automatic ACH reversal and technician tips work only with FieldRoutes Payments. The soft-decline threshold excludes listed legacy merchant integrations. The Payment History screen is branded "with Payrix" (Observed, 235-trigger-ach-return, 220-office-billing-preferences-editor).
  • Convenience Payments is an advance payment plan, not a billing frequency. It collects a regular amount and charges service invoices against that balance. It does not work with Renewal Billing or consolidated invoices, and its invoices are left out of AR totals by default (Documented and Observed, 047-convenience-payments).
  • The account showed real records: one failed card payment (API origin, FieldRoutes Payments gateway), about 30 accounts in AR and in Collections, and one card payment in an open batch. No successful collection, allocation, settlement or reconciliation was seen (Observed, 510-payment-history-detail-attempt).

Screens: 40 captures

Upload a screen

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.

Their words for this block 36

AutoPay (Card AutoPay / ACH AutoPay): Automatic collection from a stored card or bank account. The Billing tab tooltip says it charges the full balance automatically. It can be set at customer level, and per subscription as an override. Observed 006-customer-billing; override Documented (Billing tab manual)
Auto-pay Profile: On a subscription, which AutoPay setting the subscription uses. "Customer Default" was the only choice seen. Observed (subscription detail, Service agreements and renewals)
AutoPay Balances (Auto Pay Customers with Balances): List of AutoPay-enrolled accounts that still owe money, so staff can see who should be charged. It shows readiness, not success. Observed 040-billing
Soft Decline / Hard Decline / Invalid/Missing: Payment-method status classes used as filters. Office preferences say a soft decline becomes a hard decline after the retry threshold (default 3). Observed 041-autopay-advanced, 220-office-billing-preferences-editor
Accounts Receivable (AR): The aging list of who owes money, with payer grouping and aging choices. Observed 042-accounts-receivable
Balance Age vs Payment Due vs Days Overdue: Three separate time measures. Age counts from the aging start date. Payment Due is a due-date input. Days Overdue counts days past the due date, not days since the transaction. Observed 512-receivables-advanced-filters
Recent / Current / Late / Past Due: Display labels for age bands: 0-3 Recent, 0-14 Current, 15-29 Late, 0-29 Current & Late, 30-59 Past Due, older bands more past due. They are display categories, not a contractual delinquency rule. Observed 041-autopay-advanced
Responsible Balance / Responsible Payer / Bill To: The balance and identity of the account that pays, which can differ from the account's own balance. "Self" or "Other". Observed 415-customer-billing-account-filters, 427-billing-account-filters-lower
Default Bill To: The default paying account for new invoices and subscriptions. The tooltip says the chosen account is responsible for paying invoices. Observed 453-customer-bill-to-selector
Accounts With Credits / Credit Type: Accounts holding money in their favor. Credit Type separates Credits, Prepayments or Both. Observed 504-accounts-credits-revisited
Responsible Customer vs Originating Customer: On credits, who the credit belongs to financially versus which account (and office) it came from. Observed 504-accounts-credits-revisited
Collections / Collections Stage (Not Sent / Pending / Sent): Review list of overdue accounts, and a stage marker for the external collections process. Opening the list or a row being on it does not mean the debt went to an agency. Observed 505-collections-revisited, 251-trigger-action-collections-stage
Not Set vs Not Sent: Possible false friend. Collections rows and the manual say "Not Set". Filters and the Billing tab say "Not Sent". It is not proven that they are the same stored value. Observed 506-collections-advanced; Documented (Billing tab manual)
On Hold / Subscriptions On Hold: Service hold on subscriptions, shown in Collections. It is not a payment hold. Observed 505-collections-revisited
A/R Hold Time: False friend. It is the wait before another statement can go out by the same method (15 days residential and 15 commercial here). It does not freeze service or payment. Observed 285-communication-section-4-editor
Payment History / Payment Reports: Recorded transactions with outcome, method, origin and payout link. Observed 508-payment-history-loaded
Transaction Date: Per the tooltip, the date the transaction was first created in FieldRoutes Payments. It is not the invoice, posting, payout or bank date. Observed 508-payment-history-loaded
Payment Origin: Where a payment came from: Manual, Customer Portal, Batch Process, Trigger, Collections, API, Import, Convenience Payment. It records the origin, not an authorization. Observed 508-payment-history-loaded
Office Payment / Collection Payment / Collections Agency Payment / Write Off: Flags on a payment. Write Off appears on the Coupon / Credit form. Observed 024-payment-cash, 028-payment-credit
Distribution Details (Limit to Customer / Limit to Subscription / Apply to First): Allocation limits that say where the money may go and which invoice it pays first. Observed 024-payment-cash, 510-payment-history-detail-attempt
Coupon / Credit: A non-cash payment method that records a credit with a coupon code. The Sales Tax report leaves coupon payments out. Observed 028-payment-credit, 095-report-sales-tax
Single Use Card / Use Card On File / Existing Transaction: Card payment modes: charge a new card once, charge the stored card, or record a transaction made elsewhere. Observed 026-payment-card
Payment Batches / Finalize & Post Payments: Office entry of received cash and checks in a batch, then posting. Entry, allocation, posting and recorded history are separate steps. Observed 507-payment-batches-revisited
Import Lockbox Batch: Entry point for importing a bank lockbox file of payments. Format and bank link not shown. Observed 507-payment-batches-revisited
Convenience Payments (CPP): An advance payment plan: the customer prepays a regular amount on a set frequency, and service invoices are charged against that balance. Observed 047-convenience-payments; Documented (manual)
Prepayments / Prepay offer: Offers to pay a service plan ahead, usually with a prepayment discount. False friend: Customers > Prepayments (finding customers to offer), the Payment Batches Prepayments tab, the Prepayments credit type and the Prepayments report (offers sent) are four different things. Observed 460-customer-prepayments, 087-report-prepayments
Paid in Full / Year In Full (YIF) / Paid Year in Advance: Flags and filters for customers who prepaid a year. A flag only, not a reconciled zero balance. Observed 504-accounts-credits-revisited, 078-report-expiring-paid-in-full
Max Monthly / Max Monthly Charge: A cap on automatic charges. The manual defines it as a rolling 30-day cap from the payment source's previous payment, not a calendar month. Observed 415-customer-billing-account-filters; Documented (Billing tab manual)
Invalid Payment Method: In Billing Letter Templates, an account whose last credit-card transaction failed. Separate from the Invalid Payment Method Flag and from Payment Profile Status (Valid/Invalid) in Customer Search. Observed 205-billing-letter-template-editor, 422-customer-account-filters-lower
Stored Cards / Token ID / Bank Update: Stored card records with expiry, last successful use and account-updater fields. Observed 048-manage-stored-cards
Disbursement: A processor payout to the company bank account that contains a payment. Different from the transaction date and from bank settlement. Observed 049-disbursements, 509-payment-history-prior-month
Gateway / FieldRoutes Payments / Payrix: The processing path. The failed payment names Gateway "FieldRoutes Payments", and the Payment History screen says "with Payrix". Observed 510-payment-history-detail-attempt, 508-payment-history-loaded
A/R Turnover: Customer Card metric. The manual defines it as average days until the full account balance is paid. Observed 435-populated-customer-overview; Documented (Customer Card Overview manual)
Record Payments (Commission report): False friend. It records commission payouts to employees, not customer payments. Observed 073-report-commission
Admin Billing / Usage: False friend. It is FieldRoutes' own subscription and usage billing to the company, not customer receivables. See FieldRoutes hub. Observed (hub captures)
Payment collected vs revenue vs production vs contract value: Different measures. A failed attempt amount is not collected revenue. Documented in the research summary (report)

Where it lives in FieldRoutes

Menus, pages and settings where this block appears 27 menu paths

Connections to other blocks

How FieldRoutes does it

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.

  • Cash: Payment Amount, Confirm Amount, notes, Record Cash / Record Payment.
  • Check: the same plus Check Number, with Record Check.
  • Card: Use Card On File (crossed out here because no card was stored), Single Use Card (selected) or Existing Transaction; billing name and address, an embedded processor card-entry area, and Charge Single Card. The card-entry area was blank in the capture, so working card entry is unverified.
  • ACH: Use Account On File or Existing Transaction (selected); for an existing transaction it asks for amount, confirm amount, date, transaction ID and notes, with Record Existing.
  • Coupon / Credit: amount, confirm amount, Coupon Code, Description and notes, Record Coupon, plus a Write Off flag.

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:

  • Block Completion if There is Balance (No / Yes / Residential Only / Commercial Only)
  • Max Over Collect
  • Enforce Payment Hold Date and Enforce Max Monthly Charge
  • Tech Collection Auto Apply. Its tooltip says a cash or check collection on a completed visit is applied automatically, the applied payment is replaced if the technician changes the collection, and the technician needs the Apply Payments permission.

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)

Settings and controls

All settings and controls seen 138 rows

Shared Billing report controls

  • Billing submenu: AutoPay Balances, Accounts Receivable, Accounts With Credits, Collections, Payment History, Payment Batches, Convenience Payments, Manage Stored Cards, Disbursements 040-billing.
  • Refresh, Clear Filters, Search (searches the page output, not global lookup), sortable headers, Show entries, pagination. Export / Export to CSV / Export to Excel exist on specific pages; none was run.
  • Saved reports (AutoPay Balances, AR, Credits, Collections): Enter Report Name; scope User / Office / Global (User selected, Global disabled for unknown reasons); Not Default / Default; Save / Save as New; No Saved Reports / Show Saved Filters.
  • Advanced Filters / Basic Filters expand or collapse criteria.

Common filters (subsets differ by page) 041-autopay-advanced, 506-collections-advanced, 512-receivables-advanced-filters

FilterOptions
Acct. StatusAll / 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 StatusAny AutoPay State or N/A; Successful; Soft Decline; Hard Decline; Soft or Hard Decline; Invalid/Missing
Prop. TypeAll Properties / Residential Only / Commercial Only
As Of DateBlank date input (AR, Credits, Collections); calculation basis, default and time zone unspecified
Balance AgeAny; 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 DueSeparate blank Payment Due Date (AR, Collections)
Days OverdueAny; same bands as Balance Age; Custom Range
Pref. Paper / Has EmailAll / Yes / No
Max MonthlyN/A / Yes / No
Incl. / Excl. CollectionsMulti-select Not Sent / Pending / Sent
Incl. / Excl. FlagsCustomer flag multi-select (AND/OR not tested)

AutoPay Balances 040-billing, 041-autopay-advanced

  • Balance >= (0.05 shown); advanced Balance Age, Pref. Paper, Has Email, Max Monthly, Incl. Collections, Incl./Excl. Flags.
  • Actions: Batch Charge (bulk charge, not opened), Update Actions (not opened).
  • Columns: Billing CustomerID, Subscription, Billing Name, Billing Phone, Card Status, Attempts, Age, Prefers, Monthly, Due, Charging, Action; Total. Prefers and Charging arithmetic is not documented on screen.

Accounts Receivable 042-accounts-receivable, 512-receivables-advanced-filters, 513-receivables-actions

  • Balance Range (minimum 0.01, maximum blank).
  • Group By: Group By Bill To (default) / Group By Invoice.
  • Determine Aging By: Account Balance (default) / Ind. Invoice Balances.
  • Aging Start Date: Invoice Date (default) / Invoice Due Date.
  • Convenience Payments Invoices: Do Not Include (default) / Include in Total / Only Show Convenience Payments Invoices.
  • Refresh, Export to CSV, Clear Filters, Search; Toggle (unexplained, not used).
  • Actions: Send Message, Print Statements, Snail Mail Statements, Email Statements.
  • Columns: Customer ID, Name, Phone, Zip, Email, AutoPay, Max Monthly, Age, Total Due, Send SMS, Send Voice, Email Statement, Print Statement. Cards: Total Owed, Current, Over 30, Over 60, Over 90 Days.

Accounts With Credits 504-accounts-credits-revisited

  • Credit Type: Credits (default) / Prepayments / Both; plus common filters.
  • Actions and Toggle (not opened).
  • Columns: Responsible Customer ID, Originating Customer ID, Originating Office Name, Name, Phone, Zip, Email, AutoPay, Paid in Full Flag, Max Monthly, Total Credit, Send SMS, Send Voice, Email Statement, Print Statement. Result: zero rows, 0.00 total.

Collections 505-collections-revisited, 506-collections-advanced

  • Basic: As Of Date, Acct. Status, Balance Age, Payment Due, Days Overdue. Advanced: AutoPay, Status, Prop. Type, Pref. Paper, Has Email, Max Monthly, Incl./Excl. Collections, Balance >= (0.01), On Hold (N/A / Yes / No), Incl./Excl. Flags.
  • Selection checkboxes (all 30 rows checked, select-all unchecked, in 505-collections-revisited, 506-collections-advanced and 538-collections-totals-clear); Actions (not opened).
  • Columns: CustomerID, Name, Address, City, State, Zip, Email, Phone, Balance, Age, Earliest Due Date, Days Overdue, Status, Stage, Subscriptions On Hold, AutoPay, Payment Status, Last Payment; aging cards.

Payment History (Payment Reports) 508-payment-history-loaded, 509-payment-history-prior-month

ControlOptions / meaning
Method tabsToggle Menu; All / Card / ACH / Cash / Check / Coupon
Transaction Date RangeCreation date in FieldRoutes Payments (shown 11/02-11/02/2026, then 10/01-10/31/2026)
Office Payment / Collection PaymentEither / Yes / No
Payment StatusesAll; Success; Failed; In Dispute; Disputed - Won; Disputed - Lost; Disputed - Closed; ACH Returned
Last 4 #sMasked-method lookup
Card TypesMastercard / Other (this account's list, not all supported cards)
Coupon CodesMulti-select, empty
Payment MethodsCoupon / Cash / Check / Card / ACH (all selected)
OfficesCurrent office
Reversed PaymentsInclude Reversed Payments (default) / Exclude Reversed Payments
DisbursementAny or None; narrows to payments in a chosen payout
Payment OriginsManual; Customer Portal; Batch Process; Trigger; Collections; API; Import; Convenience Payment
Collections Agency Payments / Write OffsEither / Yes / No
Include / Exclude FlagsCustomer flags
SummarySuccessful, Coupons, Cash, Check, Card, ACH, Total Collected, Gateway Fees, Net Collected
ColumnsCustomer ID, Customer, Transaction Date, Payment Method, Type, Status, Payment Amount, Fees, Net, Recorded By, Disbursement

Payment detail 510-payment-history-detail-attempt, 511-failed-payment-actions

  • Back; status banner; Transaction Status; Transaction Amount; Transaction Date; Payment Method; Cardholder Name; Billing Name; Recorded By; Customer Payment Notes; Status Detail; Transaction ID with copy control; Authorization Code; AVS Results; CVV Results; Payment Origin; Gateway.
  • Flags (disabled in view): Office Payment, Collection Payment, Collections Agency Payment, Write Off.
  • Applied To list; Distribution Details: Limit to Subscription, Limit to Customer, Apply to First (disabled).
  • Actions: Update Payment, Email Receipt, Print. Customer shell: Close, Schedule, Transfer.

Add Payment forms 023-customer-add-payment to 028-payment-credit

MethodFields and buttons
CashPayment Amount, Confirm Amount, customer payment notes; Record Cash / Record Payment
CheckAs Cash plus Check Number; Record Check
CardUse Card On File / Single Use Card / Existing Transaction; amount, confirm amount, billing name and address, embedded card entry; Charge Single Card
ACHUse Account On File / Existing Transaction; amount, confirm amount, date, transaction ID, notes; Record Existing
Coupon / CreditAmount, confirm amount, Coupon Code, Description, notes; Record Coupon; Write Off flag
AllDistribution Details (customer, subscription, apply-to-first invoice); Payment Flags (office, collection, collections agency); Cancel Payment (not clicked)

Payment Batches 507-payment-batches-revisited

  • Tabs: Payment Batches / Prepayments (Prepayments not opened). Date, Batches selector, Refresh.
  • Close Batch; Import Lockbox Batch; Choose a Customer / Search by Invoice (three more disabled, unlabeled textboxes); Method (Cash / Check); Amount / Confirm Amount; Payment Notes; Any Customers / Any Subscriptions / Any Invoices; Collections Agency Payment; Add; Cash(0) / Check(0) / Total(0); Finalize & Post Payments.
  • Recorded Payments: Search, Export Excel (not run); columns Customer, Payment Method, Recorded By, Date Open, Date Closed, Office, Batch ID, Collections, Check #, Date Paid, Amount; totals Cash, Checks, CC, ACH, Coupons, Total.

Convenience Payments report 047-convenience-payments

  • Date (future window), Payment Method Status (N/A / Successful / Soft Decline / Hard Decline / Soft or Hard Decline / Invalid/Missing), Included Subscriptions (all offerings selected), Refresh, Export to Excel, Send Message, Search, paging.
  • Columns: Customer ID, Customer Name, Charge Date, Charge Amount, Subscriptions, Payment Method Status.

Manage Stored Cards 048-manage-stored-cards

  • Expires: All / Already Expired / Expires This Month / Expires Next Three Months.
  • Unused: All / Not Used This Month / Not Used Prior 3 Months / Not Used Prior 6 Months / Not Used Prior 1 Year / Never Used.
  • Customer Status: All / Active / Frozen / Pending Cancel. Offices, Refresh, Export to CSV, Search, page size, select-all.
  • Columns: Customer ID, Cardholder Name, Card, Token ID, Expires, Last Successful Transaction Date, Customer Status, AutoPay Card, Bill-To, Bank Update, Date Refreshed.

Disbursements 049-disbursements

  • Date (11/01-11/02/2026), Offices, Refresh, Export to CSV.

Customer Card billing controls 452-customer-billing-populated, 453-customer-bill-to-selector, 435-populated-customer-overview, 440-populated-customer-invoices, 444-account-balance-summary

  • Billing tab: billing name, company, address, phone, email; AutoPay (No Auto Pay shown); Collections Stage (Not Sent shown); include individual invoice numbers on consolidated invoices; auto-consolidate multiservice appointment invoices; Copy Billing Info; Assign New Billing Account (manual: changes the responsible customer / Default Bill To); Save Billing Info; Default Bill To / Select Bill To (Select Billing Account dialog: search, Select, Cancel); + Add Payment Method; + Convenience Payments.
  • Subscription billing: Billing Account (SELF), Auto-pay Profile (Customer Default), Net Billing Days, Next Billing.
  • Overview: Account Balance, A/R Turnover, prompts to collect the balance and offer AutoPay.
  • Invoices tab: Account Summary / Account Balance Summary, Last Letter / Last Email, Email / Snail Mail / Print, Payments, + Add Payment. Invoice Actions include Credit Memo and Delete Invoice.
  • Account Balance Summary: Actions, refresh, date range with presets (Today, Yesterday, This Week, Last Week, This Month, Last Month, This Year, Last Year, All History, Custom Range), This Account / Responsible For, Beginning / Ending Balance, columns Item, Account #, Description, Invoice Amount, Payment.

Office Billing Preferences (payment part) 220-office-billing-preferences-editor

ControlOptions / meaning
Default Net Billing DaysOffice payment terms default
Customer Portal Max Payment LimitSeparate Residential and Commercial caps
Customer Portal Plan DisplayHide / details only / details plus 30/60/90/180-day prepay
Customer Portal Display RenewalsHide / always / day window
Technician TipPortal tipping; only with FieldRoutes Payments
ACH Auto ReturnsNo system response / Automatic Reversal (restores unpaid balance; FieldRoutes Payments only)
PO Expiration Auto FreezeNo / freeze subscription (stops future services until reactivated)
Convenience Payments ReceiptsReceipt delivery policy
Retry Soft Declines / Soft Decline Payment Hold DaysToggle; default or 0-10 days
Soft Decline Threshold1-20, currently 3 (default); then hard decline; excludes listed legacy merchant integrations
Month Closing / Close MonthCloses an accounting period; not run

Customer Communication (payment part) 281-customer-communication-preferences-editor, 285-communication-section-4-editor, 313-communication-section-32-editor

  • Enable Online Payments; Email Payment Receipts; Send Recurring Billing Email; Show Invoice on Service Notification/Follow-up.
  • Send Bad Payment Method Notifications: No / SMS / email / both.
  • Portal Payment Method on Account: keeps at least one method on file.
  • FieldRoutes Payments Language: editable authorization text, max 1600 characters including placeholders.
  • Group 3 Account Statement Tear Sheet: No / Yes; the mailed version adds a return envelope and costs an extra $0.20 per statement (current No).
  • Group 4 Accounts Receivable Hold Time: residential and commercial days (15 / 15).
  • Group 9 Statement and Invoice Footer Text: contains finance-charge prose. That is template content, not a charge rule that ran.
  • Groups 11-14 Service Plan Pre-Pay email and postal templates (new and renewal); groups 22, 23, 33 and 34 welcome and renewal SMS and voice templates, where the welcome ones have optional prepayment wording.
  • Group 32 SalesRoutes and Customer Portal Auto Payment Message: authorization text above the AutoPay initials; standard text if blank.

Plan, fee and offer settings

  • Service Plan: Net Billing Days / office default, Include in Convenience Payments, Prepay Discount, Send Recurring Billing Email, Email Payment Receipt 137-settings-service-plan-form.
  • Add-ons include cancellation, late-payment, NSF and service fees and service discounts 144-settings-addons.
  • Frequency Options type Convenience Payments 169-settings-frequency-options.
  • Prepayment Discounts: Discount Name, Discount (no unit shown), Description (all required), Hidden/Visible 336-prepayment-discount-editor. Prepayment Letter Templates: Description, scope, visibility, Body, Closing, preview (Services section not customizable), placeholders including discount, offer date and expiry, portal prepayment link and upsell link.
  • Renewal Notices variables include balances and separate bill-to information (Service agreements and renewals).

Trigger Rules (payment part) 230-trigger-rule-editor, 234-trigger-auto-payment, 546-trigger-placeholders-clear

  • Shared: Description, office scope, Start / End Date, Active / Not Active.
  • AR: Age/Past Due + Days; Minimum / Maximum Balance; Customer Status (Active / Frozen / Pending Cancel); Multi Unit; Include/Exclude Customer Flags, Divisions, Collections Stages; Prefers Paper; Property Type; Include Convenience Payments (exclude / only CP invoices).
  • Auto Payment: Account Status (Active / Any / Frozen); Balance Age (buckets or Custom Age Range); AutoPay Type (ACH / card / any); Minimum Balance (required), Maximum Balance; Property Type; Include/Exclude Customer Flags.
  • ACH Return; Chargeback (FieldRoutes Payments only).
  • Actions: Create Invoices (Value Type fixed/percentage, Value, Service Type); Freeze Customers (reason, message); Place Subscription On Hold (reason, cancel pending appointments, notes); Set Collections Stage; Send Email (statement or new message, Ignore Contact Prefs) / SMS / Snail Mail (letter or statement) / Voice (Ignore Contact Prefs); Add Flags; Webhook.
  • Placeholders (24): portal login link, portal URL, account number, customer ID and number, customer and billing name and address, email, total due, balance age, responsible balance, days past due.

Customer Search money filters and columns 415-customer-billing-account-filters, 427-billing-account-filters-lower, 422-customer-account-filters-lower, 424-subscription-filters-agreements-billing, 426-subscription-filters-lower

  • Billing Account group: Balance Age, Account Balance, Responsible Balance Age, Responsible Balance, Max Monthly Charge (seven comparison operators each); Customer Auto Pay (N/A / No / Yes / Credit Card / ACH); Payment Profile Status (N/A / Valid / Invalid); Invoice Numbers; Invoice PO Numbers; Earliest Due Date; Payment Days Past Due; Year In Full; Customer Has Credit Card; Customer Has ACH; Has Active Convenience Payments Plan; Responsible Payer (N/A / Self / Other); Collections Stage (Not Sent / Pending / Sent).
  • Customer Account group: Has Child Billing; Invalid Payment Method Flag; Switch Over Flag (meaning not given).
  • Subscription group: Subscription Has Auto Pay; Subscription Bill To (Self / Other); Recurring Billing; Billing Frequency; Billing Date; Last Completed Paid.
  • Output columns: Customer Auto Pay, Subscription Auto Pay, Payment Profile Type, Payment Profile Gateway, Payment Profile Last Four, Payment Profile Token, Monthly Plan, YIF; Account Balance, Responsible Balance, Subscription Balance, A/R Aging, Responsible A/R Aging, Days Past Due, Earliest Due Date, Max Monthly Charge, Last Service Balance; Collections Stage, Collections Update Date, Collections Updated By; Bill To Customer ID and Bill To billing identity and address fields.
  • Sales Report extra columns: Balance, Aging, OverDue Status, Paid Year in Advance, Invalid Payment Method, Subscription Charges, Subscription Payments, Subscription Balance.

Permissions (Access Control Profiles) Technicians and licenses

  • Transactions: View Transactions, Add Charges, Apply Payments, Edit Transactions, Refund Payments, Delete Invoices, Create Coupon, Negative Charges, Add/Edit Credit Memos, Complete appointment when period is locked.
  • Billing: Assign Billing Account, View / Edit / Add Own Billing, View / Edit / Add Other Billing, Approve Forms, Create/Edit Convenience Payments.
  • Reports: View and Edit/Actions, separately, for Autopay Balances, Accounts Receivable, Accounts with Credits, Payment History, Consolidated Invoices, Collections, Disbursements and Managed Stored Cards. Payment Batches has View Payment Batches, Edit/Actions Payment Batches, View Prepayments and Edit/Actions Prepayments. Also Freeze Accounts/Subscriptions and Send Message.
  • Financial Reports: View Billing by Service Type, View Payments by Service Type, View Forecast Report, View Tech Collections, View Sales Collections, View AR Oversight Report.
  • Dashboard widgets: Collections Percentage, Autopay Percentage, Receivables Aging, Payment Types, Frozen with Account, Recurring Billing, Debit Balance.
  • Mobile: Override Payment & Agreement Schedule Requirements.

Payment reports 064-report-ar-oversight, 088-report-payments-service-type

ReportControls
AR OversightSaved-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 TypeSaved-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 CardsStart / End month; Customer Status (any / active / frozen); Offices; Refresh; Export to CSV; Send Messages
Failed Payment MethodsCustomer ID; Last Four; Balance >=; Payment Method (all / credit card / ACH); Refresh; Export to CSV
Frozen Customers w/ Payment AccountsRefresh; Export to CSV
Expiring Paid In FullRefresh; Export to CSV; search; columns customer, subscription, phone, remaining prepayment, recurring price
PrepaymentsDate Created; Expiration Date; Service Plans; Offices; Hide Filters; Refresh; Export to CSV; search
Sales CollectionsStart / End Date; Include $0 Collected (default No); Refresh; Export to CSV
Tech CollectionsStart / End Date; Include $0 Collected; Exclude Initial Appointments; Incl. $0 invoice/customer balances; Refresh; Export to CSV; Appointment Breakdown
Unpaid InitialStart / 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 > PrepaymentsClear 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 TaxCash 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.

Dashboard payment measures (vendor help text, not checked against records)

  • AutoPay Percentage: active customers split into Valid AutoPay, Invalid AutoPay (payment details missing or invalid) and Not on AutoPay 395-dashboard-metric-help-7.
  • Receivables Aging: money owed by balance age; invoice balances under 30 days are current, everything else past due; also shows the balance of customers who prefer monthly billing; points to Billing > Accounts Receivable 396-dashboard-metric-help-8.
  • Payment Types: revenue collected in the period by payment type, with card and ACH flagged as AutoPay opportunities; points to Payment History 397-dashboard-metric-help-9.
  • Frozen w/ Stored Acct: count of frozen customers still storing a payment account 402-dashboard-metric-help-14.
  • Debit Balance: total balance of active customers compared with revenue of the past 30 days, as a ratio that can exceed 100% 404-dashboard-metric-help-16.
  • Recurring Billing: active recurring-billed subscriptions that paid their first bill, rated on the last paid invoice (Reporting and analytics).
  • Collections % (Accrual): shows collected amount, total owed, sales and tax with date inputs; no help was captured, so its formula is unknown 386-dashboard-resumed.

What the research did not prove

  • No financial action ran: no charge, Batch Charge, payment record, batch Add, Finalize & Post, Close Batch, lockbox import, refund, reversal, write-off, credit memo, collections submission or agency transfer, statement send, print or mail, receipt, export, stored-card change or saved report.
  • No successful payment, allocation, settlement, month close, or bank or GL reconciliation was seen. The only opened payment had failed, and its error text is not a diagnosed cause. The open-batch card record was not created by the research.
  • Empty results do not mean a feature is missing: AutoPay Balances (empty at the 0.05 minimum), Credits (zero rows), Convenience Payments (zero rows), Stored Cards (empty), Disbursements ("No data to display"), Expiring Paid In Full and Prepayments (zero entries). Expiring Credit Cards, Failed Payment Methods, Sales Collections, Tech Collections and Unpaid Initial had blank result areas. Frozen Customers w/ Payment Accounts was blank twice (491-frozen-payment-accounts-revisited) and stays unknown. Payments by Service Type was still loading.
  • The early views 043-accounts-credits, 044-collections, 045-payment-history and 046-payment-batches are superseded by the loaded states. They are not module limits.
  • The embedded card-entry area in 026-payment-card was blank, so working card entry is unverified.
  • Unopened or unexplained controls: AutoPay Batch Charge and Update Actions, Credits and Collections Actions menus, the AR Toggle, the Payment Batches Prepayments tab, custom age range fields, three unlabeled batch textboxes, the batch-record green dot, and the Bank Update column.
  • Unknown semantics: Prefers and Charging arithmetic; Max Over Collect units; how Max Monthly is enforced; the As Of Date calculation; the batch date filter basis; Office Payment; Switch Over flag; Year In Full rules; Not Set vs Not Sent; how On Hold applies to account vs subscription; AND/OR for flag filters; Collections % (Accrual), for which no help was captured.
  • Retry algorithms, decline codes, dispute handling and payout timing are not proven. The Payrix cutoff and statuses are vendor release claims, not confirmed for this account.
  • The account's processor, fees and entitlement are not established. The screen says "with Payrix" and the gateway says FieldRoutes Payments; the research did not assume every payment uses one path.
  • Not tested: responsible-payer AR across several accounts, alternate payers, linked-property payments, partial payments and overpayments, multi-office allocation, convenience-plan catch-up charges, duplicate-payment controls, and non-US billing.
  • Portal payment self-service, mobile collection on a device, and role enforcement of the payment permissions were not tested. Prepayments could not run because the Service Plan list was empty.
  • Account Balance Summary was captured only with the Responsible For switch selected. Its table stayed empty for Today and for All History (01/01/1900 onward), which is expected unless another account names this customer as its payer. The This Account view was never shown, so the customer's own ledger was not demonstrated, and the empty table is not a sign that it is missing (444-account-balance-summary, 446-customer-historical-balance).
  • Authorization, charging, settlement, reversal, refund and void are separate operations. Their manuals were not accessible, so none of them is described here from generic payment practice.
  • The Billing tab manual excludes non-US billing addresses. The Card payment form itself shows a billing-address country list (Brazil, Canada, Germany, Guam, United Kingdom, United States, Virgin Islands; United States selected), and card entry happens in an embedded Payrix frame (payrixSingleChargeIFrame) that was blank in the capture. Neither proves non-US billing works (Observed 026-payment-card). The assessment treats this as the main conditional mismatch: a non-US billing need conflicts unless the vendor shows a supported alternative (assessment).
  • Open acceptance questions from the assessment: supported billing countries, processor terms, payout timing, disputes and chargebacks, retry rules, payment-token portability, the accounting export or integration, month-end corrections and who may make them, closed-period corrections, delayed ZIP tax updates, PO-expiry interruption, and invoice-level vs responsible-balance automation scope. Each rule must be checked against the chosen processor (assessment).
  • Indexed manuals whose bodies were not read are listed below. Do not infer their content from titles, for example "Prefers After" and "Will Charge".

Ideas for Our CRM

Agent proposals, not decisions
  • Proposal: keep enrollment, stored method, method validity, scheduled charge, transaction outcome and payout as separate records and states, as the research recommends.
  • Proposal: make the aging basis explicit and visible on every AR view: grouping, account vs invoice balance, and invoice date vs due date.
  • Proposal: model the payer (Bill To / responsible party) separately from the serviced account, and state for each automation whether it acts per invoice or on the responsible payer's balance.
  • Proposal: show the processor dependency next to any rule that only works with one processor (ACH return, chargeback, auto reversal, tips, soft-decline retry).
  • Proposal: define Transaction Date, posting date and payout date as separate fields with in-page help, following FieldRoutes' tooltips.
  • Proposal: require a review step before activating rules that create fees, charge, freeze or hold service, or override contact preferences. The research suggests this as an operating control, not a FieldRoutes feature.
  • Proposal: build the acceptance test the assessment asks for: reconcile service charges, advance payments, partial payments, credits, refunds, failed ACH and card payments, taxes and consolidated invoices to the bank and the ledger.

Official FieldRoutes manuals

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.

Screenshots kept in other blocks that also matter here 57
Research sections used for this page 113

The original research reports are kept unchanged in the archive. These are the sections that speak about this block: