Overview
This page is a practical companion to the AR Reference Manual. Each scenario includes recommended actions, links to the relevant screens, and a note on when supervisor approval is required.
Rule of thumb: If the action changes posted results (void/transfer/modify paid),
treat it as manager-controlled and document it.
Billing & Invoice Scenarios
BillingCustomer disputes an invoice amount
- Open the customer in AR Inquiries and locate the invoice.
- Verify charge details and bill codes (cross-check billing inputs if applicable).
- If correction is needed: use Invoice Adjustment (preferred control path).
- If invoice must be cancelled and reissued: use Void Invoice then rebill using normal billing workflow.
Approval: Any change that reduces billed revenue or changes tax/fees should be approved per company policy.
BillingInvoice billed to the wrong customer
- Confirm the correct customer and the invoice is not already paid/cleared.
- Use Transfer Invoices to move the invoice to the correct customer where appropriate.
- If transfer is not permitted or the invoice must be reissued: Void Invoice and rebill correctly.
Document: Note the reason, who approved the change, and the rebill reference.
BillingNeed to increase a standard fee across all customers (bulk change)
- Identify the Bill Code to change (example: Entry Fee).
- Use Update Customer / Manufacturer Standard Charges.
- Run a spot-check on a few customers/manufacturers to confirm the new standard charge.
Best practice: Communicate the effective date and keep a copy of the pre-change rates for audit/reference.
Cash Receipts Scenarios
CashPayment received with no invoice reference
- Enter the receipt in Cash Receipts.
- Apply as Cash on Account (unapplied) until invoice matching is confirmed.
- When identified, apply using Apply Credits & Cash on Account.
Control: Review unapplied balances daily/weekly to prevent hidden credits and customer confusion.
CashCustomer overpaid
- Confirm the overpayment is valid (not an unposted invoice or timing issue).
- Apply to open invoices if intended; otherwise leave as credit on account.
- Follow company policy for refunds vs carrying credit.
Note: Overpayments affect statements and can create collection noise if not handled consistently.
Statements & Collections
StatementsStatements don’t look branded / logo missing in email
- Verify Statement Setup has HTML emailing enabled.
- Confirm Logo Location is a publicly accessible URL (recipients must be able to load it).
- Send a test statement to internal recipients using multiple email clients.
Tip: Keep colors high-contrast and use subtle alternating row colors for readability.
CollectionsCustomer says invoices are missing from their statement
- Confirm invoices are posted and open (not paid/voided/transferred).
- Verify department/reporting selection and aging criteria used for statement run.
- Use AR Inquiries to validate open items vs statement output.
Month-End & Reconciliation
Month-EndAR Aging doesn’t match expectation
- Confirm aging columns are correct under Define Statement Aging Columns.
- Check for unapplied cash/credits, old disputes, or misapplied items.
- Use AR Month-End Procedures for the closing checklist.
Reminder: Aged receivables are usually a process issue (timing, disputes, application), not a report issue.
Manager Controls
The following actions are typically restricted to supervisors/managers due to audit risk:
- Modify Paid Invoice
- Void Invoice
- Transfer Accounting
- Setup & Maintenance
- Bulk Standard Charge Updates
Documentation standard: Record the reason, approver, date/time, and the customer/invoice references impacted.