Five recognition rules native.
T&M as hours log. Fixed Fee on milestones. Retainer monthly. License per ARR. Managed services per hours-bank period. Engagement type determines the rule, automatically.
Revenue recognition and close, built for the engagement mix.
| Number | Client | Total | Outstanding | Status | QBO | Age |
|---|---|---|---|---|---|---|
| INV-2026-0050 | Harbor Logistics | $7,400 | $7,400 | ● Sent | ● Pending | 1d |
| INV-2026-0048 | Riverbend Health | $42,300 | $42,300 | ● Sent | ● Synced | 8d |
| INV-2026-0049 | Birchwood Auto | $25,700 | $0 | ● Paid | ● Synced | 15d |
| INV-2026-0042 | Riverbend Health | $42,000 | $0 | ● Paid | ● Synced | 16d |
| INV-2026-0044 | Harbor Logistics | $11,000 | $0 | ● Paid | ● Synced | 21d |
Generic accounting tools assume one revenue stream and one recognition rule. Partner services firms run five engagement types and five recognition rules in parallel. Services revenue recognizes by milestone or as hours burn. Commission revenue recognizes on receipt. Retainers go monthly. License revenue recognizes on its own rules. Managed services recognize per hours-bank period with rollover and overage. PartnerView handles each correctly, runs month-end as a repeatable workflow rather than a multi-week project, and pushes clean entries to QuickBooks Online with full Chart of Accounts mapping.
QuickBooks does not know your commission revenue recognizes on receipt while your services revenue recognizes by milestone. The bookkeeper learns the rules manually, every month.
Five recognition rules applied by hand across dozens of engagements makes month-end a multi-week project. Investors and lenders see numbers a quarter behind reality.
Fixed-fee, T&M, retainer, and milestone each need a different invoice cadence and structure. Generic invoicing tools force you to pick a default and override it every time.
| Generic accounting software | PartnerView | |
|---|---|---|
| Revenue streams | Cannot tell commission revenue from milestone revenue from retainer. | Five recognition rules, one per engagement type, applied automatically. |
| Month-end | Weeks of manual rule application. | A month-end close workflow: reconcile, confirm, lock. |
| Invoicing | One invoice cadence, overridden by hand every time. | Payment schedules configured per deal, per engagement type. |
| Vendor-billed lines | Treated as services revenue against the client, requires manual rewiring. | Per-line payer dropdown, vendor-routed invoices, three revenue reports built in. |
| Engagement awareness | The engagement model lives in the bookkeeper's head. | The engagement type drives recognition without anyone re-deciding. |
| QuickBooks | A separate system the project data never reaches. | A live QuickBooks Online connection that pushes customers, invoices, and rev-rec journal entries, and reads payments back. |
T&M as hours log. Fixed Fee on milestones. Retainer monthly. License per ARR. Managed services per hours-bank period. Engagement type determines the rule, automatically.
Payment schedules configured per deal. T&M, fixed-fee, retainer, and milestone each invoice on their own structure.
Reconcile invoices against payments, confirm revenue recognized, lock the period. Repeatable, not improvised.
Live QBO connection via OAuth at /admin/integrations/qbo. Customers, service items, practice classes, and approved invoices push to QBO through a submit, approve, push gate with idempotency keys, automatic retry with back-off, and a failed-3x review queue. Payments sync back webhook-primary with a 15-minute polling backstop; unmatched payments queue for manual reconciliation. Monthly rev-rec journal entries post one per recognition event, balanced by construction (the system refuses to create an unbalanced journal), with reversing entries on schedule changes.
Ten canonical revenue flows documented end to end at /help/revenue-flows: direct, subcontracted, partner-led, co-sell, commission-only, license resale, retainer, internal, and time-to-payroll. Each flow carries a mermaid diagram, a step-by-step walkthrough naming the real route, table, and QBO entity at each stage, a worked dollar example, and a P&L impact summary. An interactive decision tree routes any scenario to the exact flow.
Invoices that match how the engagement is actually structured.
When the vendor pays for the license and the client pays for the services, the invoices flow correctly without operator gymnastics. This is the capability that makes the "vendor pays the commission, client pays for services" reality clean instead of clerical.
Five engagement types, five recognition rules, one close.
Month-end as a repeatable workflow.
End-to-end QuickBooks Online integration, in production.
Bring an active engagement. We will model it in PartnerView live.
Get a demo→