Payment reports
Payment reports maps to fixed source for Business payment invoices, payment-history PDF generation, general payment-report CSV generation, and an optional external-report integration. These are private financial/export surfaces, not safe runtime instructions.
The fixed /intelligence/business-payments route allows levels 0 and 2. The sidebar item is enabled for level 0 and depends on configured Reports membership for level 2. Route/menu presence does not prove record access, export authorization, plugin availability, or deployment.
Source-defined modes
The UI source renders Reports by business and General report modes. Business mode selects a Business; General report derives billing periods from payment-method cycle configuration.
The screenshot is an empty mode selector only. It is not evidence of current invoices, methods, periods, files, or deployed authorization.
Invoice and payment-history boundary
Fixed source can read business_payment_invoices, optionally filtered by Business, and open invoice detail state. A separate authenticated request constructs a payment-history PDF using Business ID and explicit start/end values. The proposed filename also incorporates those values.
Invoice and history content can contain Business identity, orders, payment methods, fees, refunds or claw-backs, totals, deposits, and timestamps. No invoice, Business, PDF, or response header/body was accessed; GET is not presumed safe.
General CSV boundary
Fixed source derives weekly or monthly periods from the selected payment method and calls a payment-report download path with gateway, period start, and period end. It handles the response as a Blob and proposes a CSV filename. Plugin-controlled formatting means the source does not establish a fixed output schema.
No method, period, CSV, financial value, file, or download was selected or produced. Source construction does not prove deployed data, authorization, completeness, or successful export.
External integration boundary
The source also contains an optional external-report branch: plugin detection and a selected Business external identifier can lead to provider POST calls that import and list reports, with an external detail/print surface. This branch can cause outbound synchronization and is excluded from runtime documentation under this lease. No provider destination, token, Business, import, list, print, or callback was exercised.
Maintenance boundary
Revalidate route/sidebar role gates, invoice/method reads, billing-period calculations, PDF and CSV request parameters, Blob/file handling, plugin detection, and external synchronization whenever pins or controls drift. Positive behavior requires synthetic financial fixtures, intercepted exports/provider egress, immutable serving receipts, and independent admission.
Related guides: Invoice manager · Reports overview