All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

  1. Invoicing & Billing System
  2. Features
  3. Collections and reporting
Feature · Collections and reporting

Collections and reporting

Follow up on outstanding invoices with the right customer context. A customer may have one overdue invoice, one invoice that is not yet due and a payment still being confirmed. Collection work should distinguish those positions. Use the due date and current outstanding amount for the particular document rather than sending a demand based on the customer’s total historical invoice value.

OverviewPending Reminders
Invoicing & Billing System · Collections and reporting

Pending Reminders

Reminders

New
InvoiceReminder typeScheduled atChannelStatus
INV-2026-0417, monthly supportDue soon19 OctEmailScheduled
INV-2026-0414, event signageOverdue day 728 OctEmailScheduled
INV-2026-0415, website updatesOverdue day 1418 OctEmailScheduled
INV-2026-0413, October retainerOverdue day 3031 OctEmailScheduled
INV-2026-0413, October retainerManual03 NovEmailScheduled
6 of 6 records
INV-2026-0417, monthly supportReminders · RMN-79106
Due soon
Scheduled at19 Oct
ChannelEmail
StatusScheduled
Example screen with sample data

What you can do

Keep the business context together

The reminder queue shows the planned message, customer invoice and scheduled date. Use the current amount due and actual due date when selecting follow-up. Income, aging and payment-method reports distinguish invoiced amounts, collected amounts and unsettled payment activity so the team can explain a balance.

A reminder prepared yesterday can become inappropriate when a payment arrives this morning. Recheck the invoice immediately before delivery, skip a fully settled or voided document and preserve that decision in the reminder history. The team can then see why a planned message did not go out without reopening a paid invoice.

Give each decision a clear owner

Bookkeeper reviews and can skip or send an appropriate reminder. Owner / Admin controls message settings and retained reporting exports. Tax workpapers are reviewed separately using verified source data; their existence does not authorize a filing or establish a tax result.

Partial payments call for a clear remaining amount. The reminder should refer to the unpaid portion of the invoice and retain its invoice number, rather than repeating the original total as if nothing had been received. The payment records explain the difference if the customer asks how the balance was calculated.

Handle exceptions with the original record

Recheck invoice status immediately before sending. Paid or voided documents must not receive a stale demand for payment. A failed mail delivery stays available for retry without duplicating the business action. Sales-tax reporting supports the customer’s reviewed filing process and does not infer nexus or certification.

Income, invoice aging and payment-method summaries answer different questions. Invoice aging explains the open customer position; collected-payment reporting follows verified receipts. Processor fees and deposits explain bank differences. Keeping those bases distinct prevents a sent invoice from being counted as cash collected or a fee deduction from being shown as customer nonpayment.

Find the work that needs attention

Sales-tax workpapers use the configured tax treatment and retained invoice amounts for the selected period. Separate any contractor information-return workpaper from this collection data: incoming client payments do not establish outgoing reportable contractor payments. An independently checked accounting source and the applicable filing rules determine those workpaper amounts.

Configure it around your business

Configure reminder timing, channels, message wording and who can skip or send a message. Review an overdue invoice, a partial receipt and an invoice paid just before its reminder date. The collection queue should direct the next useful conversation and retain the result without multiplying messages when a delivery attempt is retried.

What your team sees

  • Pending Reminders — Review the work and supporting records for this module.

What it keeps track of

Data model
Reminders
Scheduled and sent late-payment reminders against an Invoice. The late-payment-reminder workflow seeds the four standard rows on Invoices.Status = Sent (Day 1 before due, Day 7 / 14 / 30 after due) and sends each at its scheduled time unless the Invoice is already Paid or Voided.
Invoices
The bill the Client owes. Draft becomes Sent after validation and sealing; the first permitted view may mark an unpaid Sent document Viewed. Recognized receipts derive partial paid or Paid from the issued balance. An unpaid Sent, Viewed or partial paid invoice becomes Overdue only after its due date. Paid never becomes Overdue merely as time passes. An evidenced refund or reversal can reopen a positive balance into partial paid or Overdue. An authorized void produces terminal Voided; viewing, reminders or delayed callbacks cannot undo it. Generated by direct user create, by estimate-converts-to-invoice, or by recurring-invoice-generation on the RecurringSchedules cadence. The rendered invoice PDF and the line-snapshot are frozen on Send. Line snapshot is a sealed JSON snapshot frozen at Status: Sent — never edited; for the live editable line set see invoice lines.
Payments
Records of money received against an Invoice. Webhook-fed for Stripe / Square; manually entered for Check, Cash, and Other. Carries the processor reference and the processor fee so the net deposit reconciles to the bank.
Tax forms 1099sent
Year-end 1099-MISC forms issued by the user (the small business) to Clients (typically contractor / vendor clients) the user paid above the IRS reporting threshold during the calendar year. The year-end-1099-misc-generation workflow runs in late January, identifies eligible Clients (Issue1099 = true AND YTDPaidAmount > Threshold for the closed tax year), generates one row per Client per tax year, and queues e-file via the IRS filing partner. Note: this is the user issuing 1099-MISC outbound to their own contractors — the reverse direction of a 1099-NEC the user receives from clients of theirs.
Clients
The customer record — kept light. Email is the natural key for dedupe. Carries a default payment term that overrides the business default at invoice creation time.

Who uses it

Permissions
Owner / Admin
Owner / Admin works within the record, field and action scope below.
Bookkeeper
Bookkeeper works within the record, field and action scope below.
Viewer
Viewer works within the record, field and action scope below.

Set up Invoicing & Billing System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appInvoicing & Billing System

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.