Skip to content
NG One
Role solution

From opportunity to collected invoice in one record

A sales director answers for a number that is created in four different places and assembled only at month end. The pipeline lives in a spreadsheet and in people's heads, the quote sits in someone's folder, the order is in the ERP, and whether the deal was ever collected is known by finance — so the forecast is a sum of estimates, and margin is learned when there is nothing left to change about it. NG One removes that separation simply: opportunity, quote, order, shipment, invoice and collection are states of the same record, not six ledgers someone reconciles afterwards. That is why an approved discount is visible on the document it was granted on rather than in an analysis after the quarter; why a credit limit stops an order rather than a report; and why margin per customer is the same figure finance sees in the ledger — because it comes out of it.

  • Pipeline as a record
  • Quote → order → invoice
  • Credit limit on the document
  • Discount control
  • Margin per customer
  • Collection risk

Why the sales number arrives too late

None of this is laziness on the sales floor. All of it follows from sales and its consequences living in different systems.

  • The pipeline lives in a spreadsheet and in a salesperson's head

    The stage of a deal moves in a meeting rather than when something actually happened, so a probability percentage means something different to every person on the team. When a salesperson leaves, the history of the relationship leaves with them — what remains is a phone number and an impression. The forecast is therefore a sum of optimism that cannot be checked, and it is argued not with evidence but with experience of each individual.

  • The quote and the order are not the same document

    The quote is written in a word processor or a spreadsheet, with prices copied from a price list that may or may not be the latest. When the customer accepts, everything is entered again — so a typing error surfaces on the invoice, and a special price agreement stays in an email nobody searches. What exactly was promised is known from correspondence rather than from the system, and only while the person who ran the deal is still there.

  • What is sold cannot be delivered

    The order is confirmed against a balance that does not separate free stock from stock already promised, so two days later the warehouse reports the quantity exists only on paper. The customer does not experience that as a warehouse problem but as a broken sales promise, and next time asks for a date you do not control. The fix is usually manual — someone's order is pushed back — and the person who promised that deal does not see that it was.

  • The credit limit is a number on a card that stops nothing

    A customer who is late paying keeps ordering, because the check is done by a person who may not be in, or who is in but does not know the current exposure. Exposure is not one number either: open invoices, goods in transit, advances and the order being entered right now are rarely added up in the same place at the same moment. When it is noticed, it is noticed at quarter end — and by then it is no longer a credit decision but a collection problem.

  • Revenue per customer is known; margin is not

    The biggest customer is the one with the highest revenue, and that sentence is repeated for years without anyone testing it — because discounts, delivery costs, returns and extended terms are not on the same side of the page as revenue. Sales commission is therefore calculated on something that is not the result, and the decision about who gets a better price is made on volume. By the time margin is finally computed it is history: the quarter is over, the terms are granted, the annex is signed.

How NG One answers

Everything rests on one decision: opportunity, quote, order, invoice and collection are states of the same record. That is why the consequence of a sales decision appears on the document the decision was made on, rather than in an analysis after the quarter.

  • A pipeline that is a record, not a spreadsheet

    An opportunity carries a stage, a value, an expected date and an owner, and the kanban shows the whole funnel with movement between stages. Activities and the timeline hold the history of the relationship in the Partner 360 view — calls, meetings, quotes, orders, invoices and complaints in one place — so a person leaving does not mean the deal leaves too. Sales KPIs and the forecast are computed from those records rather than from estimates: every figure in the forecast opens the opportunities it was assembled from, so the forecast conversation stops being a conversation about personalities.

  • A quote that becomes an order without a single retype

    The quote is built from the price list and discount policy effective for that customer on that day, and acceptance turns it into a sales order with no re-entry — so a transcription error has nowhere to arise. Sales contracts and special prices live in the system rather than in email, so the question of what was promised is settled by opening a document. Recurring invoices, subscriptions and rental run through the same flow, because they too are sales invoiced on a schedule, not a separate world beside the ERP.

  • A promise stock covers at the moment of entry

    Availability is shown on the order through five stock states — physical, reserved, available, on order and in transit — so goods already promised are not promised again. The reservation is created immediately and holds the quantity until dispatch, and dispatch leaves the same sales flow, so between the promise and the delivery there is no step in which someone checks again whether the goods exist. If the quantity is not there, that is visible while the customer is still on the line — not two days later, when the only remaining move is an apology.

  • A credit limit that stops the document, not the report

    The limit and payment terms sit on the partner, and exposure is computed from everything open — invoices, orders in progress, goods shipped but not invoiced, and advances — at the moment the document is created. An overrun stops the document and requires approval instead of leaving a warning in a report; who approved, when and why stays in the trace. The same logic covers deviations from the price list: a discount above policy is a decision that requires a signature, so afterwards you know not only how large the discount was but who granted it.

  • Margin per customer, item and channel — out of the same ledger

    Customer, item, channel and salesperson are dimensions on the ledger line from the first posting, so margin per customer leaves the same ledger as the trial balance and cannot diverge from it. Discounts, returns, credit notes and landed costs enter the same calculation, so the biggest customer by revenue and the best customer by result stop being automatically the same. Every figure opens down to the invoice and the line, so a conversation about terms is a conversation about documents rather than impressions.

  • Carried by AI or automation

    Collection that starts before the due date

    Open items by due date, dunning levels and statements of open items work deterministically, out of your own documents. Above them sits collection risk per partner — derived from how that customer actually pays rather than from the agreed terms — scored before a document is approved, and detection of deviations in unusual discounts and duplicate invoices. A forecast is only as good as the history beneath it: it starts on migrated data and contractual terms and sees more precisely with every month in the system. That is true of every model, and we say it out loud rather than promise you an accuracy the data does not yet carry.

A sales director's cycle

The same flow the Atlas draws as order-to-cash, seen from the chair of the person answerable for the number before it becomes a posting.

  1. Step 1

    Opportunity

    A deal enters the system when it arises, not when it is signed — otherwise the forecast has nothing to be built from.

    • Leads and a pipeline kanban by stage
    • Activities and timeline in Partner 360
    • Lead scoring and next-best-action
    • Sales KPIs and a forecast from records
  2. Step 2

    Quote

    The price comes from the policy effective that day, and a deviation is a decision with a signature.

    • Price lists and discount policies per customer
    • Sales contracts and special prices
    • Approval of deviations from policy
    • The quote as a document, not an email attachment
  3. Step 3

    Order

    The two checks that cannot be skipped — is there stock and may this customer buy — happen while the customer is still on the line.

    • Sales order from the accepted quote
    • Availability and reservation of the quantity
    • Credit limit and exposure at that moment
    • Maker-checker over approval of deviations
  4. Step 4

    Delivery and invoice

    The invoice follows the shipment rather than being a separate entry — so what never left is never invoiced.

    • Dispatch from the sales flow with its reservation
    • Outgoing invoice with advances and settlement
    • UBL 2.1 and sending through SEF e-invoicing
    • Credit notes, returns and complaints
  5. Step 5

    Collection

    Collection is part of sales, not a job that starts once sales is finished.

    • Open customer items and ageing
    • Dunning levels, statements of open items and netting
    • Collection risk from the customer's payment behaviour
    • Statement matching and settlement of items
  6. Step 6

    Margin and decision

    The goal is not a report on the quarter but the terms you will grant the next customer.

    • Margin by customer, item, channel and salesperson
    • Discounts, returns and landed costs in one calculation
    • Drill-down to the invoice and the line
    • Terms and limits revised on the result
Modules

The spaces that carry this solution

A solution is neither a separate product nor a separate licence. It is the same system seen from one angle, and these business spaces carry most of the work this page describes.

  • Sales and customers

    From opportunity to cash, in one chain with nothing retyped.

    30 capabilities
  • Finance and compliance

    Serbian statutory accounting, dimensions and VAT — in the core, not bolted on.

    30 capabilities
All modules
FAQ

Questions about this solution

Scope, boundaries, and the rules this entry point works by.

How does the forecast stop being a sum of optimism?

By being assembled from records rather than from estimates. An opportunity carries a stage, a value, an expected date, an owner and a history of activity, so the forecast opens the opportunities it was assembled from — every figure unpacks down to the deal and to the person running it. That does not mean the forecast will be accurate: it measures what has been entered, so a company where opportunities are not entered will not get a better forecast, only a tidier list. What changes is the nature of the conversation — instead of arguing about whose optimism is realistic, you look at how long a deal has sat in the same stage and when there was last any activity.

Can a salesperson promise a quantity and a date the warehouse cannot meet?

Not if the goods are already promised — and that is the point. The order shows five stock states, so available differs from physical: what is reserved for other orders is not available, and what is on order or in transit carries its own date. The reservation is created as the order is entered and holds the quantity until dispatch, so the same goods are not promised twice. What the system cannot do is prevent a supplier delay or a stoppage on the floor — it can only show it the day it happens, while there is still a choice about whose date moves, rather than letting the day of dispatch make that choice.

How does credit control work and who may override it?

The limit and payment terms sit on the partner, and exposure is computed at the moment the document is created — from open invoices, orders in progress, goods shipped but not invoiced, and advances. An overrun does not leave a warning in a report; it stops the document and requires approval. Who may approve is set by rights and limits, and maker-checker means the person requesting an exception is not the person granting it; approval, amendment and rejection all stay in the trace with a reason. The same mechanism covers a discount above policy, because that is a credit decision too — it is simply paid for through margin instead of through delay.

How do I get margin per customer rather than only revenue?

By customer, item, channel and salesperson being dimensions on the ledger line, written from the first posting, rather than extra fields. The consequence is that margin per customer and the trial balance cannot diverge — they do not have two sources — and that discounts, returns, credit notes and landed costs enter the same calculation as revenue. This is therefore not a report that can be added later: a posting made without a dimension cannot acquire one without reposting history. The question worth asking every vendor before signing is whether the dimension is written onto the line or the report is assembled from a second source.

Is this a CRM or an ERP — and what do I lose by separating them?

It is one record, so the question of separating them is really a question of what is lost at the seam. Opportunities, kanban, activities, campaigns, segmentation, lead scoring and next-best-action run in the same system in which the order, the invoice and the open item are created. When they are separate, the seam is made by synchronisation — and that is where you lose exactly what you wanted the CRM for: the salesperson does not see the overdue balance while promising terms, margin per opportunity does not exist because cost lives in another system, and collection is someone else's job because it is not visible on the customer card. Integration with an external CRM is possible and supported, but it is a compromise rather than the goal — and it is fair to say so up front.

What does early enrolment bring for sales specifically?

The discount is the easy part: 40% off the solution price for enrolments by 1 September 2026, against a 10% reservation advance. For a sales director the influence over configuration is worth more. A handful of decisions are made once and then govern how sales works for years: the structure of price lists and discount policies, the dimensions you will measure margin along, approval thresholds for deviations, credit limits and dunning levels. Early enrolment means those decisions run through your customers and your terms while the scope is still being established — the analysis of your processes is the first step of the programme, not the last. Later, the same thing is a request added to a list, with a price list already running under someone else's template.

Test NG One against your own funnel

Book a working review for sales. We walk your flow from opportunity to collection — price lists and discount policies, how deviations are approved, credit limits, and the dimensions you want to measure margin along — on your customers, in the system.