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
- Invoices and lines
Invoices and lines
Connect invoice detail, service periods and revenue schedules.
OverviewDraft Invoices Pending Send×
Revenue Recognition · Invoices and lines
New
Draft Invoices Pending Send
Approval conditions
| Invoice number | Customer | Invoice owner | Billing run | Invoice date | Due date | |
|---|---|---|---|---|---|---|
| INV-10644 | CUS-125 | BR-66958 | 13 Oct | 19 Oct | ||
| INV-71626 | CUS-189 | BR-75959 | 02 Oct | 08 Oct | ||
| INV-15812 | CUS-154 | BR-88247 | 10 Oct | 18 Oct | ||
| INV-32179 | CUS-073 | BR-82492 | 13 Oct | 19 Oct | ||
| INV-32231 | CUS-208 | BR-47212 | 04 Oct | 11 Oct |
6 of 6 records
TTL-784Invoices · INV-10644
DraftCustomerCUS-125
Billing runBR-66958
Invoice date13 Oct
Due date19 Oct
What you can do
Invoices and lines in practice
An invoice names its customer, issue date, due date, billing run and owning organization. Its lines carry a product, quantity, unit price and service period. An invoice line may reference a revenue schedule, letting Billing Operations and Revenue Accounting compare what was billed with the recognition schedule for the same work. Invoice status gives Collections a separate view of what has been sent and paid.
How the work is organized
- Prepare. Billing Operations Manager assigns the customer, dates, organization and billing run on the invoice.
- Price. Each line carries a product, quantity, unit price and service period for review.
- Compare. Revenue Accountant follows the optional schedule reference on a line when billed and recognition periods need checking.
Take an invoice for a subscription that begins midmonth. Check each line’s service start and end against the linked schedule and the product’s recognition method. Inspect quantity and unit price beside the calculated line total, then compare the invoice subtotal, tax and total. The billing run groups the invoice with others for its period; the line-level schedule reference makes an unusual date range easier to explain.
What to agree during setup
Agree invoice numbering, product ownership, payment terms and the rule for including an invoice in a run. Determine who corrects a line when its product or service period is wrong. Review tax and currency treatment with the owning finance systems. The invoice notes can carry operational context, while evidence documents retain source files needed for review.
For the first billing period, choose an invoice whose service dates cross a month boundary. Check the product and schedule reference on each line before assigning the invoice to a run. Decide who corrects a line if the service period differs from the customer agreement.
Check the handoff on an actual case
Billing Operations Manager selects a Draft invoice and follows its lines. Revenue Accountant checks the linked schedule on a line with a period that crosses a month boundary. Collections Specialist later follows the same invoice through Sent, partially paid or Overdue and inspects amount paid and balance due. Keep the invoice decision separate from the schedule’s recognition balance.
Ask Collections Specialist to open the same invoice from Open Invoices after its status is Sent. The specialist should find the customer, due date, amount paid and balance due, then compare any related payment with the invoice before starting follow-up.
What your team sees
- Draft Invoices Pending Send — Check customer, dates and lines before recording a Sent state.
- Open Invoices — Follow Sent, partially paid and Overdue balances by customer.
- Overdue Invoices — Prioritize due dates and remaining balances for collection.
Follow the work through
Use invoice to payment follow-up to trace the receivable after billing. Review the data model when mapping source identifiers and roles when assigning the people who may act.
What it keeps track of
Data model- Invoices
- Customer invoices with issue and due dates, subtotal, tax, total and status.
- Invoice lines
- Invoice detail lines with product, quantity, unit price and revenue schedule link.
- Customers
- Customer master with numbers, payment terms and billing status.
- Products
- Billable products and services with unit, list price and revenue type.
- Revenue schedules
- Revenue recognition schedules with method, recognized to date and deferred balance.
- Billing runs
- Billing cycle headers with period, invoice counts, total and validation status.
Who uses it
Permissions- Billing Operations Manager
- Prepares invoices and corrects their lines.
- Revenue Accountant
- Checks the linked revenue schedule.
- Collections Specialist
- Follows the invoice balance after billing; Admin maintains customer and product reference records.
Set up Revenue Recognition your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.