Sales Documents

Explore the Must-See Sage Active Public API V1 Quoting Example!

Dive into the invaluable resource of our front-end app example!
This example showcases the practical use of Sage Active Public API for efficient quote management.

It’s a perfect demonstration of how you can leverage the API’s capabilities in real-world scenarios, significantly simplifying the quoting process.

Now, this application also allows you to import a complete set of demo data into the current company if it does not yet have any data.

Click here to access the example : Sample quotes

img

This section outlines various types of sales documents that are essential to the sales process.
These include:

Each type of document holds specific information and serves unique purposes.

Shared Characteristics and Unique Fields in Sales Documents

While Quotes, Orders, Delivery Notes, and Invoices are distinct types of sales documents, they share a significant amount of common structure.
The majority of fields and attributes are identical across these documents, promoting a consistent user experience and facilitating document management.

  • Common Fields: All four types of documents include basic information such as customer details, product listings, quantities, and pricing.
  • Unique Fields: However, each document type also has specific fields and attributes that are unique to its role in the sales process.
    For example, a Delivery Note may have fields related to shipment tracking, while an Invoice includes fields for payment terms and due dates.

This architecture simplifies the sales workflow, while also providing the necessary granularity where required, for each stage of the sales process.

Resources

Sales quotes

Both known as Sales quotes in the API context and in the product interface.
This resource serves as the blueprint for creating, modifying, and tracking sales quotes within the sales pipeline.
It leverages standard and customized data fields to accurately represent quotes for customers, which are crucial for managing and closing sales opportunities.

Note that it is possible to enter quotes for leads by providing the lead’s identification information within the context of the quote.
This avoids the need to always create a customer in advance.
However, this possibility is limited to the quote; as soon as a quote is won and generates an order, a customer becomes mandatory.

img

Sales orders

Both known as Sales orders in the API context and in the product interface.
This resource serves as the comprehensive record for managing customer orders within the order-to-cash process.
Utilizing the standardized and custom data fields, it captures detailed information such as customer codes, discounts, and product lines, which are essential for fulfilling customer orders.

img

Sales delivery notes

Both known as Sales delivery notes in the API context and in the product interface.
This resource is the backbone for organizing and managing the shipping and handling details associated with sales orders.
With the flexibility to incorporate both standard and customized fields, Sales Delivery Notes offer granular visibility into the logistical aspects of the order-to-cash process.
This is critical for ensuring timely and accurate deliveries to customers.

img

Sales invoices

Both known as Sales Invoices in the API context and in the product interface.
This resource is pivotal for invoicing customers after order fulfillment and serves as a legally binding request for payment.
The Sales Invoices entity leverages both standard and custom fields, allowing businesses to create detailed invoices that include necessary information like customer codes, discounts, product lines, and tax details.
This ensures compliance and contributes to a smoother accounts receivable process.

img

Workflow

  1. Quote Generation: Initial offer made to a potential customer.
  2. Order Confirmation: Formalization of terms agreed upon in the quote.
  3. Delivery Note: Confirmation of goods shipped or services rendered.
  4. Invoice: Finalization of the sales process with a request for payment.