Once the customer accepts the quote, operations and finance join the work: operations plans the delivery, finance follows the payment plan and the invoice. If the current quote version, who approved the discount or the payment terms reach the next team incomplete, the work stalls before it gets to the invoice.

1. The quote: the first financial record

The invoice amount comes from the approved quote, so decisions made at the quote stage need to stay traceable. In XON CRM, quotes are built from products, services, prices and descriptions in a standard structure, using templates. For every quote sent to the customer for approval, the version, the date it was shared and the customer's response are kept on the same record; when a quote goes through several revisions, that record shows which version is current.

When the amount changes, the reason belongs on the record too. In XON CRM, changes such as discounts, scope reductions or added services are recorded with their reason as well as the new amount. Six months later, when someone prepares a new quote for the same customer or questions an invoice amount, that note is where they look. The same record shows which quotes were opened, which are waiting for a reply and which line items drew objections; those line items show where negotiation concentrates.

2. From opportunity to sale: what moves at handover

XON CRM tracks opportunities through their stages, from the first discovery call and needs analysis to quote preparation, waiting for approval and closing. Each opportunity has an owner, an estimated value and an expected close date, and the record shows who holds the next step. This makes it possible to see where a quote is waiting even before a sales record exists.

When the opportunity turns into a sale, the quote, the customer, the product or service scope and the commercial terms stay on the same record. The sales record adds the contract status, approval notes and details such as the delivery or implementation start date. Operations takes the work over from that record and does not need to ask sales which version the customer accepted. For a clean handover, check the accepted quote version, the approval note and the invoice information when the sales record is opened. If that information is missing at the time of sale, someone has to go back to the customer during invoicing.

3. The sales record: payment plan, invoice information and collections

The sales record is where finance and operations look at the same piece of work. In XON CRM, the payment plan, collection status, invoice information and pending actions are linked to the sales record, and each sale is tracked with its financial status and responsible team. Whatever software the invoice is issued in, once the invoice information is entered on the sales record, the link between quote, sale and invoice holds.

Income and expense management continues from there. Collections, payments, cash and bank movements sit in one place, planned collections are tracked alongside actual payments, and each income item can be linked to its sale. A reminder can be added to the sales record to follow up on a collection, so whoever chases a late payment sees the sale's quote terms on the same record.

Terms can change after the sales record opens. Cancellation and delay reasons, additional requests and scope changes are also kept on the sales record. The team should decide in advance whether an additional request goes into the existing sale as a scope change or into a separate sale; when the two methods are mixed, the same kind of work ends up in two places in the reports.

4. Permissions and approval structure

Steps that change the amount need their own controls: granting a discount, revising an approved quote, changing the payment plan, cancelling a sale. If it is unclear who can take these steps and whose approval they need, the process is not under control, however tidy the records are.

How permissions work in XON CRM

In XON CRM, permissions are defined by module, action and target. Separate permission sets can be created for sales, operations, finance, management and support teams, and each user sees only the modules and fields their work requires. New users are not configured one permission at a time; they are assigned from the defined role model. During XON CRM implementation, role-based access, visibility and process controls are set up in a dedicated stage, so the permission structure is not left until after go-live.

Which actions to separate

Segregation of duties is one of the core principles of internal control: the person who starts a transaction should not be the person who approves it. In the work that runs from quote to invoice, the principle translates into these separations:

  • The representative who prepares the quote should not approve a discount above their own limit. The company's approval policy should state which discount levels go to which role.
  • A change to an approved quote should be prepared as a new version, not written over the existing one, and the new version should go back for approval.
  • The right to change the payment plan and due dates should sit with finance; sales should record the change request.
  • Finance should update the collection status; sales should be able to see it but not change it.
  • Cancellations and scope changes should be recorded with their reason; the team rule should not allow a change without one.

Field visibility

Support gains nothing from seeing a customer's payment plan, and operations gains nothing from seeing the reason behind a quote discount; when those fields are closed to them, each team works with the information that belongs to its job. Field-level visibility in XON CRM makes it possible to give each team its own view of the sales record: sales sees quote versions and approval notes, operations sees delivery details, finance sees the payment plan and collection fields.

Conflict with commissions and targets

XON CRM also manages role-based targets and commission structures through the same role model. Permission design has to take this into account: a representative whose commission depends on closing the sale or hitting a sales target should not be able to approve the discount on that same sale alone. When discount approval sits with a role whose commission does not depend on that sale, both the approval and the commission calculation are easier to defend.

An example approval flow

Suppose a representative prepares a quote that needs a discount above their limit. Under the company's approval policy, the representative gets the manager's approval before sending the quote to the customer. If the manager approves, the reason for the discount and the approver's name go into the quote's change note, and the new version goes to the customer. When the customer accepts, the opportunity turns into a sale, the approval is written into the approval notes on the sales record, and operations and finance take over from that record. Months later, if someone asks about the invoice amount, the sales record shows who approved the discount and why.

5. Visibility and reporting

For a manager, the useful information is where the process gets stuck: which opportunities sit too long in the approval stage, which quotes are waiting for the customer, which sales have late collections. Reports in XON CRM bring sales, customer and finance data together, and collection discipline can be tracked as part of team evaluation.

Two questions matter most for finance: for sales where the quote amount and the invoice amount differ, is the reason on record, and how many of the due dates in the payment plans were collected on time? When quote versions, change reasons and collection status sit on the same sales record, the data needed to answer them is in one place.

Conclusion

The first step is to write down whose approval each amount-changing action needs, and to define the roles to match that policy during the permission stage of implementation. When quote versions, change reasons, approval notes and collection status sit on the same sales record, the origin of every amount on the invoice can be traced from one place.