Prepare commercial records
Keep agreed amounts connected to the customer and order.
- Quotes
- Proforma invoices
- Invoices

Connect invoices and payment records to customers and orders. Give your team a clear view of balances, due dates and the follow-up each account needs.
An invoice may be raised in one place while a payment is recorded elsewhere. A connected view helps the team understand the balance, link the activity to the customer and decide what needs attention.
Keep agreed amounts connected to the customer and order.
Record payments without losing the remaining balance.
Make time-sensitive work easier to see.
Explore this interactive concept using illustrative records. The real system would be designed around your requirements.
| Invoice | Customer | Amount | Status |
|---|---|---|---|
| INV-0142 | Account A | LKR 1,200 | Paid |
| INV-0143 | Account B | LKR 480 | Partial |
| INV-0144 | Account C | LKR 920 | Overdue |
| INV-0145 | Account D | LKR 360 | Due soon |
Invoice LKR 800 − recorded LKR 320 = remaining LKR 480
Illustrative records only. Payment processing would be handled by a suitable external service, not ITSoft.
Illustrative interface — sample data, not a live client system.
An example journey. Rules, ownership and exceptions are agreed around your operation.
See invoiced, recorded and remaining amounts together.
Link invoices and payments to the relevant customer and order.
Distinguish overdue records from those due soon.
Review payment status using the definitions your team agrees.
ITSoft builds the management software; it does not itself process payments. Suitable external payment services may be integrated where required.
Review invoice numbering, payment states and required fields with your team.
Define how payments are matched and partial amounts or corrections are recorded.
Test balances, due dates, permissions and integrations against agreed examples.
Scope, user needs, integrations, migration and testing shape the proposal. Cost and delivery milestones are agreed after that review.
These are starting points, not limits on the businesses we work with.
Invoices and follow-ups linked to client work.
Payment status visible to sales and fulfilment.
A shared view of outstanding and recorded activity.
Practical questions about payments & invoicing systems.
No. The software can manage invoice and payment records, and may connect to suitable external payment services. Processing and settlement are handled by the chosen provider.
Partial payments can be linked to an invoice so the remaining balance is visible. We agree how allocations, corrections and overpayments should be handled.
Due-date rules can create reminders or follow-up tasks. Timing, wording, approval and contact preferences should be defined before enabling automated messages.
Not automatically. An operational invoice view may complement an accounting platform. Accounting, tax and statutory requirements need a separate review before deciding the scope.
We agree the source of truth, allocation rules and reconciliation process, then test sample invoices and payments with your team before migration or launch.
Tell us how your business works today and what you’re trying to improve.