The business problem
Finance receives payments through multiple modes and references. Without a verification step, revenue numbers disagree between sales and finance; allocations to the wrong service are hard to trace.
Commercial | Payments
Record payments, verify receipts, allocate to invoices and services, and report collections, with immutable rows and reference-linked audit trails.
Finance receives payments through multiple modes and references. Without a verification step, revenue numbers disagree between sales and finance; allocations to the wrong service are hard to trace.
Payments capture amount, mode, and reference fields, then move through verification before allocation. Original payment rows are not deleted, corrections use refund records. Sales contributions split revenue across agents.
Key workflows
Draft and issue invoices with PDF documents linked to the customer.
Capture payment with mode, reference/UTR, and amount, status pending verification.
Finance confirms receipt; verified payments become available for allocation.
Apply payment to invoice lines and subscriptions; balances update accordingly.
Revenue and collections reports aggregate verified amounts with contributor splits.
Each payment links to customer, optional subscription, and sales contributors. Pending verification queues keep unconfirmed receipts visible.
Connected in the platform
Role & use case
Payroll/finance roles verify and allocate payments. Sales managers view revenue reports within team scope. Sensitive actions require explicit permissions.
Payment rows are immutable after processing. Corrections use refund or reversal records to preserve audit history.
Payment capture includes configurable reference fields suitable for UTR, transaction ID, or internal reference numbers via lookup configuration.
Sales contributions on opportunities and subscriptions split verified payment amounts across unlimited agent roles such as primary and assist.
Walk through these workflows with our team, tailored to your modules and roles.