These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Revenue Recognition
- Features
- Payments and collections
Payments and collections
Follow customer receipts and the invoices they address.
OverviewFailed Payments×
Revenue Recognition · Payments and collections
New
Failed Payments
Payments
| Payment number | Customer | Invoice | Received date | Amount | Payment method | |
|---|---|---|---|---|---|---|
| PYM-44931 | CUS-160 | INV-24326 | 12 Oct | 90 | ACH | |
| PYM-78862 | CUS-198 | INV-67719 | 12 Oct | 370 | Wire | |
| PYM-78980 | CUS-094 | INV-82660 | 11 Oct | 520 | Credit Card | |
| PYM-34189 | CUS-227 | INV-63364 | 09 Oct | 920 | Check | |
| PYM-97234 | CUS-146 | INV-91456 | 08 Oct | 290 | Lockbox |
6 of 6 records
BR-411Payments · PYM-44931
ACHCustomerCUS-160
InvoiceINV-24326
Received date12 Oct
Amount90
Payment statusFailed
What you can do
Payments and collections in practice
Collections Specialist records a received date, amount, payment method and customer. A payment may point to an invoice, so the team can see which receivable it addresses. The bank reference and notes identify the receipt for investigation. Payment status distinguishes a scheduled receipt from one received, applied, reconciled or failed.
How the work is organized
- Receive. Collections Specialist records the customer, amount, date, method and bank reference on a payment.
- Apply. The payment can point to an invoice, whose amount paid and balance due show the current receivable.
- Investigate. Failed payments stay visible for follow-up; a scheduled payment is not a received one.
For a customer with a partially paid invoice, compare the payment amount and bank reference with the invoice’s amount paid and balance due. Confirm that the customer on the payment matches the invoice customer before the application is treated as settled work. A failed payment belongs in its own list with a clear next action; it should not be read as cash collected.
What to agree during setup
Agree who records bank references, who changes payment status, and how the team reconciles receipts with the bank or payment provider. Decide how disputed or duplicate receipts are investigated and which source reference remains visible. The app’s payment and invoice records support operational follow-up; external cash confirmation has its own owner.
For the pilot, include a partial payment and a failed payment for different invoices. Decide who checks bank confirmation, who updates the payment status and how the bank reference is retained. Reconcile the invoice amount paid and balance due after each recorded application.
Check the handoff on an actual case
Collections Specialist opens the Open Invoices list, checks an overdue invoice and then follows its related payment. Billing Operations Manager examines any invoice balance affected by that payment. For a failed receipt, inspect the method, bank reference and status before contacting the customer. The team can use payment notes to preserve the reason for its next action.
Have another Collections Specialist find the failed receipt through Failed Payments and follow its invoice reference. That person should distinguish the failed amount from the amount already paid and record the next customer follow-up in payment notes.
What your team sees
- Failed Payments — Investigate the method, bank reference and linked invoice for each failure.
- Open Invoices — Compare recorded payments with amount paid and balance due.
- Overdue Invoices — Find customers with past-due balances that still need follow-up.
Follow the work through
Use invoice to payment follow-up to trace a balance through collection. Review the data model when mapping source identifiers and roles when assigning the people who may act.
What it keeps track of
Data model- Payments
- Customer payments with receipt date, amount, method, status and invoice application.
- Invoices
- Customer invoices with issue and due dates, subtotal, tax, total and status.
- Customers
- Customer master with numbers, payment terms and billing status.
- People
- People who own revenue recognition work: contract owners, recognition reviewers and billing operations staff. Each person links to their organization, role title and department.
Who uses it
Permissions- Collections Specialist
- Records receipts and investigates failed payments.
- Billing Operations Manager
- Checks invoice balances affected by a payment.
- Admin
- Maintains customer access and reference records.
Set up Revenue Recognition your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.