Merge pull request #1109 from anandpdoshi/remove-docs-from-repo
[docs] removed from repository
This commit is contained in:
Anand Doshi
commit
80b59c8050
@ -1,24 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Calculate Incentive for Sales Team"
|
||||
}
|
||||
---
|
||||
Can be used in any Sales Transaction with **Sales Team** Table:
|
||||
|
||||
|
||||
cur_frm.cscript.custom_validate = function(doc) {
|
||||
// calculate incentives for each person on the deal
|
||||
total_incentive = 0
|
||||
$.each(wn.model.get("Sales Team", {parent:doc.name}), function(i, d) {
|
||||
|
||||
// calculate incentive
|
||||
var incentive_percent = 2;
|
||||
if(doc.grand_total > 400) incentive_percent = 4;
|
||||
|
||||
// actual incentive
|
||||
d.incentives = flt(doc.grand_total) * incentive_percent / 100;
|
||||
total_incentive += flt(d.incentives)
|
||||
});
|
||||
|
||||
doc.total_incentive = total_incentive;
|
||||
}
|
||||
@ -1,20 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Custom Script: Fetch Values from Master"
|
||||
}
|
||||
---
|
||||
To pull a value of a link on selection, use the `add_fetch` method.
|
||||
|
||||
add_fetch(link_fieldname, source_fieldname, target_fieldname)
|
||||
|
||||
### Example
|
||||
|
||||
You create Custom Field **VAT ID** (`vat_id`) in **Customer** and **Sales Invoice** and want to make sure this value gets updated every time you select a Customer in a Sales Invoice.
|
||||
|
||||
Then in the Sales Invoice Custom Script, add this line:
|
||||
|
||||
cur_frm.add_fetch('customer','vat_id','vat_id')
|
||||
|
||||
|
||||
---
|
||||
See: [How to create a custom script](!docs.dev.custom_script.html)
|
||||
@ -1,35 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Generate Item Code based on Custom Logic"
|
||||
}
|
||||
---
|
||||
Add this in the Custom Script of **Item**, so that the new Item Code is generated just before the a new Item is saved.
|
||||
|
||||
cur_frm.cscript.custom_validate = function(doc) {
|
||||
// clear item_code (name is from item_code)
|
||||
doc.item_code = "";
|
||||
|
||||
// first 2 characters based on item_group
|
||||
switch(doc.item_group) {
|
||||
case "Test A":
|
||||
doc.item_code = "TA";
|
||||
break;
|
||||
case "Test B":
|
||||
doc.item_code = "TB";
|
||||
break;
|
||||
default:
|
||||
doc.item_code = "XX";
|
||||
}
|
||||
|
||||
// add next 2 characters based on brand
|
||||
switch(doc.brand) {
|
||||
case "Brand A":
|
||||
doc.item_code += "BA";
|
||||
break;
|
||||
case "Brand B":
|
||||
doc.item_code += "BB";
|
||||
break;
|
||||
default:
|
||||
doc.item_code += "BX";
|
||||
}
|
||||
}
|
||||
@ -1,13 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Make an Item read-only after Saving"
|
||||
}
|
||||
---
|
||||
Use the method `cur_frm.set_df_property` to update the field's display.
|
||||
|
||||
In this script we also use the `__islocal` property of the doc to check if the document has been saved atleast once or is never saved. If `__islocal` is `1`, then the document has never been saved.
|
||||
|
||||
cur_frm.cscript.custom_refresh = function(doc) {
|
||||
// use the __islocal value of doc, to check if the doc is saved or not
|
||||
cur_frm.set_df_property("myfield", "read_only", doc.__islocal ? 0 : 1);
|
||||
}
|
||||
@ -1,12 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Date Validation: Do not allow past dates in a date field"
|
||||
}
|
||||
---
|
||||
|
||||
cur_frm.cscript.custom_validate = function(doc) {
|
||||
if (doc.from_date < get_today()) {
|
||||
msgprint("You can not select past date in From Date");
|
||||
validated = false;
|
||||
}
|
||||
}
|
||||
@ -1,12 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Restrict Purpose of Stock Entry"
|
||||
}
|
||||
---
|
||||
|
||||
cur_frm.cscript.custom_validate = function(doc) {
|
||||
if(user=="user1@example.com" && doc.purpose!="Material Receipt") {
|
||||
msgprint("You are only allowed Material Receipt");
|
||||
validated = false;
|
||||
}
|
||||
}
|
||||
@ -1,22 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Restrict User Based on Child Record (Warehouse)"
|
||||
}
|
||||
---
|
||||
|
||||
// restrict certain warehouse to Material Manager
|
||||
cur_frm.cscript.custom_validate = function(doc) {
|
||||
if(user_roles.indexOf("Material Manager")==-1) {
|
||||
|
||||
var restricted_in_source = wn.model.get("Stock Entry Detail",
|
||||
{parent:cur_frm.doc.name, s_warehouse:"Restricted"});
|
||||
|
||||
var restricted_in_target = wn.model.get("Stock Entry Detail",
|
||||
{parent:cur_frm.doc.name, t_warehouse:"Restricted"})
|
||||
|
||||
if(restricted_in_source.length || restricted_in_target.length) {
|
||||
msgprint("Only Material Manager can make entry in Restricted Warehouse");
|
||||
validated = false;
|
||||
}
|
||||
}
|
||||
}
|
||||
@ -1,17 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Restrict Cancel Rights based on Certain Order Value"
|
||||
}
|
||||
---
|
||||
Add a handler to `custom_before_cancel` event:
|
||||
|
||||
cur_frm.cscript.custom_before_cancel = function(doc) {
|
||||
if (user_roles.indexOf("Accounts User")!=-1 && user_roles.indexOf("Accounts Manager")==-1
|
||||
&& user_roles.indexOf("System Manager")==-1) {
|
||||
if (flt(doc.grand_total) > 10000) {
|
||||
msgprint("You can not cancel this transaction, because grand total \
|
||||
is greater than 10000");
|
||||
validated = false;
|
||||
}
|
||||
}
|
||||
}
|
||||
@ -1,177 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Web Service API"
|
||||
}
|
||||
---
|
||||
All communication with the ERPNext server happens via web services using HTTP requests and passing data via JSON (Javascript Object Notation). Using web requests you can insert, update, query, run public triggers etc. The basic scheme is as follows:
|
||||
|
||||
1. All API calls are to me made to `server.py` on your public folder of your erpnext account. For hosted users, it is (yourdomain.erpnext.com).
|
||||
1. The `cmd` parameter points to the python function to be executed.
|
||||
1. Authentication is managed using cookies.
|
||||
|
||||
### Authentication
|
||||
|
||||
Authentication is done via the login method:
|
||||
|
||||
GET server.py?cmd=login&usr=[username]&password=[password]
|
||||
|
||||
The login method returns a session id `sid` cookie in the header and a status in the
|
||||
body of the request. The `sid` cookie must be sent for each subsequent request.
|
||||
|
||||
Example:
|
||||
|
||||
$ curl -I http://localhost/webnotes/erpnext/public/server.py?cmd=login\&usr=Administrator\&pwd=admin
|
||||
HTTP/1.1 200 OK
|
||||
Date: Tue, 23 Jul 2013 05:29:24 GMT
|
||||
Server: Apache/2.2.22 (Unix) DAV/2 mod_ssl/2.2.22 OpenSSL/0.9.8r
|
||||
Set-Cookie: country=None
|
||||
Set-Cookie: sid=d0ce00d49c24869984960607a2467b50ff59b0024741922db4b23818; expires=Fri, 26 Jul 2013 10:59:25
|
||||
Content-Length: 32
|
||||
Content-Type: text/html; charset: utf-8
|
||||
|
||||
{"message":"Logged In","exc":""}
|
||||
|
||||
$ curl http://localhost/webnotes/erpnext/public/server.py?cmd=webnotes.client.get\&doctype=Profile\&name=Administrator -b sid=d0ce00d49c24869984960607a2467b50ff59b0024741922db4b23818
|
||||
|
||||
{
|
||||
"message":[
|
||||
{
|
||||
"user_image":null,
|
||||
"last_name":"User",
|
||||
"last_ip":"::1",
|
||||
..
|
||||
..
|
||||
### Python Remote Client
|
||||
|
||||
You can use the `webclient.py` module as an example of how to access data using the webservice API
|
||||
|
||||
- [Code](https://github.com/webnotes/wnframework/blob/master/webnotes/utils/webclient.py)
|
||||
- [Docs](http://erpnext.org/docs.dev.framework.server.webnotes.utils.webclient.html)
|
||||
|
||||
### Passing and Receiving Documents (`doclist`)
|
||||
|
||||
To insert or update documents in ERPNext you have to pass them as a JSON Object. The structure of a Document is a list of plain objects (called `doclist`). The `doclist`
|
||||
contains the the parent document and any child documents (if they are present).
|
||||
|
||||
Example:
|
||||
|
||||
[{
|
||||
"doctype": "Parent"
|
||||
"key1": "value1"
|
||||
..
|
||||
},{
|
||||
"doctype": "Child",
|
||||
"parenttype": "Parent",
|
||||
"parentfield": "children",
|
||||
"key1", "value1",
|
||||
..
|
||||
}]
|
||||
|
||||
### webnotes.client
|
||||
|
||||
`webnotes.client` is the easiest way to interact with the ERPNext Server. It contains
|
||||
a bunch of server-side public methods that can be used by any client.
|
||||
|
||||
- [Code](https://github.com/webnotes/wnframework/blob/master/webnotes/client.py)
|
||||
- [Docs](http://erpnext.org/docs.dev.framework.server.webnotes.client.html)
|
||||
|
||||
### Example
|
||||
|
||||
Here is an example how you can use the webclient module to insert a new Sales Invoice
|
||||
in ERPNext.
|
||||
|
||||
from webclient import *
|
||||
|
||||
server = "http://myaccount.erpnext.com/server.py"
|
||||
user = "your user name"
|
||||
password = "your password"
|
||||
|
||||
login()
|
||||
|
||||
customer = get_doc("Customer", customer_name)
|
||||
|
||||
# make customer if required
|
||||
if not customer:
|
||||
response = insert([{
|
||||
"doctype":"Customer",
|
||||
"customer_name": customer_name,
|
||||
"customer_type": "Company",
|
||||
"customer_group": "Standard Group",
|
||||
"territory": "Default",
|
||||
"customer_details": "some unique info",
|
||||
"company": "Alpha"
|
||||
}])
|
||||
|
||||
# make invoice
|
||||
resonse = insert([
|
||||
# main
|
||||
{
|
||||
"naming_series": "_T-Sales Invoice-",
|
||||
"company": "_Test Company",
|
||||
"conversion_rate": 1.0,
|
||||
"currency": "INR",
|
||||
"debit_to": "_Test Customer - _TC",
|
||||
"customer": "_Test Customer",
|
||||
"customer_name": "_Test Customer",
|
||||
"doctype": "Sales Invoice",
|
||||
"due_date": "2013-01-23",
|
||||
"fiscal_year": "_Test Fiscal Year 2013",
|
||||
"grand_total": 561.8,
|
||||
"grand_total_export": 561.8,
|
||||
"net_total": 500.0,
|
||||
"plc_conversion_rate": 1.0,
|
||||
"posting_date": "2013-01-23",
|
||||
"price_list_currency": "INR",
|
||||
"selling_price_list": "_Test Price List",
|
||||
"territory": "_Test Territory"
|
||||
},
|
||||
|
||||
# items
|
||||
{
|
||||
"amount": 500.0,
|
||||
"basic_rate": 500.0,
|
||||
"description": "138-CMS Shoe",
|
||||
"doctype": "Sales Invoice Item",
|
||||
"export_amount": 500.0,
|
||||
"export_rate": 500.0,
|
||||
"income_account": "Sales - _TC",
|
||||
"cost_center": "_Test Cost Center - _TC",
|
||||
"item_name": "138-CMS Shoe",
|
||||
"parentfield": "entries",
|
||||
"qty": 1.0
|
||||
},
|
||||
|
||||
# taxes
|
||||
{
|
||||
"account_head": "_Test Account VAT - _TC",
|
||||
"charge_type": "On Net Total",
|
||||
"description": "VAT",
|
||||
"doctype": "Sales Taxes and Charges",
|
||||
"parentfield": "other_charges",
|
||||
"tax_amount": 30.0,
|
||||
},
|
||||
{
|
||||
"account_head": "_Test Account Service Tax - _TC",
|
||||
"charge_type": "On Net Total",
|
||||
"description": "Service Tax",
|
||||
"doctype": "Sales Taxes and Charges",
|
||||
"parentfield": "other_charges",
|
||||
"tax_amount": 31.8,
|
||||
},
|
||||
|
||||
# sales team
|
||||
{
|
||||
"parentfield": "sales_team",
|
||||
"doctype": "Sales Team",
|
||||
"sales_person": "_Test Sales Person 1",
|
||||
"allocated_percentage": 65.5,
|
||||
},
|
||||
{
|
||||
"parentfield": "sales_team",
|
||||
"doctype": "Sales Team",
|
||||
"sales_person": "_Test Sales Person 2",
|
||||
"allocated_percentage": 34.5,
|
||||
},
|
||||
)]
|
||||
|
||||
|
||||
@ -1,31 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Custom Script Examples",
|
||||
"_toc": [
|
||||
"docs.dev.custom_script.fetch",
|
||||
"docs.dev.custom_script.validate",
|
||||
"docs.dev.custom_script.validate1",
|
||||
"docs.dev.custom_script.validate2",
|
||||
"docs.dev.custom_script.validate3",
|
||||
"docs.dev.custom_script.read_only",
|
||||
"docs.dev.custom_script.calculate",
|
||||
"docs.dev.custom_script.item_code"
|
||||
]
|
||||
}
|
||||
---
|
||||
### How to Create a Custom Script
|
||||
|
||||
Create a Custom Script (you must have System Manager role for this):
|
||||
|
||||
1. Got to: Setup > Custom Script > New Custom Script
|
||||
1. Select the DocType in which you want to add the Custom Script
|
||||
|
||||
---
|
||||
### Notes
|
||||
|
||||
1. Server Custom Scripts are only available for the Administrator.
|
||||
1. Client Custom Scripts are in Javascript and Server Custom Scripts are in Python.
|
||||
1. For testing, make sure to go to Tools > Clear Cache and refresh after updating a Custom Script.
|
||||
|
||||
|
||||
|
||||
@ -1,46 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "How to Build ERPNext Documentation"
|
||||
}
|
||||
---
|
||||
This page explains how to build the ERPNext documentation.
|
||||
|
||||
The documentation sources are in the [`docs` folder of the erpnext repository](https://github.com/webnotes/erpnext/tree/master/docs). The source files are in markdown format and they have a custom header that is separated by `---`
|
||||
|
||||
## Documentation Header
|
||||
|
||||
The header contains the title of the page and sub pages (table of contents) in any. Example of a simple header with title is:
|
||||
|
||||
---
|
||||
{
|
||||
"_label": "How to Build ERPNext Documentation"
|
||||
}
|
||||
---
|
||||
|
||||
#### Adding Table of Contents
|
||||
|
||||
Table of contents is added by setting the `_toc` property as below:
|
||||
|
||||
---
|
||||
{
|
||||
"_label": "Developer",
|
||||
"_toc": [
|
||||
"docs.dev.install",
|
||||
"docs.dev.quickstart",
|
||||
"docs.dev.framework",
|
||||
"docs.dev.api",
|
||||
"docs.dev.modules",
|
||||
"docs.dev.translate"
|
||||
]
|
||||
}
|
||||
---
|
||||
|
||||
## Building the Output pages
|
||||
|
||||
Once the sources have been edited / updated, to build the documentation, login into your local ERPNext account.
|
||||
|
||||
1. Open __Documenation Tool__ by adding `#Form/Documentation Tool` to the address bar.
|
||||
1. Check on all the pages to be generated
|
||||
1. Click on "Make Docs"
|
||||
|
||||
All the output pages are generated in the `public/docs` folder
|
||||
@ -1,65 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "How to Install ERPNext",
|
||||
"_toc": [
|
||||
"docs.dev.install.restore_from_backup"
|
||||
]
|
||||
}
|
||||
---
|
||||
|
||||
> These are instructions that will help you to install ERPNext on your Unix like system (Linux / Ubuntu / MacOS) using the Terminal. If you are looking at easier ways to evaluate ERPNext, [see this page](docs.user.intro.try.html).
|
||||
|
||||
### ERPNext Installer (Beta)
|
||||
|
||||
1. Make sure that you have Python 2.7+
|
||||
```
|
||||
$ python -c "import platform; print platform.python_version()"
|
||||
2.7.3
|
||||
```
|
||||
or
|
||||
```
|
||||
$ which python2.7
|
||||
/usr/bin/python2.7
|
||||
```
|
||||
If your python version is less than 2.7, then follow,
|
||||
* For CentOS, you can refer to http://toomuchdata.com/2012/06/25/how-to-install-python-2-7-3-on-centos-6-2/
|
||||
* For Ubuntu, refer to http://askubuntu.com/questions/101591/how-do-i-install-python-2-7-2-on-ubuntu/101595#101595
|
||||
1. Make sure the 'passwd' command exists. Install passwd if necessary (e.g. on CentOS, run `yum install passwd`)
|
||||
1. Switch to root user using `sudo su`
|
||||
1. `wget https://raw.github.com/webnotes/erpnext/master/install_erpnext.py`
|
||||
1. `python2.7 install_erpnext.py --create_user`
|
||||
|
||||
This will create a user 'erpnext' and install erpnext in its home directory.
|
||||
To start a development server, login as erpnext with password erpnext (or `su erpnext` from your root shell)
|
||||
```
|
||||
cd /home/erpnext/erpnext
|
||||
./lib/wnf.py --serve
|
||||
```
|
||||
|
||||
> If you are installing on your server for deployment, remember to change Administrator's password!
|
||||
> You can set the erpnext username and password by passing it to the install script,
|
||||
`python2.7 install_erpnext.py --create_user --username erpnext_username --password secretpassword`
|
||||
|
||||
> If you get stuck, post your questions at [ERPNext Developer Forum](https://groups.google.com/forum/#!forum/erpnext-developer-forum)
|
||||
|
||||
> [Troubleshooting SELinux](http://www.crypt.gen.nz/selinux/disable_selinux.html)
|
||||
|
||||
--
|
||||
|
||||
> [Server Setup Tips](http://plusbryan.com/my-first-5-minutes-on-a-server-or-essential-security-for-linux-servers)
|
||||
|
||||
> [MySQL configuration file - my.cnf](https://github.com/webnotes/erpnext/wiki/MySQL-configuration-file)
|
||||
|
||||
> [Some Useful Aliases](https://github.com/webnotes/erpnext/wiki/Some-Useful-Aliases)
|
||||
|
||||
---
|
||||
### Upgrade / run latest patches
|
||||
|
||||
1. Backup your database!
|
||||
```
|
||||
./lib/wnf.py --backup
|
||||
```
|
||||
1. Pull changes
|
||||
```
|
||||
./lib/wnf.py --update origin master
|
||||
```
|
||||
@ -1,26 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Restoring From ERPNext Backup"
|
||||
}
|
||||
---
|
||||
|
||||
* Download backup files
|
||||
|
||||
cd /tmp
|
||||
wget [DATABASE BACKUP FILE URL]
|
||||
wget [FILES BACKUP FILE URL]
|
||||
|
||||
* Suppose your backup files are downloaded at /tmp
|
||||
|
||||
gunzip [DATABASE BACKUP FILE.sql.gz]
|
||||
tar xvf [FILES BACKUP.tar]
|
||||
|
||||
* Go to your ERPNext installation folder
|
||||
* When restoring from database, the 'Administrator' user password gets reset to 'admin'. To set a better password when restoring, set admin_password variable in conf.py to the desired 'Administrator' user password.
|
||||
* Restore database using:
|
||||
|
||||
lib/wnf.py --install [DATABASE NAME] /tmp/[DATABASE BACKUP FILE.sql]
|
||||
|
||||
* Copy extracted files
|
||||
|
||||
cp /tmp/[FILES BACKUP EXTRACTED FOLDER/---/public/files/*] [YOUR ERPNEXT INSTALLATION]/public/files/
|
||||
@ -1,20 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Developer",
|
||||
"_toc": [
|
||||
"docs.dev.install",
|
||||
"docs.dev.quickstart",
|
||||
"docs.dev.framework",
|
||||
"docs.dev.modules",
|
||||
"docs.dev.custom_script",
|
||||
"docs.dev.api",
|
||||
"docs.dev.translate",
|
||||
"docs.dev.docs"
|
||||
]
|
||||
}
|
||||
---
|
||||
### Is this for me?
|
||||
|
||||
To start hacking into ERPNext, you must have some understanding of how a dynamic web application works. There are hundreds of architectures and frameworks to make web development easier, but at the core there are a few elements that are important to understand.
|
||||
|
||||
ERPNext is built on `wnframework` which is primarily developed for ERPNext but can be extended to make similar database driven applications. wnframework uses Python on the server-side and has a javascript based client for entering data, managing workflow and making reports.
|
||||
@ -1,6 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Modules"
|
||||
}
|
||||
---
|
||||
The models used in both `wnframework` (**Core** module) and ERPNext are listed here. The basic element of the model is a `DocType`, which is most often also a database table. The model properties are called `DocFields`, which describe the view and the database columns.
|
||||
@ -1,64 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Managing Translations"
|
||||
}
|
||||
---
|
||||
This document shows how to translations are managed in ERPNext and how to add a new language or update translations of an existing language.
|
||||
|
||||
### Source
|
||||
|
||||
Translatable text exists in 3 main sources:
|
||||
|
||||
1. Javascript Code Files (both framework and application)
|
||||
1. Python Code Files
|
||||
1. DocTypes (names, labels and select options)
|
||||
|
||||
#### Strings in Code Files
|
||||
|
||||
Strings in code files are annotated using the `_` (underscore) method
|
||||
|
||||
1. In Python it is the `webnotes._` method. Example:
|
||||
|
||||
webnotes._("This string must be translated")
|
||||
|
||||
1. In Javascript it is the `wn._` method. Example:
|
||||
|
||||
`wn._("This string must be translated")`
|
||||
|
||||
### How Translations Are Picked up During Execution
|
||||
|
||||
When the __build__ (`lib/wnf.py -b`) process is run, along with generating the `public` folders, it will also add a `locale` folder in each folder where translations need to be applied. This `locale` folder is rebuilt every time new translations are made.
|
||||
|
||||
Based on the user preferences or request preferences, the appropriate translations are loaded at the time of request on the server side. Or if metadata (DocType) is queried, then the appropriate translations are appended when the DocType data is requested.
|
||||
|
||||
The underscore `_` method will replace the strings based on the available translations loaded at the time.
|
||||
|
||||
### Master Translations
|
||||
|
||||
Master translations are stored in the application (erpnext repository) in the `translations` folder. [Translations master folder](https://github.com/webnotes/erpnext/tree/master/translations)
|
||||
|
||||
These are built using the `webnotes.translate module` ([Docs](http://erpnext.org/docs.dev.framework.server.webnotes.translate.html) | [Code](https://github.com/webnotes/wnframework/blob/master/webnotes/translate.py)).
|
||||
|
||||
### Building Translations
|
||||
|
||||
Translations can be built using the `lib/wnf.py` utility. Do `lib/wnf.py --help` for more info.
|
||||
|
||||
> New translations are built using Google Translate API. As of the time of writing of this document, Google Translate API is not free. To build a translation of your own from Google, you will have to register with Google API and add your API key in `conf.py`
|
||||
|
||||
To add a new language just add:
|
||||
|
||||
1. Build new translation from Google: `lib/wnf.py --translate ru`
|
||||
1. Get user the ability to select this language: Go to #Form/DocType/Profile and update the options in `langauge` field.
|
||||
1. Map the language name to the abbreviation: Update `startup/__init__.py` ([Link](https://github.com/webnotes/erpnext/blob/master/startup/__init__.py))
|
||||
|
||||
### Updating Translations
|
||||
|
||||
#### Updating Sources:
|
||||
|
||||
If you find translatable strings are not properly annotated using the `_` method, you can add them in the code and rebuild the translations.
|
||||
|
||||
#### Improving Translations:
|
||||
|
||||
To improve an existing translation, just edit the master translation files in `app/translations` and rebuild using `lib/wnf.py -b`
|
||||
|
||||
> Please contribute your translations back to ERPNext by sending us a Pull Request.
|
||||
@ -1,95 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "About ERPNext"
|
||||
}
|
||||
---
|
||||
ERPNext is a web based, open source ERP for small, medium sized businesses. Includes Accounting, Inventory, CRM, Sales, Purchase, Projects, HRMS. Built on Python / MySQL. ERPNext also contains a CMS (Content Management System) to generate a website and webshop.
|
||||
|
||||
Published by [Web Notes Technlogies Pvt Ltd, Mumbai](https://erpnext.com/about).
|
||||
|
||||
- [User Guide](https://erpnext.org/docs.user.html)
|
||||
- [Getting Help](https://erpnext.org/docs.user.help.html)
|
||||
- [Developer Forum](http://groups.google.com/group/erpnext-developer-forum)
|
||||
- [User Forum](http://groups.google.com/group/erpnext-user-forum)
|
||||
- [Donate](https://erpnext.com)
|
||||
|
||||
---
|
||||
|
||||
### Download and Install
|
||||
|
||||
##### Virtual Image:
|
||||
|
||||
- [ERPNext Download](http://erpnext.com/erpnext-download)
|
||||
|
||||
##### On Linux:
|
||||
|
||||
1. Switch to root user using `sudo su`
|
||||
1. create a folder where you want to install erpnext
|
||||
1. go to the new folder
|
||||
1. `wget https://raw.github.com/webnotes/erpnext/master/install_erpnext.py`
|
||||
1. `python install_erpnext.py`
|
||||
|
||||
[See installation notes](https://github.com/webnotes/erpnext/wiki/How-to-Install-ERPNext)
|
||||
|
||||
##### Patch and update
|
||||
|
||||
To patch and update from the latest git repository the erpnext folder and run.
|
||||
You will have to set your origin in git remote
|
||||
|
||||
$ lib/wnf.py --update origin master
|
||||
|
||||
---
|
||||
|
||||
## License
|
||||
|
||||
GNU/General Public License (see LICENSE.txt)
|
||||
|
||||
The ERPNext code is licensed as GNU General Public License (v3) and the Documentation is licensed as Creative Commons (CC-BY-SA-3.0) and the copyright is owned by Web Notes Technologies Pvt Ltd (Web Notes).
|
||||
|
||||
### Copyright for Contributors
|
||||
|
||||
Unless otherwise asserted in the code files, Web Notes will own the copyright of all contributions too. That means Web Notes holds the rights to change the license in the future or offer Commercial Licenses.
|
||||
|
||||
Web Notes will only accept copyright assertions in case of a significant contribution like a whole new functionality or a major rewrite. We believe if your contribution is significant then you should have a say in what license Web Notes selects in the future and/or have a right to any revenue Web Notes gets from a Commercial License. Either ways Web Notes will have the right to decide what is a "significant" contribution.
|
||||
|
||||
Note: At the moment, Web Notes does not give Commercial License for ERPNext nor has specific plans do so in the future.
|
||||
|
||||
---
|
||||
|
||||
## Logo and Trademark
|
||||
|
||||
The brand name ERPNext and the logo are trademarks of Web Notes Technologies Pvt. Ltd.
|
||||
|
||||
### Introduction
|
||||
|
||||
Web Notes Technologies Pvt. Ltd. (Web Notes) owns and oversees the trademarks for the ERPNext name and logos. We have developed this trademark usage policy with the following goals in mind:
|
||||
|
||||
- We’d like to make it easy for anyone to use the ERPNext name or logo for community-oriented efforts that help spread and improve ERPNext.
|
||||
- We’d like to make it clear how ERPNext-related businesses and projects can (and cannot) use the ERPNext name and logo.
|
||||
- We’d like to make it hard for anyone to use the ERPNext name and logo to unfairly profit from, trick or confuse people who are looking for official ERPNext resources.
|
||||
|
||||
### Web Notes Trademark Usage Policy
|
||||
|
||||
Permission from Web Notes is required to use the ERPNext name or logo as part of any project, product, service, domain or company name.
|
||||
|
||||
We will grant permission to use the ERPNext name and logo for projects that meet the following criteria:
|
||||
|
||||
- The primary purpose of your project is to promote the spread and improvement of the ERPNext software.
|
||||
- Your project is non-commercial in nature (it can make money to cover its costs or contribute to non-profit entities, but it cannot be run as a for-profit project or business).
|
||||
Your project neither promotes nor is associated with entities that currently fail to comply with the GPL license under which ERPNext is distributed.
|
||||
- If your project meets these criteria, you will be permitted to use the ERPNext name and logo to promote your project in any way you see fit with one exception: Please do not use ERPNext as part of a domain name.
|
||||
|
||||
Use of the ERPNext name and logo is additionally allowed in the following situations:
|
||||
|
||||
All other ERPNext-related businesses or projects can use the ERPNext name and logo to refer to and explain their services, but they cannot use them as part of a product, project, service, domain, or company name and they cannot use them in any way that suggests an affiliation with or endorsement by the ERPNext or WebNotes or the ERPNext open source project. For example, a consulting company can describe its business as “123 Web Services, offering ERPNext consulting for small businesses,” but cannot call its business “The ERPNext Consulting Company.”
|
||||
|
||||
Similarly, it’s OK to use the ERPNext logo as part of a page that describes your products or services, but it is not OK to use it as part of your company or product logo or branding itself. Under no circumstances is it permitted to use ERPNext as part of a top-level domain name.
|
||||
|
||||
We do not allow the use of the trademark in advertising, including AdSense/AdWords.
|
||||
|
||||
Please note that it is not the goal of this policy to limit commercial activity around ERPNext. We encourage ERPNext-based businesses, and we would love to see hundreds of them.
|
||||
|
||||
When in doubt about your use of the ERPNext name or logo, please contact the Web Notes Technologies for clarification.
|
||||
|
||||
(inspired from Wordpress)
|
||||
|
||||
@ -1,8 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Blog"
|
||||
}
|
||||
---
|
||||
Here is the list of latest blogs from erpnext.com
|
||||
|
||||
[https://erpnext.com/blog](https://erpnext.com/blog)
|
||||
@ -1,58 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Download ERPNext",
|
||||
"_icon": "download"
|
||||
}
|
||||
---
|
||||
### Download a pre-installed Virtual Box Image
|
||||
|
||||
#### How To Install
|
||||
|
||||
> You will need Oracle's Virtual Box to use the image:
|
||||
|
||||
[https://www.virtualbox.org/](https://www.virtualbox.org/)
|
||||
|
||||
Import the .ova file into VirtualBox. Though the default settings of the appliance should be good enough for most users, you may need to change them if you face performace issues.
|
||||
|
||||
Also, you will need to change its timezone to match yours, once the Virtual Machine boots up.
|
||||
|
||||
The virtual appliance uses Elementary OS.
|
||||
|
||||
The credentials of the virtual image are:
|
||||
|
||||
- username: erpnext
|
||||
- password: erpnext
|
||||
- mysql root password: erpnext
|
||||
- erpnext database name: erpnext
|
||||
- erpnext database password: erpnext
|
||||
|
||||
Once the Virtual Machine boots, you need to start firefox, go to:
|
||||
|
||||
http://localhost:8080
|
||||
|
||||
and login using:
|
||||
|
||||
- user: Administrator
|
||||
- password: admin
|
||||
|
||||
#### Download Image
|
||||
|
||||
[https://erpnext.com/downloads/erpnext-1305.ova](https://erpnext.com/downloads/erpnext-1305.ova) (~1.6 GB, MD5 Checksum - 60fe727f3a7a689edb6b2d4bd0ff55ad)
|
||||
|
||||
Created on 15th May 2013.
|
||||
|
||||
---
|
||||
|
||||
### Get the Source
|
||||
|
||||
#### wnframework
|
||||
|
||||
The web application framework that powers ERPNext:
|
||||
|
||||
- [https://github.com/webnotes/wnframework](https://github.com/webnotes/wnframework)
|
||||
|
||||
#### erpnext
|
||||
|
||||
ERPNext modules:
|
||||
|
||||
- [https://github.com/webnotes/erpnext](https://github.com/webnotes/erpnext)
|
||||
31
docs/docs.md
31
docs/docs.md
@ -1,31 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "ERPNext",
|
||||
"_no_title": 1,
|
||||
"_toc": [
|
||||
"docs.user",
|
||||
"docs.dev",
|
||||
"docs.download",
|
||||
"docs.community",
|
||||
"docs.blog"
|
||||
],
|
||||
"_no_toc": 1
|
||||
}
|
||||
---
|
||||
<div class="text-center" style="margin: 10px 0px">
|
||||
<h1>ERPNext Docs (beta)</h1>
|
||||
<h3 class="text-muted">Open Source ERP Built for The Web.</h3>
|
||||
<p>For the main site, go to <a href="https://erpnext.com/">https://erpnext.com</a></p>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
Welcome to the ERPNext Documentation + Community Site
|
||||
|
||||
### What is ERPNext?
|
||||
|
||||
ERPNext is an Open Source integrated app (that manages Financial Accounting, Inventory, CRM) that is built grounds up for the web, using some of the latest web technologies and frameworks. ERPNext helps your organization manage Financial Accounting, Inventory, Sales, Purchase, Payroll, Customer Support, E-Commerce all in one platform. Learn more at [https://erpnext.com](https://erpnext.com)
|
||||
|
||||
### Site Contents
|
||||
|
||||
This site contains the full User and Developer Documentation for ERPNext. This is still a work-in-progress. Please feel free to contribute issues and documentation.
|
||||
51
docs/templates/docs.html
vendored
51
docs/templates/docs.html
vendored
@ -1,51 +0,0 @@
|
||||
{% extends "lib/core/doctype/documentation_tool/docs.html" %}
|
||||
|
||||
{% block navbar %}
|
||||
<div class="navbar navbar-default" style="border-bottom: 2px solid #c0392b">
|
||||
<div class="container">
|
||||
<button type="button" class="navbar-toggle"
|
||||
data-toggle="collapse" data-target=".navbar-responsive-collapse">
|
||||
<span class="icon-bar"></span>
|
||||
<span class="icon-bar"></span>
|
||||
<span class="icon-bar"></span>
|
||||
</button>
|
||||
<a class="navbar-brand" href="index.html">
|
||||
<object data="img/splash.svg" class="erpnext-logo"
|
||||
type="image/svg+xml"></object> erpnext.org</a>
|
||||
<div class="collapse navbar-collapse navbar-responsive-collapse">
|
||||
<ul class="nav navbar-nav">
|
||||
<li><a href="docs.user.html">User</a></li>
|
||||
<li><a href="docs.dev.html">Developer</a></li>
|
||||
<li><a href="docs.user.help.html">Help</a></li>
|
||||
<li><a href="docs.download.html">Download</a></li>
|
||||
<li><a href="https://erpnext.com" target="_blank">Cloud</a></li>
|
||||
</ul>
|
||||
<ul class="nav navbar-nav pull-right">
|
||||
<li><a href="docs.about.html">About</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
{% endblock %}
|
||||
|
||||
{% block footer %}
|
||||
<hr />
|
||||
<div class="footer text-muted" style="font-size: 80%;">
|
||||
<div class="content row">
|
||||
<div class="col-md-12">
|
||||
© <a href="https://erpnext.com">Web Notes</a> |
|
||||
<a href="docs.user.help.html">Help</a> |
|
||||
<a href="https://github.com/webnotes/erpnext" target="_blank">Code</a> |
|
||||
<a href="docs.attributions.html">Attributions</a> |
|
||||
<a href="https://erpnext.com">ERPNext Cloud</a> |
|
||||
<a href="https://erpnext.com/partners">Find a Partner</a> |
|
||||
<a href="https://erpnext.com/donate">Donate</a>
|
||||
<br>
|
||||
<p>
|
||||
Code License: <a href="https://www.gnu.org/licenses/gpl.html">GNU/GPL 3</a>.
|
||||
Documentation License: <a href="https://creativecommons.org/licenses/by-sa/3.0/">CC-BY-SA-3.0</a>.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
{% endblock %}
|
||||
@ -1,30 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Closing a Financial Period"
|
||||
}
|
||||
---
|
||||
At the end of every year or (quarterly or maybe even monthly), after completing auditing, you close your books of accounts. This means that you make all your special entries like:
|
||||
|
||||
- Depreciation
|
||||
- Change in value of Assets
|
||||
- Defer taxes and liabilities
|
||||
- Update bad debts
|
||||
|
||||
etc. and book your Profit or Loss.
|
||||
|
||||
By doing this, your Income and Expense Accounts become zero .You start a new Fiscal Year (or period) with a balanced Balance Sheet and fresh Profit and Loss account.
|
||||
|
||||
In ERPNext after making all the special entries via Journal Voucher, you can make all your Income and Expense accounts to zero via:
|
||||
|
||||
> Accounts > Tools > Period Closing Voucher
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
The Period Closing Voucher will make accounting entries (GL Entry) making all your Income and Expense Accounts zero and transferring the balance to the Account you define.
|
||||
@ -1,63 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Journal Vouchers"
|
||||
}
|
||||
---
|
||||
All types of accounting entries other than **Sales Invoice** and **Purchase Invoice** are made using the **Journal Voucher**. A **Journal Voucher** (also called Journal Entry) is a standard accounting transaction that affects multiple Accounts and the sum of debits is equal to the sum of credits.
|
||||
|
||||
To create a Journal Voucher go to:
|
||||
|
||||
> Accounts > Journal Voucher > New Journal Voucher
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
In a Journal Voucher, you must select.
|
||||
|
||||
- Type of Voucher from the drop down.
|
||||
- Add rows for the individual accounting entries. In each row, you must specify:
|
||||
- The Account that will be affected
|
||||
- The amount to Debit or Credit
|
||||
- The Cost Center (if it is an Income or Expense)
|
||||
- Against Voucher: Link it to a voucher or invoice if it affects the “outstanding” amount of that invoice.
|
||||
- Is Advance: Select “Yes” if you want to make it selectable in an Invoice.
|
||||
Other information in case it is a Bank Payment or a bill.
|
||||
|
||||
#### Difference
|
||||
|
||||
The “Difference” field is the difference between the Debit and Credit amounts. This should be zero if the Journal Voucher is to be “Submitted”. If this number is not zero, you can click on “Make Difference Entry” to add a new row with the amount required to make the total as zero.
|
||||
|
||||
---
|
||||
|
||||
## Common Entries
|
||||
|
||||
A look at some of the common accounting entries that can be done via Journal Voucher.
|
||||
|
||||
#### Expenses (non accruing)
|
||||
|
||||
Many times it may not be necessary to accrue an expense, but it can be directly booked against an expense Account on payment. For example a travel allowance or a telephone bill. You can directly debit Telephone Expense (instead of your telephone company) and credit your Bank on payment.
|
||||
|
||||
- Debit: Expense Account (like Telephone expense)
|
||||
- Credit: Bank or Cash Account
|
||||
|
||||
#### Bad Debts or Write Offs
|
||||
|
||||
If you are writing off an Invoice as a bad debt, you can create a Journal Voucher similar to a Payment, except instead of debiting your Bank, you can debit an Expense Account called Bad Debts.
|
||||
|
||||
- Debit: Bad Debts Written Off
|
||||
- Credit: Customer
|
||||
|
||||
> Note: There may be regulations in your country before you can write off bad debts.
|
||||
|
||||
#### Depreciation
|
||||
|
||||
Depreciation is when you write off certain value of your assets as an expense. For example if you have a computer that you will use for say 5 years, you can distribute its expense over the period and pass a Journal Voucher at the end of each year reducing its value by a certain percentage.
|
||||
|
||||
- Debit: Depreciation (Expense)
|
||||
- Credit: Asset (the Account under which you had booked the asset to be depreciated)
|
||||
|
||||
> Note: There may be regulations in your country that define by how much amount you can depreciate a class of Assets.
|
||||
@ -1,58 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Accounts",
|
||||
"_toc": [
|
||||
"docs.user.accounts.sales_invoice",
|
||||
"docs.user.accounts.purchase_invoice",
|
||||
"docs.user.accounts.payments",
|
||||
"docs.user.accounts.journal_voucher",
|
||||
"docs.user.accounts.opening_entry",
|
||||
"docs.user.accounts.closing",
|
||||
"docs.user.accounts.reports",
|
||||
"docs.user.accounts.voucher_import",
|
||||
"docs.user.accounts.pos"
|
||||
]
|
||||
}
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
At end of the sales and purchase cycle is billing and payments. You may have an accountant in your team, or you may be doing accounting yourself or you may have outsourced your accounting. Financial accounting forms the core of any business management system like an ERP.
|
||||
|
||||
In ERPNext, your accounting operations consists of 3 main transactions:
|
||||
|
||||
- Sales Invoice: The bills that you raise to your Customers for the products or services you provide.
|
||||
- Purchase Invoice: Bills that your Suppliers give you for their products or services.
|
||||
- Journal Vouchers: For accounting entries, like payments, credit and other types.
|
||||
|
||||
---
|
||||
|
||||
### Accounting Basics
|
||||
|
||||
#### Debit and Credit
|
||||
|
||||
People new to accounting are often confused with the terms Debit and Credit. Contrary to their meaning, these terms have nothing to do with who owes what.
|
||||
|
||||
Debit and Credit are conventions. All accounting follows these so that it is easy to understand the state of finances in a universal manner. These conventions are:
|
||||
|
||||
- All Accounts are of type Debit or Credit.
|
||||
- Assets and Expenses (and their sub-groups) are always Debit.
|
||||
- Liabilities and Income (and their sub-groups) are always Credit.
|
||||
- In all accounting entries, you “debit” an Account or “credit” one.
|
||||
- When you “debit” an Debit Account (an asset or expense), its value increases (“add” operation). When you “credit” a Debit Account, its value decreases (“subtract” operation). The same rule applies for Credit Accounts. “Crediting” a Credit Account, increases its value, “debiting” it decreases its value.
|
||||
- All accounting transactions (like a sales or a payment) must affect at least two different Accounts and sum of debits must be equal to sum of credits for the transaction. This is called the “double-entry bookkeeping system”.
|
||||
|
||||
Still confused? These conventions will become clearer as you make transactions.
|
||||
|
||||
#### Accrual System
|
||||
|
||||
Another important concept to understand in Accounting is accrual. This is important when your payment happens separately from delivery.
|
||||
|
||||
For example you buy X from a Supplier and your Supplier sends you a bill and expects you to pay in, for example, seven days. Even if you have not yet paid your Supplier, your expense must be booked immediately. This expense is booked against a group of Accounts called “Accounts Payable” that is the sum of all your outstanding dues to your Suppliers. This is called accrual. When you pay your Supplier, you will cancel his dues and update your bank account.
|
||||
|
||||
ERPNext works on an accrual system. The transactions that accrue income and expense are Sales Invoice and Purchase Invoice.
|
||||
|
||||
In retail, typically, delivery and payment happens at the same time. To cover this scenario, we have in ERPNext a POS Invoice (POS = Point of Sales). More on that later.
|
||||
|
||||
@ -1,10 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Opening Entry"
|
||||
}
|
||||
---
|
||||
|
||||
If you are a new company you can start using ERPNext accounting module by going to chart of accounts.
|
||||
|
||||
However, if you are migrating from a legacy accounting system like Tally or a Fox Pro based software, please visit [Opening Entry](docs.user.setup.opening.html)
|
||||
|
||||
@ -1,44 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Opening Stock"
|
||||
}
|
||||
---
|
||||
|
||||
|
||||
You can upload your opening stock in the system using Stock Reconciliation. Stock Reconciliation will update your stock for a given Item on a given date for a given Warehouse to the given quantity.
|
||||
|
||||
Stock Reconciliation will make a “difference entry” (the difference between the system stock and the actual stock in your file) for the Item.
|
||||
|
||||
Tip: Stock Reconciliation can also be used to update the “value” of an Item.
|
||||
|
||||
To make a Stock Reconciliation, go to:
|
||||
|
||||
> Stock > Stock Reconciliation > New Stock Reconciliation
|
||||
|
||||
and follow the steps mentioned on the page.
|
||||
|
||||
#### Step 1: Download Template
|
||||
|
||||
|
||||
|
||||
|
||||
#### Step 2: Enter Data in csv file.
|
||||
|
||||
|
||||
|
||||
|
||||
The csv format is case-sensitive. Thus special care should be taken to avoid spelling errors or wrong names. Even if you do not list some quantities or valuation rates, the file will still process the data.
|
||||
|
||||
#### Step 3: Upload the csv file with data
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
#### Step 4: Attach the uploaded file.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
After reviewing saved Reconciliation Data, submit the Stock Reconciliation. On successful submission, the data will be updated in the system. To check the uploaded data go to Stock and view Stock Level Report.
|
||||
@ -1,85 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Making Payments"
|
||||
}
|
||||
---
|
||||
Payments made against Sales Invoices or Purchase Invoices can be made by clicking on “Make Payment Entry” button on “Submitted” invoices.
|
||||
|
||||
1. Update the “Bank Account” (you can also set the default account in the Company master).
|
||||
1. Update posting date.
|
||||
1. Enter the cheque number, cheque date.
|
||||
1. Save and Submit.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Payments can also be made independent of invoices by creating a new Journal Voucher and selecting the type of payment.
|
||||
|
||||
#### Incoming Payment
|
||||
|
||||
For payments from Customers,
|
||||
|
||||
- Debit: Bank or Cash Account
|
||||
- Credit: Customer
|
||||
|
||||
> Note: Remember to the “Against Sales Invoice” or “Is Advance” as applicable.
|
||||
|
||||
#### Outgoing Payment
|
||||
|
||||
For payments to Suppliers,
|
||||
|
||||
- Debit: Supplier
|
||||
- Credit: Bank or Cash Account
|
||||
|
||||
> Note: Remember to the “Against Purchase Invoice” or “Is Advance” as applicable.
|
||||
|
||||
---
|
||||
|
||||
### Reconciling Cheque Payments
|
||||
|
||||
If you are receiving payments or making payments via cheques, the bank statements will not accurately match the dates of your entry, this is because the bank usually takes time to “clear” these payments. Also you may have mailed a cheque to your Supplier and it may be a few days before it is received and deposited by the Supplier. In ERPNext you can synchronize your bank statements and your Journal Vouchers using the “Bank Reconciliation” tool.
|
||||
|
||||
To use this, go to:
|
||||
|
||||
> Accounts > Bank Reconciliation
|
||||
|
||||
Select your “Bank” Account and enter the dates of your statement. Here you will get all the “Bank Voucher” type entries. In each of the entry on the right most column, update the “Clearance Date” and click on “Update”.
|
||||
|
||||
By doing this you will be able to sync your bank statements and entries into the system.
|
||||
|
||||
|
||||
---
|
||||
|
||||
## Managing Outstanding Payments
|
||||
|
||||
In most cases, apart from retail sales, billing and payments are separate activities. There are several combinations in which these payments are done. These cases apply to both sales and purchases.
|
||||
|
||||
- They can be upfront (100% in advance).
|
||||
- Post shipment. Either on delivery or within a few days of delivery.
|
||||
- Part in advance and part on or post delivery.
|
||||
- Payments can be made together for a bunch of invoices.
|
||||
- Advances can be given together for a bunch of invoices (and can be split across invoices).
|
||||
|
||||
ERPNext allows you to manage all these scenarios. All accounting entries (GL Entry) can be made against a Sales Invoice, Purchase Invoice or Journal Vouchers (in special cases, an invoice can be made via a Sales Invoice too).
|
||||
|
||||
The total outstanding amount against an invoice is the sum of all the accounting entries that are made “against” (or are linked to) that invoice. This way you can combine or split payments in Journal Vouchers to manage the scenarios.
|
||||
|
||||
### Matching Payments to Invoices
|
||||

|
||||
In complex scenarios, especially in the capital goods industry, sometimes there is no direct link between payments and invoices. You send invoices to your Customers and your Customer sends you block payments or payments based on some schedule that is not linked to your invoices.
|
||||
|
||||
In such cases, you can use the Payment to Invoice Matching Tool.
|
||||
|
||||
> Accounts > Payment Reconciliation
|
||||
|
||||
In this tool, you can select an account (your Customer’s account) and click on “Pull Payment Entries” and it will select all un-linked Journal Vouchers and Sales Invoices from that Customer.
|
||||
|
||||
To cancel off some payments and invoices, select the Invoices and Journal Vouchers and click on “Reconcile”.
|
||||
@ -1,87 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Point of Sale (POS) Invoice"
|
||||
}
|
||||
---
|
||||
Point of sale (POS) is the place where a retail transaction is completed. It is the point at which a customer makes a payment to the merchant in exchange for goods or services. For retail operations, the delivery of goods, accrual of sale and payment all happens in one event, that is usually called the “Point of Sale”.
|
||||
|
||||
You can make a Sales Invoice of type POS by checking on “Is POS”. When you check this, you will notice that some fields get hidden and some new ones emerge.
|
||||
|
||||
> Tip: In retail, you may not create a separate Customer record for each customer. You can create a general Customer called “Walk-in Customer” and make all your transactions against this Customer record.
|
||||
|
||||
#### Different sections of the POS
|
||||
|
||||
- Update Stock: If this is checked, Stock Ledger Entries will be made when you “Submit” this Sales Invoice thereby eliminating the need for a separate Delivery Note.
|
||||
- In your Items table, update inventory information like Warehouse (saved as default), Serial Number, or Batch Number if applicable.
|
||||
- Update Payment Details like your Bank / Cash Account, Paid amount etc.
|
||||
- If you are writing off certain amount. For example when you receive extra cash as a result of not having exact denomination of change, check on ‘Write off Outstanding Amount’ and set the Account.
|
||||
|
||||
|
||||
#### Enable POS View
|
||||
|
||||
- Every Sales & Purchase documents has 2 different interfaces, Invoice View and POS View. The current view used by most users is the Invoice View. This view is preferred by non-retailing companies.The POS view is used by retailing companies. For retailers it is very important to provide bill or sales invoice at the point of sale. Their customers cannot wait to receive the bill by post. The customers want an immediate bill for the payment which they make. In such cases, the POS View is preferred.
|
||||
|
||||
> Setup > Show/Hide Features
|
||||
|
||||
|
||||
|
||||
- Setup [POS Setting](docs.user.setup.pos_setting.html)
|
||||
|
||||
### Adding an Item
|
||||
|
||||
At the billing counter, the retailer needs to select Items which the consumer buys. In the POS interface you can select an Item by two methods. One, is by clicking on the Item image and the other, is through the Barcode / Serial No.
|
||||
|
||||
**Select Item** - To select a product click on the Item image and add it into the cart. A cart is an area that prepares a customer for checkout by allowing to edit product information, adjust taxes and add discounts.
|
||||
|
||||
**Barcode / Serial No** - A Barcode / Serial No is an optical machine-readable representation of data relating to the object to which it is attached. Enter Barcode / Serial No in the box as shown in the image below and pause for a second, the item will be automatically added to the cart.
|
||||
|
||||
|
||||
|
||||
> Tip: To change the quantity of an Item, enter your desired quantity in the quantity box. These are mostly used if the same Item is purchased in bulk.
|
||||
|
||||
|
||||
If your product list is very long use the Search field, type the product name in Search box.
|
||||
|
||||
### Removing an Item
|
||||
|
||||
There are two ways to remove an Item.
|
||||
|
||||
- Select an Item by clicking on the row of that Item from Item cart. Then click on “Del” button. OR
|
||||
|
||||
|
||||
- Enter 0(zero) quantity of any item to delete that item.
|
||||
|
||||
To remove multiple Items together, select multiple rows & click on “Del” button.
|
||||
|
||||
> Delete button appears only when Items are selected.
|
||||
|
||||
|
||||
|
||||
### Make Payment
|
||||
|
||||
After all the Items and their quantities are added into the cart, you are ready to make the Payment. Payment process is divided into 3 steps -
|
||||
|
||||
1. Click on “Make Payment” to get the Payment window.
|
||||
1. Select your “Mode of Payment”.
|
||||
1. Click on “Pay” button to Save the document.
|
||||
|
||||
|
||||
|
||||
Submit the document to finalise the record. After the document is submitted, you can either print or email it directly to the customer.
|
||||
|
||||
#### Accounting entries (GL Entry) for a Point of Sale:
|
||||
|
||||
Debits:
|
||||
|
||||
- Customer (grand total)
|
||||
- Bank / Cash (payment)
|
||||
|
||||
Credits:
|
||||
|
||||
- Income (net total, minus taxes for each Item)
|
||||
- Taxes (liabilities to be paid to the government)
|
||||
- Customer (payment)
|
||||
- Write Off (optional)
|
||||
|
||||
To see entries after “Submit”, click on “View Ledger”.
|
||||
|
||||
@ -1,61 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Purchase Invoice"
|
||||
}
|
||||
---
|
||||
Purchase Invoice is the exact opposite of your Sales Invoice. It is the bill that your Supplier sends you for products or services delivered. Here you accrue expenses to your Supplier. Making a Purchase Invoice is very similar to making a Purchase Order.
|
||||
|
||||
To make a new Purchase Invoice, go to:
|
||||
|
||||
> Accounts > Purchase Invoice > New Purchase Invoice
|
||||
|
||||
or click on “Make Purchase Invoice” in Purchase Order or Purchase Receipt.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
The concept of “Posting Date” is again same as Sales Invoice. “Bill No” and “Bill Date” helps to track the bill number as set by your Supplier for reference.
|
||||
|
||||
#### Accounting Impact
|
||||
|
||||
Like in Sales Invoice, you have to enter an Expense or an Asset account for each row in your Items table. This helps to indicate if the Item is an Asset or an Expense. You must also enter a Cost Center. These can also be set in the Item master.
|
||||
|
||||
The Purchase Invoice will affect your accounts as follows:
|
||||
|
||||
Accounting entries (GL Entry) for a typical double entry “purchase”:
|
||||
|
||||
Debits:
|
||||
|
||||
- Expense or Asset (net totals, excluding taxes)
|
||||
- Taxes (assets if VAT-type or expense again).
|
||||
|
||||
Credits:
|
||||
|
||||
- Supplier
|
||||
|
||||
To see entries in your Purchase Invoice after you “Submit”, click on “View Ledger”.
|
||||
|
||||
---
|
||||
|
||||
#### Is purchase an “Expense” or an “Asset”?
|
||||
|
||||
If the Item is consumed immediately on purchase, or if it is a service, then the purchase becomes an “Expense”. For example, a telephone bill or travel bill is an “Expense” - it is already consumed.
|
||||
|
||||
For inventory Items, that have a value, these purchases are not yet “Expense”, because they still have a value while they remain in your stock. They are “Assets”. If they are raw-materials (used in a process), they will become “Expense” the moment they are consumed in the process. If they are to be sold to a Customer, they become “Expense” when you ship them to the Customer.
|
||||
|
||||
---
|
||||
|
||||
#### Deducting Taxes at Source
|
||||
|
||||
In many countries, the law may require you to deduct taxes, while paying your suppliers. These taxes could be based on a standard rate. Under these type of schemes, typically if a Supplier crosses a certain threshold of payment, and if the type of product is taxable, you may have to deduct some tax (which you pay back to your government, on your Supplier’s behalf).
|
||||
|
||||
To do this, you will have to make a new Tax Account under “Tax Liabilities” or similar and credit this Account by the percent you are bound to deduct for every transaction.
|
||||
|
||||
For more help, please contact your Accountant!
|
||||
@ -1,61 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Accounting Reports"
|
||||
}
|
||||
---
|
||||
Some of the major accounting reports are:
|
||||
|
||||
### General Ledger
|
||||
|
||||
General Ledger is based on the table GL Entry and can be filtered by Account and between a period. This will help you get a full update for all entries done in that period for that Account.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Trial Balance
|
||||

|
||||
Trial Balance is the list of Account balances for all your Accounts (“Ledger” and “Group”) on a particular date. For each Account it will give you the:
|
||||
|
||||
- Opening
|
||||
- Debits
|
||||
- Credits
|
||||
- Closing
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
The sum of all closing balances in a Trial Balance must be zero.
|
||||
|
||||
### Accounts Payable and Accounts Receivable (AP / AR)
|
||||
|
||||
These reports help you to track the outstanding invoices sent to Customer and Suppliers. In this report, you will get your outstanding amounts period wise. i.e. between 0-30 days, 30-60 days and so on.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
You can also get your payables and receivables from direct reports on Sales Invoice and Purchase Invoice.
|
||||
|
||||
### Sales and Purchase Register
|
||||
|
||||
In this report, each tax Account is transposed in columns.For each Invoice and invoice Item, you will get the amount of individual tax that has been paid, based on the Taxes and Charges table.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,30 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Handling Returns"
|
||||
}
|
||||
---
|
||||
Returns are a part of doing business. Your Customers may return Items in exchange of other Items or money back or you may return Items to your Supplier. In each case there could be a variety of scenarios.
|
||||
|
||||
### Credit and Debit Notes
|
||||
|
||||
Credit Notes are given to your Customers against a return that can be redeemed as cash or adjusted in another purchase. You can create a Journal Voucher of type Credit Note as follows:
|
||||
|
||||
- Debit: Income
|
||||
- Credit: Customer
|
||||
|
||||
Similarly if you are deducting an amount from your Supplier’s bill due to rejection or similar, you can issue a Debit Note to your Supplier. You can adjust the Debit Note against another pending Purchase Invoice (in which case, remember to set the “Against Purchase Invoice” column or return the money. In the second case you will have to create a new payment entry (Journal Voucher) when you receive the money. Entry for a Debit Note would be:
|
||||
|
||||
- Debit: Supplier
|
||||
- Credit: Expense
|
||||
|
||||
> If Items are also returned, remember to make a Delivery Note or Stock Entry for the Items.
|
||||
|
||||
### Exchange
|
||||
|
||||
If there is an exchange with your Customer, you can create a new POS type Sales Invoice in which the returning item has a negative quantity and the selling item has a positive quantity. In this way your taxes will also be adjusted against the return.
|
||||
|
||||
### Sales and Purchase Return Wizard
|
||||
|
||||
This is a tool that can help you automate the entry for this process. Go to:
|
||||
|
||||
> Accounts > Tools > Sales and Purchase Return
|
||||
@ -1,68 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Sales Invoice"
|
||||
}
|
||||
---
|
||||
A Sales Invoice is a bill that you send to your Customers, against which they will process your payment.
|
||||
|
||||
If you have managed to create Sales Orders or Delivery Notes, creating a Sales Invoice follows the same process.
|
||||
|
||||
You can create a Sales Invoice directly from
|
||||
|
||||
> Accounting > Sales Invoice > New Sales Invoice
|
||||
|
||||
or from the “Make Sales Invoice” button in the Sales Order or Delivery Note.
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
|
||||
|
||||
#### Accounting Impact
|
||||
|
||||
All Sales must be booked against an “Income Account”. This refers to an Account in the “Income” section of your Chart of Accounts. It is a good practice to classify your income by type (like product income, service income etc). The Income Account must be set for each row of the Items table.
|
||||
|
||||
> Tip: To set default Income Accounts for Items, you can set it in the Item or Item Group.
|
||||
|
||||
The other account that is affected is the Account of the Customer. That is automatically set from “Debit To” in the heading section.
|
||||
|
||||
You must also mention the Cost Centers in which your Income must be booked. Remember that your Cost Centers tell you the profitability of the different lines of business or product. You can also set a default Cost Center in the Item master.
|
||||
|
||||
#### Accounting entries (GL Entry) for a typical double entry “Sale”:
|
||||
|
||||
When booking a sale (accrual):
|
||||
|
||||
**Debit:** Customer (grand total)
|
||||
**Credit:** Income (net total, minus taxes for each Item)
|
||||
**Credit:** Taxes (liabilities to be paid to the government)
|
||||
|
||||
> To see entries in your Sales Invoice after you “Submit”, click on “View Ledger”.
|
||||
|
||||
#### Dates
|
||||
|
||||
Posting Date: The date on which the Sales Invoice will affect your books of accounts i.e. your General Ledger. This will affect all your balances in that accounting period.
|
||||
|
||||
Due Date: The date on which the payment is due (if you have sold on credit). This can be automatically set from the Customer master.
|
||||
|
||||
#### Recurring Invoices
|
||||
|
||||
If you have a contract with a Customer where you bill the Customer on a monthly, quarterly, half-yearly or annual basis, you can check the “Recurring Invoice” box. Here you can fill in the details of how frequently you want to bill this Invoice and the period for which the contract is valid.
|
||||
|
||||
ERPNext will automatically create new Invoices and mail it to the email ids you set.
|
||||
|
||||
---
|
||||
|
||||
#### "Pro Forma" Invoice
|
||||
|
||||
If you want to give an Invoice to a Customer to make a payment before you deliver, i.e. you operate on a payment first basis, you should create a Quotation and title it as a “Pro-forma Invoice” (or something similar) using the Print Heading feature.
|
||||
|
||||
“Pro Forma” means for formality. Why do this? Because if you book a Sales Invoice it will show up in your “Accounts Receivable” and “Income”. This is not ideal as your Customer may or may not decide to pay up. But since your Customer wants an “Invoice”, you could give the Customer a Quotation (in ERPNext) titled as “Pro Forma Invoice”. This way everyone is happy.
|
||||
|
||||
This is a fairly common practice. We follow this at Web Notes too.
|
||||
@ -1,53 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Material Request"
|
||||
}
|
||||
---
|
||||
A Material Request is a simple document identifying a requirement of a set of Items (products or services) for a particular reason.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
To generate a Material Request manually go to:
|
||||
|
||||
> Buying > Material Request > New Material Request
|
||||
|
||||
**Step 1**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
A Material Request can be generated:
|
||||
|
||||
- By a User.
|
||||
- Automatically from a Sales Order.
|
||||
- Automatically when the Projected Quantity of an Item in stores reaches a particular level.
|
||||
- Automatically from your Bill of Materials if you use Production Plan to plan your manufacturing activities.
|
||||
|
||||
**Step 2**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
In the Material Request form,
|
||||
|
||||
- Fill in the Items you want and their quantities.
|
||||
|
||||
- If your Items are inventory items, you must also mention the Warehouse where you expect these Items to be delivered. This helps to keep track of the [Projected Quantity](docs.user.stock.projected_quantity.html)for this Item.
|
||||
|
||||
|
||||
- You can optionally add the Terms, using the Terms and Conditions master and also the reason.
|
||||
|
||||
|
||||
> Info: Material Request is not mandatory. It is ideal if you have centralized buying so that you can collect this information from various departments.
|
||||
|
||||
#### Authorization
|
||||
|
||||
If you want your Material Request to be authorized by a senior person like a Purchase Manager then you can give “Submit” rights only to that person. Everyone can create requests, but only the authorized person can “Submit”.
|
||||
@ -1,28 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Buying",
|
||||
"_toc": [
|
||||
"docs.user.buying.supplier_type",
|
||||
"docs.user.buying.supplier",
|
||||
"docs.user.buying.material_request",
|
||||
"docs.user.buying.supplier_quotation",
|
||||
"docs.user.buying.purchase_order",
|
||||
"docs.user.buying.purchase_taxes",
|
||||
"docs.user.buying.price_lists",
|
||||
"docs.user.buying.sub_contracting"
|
||||
]
|
||||
}
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
If your business involves physical goods, buying is one of your core business activity. Your suppliers are as important as your customers and they must be provided with as much accurate information as possible.
|
||||
|
||||
Buying in right amounts, in right quantities, can affect your cash flow and profitability.
|
||||
|
||||
ERPNext contains a set of transactions that will make your buying process as efficient and seamless as possible.
|
||||
@ -1,42 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Purchase Order"
|
||||
}
|
||||
---
|
||||
A Purchase Order is analogous to a Sales Order. It is usually a binding contract with your Supplier that you promise to buy a set of Items under the given conditions.
|
||||
|
||||
|
||||
A Purchase Order can be automatically created from a Material Request or Supplier Quotation.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
In ERPNext, you can also make a Purchase Order directly by going to:
|
||||
|
||||
> Buying > Purchase Order > New Purchase Order
|
||||

|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Entering a Purchase Order is very similar to a Purchase Request, additionally you will have to set:
|
||||
|
||||
- Supplier.
|
||||
- A “Required By” date on each Item: If you are expecting part delivery, your Supplier will know how much quantity to deliver at which date. This will help you from preventing over-supply. It will also help you to track how well your Supplier is doing on timeliness.
|
||||
|
||||
### Taxes
|
||||
|
||||
If your Supplier is going to charge you additional taxes or charge like a shipping or insurance charge, you can add it here. It will help you to accurately track your costs. Also, if some of these charges add to the value of the product you will have to mention them in the Taxes table. You can also use templates for your taxes. For more information on setting up your taxes see the Purchase Taxes and Charges Master.
|
||||
|
||||
|
||||
### Value Added Taxes (VAT)
|
||||
|
||||
Many a times, the tax paid by you to a Supplier, for an Item, is the same tax which you collect from your Customer. In many regions, what you pay to your government is only the difference between what you collect from your Customer and what you pay to your Supplier. This is called Value Added Tax (VAT).
|
||||
|
||||
For example you buy Items worth X and sell them for 1.3X. So your Customer pays 1.3 times the tax you pay your Supplier. Since you have already paid tax to your Supplier for X, what you owe your government is only the tax on 0.3X.
|
||||
|
||||
This is very easy to track in ERPNext since each tax head is also an Account. Ideally you must create two Accounts for each type of VAT you pay and collect, “Purchase VAT-X” (asset) and “Sales VAT-X” (liability), or something to that effect. Please contact your accountant if you need more help or post a query on our forums!
|
||||
@ -1,37 +0,0 @@
|
||||
---
|
||||
{
|
||||
|
||||
"_label": "Purchase Taxes"
|
||||
}
|
||||
---
|
||||
For Tax Accounts that you want to use in the tax templates, you must mention them as type “Tax” in your Chart of Accounts.
|
||||
|
||||
Similar to your Sales Taxes and Charges Master is the Purchase Taxes and Charges Master. This is the tax template that you can use in your Purchase Orders and Purchase Invoices.
|
||||
|
||||
> Buying > Purchase Taxes and Charges Master > New Purchase Taxes and Charges Master
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
You can specify if the tax / charge is only for valuation (not a part of total) or only for total (does not add value to the item) or for both.
|
||||
|
||||
If you select a particular tax as your Default tax, the system will apply this tax to all the purchase transactions by default.
|
||||
Calculation Type:
|
||||
|
||||
This can be on Net Total (that is the sum of basic amount).
|
||||
On Previous Row Total / Amount (for cumulative taxes or charges). If you select this option, the tax will be applied as a percentage of the previous row (in the tax table) amount or total.
|
||||
Actual (as mentioned).
|
||||
|
||||
- **Account Head:** The Account ledger under which this tax will be booked.
|
||||
- **Cost Center:** If the tax / charge is an income (like shipping) or expense it needs to be booked against a Cost Center.
|
||||
- **Description:** Description of the tax (that will be printed in invoices / quotes).
|
||||
- **Rate:** Tax rate.
|
||||
- **Amount:** Tax amount.
|
||||
- **Total:** Cumulative total to this point.
|
||||
- **Enter Row:** If based on "Previous Row Total" you can select the row number which will be taken as a base for this calculation (default is the previous row).
|
||||
- **Consider Tax or Charge for:** In this section you can specify if the tax / charge is only for valuation (not a part of total) or only for total (does not add value to the item) or for both.
|
||||
- **Add or Deduct:** Whether you want to add or deduct the tax.
|
||||
@ -1,41 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Supplier Master"
|
||||
}
|
||||
---
|
||||
Suppliers are companies or individuals who provide you with products or services. They are treated in exactly the same manner as Customers in ERPNext.
|
||||
|
||||
|
||||
You can create a new Supplier via:
|
||||
|
||||
> Buying > Supplier > New Supplier
|
||||
|
||||
|
||||
|
||||
|
||||
### Contacts and Addresses
|
||||
|
||||
Contacts and Addresses in ERPNext are stored separately so that you can attach multiple Contacts or Addresses to Customers and Suppliers. To add a Contact or Address go to Buying and click on “New Contact” or “New Address”.
|
||||
|
||||
|
||||
> Tip: When you select a Supplier in any transaction, one Contact and Address gets pre-selected. This is the “Default Contact or Address”. So make sure you set your defaults correctly!
|
||||
|
||||
### Integration with Accounts
|
||||
|
||||
In ERPNext, there is a separate Account record for each Supplier, of Each company.
|
||||
|
||||
When you create a new Supplier, ERPNext will automatically create an Account Ledger for the Supplier under “Accounts Receivable” in the Company set in the Supplier record.
|
||||
|
||||
> Advanced Tip: If you want to change the Account Group under which the Supplier Account is created, you can set it in the Company master.
|
||||
|
||||
If you want to create an Account in another Company, just change the Company value and “Save” the Supplier again.
|
||||
|
||||
|
||||
> Buying > Contact > New Contact
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
You can also import from the Data Import Tool
|
||||
@ -1,34 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Supplier Quotation"
|
||||
}
|
||||
---
|
||||
A Supplier Quotation is a formal statement of promise by potential supplier to supply the goods or services required by a buyer, at specified prices, and within a specified period. A quotation may also contain terms of sale and payment, and warranties. Acceptance of quotation by the buyer constitutes an agreement binding on both parties.
|
||||
|
||||
|
||||
You can make a supplier quotation from a Material Request
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
You can also make a Supplier Quotation directly from:
|
||||
|
||||
> Buying > Supplier Quotation > New Supplier Quotation
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
If you have multiple **Suppliers** who supply you with the same **Item**, you usually send out a message (Request for Quote) to various **Suppliers**. In many cases, especially if you have centralized buying, you may want to record all the quotes so that
|
||||
|
||||
- You can easily compare prices in the future
|
||||
- Audit whether all Suppliers were given the opportunity to quote.
|
||||
|
||||
Supplier Quotations are not necessary for most small businesses. Always evaluate the cost of collecting information to the value it really provides! You could only do this for high value items.
|
||||
|
||||
@ -1,21 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Supplier Type"
|
||||
}
|
||||
---
|
||||
A supplier may be distinguished from a contractor or subcontractor, who commonly adds specialized input to deliverables. A supplier is also known as a vendor. There are different types of suppliers based on their goods and products.
|
||||
|
||||
ERPNext allows you to create your own categories of suppliers. These categories are known as Supplier Type. For Example, if your suppliers are mainly pharmaceutical companies and FMCG distributors, You can create a new Type for them and name them accordingly.
|
||||
|
||||
Based on what the suppliers supply, they are classified into different categories called Supplier Type. There can be different types of suppliers. You can create your own category of Supplier Type.
|
||||
|
||||
> Buying > Supplier Type > New Supplier Type
|
||||
|
||||
|
||||
|
||||
You can classify your suppliers from a range of choice available in ERPNext. Choose from a set of given options like Distributor, Electrical,Hardware, Local, Pharmaceutical, Raw material, Services etc.
|
||||
|
||||
Classifying your supplier into different types facilitates accounting and payments.
|
||||
|
||||
|
||||
Type your new supplier category and Save.
|
||||
@ -1,8 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Portal Login"
|
||||
}
|
||||
---
|
||||
To login into the customer account, the customer has to use his email id and the password sent by ERPNext; generated through the sign-up process.
|
||||
|
||||
|
||||
@ -1,16 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Customer Portal",
|
||||
"_toc": [
|
||||
"docs.user.customer_portal.sign_up",
|
||||
"docs.user.customer_portal.login",
|
||||
"docs.user.customer_portal.order",
|
||||
"docs.user.customer_portal.tickets"
|
||||
]
|
||||
}
|
||||
---
|
||||
|
||||
Customer Portal is designed to give easy accesibility to customers of a company.
|
||||
|
||||
|
||||
|
||||
@ -1,30 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Customer Orders, Invoices, and Shipping Status"
|
||||
}
|
||||
---
|
||||
ERPNext Web Portal gives your customers quick access to their Orders, Invoices and Shipments
|
||||
Customers can check the status of their orders, invoices, and shipping status by logging on to the web.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Once an order is raised, either using the Shopping Cart or from within ERPNext, your customer can view the order and keep an eye on the billing and shipment status. When the invoice and payment against these orders are submitted, the customer can see the updated status on the portal, at a glance.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
#### Invoice with paid status.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
#### Invoice with billed status.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,25 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Sign-Up"
|
||||
}
|
||||
---
|
||||
Customers have to log-in to the Company Website, and sign-up as a customer.
|
||||
|
||||
#### Step 1: Click on Login Icon
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
#### Step 2: Click on Sign Up Icon
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
#### Step 3: Enter Customer Name and ID
|
||||
|
||||
|
||||
|
||||
After the sign up process, a mail will be sent to the customers email id with the password details.
|
||||
|
||||
@ -1,28 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Support Tickets"
|
||||
}
|
||||
---
|
||||
|
||||
The customer portal makes it very easy for a customer to raise concerns. A simple and intuitive interface facilitates your customer to report their concerns as Support Tickets. They can view the complete thread of their conversation.
|
||||
|
||||
#### Empty Ticket List
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
#### New Support Ticket
|
||||
|
||||
|
||||
|
||||
|
||||
#### Open Support Ticket
|
||||
|
||||
|
||||
|
||||
|
||||
#### Reply on Support Ticket
|
||||
|
||||
|
||||
|
||||
@ -1,26 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Custom Field"
|
||||
}
|
||||
---
|
||||
A very common customization is adding of custom fields. You can add Custom Fields in any Master or Transaction in ERPNext. To add a Custom Field, go to:
|
||||
|
||||
> Setup > Custom Field > New Custom Field
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
In the form:
|
||||
|
||||
- Select the Document on which you want to add the Custom Field.
|
||||
- Select the Type of field and the Options .
|
||||
- Select where you want the field to appear in the Form (“after field” section).
|
||||
|
||||
and save the Custom Field. When you open a new / existing form of the type you selected in step 1, you will see it with the Custom Fields.
|
||||
|
||||
To understand Custom Fields in detail, visit [DocType-Fields](docs.user.knowledge.doctype_fields.html)
|
||||
|
||||
#### Naming
|
||||
|
||||
Many times you want your fields to be carried over from one form to another. For example, you may have added a Custom Field in Quotation that you want to include in Sales Order when a Sales Order is created from the Quotation. This is simple in ERPNext, just make sure the fields have the same “fieldname”
|
||||
@ -1,38 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Customize Form"
|
||||
}
|
||||
---
|
||||
|
||||
You can Customize Forms by changing its layout, making certain fields mandatory, hiding others and changing permission levels on fields by going to:
|
||||
|
||||
> Setup > Customize ERPNext > Customize Forms
|
||||
|
||||
#### Step 1: Select the required Form Type for Customization.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Select the Form you want to customize and the fields table will be updated with the fields from that form. Here you can:
|
||||
|
||||
- Change field types (for e.g. you want to increase the number of decimal places, you can convert some fields from Float to Currency).
|
||||
- Change labels to suit your industry / language.
|
||||
- Make certain fields mandatory.
|
||||
- Hide certain fields.
|
||||
- Change layout (sequence of fields). To do this, select a field in the grid and click on “Up” or “Down” in the grid toolbar.
|
||||
- Add / edit “Select” Options. (for example, you can add more sources in Leads etc).
|
||||
|
||||
You can also allow attachments, set max number of attachments and set the default Print Format.
|
||||
|
||||
#### Step 2: Replace Fields with required changes.
|
||||
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
To understand field definitions, visit [Doctype-Fields](docs.user.knowledge.doctype_fields.html)
|
||||
|
||||
|
||||
> Though we want you to do everything you can to customize your ERP based on your business needs, we recommend that you do not make “wild” changes to the forms. This is because, these changes may affect certain operations and may mess up your forms. Make small changes and see its effect before doing some more.
|
||||
@ -1,6 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Custom Scripts"
|
||||
}
|
||||
---
|
||||
|
||||
@ -1,12 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Custom Scripts"
|
||||
}
|
||||
---
|
||||
If you wish to change any ERPNext form formats, you can do so by using Custom Scripts. For example, if you wish to add a submit button after saving, to a Lead form, you can do so by creating your own script.
|
||||
|
||||
> Setup > Customization > Custom Script
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,28 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Hiding Modules and Features"
|
||||
}
|
||||
---
|
||||
### Hiding Unused Features
|
||||
|
||||
As you have seen from this manual that ERPNext contains tons of features which you may not use. We have observed that most users start with using 20% of the features, though a different 20%. To hide fields belonging to features you dont require, go to:
|
||||
|
||||
> Setup > Tools > Hide/Unhide Features
|
||||
|
||||
|
||||
|
||||
|
||||
Check / uncheck the features you want to use and refresh your page for the changes to take effect.
|
||||
|
||||
---
|
||||
|
||||
### Hiding Module Icons
|
||||
|
||||
To hide modules (icons) from the home page, go to:
|
||||
|
||||
Setup > Tools> Modules Setup
|
||||
|
||||
|
||||
|
||||
|
||||
> Note: Modules are automatically hidden for users that have no permissions on the documents within that module. For example, if a user has no permissions on Purchase Order, Purchase Request, Supplier, the “Buying” module will automatically be hidden.
|
||||
@ -1,15 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Customize ERPNext",
|
||||
"_toc": [
|
||||
"docs.user.customize.custom_field",
|
||||
"docs.user.customize.custom_form",
|
||||
"docs.user.customize.hide_unhide",
|
||||
"docs.user.customize.print_format",
|
||||
"docs.user.customize.custom_scripts"
|
||||
]
|
||||
}
|
||||
---
|
||||
ERPNext offers many tools to customize the system.
|
||||
|
||||
You simplify the forms by hiding features you don’t need using Disable Features and Module Setup, add Custom Fields, change form properties, like adding more options to drop-downs or hiding fields using Customize Form View and make your own Print Formats by using HTML Templates. You can also create multiple Letter Heads for your Prints.
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Print Format"
|
||||
}
|
||||
---
|
||||
Print Formats are the layouts that are generated when you want to Print or Email a transaction like a Sales Invoice. There are two types of Print Formats,
|
||||
|
||||
- The auto-generated “Standard” Print Format: This type of format follows the same layout as the form and is generated automatically by ERPNext.
|
||||
- Based on the Print Format document. There are templates in HTML that will be rendered with data.
|
||||
|
||||
ERPNext comes with a number of pre-defined templates in three styles: Modern, Classic and Spartan. You modify these templates or create your own. Editing ERPNext templates is not allowed because they may be over-written in an upcoming release.
|
||||
|
||||
To create your own versions, open an existing template from:
|
||||
|
||||
> Setup > Printing > Print Formats
|
||||
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
|
||||
Select the type of Print Format you want to edit and click on the “Copy” button on the right column. A new Print Format will open up with “Is Standard” set as “No” and you can edit the Print Format.
|
||||
|
||||
Editing a Print Format is a long discussion and you will have to know a bit of HTML, Javascript and Python to learn this. For help, please post on our forum.
|
||||
|
||||
> Note: Pre-printed stationary is usually not a good idea because your Prints will look incomplete (inconsistent) when you send them by mail.
|
||||
|
||||
#### Footers
|
||||
|
||||
Many times you may want to have a standard footer for your prints with your address and contact information. Unfortunately due to the limited print support in HTML pages, it is not possible unless you get it scripted. Either you can use pre-printed stationary or add this information in your header.
|
||||
|
||||
@ -1,36 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Getting Help",
|
||||
"_icon": "question"
|
||||
}
|
||||
---
|
||||
If you are stuck, have searched all the posible help that is available online, and need to talk to someone, here is how you do it:
|
||||
|
||||
### 1. Head to the Forums
|
||||
|
||||
- If you are a user or you are evaluating and want to talk to other ERPNext users, go to the [ERPNext User Forum](groups.google.com/group/erpnext-user-forum/)
|
||||
|
||||
- If you are a developer and want help in customizing or extending ERPNext, head to the developer forums [ERPNext Developer Forum](groups.google.com/group/erpnext-developer-forum/)
|
||||
|
||||
### 2. Report an Issue / Suggestion at GitHub
|
||||
|
||||
We use GitHub to manage the development of ERPNext. So if you encounter a bug or have a suggestion, feel free to add a GitHub issue. Everyone on the core team keeps a watch on that list.
|
||||
|
||||
- [ERPNext Issues on GitHub](https://github.com/webnotes/erpnext/issues)
|
||||
|
||||
### 3. Get in touch with a local partner.
|
||||
|
||||
ERPNext has an expanding partner community. So check this page out if there is a local partner in your region.
|
||||
|
||||
- [ERPNext Parter List](https://erpnext.com/partners)
|
||||
|
||||
### 4. Buy Commercial Support / Hosting
|
||||
|
||||
You can buy affordable hosting from Web Notes or buy commercial support which offers:
|
||||
|
||||
1. One-on-one sessions via screen sharing.
|
||||
1. Priority bug fixing
|
||||
1. Remote setup and installation on your linux server.
|
||||
1. Help in setting up backups and restoring.
|
||||
|
||||
- [ERPNext Commercial Support](http://erpnext.com/open-source-commercial-support)
|
||||
@ -1,178 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "User Guide",
|
||||
"_toc": [
|
||||
"docs.user.intro",
|
||||
"docs.user.five_day_setup",
|
||||
"docs.user.implement",
|
||||
"docs.user.setup",
|
||||
"docs.user.selling",
|
||||
"docs.user.buying",
|
||||
"docs.user.stock",
|
||||
"docs.user.accounts",
|
||||
"docs.user.hr",
|
||||
"docs.user.mfg",
|
||||
"docs.user.support",
|
||||
"docs.user.projects",
|
||||
"docs.user.website",
|
||||
"docs.user.tools",
|
||||
"docs.user.customize",
|
||||
"docs.user.knowledge",
|
||||
"docs.user.customer_portal"
|
||||
],
|
||||
"_no_toc": 1
|
||||
}
|
||||
---
|
||||
This manual covers all the major processes in setting up and using ERPNext. The manual is written in a way that the user can manage a self-implementation of the ERP. We recommend that the manual be read first before starting implementation.
|
||||
|
||||
Contents
|
||||
|
||||
1. [Introduction](docs.user.intro.html)
|
||||
1. [Open Source](docs.user.intro.open_source.html)
|
||||
1. [Ways to get started](docs.user.intro.try.html)
|
||||
1. [Getting Help](docs.user.help.html)
|
||||
1. [Five-Day-Setup](docs.user.five_day_setup.html)
|
||||
1. [Day-1: Setup Customer,Item, and Supplier](docs.user.five_day_setup.day_1.html)
|
||||
1. [Day-2: Setup Chart of Accounts, Opening Accounts, and HR](docs.user.five_day_setup.day_2.html)
|
||||
1. [Day-3: Sales Cycle and Purchase Cycle](docs.user.five_day_setup.day_3.html)
|
||||
1. [Day-4: Manufacturing Cycle and Accounting Reports](docs.user.five_day_setup.day_4.html)
|
||||
1. [Day-5: Projects, Calendar, and Website](docs.user.five_day_setup.day_5.html)
|
||||
1. [Implementation](docs.user.implement.html)
|
||||
1. [Implementation Strategy](docs.user.implement.strategy.html)
|
||||
1. [Concepts](docs.user.implement.concepts.html)
|
||||
1. [Setup](docs.user.setup.html)
|
||||
1. [First Login](docs.user.setup.first.html)
|
||||
1. [Setting Up Masters (Item, Customer, Supplier)](docs.user.setup.masters.html)
|
||||
1. [Chart of Accounts](docs.user.setup.accounting.html)
|
||||
1. [Chart of Cost Centers](docs.user.setup.cost_centers.html)
|
||||
1. [Company Setup](docs.user.setup.company.html)
|
||||
1. [Adding Users](docs.user.setup.users.html)
|
||||
1. [Permissions](docs.user.setup.permissions.html)
|
||||
1. [Workflows](docs.user.setup.workflows.html)
|
||||
1. [Letter Heads](docs.user.setup.letter_head.html)
|
||||
1. [Print Headings](docs.user.setup.print_headings.html)
|
||||
1. [Numbering Series](docs.user.setup.series.html)
|
||||
1. [Global Defaults](docs.user.setup.global_defaults.html)
|
||||
1. [Importing Data](docs.user.setup.data_import.html)
|
||||
1. [Email Settings](docs.user.setup.email.html)
|
||||
1. [SMS Settings](docs.user.setup.sms.html)
|
||||
1. [Setting up Taxes](docs.user.setup.taxes.html)
|
||||
1. [Price Lists](docs.user.setup.price_list.html)
|
||||
1. [Adding Opening Entries](docs.user.setup.opening.html)
|
||||
1. [POS Setting](docs.user.setup.pos_setting.html)
|
||||
1. [Third Party Backups](docs.user.setup.third_party_backups.html)
|
||||
1. [Selling](docs.user.selling.html)
|
||||
1. [Selling Setup](docs.user.selling.selling_setup.html)
|
||||
1. [Customer Group](docs.user.selling.customer_groups.html)
|
||||
1. [Territory](docs.user.selling.territory.html)
|
||||
1. [Sales Partner](docs.user.selling.sales_partner.html)
|
||||
1. [Sales Person](docs.user.selling.sales_person.html)
|
||||
1. [Campaign](docs.user.selling.campaign.html)
|
||||
1. [Terms and Conditions](docs.user.selling.terms.html)
|
||||
1. [Price Lists](docs.user.setup.price_list.html)
|
||||
1. [Discount](docs.user.selling.discount.html)
|
||||
1. [Shopping Cart](docs.user.selling.shopping_cart.html)
|
||||
1. [Customers](docs.user.selling.customer.html)
|
||||
1. [Lead](docs.user.selling.lead.html)
|
||||
1. [Opportunity](docs.user.selling.opportunity.html)
|
||||
1. [Quotation](docs.user.selling.quotation.html)
|
||||
1. [Sales Order](docs.user.selling.sales_order.html)
|
||||
1. [Buying](docs.user.buying.html)
|
||||
1. [Supplier Type](docs.user.buying.supplier_type.html)
|
||||
1. [Supplier](docs.user.buying.supplier.html)
|
||||
1. [Material Request](docs.user.buying.material_request.html)
|
||||
1. [Supplier Quotation](docs.user.buying.supplier_quotation.html)
|
||||
1. [Purchase Order](docs.user.buying.purchase_order.html)
|
||||
1. [Purchase Taxes](docs.user.buying.purchase_taxes.html)
|
||||
1. [Price Lists](docs.user.setup.price_list.html)
|
||||
1. [Sub Contracting](docs.user.stock.sub_contracting.html)
|
||||
1. [Stock (Inventory)](docs.user.stock.html)
|
||||
1. [Warehouse](docs.user.stock.warehouse.html)
|
||||
1. [Item Group](docs.user.stock.item_group.html)
|
||||
1. [Item](docs.user.stock.item.html)
|
||||
1. [Product Listing on Website](docs.user.stock.product_listing_on_website.html)
|
||||
1. [Serialized Inventory](docs.user.stock.serialized.html)
|
||||
1. [Purchase Receipt](docs.user.stock.purchase_receipt.html)
|
||||
1. [Delivery Note](docs.user.stock.delivery_note.html)
|
||||
1. [Stock Entry / Material Transfer](docs.user.stock.stock_entry.html)
|
||||
1. [Opening Stock](docs.user.accounts.opening_stock.html)
|
||||
1. [Material Issue](docs.user.stock.material_issue.html)
|
||||
1. [Purchase Return](docs.user.stock.purchase_return.html)
|
||||
1. [Projected Quantity](docs.user.stock.projected_quantity.html)
|
||||
1. [Accounting for Stock](docs.user.stock.accounting_for_stock.html)
|
||||
1. [Perpetual Inventory](docs.user.stock.perpetual_inventory.html)
|
||||
1. [How To](docs.user.stocks.how_to.html)
|
||||
1. [Repack Products](docs.user.stock.how_to_repack_products.html)
|
||||
1. [Sales Return](docs.user.stock.sales_return.html)
|
||||
1. [Migrate to Perpetual Inventory](docs.user.stock.migrate_to_perpetual.html)
|
||||
1. [Accounts](docs.user.accounts.html)
|
||||
1. [Chart of Accounts](docs.user.setup.accounting.html)
|
||||
1. [Chart of Cost Centers](docs.user.setup.cost_centers.html)
|
||||
1. [Sales Invoice](docs.user.accounts.sales_invoice.html)
|
||||
1. [Purchase Invoice](docs.user.accounts.purchase_invoice.html)
|
||||
1. [Payment Entry](docs.user.accounts.payments.html)
|
||||
1. [Journal Voucher](docs.user.accounts.journal_voucher.html)
|
||||
1. [Opening Entry](docs.user.accounts.opening_entry.html)
|
||||
1. [Period Closing](docs.user.accounts.closing.html)
|
||||
1. [Accounting Reports](docs.user.accounts.reports.html)
|
||||
1. [Point of Sale (POS) Invoice](docs.user.accounts.pos.html)
|
||||
1. [Human Resources (HR)](docs.user.hr.html)
|
||||
1. [HR Setup](docs.user.hr.setup.html)
|
||||
1. [Employee](docs.user.hr.employee.html)
|
||||
1. [Leave Management](docs.user.hr.leave.html)
|
||||
1. [Attendance](docs.user.hr.attendance.html)
|
||||
1. [Salary and Payroll](docs.user.hr.payroll.html)
|
||||
1. [Expense Claim](docs.user.hr.expense_claim.html)
|
||||
1. [Appraisal](docs.user.hr.appraisal.html)
|
||||
1. [Manufacturing](docs.user.mfg.html)
|
||||
1. [Bill of Materials](docs.user.mfg.bom.html)
|
||||
1. [Production Planning](docs.user.mfg.planning.html)
|
||||
1. [Production Order](docs.user.mfg.production_order.html)
|
||||
1. [Customer Support and Maintenance](docs.user.support.html)
|
||||
1. [Support Ticket](docs.user.support.support_ticket.html)
|
||||
1. [Customer Issue](docs.user.support.customer_issue.html)
|
||||
1. [Maintenance Schedule](docs.user.support.maintenance_schedule.html)
|
||||
1. [Maintenance Visit](docs.user.support.maintenance_visit.html)
|
||||
1. [Maintenance Schedule](docs.user.support.maintenance_schedule.html)
|
||||
1. [Newsletter](docs.user.support.newsletter.html)
|
||||
1. [Projects](docs.user.projects.html)
|
||||
1. [Projects](docs.user.projects.projects.html)
|
||||
1. [Task](docs.user.projects.task.html)
|
||||
1. [Time Log](docs.user.projects.timelog.html)
|
||||
1. [Website](docs.user.website.html)
|
||||
1. [Setup](docs.user.website.setup.html)
|
||||
1. [Web Pages](docs.user.website.web_page.html)
|
||||
1. [Style](docs.user.website.style.html)
|
||||
1. [Blog](docs.user.website.blog.html)
|
||||
1. [Shopping Cart](docs.user.website.shopping_cart.html)
|
||||
1. [Add Products](docs.user.website.add_products_to_website.html)
|
||||
1. [Tools](docs.user.tools.html)
|
||||
1. [To Do](docs.user.tools.todo.html)
|
||||
1. [Calendar](docs.user.tools.calendar.html)
|
||||
1. [Assignments](docs.user.tools.assignment.html)
|
||||
1. [Tags](docs.user.tools.tags.html)
|
||||
1. [Forms](docs.user.tools.form_tools.html)
|
||||
1. [Messages](docs.user.tools.messages.html)
|
||||
1. [Notes](docs.user.tools.notes.html)
|
||||
1. [Customize](docs.user.customize.html)
|
||||
1. [Custom Fields](docs.user.customize.custom_field.html)
|
||||
1. [Customize Form](docs.user.customize.custom_form.html)
|
||||
1. [Hide / Unhide modules](docs.user.customize.hide_unhide.html)
|
||||
1. [Print Formats](docs.user.customize.print_formats.html)
|
||||
1. [Custom Scripts](docs.user.customize.custom_scripts.html)
|
||||
1. [Knowledge Library](docs.user.knowledge.html)
|
||||
1. [Fiscal Year](docs.user.knowledge.fiscal_year.html)
|
||||
1. [Accounting Knowledge](docs.user.knowledge.accounting.html)
|
||||
1. [Accounting Entries](docs.user.knowledge.accounting_entries.html)
|
||||
1. [DocType Definitions](docs.user.knowledge.doctype.html)
|
||||
1. [DocType Fields](docs.user.knowledge.doctype_fields.html)
|
||||
1. [Attachment and CSV Files](docs.user.knowledge.attachment_csv.html)
|
||||
1. [Format using Markdown](docs.user.knowledge.markdown.html)
|
||||
1. [Make-to-Stock Manufacturing](docs.user.knowledge.make_to_stock.html)
|
||||
1. [Make-to-Order Manufacturing](docs.user.knowledge.make_to_order.html)
|
||||
1. [Engineer-to-Order Manufacturing](docs.user.knowledge.engineer_to_order.html)
|
||||
1. [Customer Portal](docs.user.customer_portal.html)
|
||||
1. [Sign Up](docs.user.customer_portal.sign_up.html)
|
||||
2. [Login](docs.user.customer_portal.login.html)
|
||||
3. [Customer Orders](docs.user.customer_portal.orders.html)
|
||||
4. [Support Tickets](docs.user.customer_portal.tickets.html)
|
||||
@ -1,28 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Report Builder"
|
||||
}
|
||||
---
|
||||
All the data that you enter in ERPNext is stored in database tables. An easy way to visualize this is to imagine each type of data like Customer, Sales Invoice, Task is stored in a separate spreadsheets, each containing all the data included in one table.
|
||||
|
||||
ERPNext gives you a simple tool called the Report Builder to extract data from these tables and show them in rows and columns where you can pick and choose which column to display and filter and sort the data by different parameters.
|
||||
|
||||
To start a new report click on the “Report” menu in the top toolbar or on the list page of any transaction click on the “Build Report” button. For example, to make a report of Sales Invoices, go to
|
||||
|
||||
> Accounts > Sales Invoice > Build Report
|
||||
|
||||
### Exporting
|
||||
|
||||
If you have “Report Manager” or “System Manager” permission, you can export the data from the Report Building via CSV to your favorite Spreadsheet application where you can do further analysis, apply formulas, make graphs etc. Selecting Columns
|
||||

|
||||
You can select columns by clicking on “Pick Columns”. Select the column you want from the drop-down.
|
||||
|
||||
You can also select columns from the “child tables”. For example if you have selected Sales Invoice, you can select columns from the Sales Invoice Item table also.
|
||||
|
||||
### Adding Filters
|
||||

|
||||
You can also add multiple filters by clicking on the “Show Filters” button.
|
||||
|
||||
### Saving
|
||||
|
||||
You can also save your selection of columns and filters by clicking on the “Save” button. You might need “System Manager” or “Report Manager” privileges for this. When you save a report, it will appear in the “Reports” section of the module page.
|
||||
@ -1,8 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Reports and Analytics",
|
||||
"_toc": [
|
||||
"docs.user.reports.builder"
|
||||
]
|
||||
}
|
||||
---
|
||||
@ -1,81 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Day-1: Setup Customer, Item, and Supplier"
|
||||
}
|
||||
---
|
||||
Login to your ERPNext account with the User ID and Password sent through the mail.
|
||||
|
||||
After logging into your account you will receive a pop-up form to fill. Please fill this form. Select the abbreviation you would wish to have for your company. The abbreviation selected here will be used in naming most of the business documents.
|
||||
|
||||
#### Form Part I
|
||||
|
||||
|
||||
<br><br>
|
||||
#### Form Part II
|
||||
To understand about Company Financial Year or Fiscal Year visit [Fiscal Year](docs.user.knowledge.fiscal_year.html)
|
||||
|
||||
|
||||
|
||||
|
||||
After filling this form, you will get a pop-up message for completing the set-up process. Click on the Setup button. The Setup page will appear.
|
||||
|
||||
<br>
|
||||
#### Setup Page - Customer
|
||||
|
||||
The Organisation details are updated in ERPNext, after filling the first form. Go directly to the Customer Icon.
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
After clicking on Customer, a new form will appear.
|
||||
<br>
|
||||
|
||||
|
||||
|
||||
To see how customer details are added, visit [Customer](docs.user.selling.customer.html). Create 5 new customer records in the system.
|
||||
|
||||
Now proceed to make an Item. To go to the main menu, click on erpnext icon which is on the left hand corner of the page. On the main menu page, click on Setup
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
#### Setup Page - Item
|
||||
|
||||
On the setup page go to Item.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Create a new Item. An Item is your company's product or a service.The term Item is applicable to your core products as well as your raw materials. It can be a product or service that you buy/sell from your customers/ suppliers.
|
||||
|
||||
Filling Item details is an important step in ERPNext. Do not postpone this step. After clicking on Item, make a new Item.
|
||||
|
||||
|
||||
|
||||
To understand how to fill an Item in detail, visit [Item](docs.user.stock.item.html). Add 5 item records to ERPnext. After adding these records, go back to the Setup Page and add Suppliers.
|
||||
|
||||
<br>
|
||||
#### Setup Page - Suppliers
|
||||
On the Setup page go to Supplier.
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
Suppliers are companies or individuals who provide you with products or services. They are treated in exactly the same manner as Customers in ERPNext. Create a new Supplier record.
|
||||
|
||||
|
||||
|
||||
|
||||
To understand how to fill Supplier details, visit [Supplier](docs.user.buying.supplier.html).
|
||||
|
||||
If you wish to import your list of customers and suppliers directly to ERPNext, you can do that via the Data Import Tool.
|
||||
|
||||
To upload Customers or suppliers in bulk, go to the Data Import Tool.
|
||||
|
||||
> Note: The data import format is case-sensitive. The file will not be processed if there are any spelling mistakes or deviations from the default values.
|
||||
|
||||
To understand how to import data, visit [Importing Data](docs.user.setup.data_import.html).
|
||||
|
||||
@ -1,54 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Day-2: Setup Chart of Accounts, Opening Accounts, and HR"
|
||||
}
|
||||
---
|
||||
|
||||
#### Setup Page - Accounts
|
||||
<br>
|
||||
Go to the Accounts icon and make ledgers under Chart of Accounts.
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
Create acccounting ledgers.
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
To begin Opening Entries, go to 'Opening Accounts and Stock' on the Setup Page.
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
To understand how to create opening entries in detail visit [Opening Entry](docs.user.setup.opening.html).
|
||||
|
||||
<br>
|
||||
|
||||
#### Opening Stock
|
||||
|
||||
You can upload your opening stock in the system using Stock Reconciliation. Stock Reconciliation will update your stock for any given Item.
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
To understand Stock Opening in detail visit [Opening Stock](docs.user.accounts.opening_stock.html).
|
||||
|
||||
<br>
|
||||
|
||||
#### Setup Page - HR Setup
|
||||
|
||||
To setup HR, begin by creating individual employee records.
|
||||
|
||||
|
||||
|
||||
|
||||
To fill the Employee Form, refer to [Employee](docs.user.hr.employee.html)
|
||||
|
||||
To complete the remaining HR-Setup, see [Human Resources](docs.user.hr.html)
|
||||
@ -1,139 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Day-3: Sales Cycle and Purchase Cycle"
|
||||
}
|
||||
---
|
||||
After completing the set-up and account opening process, it is advisable to complete a few cycles of sales, purchase, and manufacturing process.
|
||||
|
||||
|
||||
### Sales Cycle
|
||||
|
||||
Complete a standard Sales Cycle.
|
||||
> Lead > Opportunity > Quotation > Sales Order > Delivery Note > Sales Invoice > Payment (Journal Voucher)
|
||||
|
||||
<br>
|
||||
#### Lead
|
||||
|
||||
To begin the sales cycle, go to the Selling Icon. On the selling page, click on Lead.
|
||||
|
||||
|
||||
|
||||
Fill the Lead form.
|
||||
|
||||
> To understand Lead in detail, visit [Lead](docs.user.selling.lead.html)
|
||||
|
||||
<br>
|
||||
#### Opportunity
|
||||
|
||||
After completing the Lead form, assume that, this same lead is getting converted into an Opportunity. Thus, to create an Opportunity from the existing lead, click on Create Opportunity, on the Lead page.
|
||||
|
||||
##### Step 1: Go to 'Lead List' Page and open the Lead that shows interested status.
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
##### Step 2: Generate Opportunity from the selected Lead
|
||||
|
||||
|
||||
|
||||
You can also generate an Opportunity directly from the Selling Page.
|
||||
|
||||
> To understand Opportunity in detail visit [Opportunity](docs.user.selling.opportunity.html).
|
||||
|
||||
<br>
|
||||
#### Quotation
|
||||
|
||||
Imagine that your Opportunity has shown interest and asked for a Quotation. To generate a Quotation from the same Opportunity, open the submitted Opportunity and click on Create Quotation.
|
||||
|
||||
|
||||
|
||||
You can also generate a Quotation directly from the Selling Page.
|
||||
|
||||
> To understand Quotation in detail visit [Quotation](docs.user.selling.quotation.html)
|
||||
|
||||
<br>
|
||||
#### Sales Order
|
||||
|
||||
Imagine that the Quotation which you sent was accepted by the prospect. You are now reequired to send him a Sales Order. To make a sales order from this same Quotation, go to that Quotation page and click on Make Sales Order.
|
||||
|
||||
|
||||
|
||||
You can also generate a Sales Order directly from the Selling Page.
|
||||
|
||||
> To understand Sales Order in detail visit [Sales Order](docs.user.selling.sales_order.html).
|
||||
|
||||
<br>
|
||||
#### Delivery Note
|
||||
|
||||
If your organisation has the practice of sending Delivery Note, this section will be helpful. To create a Delivery Note from the a Sales Order, go to that Sales Order and click on Make Delivery.
|
||||
|
||||
|
||||
|
||||
|
||||
> To understand Delivery Note in detail, visit [Delivery Note](docs.user.stock.delivery_note.html)
|
||||
|
||||
<br>
|
||||
#### Sales Invoice
|
||||
|
||||
Save and Submit your Delivery Note to generate a Sales Invoice. You can also generate an Invoice from Sales Order.
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
#### Payment (Journal Voucher)
|
||||
|
||||
|
||||
A Journal Voucher or a payment entry can be generated directly from the Sales Invoice.
|
||||
|
||||
|
||||
|
||||
> To understand a Journal Voucher in detail, visit [Journal Voucher](docs.user.accounts.journal_voucher.html)
|
||||
|
||||
<br>
|
||||
|
||||
### Purchase Cycle
|
||||
|
||||
Complete a standard Purchase Cycle.
|
||||
> Material Request > Purchase Order > Purchase Receipt > Payment (Journal Voucher).
|
||||
|
||||
<br>
|
||||
#### Material Request
|
||||
|
||||
To create a Material Request, go to Stock/Buying and Click on Material Request.
|
||||
|
||||
|
||||
|
||||
> To understand Material Request in detail, visit [Material Request](docs.user.buying.material_request.html)
|
||||
|
||||
<br>
|
||||
#### Purchase Order
|
||||
|
||||
To create a Purchase Order go to Buying and click on Purchase Order
|
||||
|
||||
|
||||
|
||||
> To understand Purchase Order in detail, visit [Purchase Order](docs.user.buying.purchase_order.html)
|
||||
|
||||
<br>
|
||||
#### Purchase Receipt
|
||||
|
||||
To create a Purchase Receipt from an existing Purchase Order, open that purchase order and click on Make Purchase Receipt.
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
>To understand Purchase Receipt in detail, visit [Purchase Receipt](docs.user.stock.purchase_receipt.html)
|
||||
|
||||
<br>
|
||||
|
||||
#### Payment (Journal Voucher)
|
||||
|
||||
Payments made against Sales Invoices or Purchase Invoices can be made by clicking on “Make Payment Entry” button on “Submitted” invoices.
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
> To understand Payment Entry in detail, visit [Payment Entry](docs.user.accounts.payments.html).
|
||||
@ -1,86 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Day-4: Manufacturing Cycle and Accounting Reports"
|
||||
}
|
||||
---
|
||||
|
||||
### Manufacturing Cycle
|
||||
|
||||
Complete a manufacturing cycle (if applicable).
|
||||
> BOM > Production Planning Tool > Production Order > Stock Entry (Material Issue) > Stock Entry (Sales Return)
|
||||
|
||||
<br>
|
||||
#### Bill of Materials
|
||||
|
||||
To go to Bill of Materials, Click on Manufacturing. On the Manufacturing page, click on Bill of Materials.
|
||||
|
||||
|
||||
|
||||
> To understand BOM in detail, visit [Bill of Materials](docs.user.mfg.bom.html)
|
||||
|
||||
<br>
|
||||
#### Production Planning Tool
|
||||
|
||||
To go to Production Planning Tool, click on the Manufacturing Icon. On the Manufacturing Page, click on Production Planning Tool to go to that page.
|
||||
|
||||
|
||||
|
||||
> To understand Production Planning Tool in detail, visit [Production Planning](docs.user.mfg.planning.html)
|
||||
|
||||
<br>
|
||||
#### Production Order
|
||||
|
||||
To go to Production Order click on the Manufacturing Icon. On the Manufacturing Page, click on Production Order.
|
||||
|
||||
|
||||
|
||||
> To understand Production Order in detail, visit [Production Order](docs.user.mfg.production_order.html)
|
||||
|
||||
<br>
|
||||
#### Stock Entry
|
||||
|
||||
To go to Stock Entry, click on the Stock Icon and go to Stock Entry.
|
||||
|
||||
|
||||
|
||||
> To understand Material Issue, visit [Material Issue](docs.user.stock.material_issue.html).
|
||||
|
||||
> To understand Sales Return, visit [Sales Return](docs.user.stock.sales_return.html).
|
||||
|
||||
<br>
|
||||
#### Delivery Note
|
||||
|
||||
To go to Delivery Note, click on Stock. On the Stock Page, click on Delivery Note.
|
||||
|
||||
|
||||
|
||||
> To understand Delivery Note in detail, visit [Delivery Note](docs.user.stock.delivery_note.html)
|
||||
|
||||
<br>
|
||||
#### Warehouse
|
||||
|
||||
To go to Warehouse, Click on Stock. On the Stock Page, go to Warehouse.
|
||||
|
||||
|
||||
|
||||
> To understand Warehouse in detail, visit [Warehouse](docs.user.stock.warehouse.html)
|
||||
|
||||
<br>
|
||||
#### Accounts
|
||||
|
||||
Make a few Journal Vouchers. Generate some Accounting Reports.
|
||||
|
||||
#### Journal Voucher
|
||||
|
||||
To go to a Journal Voucher, click on Accounts. On the Accounts page, click on Journal Voucher.
|
||||
|
||||
|
||||
|
||||
> To understand Journal Voucher in detail, visit [Journal Voucher](docs.user.accounts.journal_voucher.html)
|
||||
|
||||
<br>
|
||||
### Accounting Reports
|
||||
|
||||
Some of the major Accounting Reports are General Ledger, Trial Balance, Accounts Payable and Accounts Receivables, and Sales and Purchase Register.
|
||||
|
||||
> To be able to generate these accounts, visti [Accounting Reports](docs.user.accounts.report.html)
|
||||
@ -1,32 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Day-5: Projects, Calendar, and Website"
|
||||
}
|
||||
---
|
||||
|
||||
#### Projects
|
||||
|
||||
ERPNext helps you to manage your Projects by breaking them into Tasks and allocating them to different people.
|
||||
|
||||
<br>
|
||||
#### Tasks
|
||||
|
||||
Project is divided into Tasks and each Task is allocated to a resource. In ERPNext, you can also create and allocate a Task independently of a Project.
|
||||
|
||||
To create a Task, go to Project and click on Task.
|
||||
|
||||
|
||||
|
||||
> To understand Projects in detail, visit [Projects](docs.user.projects.html).
|
||||
|
||||
> To understand Task in detail, visit [Tasks](docs.user.projects.tasks.html)
|
||||
|
||||
<br>
|
||||
#### Calendar
|
||||
|
||||
> To understand Calendar in detail, visit [Calendar](docs.user.tools.calendar.html)
|
||||
|
||||
<br>
|
||||
#### Website
|
||||
|
||||
> To understand Website in detail, visit [Website](docs.user.website.html)
|
||||
@ -1,48 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Five-Day Setup",
|
||||
"_toc": [
|
||||
"docs.user.five_day_setup.day_1",
|
||||
"docs.user.five_day_setup.day_2",
|
||||
"docs.user.five_day_setup.day_3",
|
||||
"docs.user.five_day_setup.day_4",
|
||||
"docs.user.five_day_setup.day_5"
|
||||
|
||||
]
|
||||
}
|
||||
---
|
||||
Welcome to ERPNext. To be able to setup ERPNext account successfully, a five-day-setup process is recommended. Perform the 5-days-setup instructions and sail through the ERPNext implementation.
|
||||
|
||||
The setup help is divided into day-wise instructions for 5 consecutive days.
|
||||
|
||||
#### Day 1
|
||||
|
||||
- Company Setup
|
||||
- Customer Setup
|
||||
- Item Setup
|
||||
- Supplier Setup
|
||||
- Data Import Tool
|
||||
|
||||
#### Day 2
|
||||
|
||||
- Opening Accounts
|
||||
- Opening Stock
|
||||
- HR Setup
|
||||
|
||||
#### Day 3
|
||||
|
||||
- Sales Cycle
|
||||
- Purchase Cycle
|
||||
|
||||
|
||||
#### Day 4
|
||||
|
||||
- Manufacturing Cycle
|
||||
- Delivery Note and Warehouse
|
||||
- Accounts
|
||||
|
||||
#### Day 5
|
||||
|
||||
- Projects
|
||||
- Calendar
|
||||
- Website
|
||||
@ -1,29 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Appraisal"
|
||||
}
|
||||
---
|
||||
In ERPNext, you can manage Employee Appraisals by creating an Appraisal Template for each role with the parameters that define the performance by giving appropriate weightage to each parameter.
|
||||
|
||||
> HR > Appraisal > New Appraisal
|
||||
|
||||
|
||||
|
||||
#### Step 1: Select an Appraisal Template
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
After you select the template, the remaining form appears.
|
||||
|
||||
|
||||
#### Step 2: Enter Employee Details
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Once the Appraisal Template is completed, you can create Appraisal records for each period where you track performance. You can give points out of 5 for each parameter and the system will calculate the overall performance of the Employee.
|
||||
|
||||
To make the Appraisal final, make sure to “Submit” it.
|
||||
@ -1,26 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Attendance"
|
||||
}
|
||||
---
|
||||
|
||||
An Attendance record stating that an Employee has been present on a particular day can be created manually by:
|
||||
|
||||
> HR > Attendance > New Attendance
|
||||

|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
It can also be done by collecting attendance information via an automated system like a swipe card. You can even upload a CSV file with the attendance information.
|
||||
|
||||
You can get a monthly report of your Attendance data by going to the “Monthly Attendance Details” report.
|
||||
|
||||
To upload the attendance go to:
|
||||
|
||||
> HR > Upload Attendance
|
||||
|
||||
|
||||
|
||||
@ -1,50 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Employee Master"
|
||||
}
|
||||
---
|
||||
There are many fields you can add in your Employee records. As the organisation grows, it becomes difficult to manage more records. It is advisable to keep updating and entering records to facilitate data management of employees.
|
||||
|
||||
Employee records also help in keeping a list of your team’s skills, previous employment history and emergency information.
|
||||
|
||||
To create new Employee go to:
|
||||
|
||||
> HR > Employee > New Employee
|
||||
|
||||
#### Step 1: Capture basic information and Employement Details.
|
||||
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
#### Step 2: Complete Job Profile and Organisation Profile.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
#### Step 3: Update contact details, personal details, and previous employement details.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Numbering Employees (Employee ID)
|
||||
|
||||
By default, in ERPNext Employee Records are Numbered. You can have multiple series if you are a really large company and want to have separate numbering series for separate locations etc. You can set the numbering series just like any other transaction by going to:
|
||||
|
||||
> Setup > Customize > Document Numbering Series.
|
||||
|
||||
Alternatively, you can create employees by the “Employee Number” field if you already have an existing Employee Numbering system you want to follow. To set this, go to
|
||||
|
||||
> Setup > Global Defaults > HR
|
||||
|
||||
and update the “Employee Records created by” field.
|
||||
@ -1,30 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Expense Claim"
|
||||
}
|
||||
---
|
||||
Expense Claim is made when Employee’s make expenses out of their pocket on behalf of the company. For example, if they take a customer out for lunch, they can make a request for reimbursement via the Expense Claim form.
|
||||
|
||||
To make a new Expense Claim, go to:
|
||||
|
||||
> HR > Expense Claim > New Expense Claim
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Set the Employee ID, date and the list of expenses that are to be claimed and “Submit” the record.
|
||||
|
||||
### Approving Expenses
|
||||
|
||||
The person making the claim must also set the id of the user who will “Approve” these expenses and set the “Assign To” to notify the user of the request Approve.
|
||||
|
||||
If the Approver sees the “form”, she or he can update the “Approved Amounts” and click on “Approve”. To cancel the claim, they can click on the “Reject” button.
|
||||
|
||||
Comments can be added in the Comments section explaining why the claim was approved or rejected.
|
||||
|
||||
### Booking the Expense and Reimbursement
|
||||
|
||||
The approved Expense Claim must then be converted into a Journal Voucher and a payment must be made. Note: This amount should not be clubbed with Salary because the amount will then be taxable to the Employee.
|
||||
@ -1,30 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Leave"
|
||||
}
|
||||
---
|
||||
|
||||
### Leave Allotment
|
||||
|
||||
Fixed number of leaves per Employee can be allocated using the Leave Allocation Tool. If you have special leaves to be allocated, you can also allocate them manually by creating new Leave Allocation records.
|
||||
|
||||
> HR > Leave Allocation > New Leave Allocation
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
### Leave Application
|
||||
|
||||
If your company has a formal system where Employees have to apply for leaves to be able to qualify as paid leaveas, you can create Leave Application to track approval and usage of leaves. You have to mention the Employee, Leave Type and the period for which the leave is taken. If you want specific users to approve leaves, you can give “Submission” rights to those users only.
|
||||
|
||||
> HR > Leave Application > Make New Leave Application
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
If you want all users to create their own Leave Applications, you can set their “Employee ID” as a match rule in the Leave Application Permission settings. See the earlier discussion on permission settings for more info. [Permissions](docs.user.setup.permissions.html)
|
||||
|
||||
|
||||
@ -1,17 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Human Resource Management",
|
||||
"_toc": [
|
||||
"docs.user.hr.set-up",
|
||||
"docs.user.hr.employee",
|
||||
"docs.user.hr.leave",
|
||||
"docs.user.hr.attendance",
|
||||
"docs.user.hr.payroll",
|
||||
"docs.user.hr.expense_claim",
|
||||
"docs.user.hr.appraisal"
|
||||
]
|
||||
}
|
||||
---
|
||||
The Human Resources (HR) Module covers the processes linked to managing a team of co-workers. Most important feature here is processing the payroll by using the Salary Manager to generate Salary Slips. Most countries have complex tax rules stating which expenses the company can make on behalf of the Employees. There are a set of rules for the company to deduct taxes and social security from employee payroll. ERPNext allows to accomodate all types of taxes and their calculation.
|
||||
|
||||
It also maintains a complete employee database including contact information, salary details, attendance, performance evaluation, and appraisal records.
|
||||
@ -1,73 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Salary and Payroll"
|
||||
}
|
||||
---
|
||||
To process Payroll in ERPNext,
|
||||
|
||||
1. Create Salary Structures for all Employees.
|
||||
1. Generate Salary Slips via the Salary Manager Tool.
|
||||
1. Book the Salary in your Accounts.
|
||||
|
||||
### Salary Structure
|
||||
|
||||
The Salary Structure represents how Salaries are calculated based on Earnings and Deductions. To create a new Salary Structure go to:
|
||||
|
||||
> HR > Salary Structure > New Salary Structure
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### In the Salary Structure,
|
||||
|
||||
- Select the Employee
|
||||
- Set the starting date from which this is valid (Note: There can only be one Salary Structure that can be “Active” for an Employee during any period)
|
||||
- In the “Earnings” and “Deductions” table all your defined Earning Type and Deductions Type will be auto-populated. Set the values of the Earnings and Deductions and save the Salary Structure.
|
||||
|
||||
### Leave Without Pay (LWP)
|
||||
|
||||
Leave Without Pay (LWP) happens when an Employee runs out of allocated leaves or takes a leave without an approval (via Leave Application). If you want ERPNext to automatically deduct salary in case of LWP, then you must check on the “Apply LWP” column in the Earning Type and Deduction Type masters. The amount of pay cut is the proportion of LWP days divided by the total working days for the month (based on the Holiday List).
|
||||
|
||||
If you don’t want ERPNext to manage LWP, just don’t click on LWP in any of the Earning Types and Deduction Types.
|
||||
|
||||
---
|
||||
|
||||
### Creating Salary Slips
|
||||
|
||||
Once the Salary Structure is created, you can make a salary slip from the same form or you can process your payroll for the month using the Salary Manager.
|
||||
|
||||
To create a salary slip from Salary Structure, click on the button Make Salary Slip.
|
||||
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
Through Salary Manager:
|
||||
|
||||
> HR > Process Payroll
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
In the Salary Manager tool,
|
||||
|
||||
1. Select the Company for which you want to create the Salary Slips.
|
||||
1. Select the Month and the Year for which you want to create the Salary Slips.
|
||||
1. Click on “Create Salary Slips”. This will create Salary Slip records for each active Employee for the month selected. If the Salary Slips are created, the system will not create any more Salary Slips. All updates will be shown in the “Activity Log” section.
|
||||
1. Once all Salary Slips are created, you can check if they are created correctly or edit it if you want to deduct Leave Without Pay (LWP).
|
||||
1. After checking, you can “Submit” them all together by clicking on “Submit Salary Slips”. 1. If you want them to be automatically emailed to the Employee, make sure to check the “Send Email” box.
|
||||
|
||||
### Booking Salaries in Accounts
|
||||
|
||||
The final step is to book the Salaries in your Accounts.
|
||||
|
||||
Salaries in businesses are usually dealt with extreme privacy. In most cases, the companies issues a single payment to the bank combining all salaries and the bank distributes the salaries to each employee’s salary account. This way there is only one payment entry in the company’s books of accounts and anyone with access to the company’s accounts will not have access to the individual salaries.
|
||||
|
||||
The salary payment entry is a Journal Voucher entry that debits the total salary of all Employees to the Salary Account and credits the company’s bank Account.
|
||||
|
||||
To generate your salary payment voucher from the Salary Manager, click on “Make Bank Voucher” and a new Journal Voucher with the total salaries will be created.
|
||||
@ -1,32 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Human Resource Setup"
|
||||
}
|
||||
---
|
||||
The HR module has a setup process where you create the masters for all the major activities.
|
||||
|
||||
### Organization Setup
|
||||

|
||||
To setup your Employee master you must first create:
|
||||
|
||||
- Employment Type (like Permanent, Temp, Contractor, Intern etc).
|
||||
- Branch (if there are multiple offices).
|
||||
- Department (if any, like Accounting, Sales etc).
|
||||
- Designation (CEO, Sales Manager etc).
|
||||
- Grade (A, B, C etc, usually based on seniority).
|
||||
|
||||
### Leave Setup
|
||||
|
||||
To setup Leaves, create:
|
||||
|
||||
- Leave Type (like Sick Leave, Travel Leave etc)
|
||||
- Holiday List (list of annual holidays for the year - these days will not be considered in Leave Applications).
|
||||
|
||||
### Payroll (Salary) Setup
|
||||
|
||||
In ERPNext, salaries have two types of components, earnings (basic salary, expenses paid by the company, like telephone bill, travel allowance etc) and deductions (amounts deducted for taxes, social security etc). To setup payroll, you must first setup all the different types of earnings and deductions. These are
|
||||
|
||||
- Earning Type
|
||||
- Deduction Type
|
||||
|
||||
These are just labels, we will see how to use them when we discuss the payroll section.
|
||||
@ -1,367 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Concepts and Terms"
|
||||
}
|
||||
---
|
||||
Before you start implementation, lets get familiar with the terminology that is used and some basic concepts in ERPNext.
|
||||
|
||||
---
|
||||
|
||||
### Basic Concepts
|
||||
|
||||
#### Company
|
||||
|
||||
This represents the Company records for which ERPNext is setup. With this same setup, you can create multiple Company records, each representing a different legal entity. The accounting for each Company will be different, but they will share the Customer, Supplier and Item records.
|
||||
|
||||
> Setup > Company
|
||||
|
||||
#### Customer
|
||||
|
||||
Represents a customer. A Customer can be an individual or an organizations. You can create multiple Contacts and Addresses for each Customer.
|
||||
|
||||
> Selling > Customer
|
||||
|
||||
#### Supplier
|
||||
|
||||
Represents a supplier of goods or services. Your telephone company is a Supplier, so is your raw materials Supplier. Again, a Supplier can be an individual or an organization and has multiple Contacts and Addresses.
|
||||
|
||||
> Buying > Supplier
|
||||
|
||||
#### Item
|
||||
|
||||
A Product, sub-product or Service that is either bought, sold or manufactured and is uniquely identified.
|
||||
|
||||
> Stock > Item
|
||||
|
||||
#### Account
|
||||
|
||||
An Account is a heading under which financial and business transactions are carried on. For example, “Travel Expense” is an account, “Customer Zoe”, “Supplier Mae” are accounts. ERPNext creates accounts for Customers and Suppliers automatically.
|
||||
|
||||
> Accounts > Chart of Accounts
|
||||
|
||||
#### Address
|
||||
|
||||
An address represents location details of a Customer or Supplier. These can be of different locations such as Head Office, Factory, Warehouse, Shop etc.
|
||||
|
||||
> Selling > Address
|
||||
|
||||
#### Contact
|
||||
|
||||
An individual Contact belongs to a Customer or Supplier or is just an independent. A Contact has a name and contact details like email and phone number.
|
||||
|
||||
> Selling > Contact
|
||||
|
||||
#### Communication
|
||||
|
||||
A list of all Communication with a Contact or Lead. All emails sent from the system are added to the Communication table.
|
||||
|
||||
> Support > Communication
|
||||
|
||||
#### Price List
|
||||
|
||||
A Price List is a place where different rate plans can be stored. It’s a name you give to a set of Item Prices stored under a particular List.
|
||||
|
||||
> Selling > Price List
|
||||
|
||||
> Buying > Price List
|
||||
|
||||
---
|
||||
|
||||
### Accounting
|
||||
|
||||
#### Fiscal Year
|
||||
|
||||
Represents a Financial Year or Accounting Year. You can operate multiple Fiscal Years at the same time. Each Fiscal Year has a start date and an end date and transactions can only be recorded in this period. When you “close” a fiscal year, it's balances are transferred as “opening” balances for the next fiscal year.
|
||||
|
||||
> Setup > Company > Fiscal Year
|
||||
|
||||
#### Cost Center
|
||||
|
||||
A Cost Center is like an Account, but the only difference is that its structure represents your business more closely than Accounts. For example in your Chart of Accounts, you separate your expenses by type (say travel, marketing etc). In your Chart of Cost Centers, you can separate them by product line or business group (for example online sales, retail sales)
|
||||
|
||||
> Accounts > Chart of Cost Centers
|
||||
|
||||
#### Journal Voucher
|
||||
|
||||
A document that contains General Ledger (GL) entries and the sum of Debits and Credits of those entries is the same. In ERPNext you can update Payments, Returns etc using Journal Vouchers.
|
||||
|
||||
> Accounts > Journal Voucher
|
||||
|
||||
#### Sales Invoice
|
||||
|
||||
A bill sent to Customers for delivery of Items (goods or services).
|
||||
|
||||
> Accounts > Sales Invoice
|
||||
|
||||
#### Purchase Invoice
|
||||
|
||||
A bill sent by a Supplier for delivery of Items (goods or services).
|
||||
|
||||
> Accounts > Purchase Invoice
|
||||
|
||||
#### Currency
|
||||
|
||||
ERPNext allows you to book transactions in multiple currencies. There is only one currency for your book of accounts though. While posting your Invoices, payments in different currencies, the amount is converted to the default currency by the specified conversion rate.
|
||||
|
||||
> Setup > Currency
|
||||
|
||||
---
|
||||
|
||||
### Selling
|
||||
|
||||
#### Customer Group
|
||||
|
||||
A classification of Customers, usually based on market segment.
|
||||
|
||||
> Selling > Setup > Customer Group
|
||||
|
||||
#### Lead
|
||||
|
||||
A person who could be a future source of business. A Lead may generate Opportunities. (from: “may lead to a sale”).
|
||||
|
||||
> Selling > Lead
|
||||
|
||||
#### Opportunity
|
||||
|
||||
A potential sale. (from: “opportunity for a business”).
|
||||
|
||||
> Selling > Opportunity
|
||||
|
||||
#### Sales Order
|
||||
|
||||
A note confirming the terms of delivery and price of an Item (product or service) by the Customer. Deliveries, Production Orders and Invoices are made on basis of Sales Orders.
|
||||
|
||||
> Selling > Sales Order
|
||||
|
||||
#### Territory
|
||||
|
||||
A geographical area classification for sales management. You can set targets for Territories and each sale is linked to a Territory.
|
||||
|
||||
> Selling > Setup > Territory
|
||||
|
||||
#### Sales Partner
|
||||
|
||||
A third party distributer / dealer / affiliate / commission agent who sells the company’s products usually for a commission.
|
||||
|
||||
> Selling > Setup > Sales Partner
|
||||
|
||||
#### Sales Person
|
||||
|
||||
Someone who pitches to the Customer and closes deals. You can set targets for Sales Persons and tag them in transactions.
|
||||
|
||||
> Selling > Setup > Sales Person
|
||||
|
||||
---
|
||||
|
||||
### Buying
|
||||
|
||||
#### Purchase Order
|
||||
|
||||
A contract given to a Supplier to deliver the specified Items at the specified cost, quantity, dates and other terms.
|
||||
|
||||
> Buying > Purchase Order
|
||||
|
||||
#### Material Request
|
||||
|
||||
A request made by a system User, or automatically generated by ERPNext based on reorder level or projected quantity in Production Plan for purchasing a set of Items.
|
||||
|
||||
> Buying > Material Request
|
||||
|
||||
---
|
||||
|
||||
### Stock (Inventory)
|
||||
|
||||
#### Warehouse
|
||||
|
||||
A logical Warehouse against which stock entries are made.
|
||||
|
||||
> Stock > Warehouse
|
||||
|
||||
#### Stock Entry
|
||||
|
||||
Material transfer from a Warehouse, to a Warehouse or from one Warehouse to another.
|
||||
|
||||
> Stock > Stock Entry
|
||||
|
||||
#### Delivery Note
|
||||
|
||||
A list of Items with quantities for shipment. A Delivery Note will reduce the stock of Items for the Warehouse from where you ship. A Delivery Note is usually made against a Sales Order.
|
||||
|
||||
> Stock > Delivery Note
|
||||
|
||||
#### Purchase Receipt
|
||||
|
||||
A note stating that a particular set of Items were received from the Supplier, most likely against a Purchase Order.
|
||||
|
||||
> Stock > Purchase Receipt
|
||||
|
||||
#### Serial Number
|
||||
|
||||
A unique number given to a particular unit of an Item.
|
||||
|
||||
> Stock > Serial Number
|
||||
|
||||
#### Batch
|
||||
|
||||
A number given to a group of units of a particular Item that may be purchased or manufactured in a group.
|
||||
|
||||
> Stock > Batch
|
||||
|
||||
#### Stock Ledger Entry
|
||||
|
||||
A unified table for all material movement from one warehouse to another. This is the table that is updated when a Stock Entry, Delivery Note, Purchase Receipt, and Sales Invoice (POS) is made.
|
||||
|
||||
#### Stock Reconciliation
|
||||
|
||||
Update Stock of multiple Items from a spreadsheet (CSV) file.
|
||||
|
||||
> Stock > Stock Reconciliation
|
||||
|
||||
#### Quality Inspection
|
||||
|
||||
A note prepared to record certain parameters of an Item at the time of Receipt from Supplier, or Delivery to Customer.
|
||||
|
||||
> Stock > Quality Inspection
|
||||
|
||||
#### Item Group
|
||||
|
||||
A classification of Item.
|
||||
|
||||
> Stock > Setup > Item Group
|
||||
|
||||
---
|
||||
|
||||
### Human Resource Management
|
||||
|
||||
#### Employee
|
||||
|
||||
Record of a person who has been in present or past, in the employment of the company.
|
||||
|
||||
Human Resources > Employee
|
||||
|
||||
#### Leave Application
|
||||
|
||||
A record of an approved or rejected request for leave.
|
||||
|
||||
> Human Resource > Leave Application
|
||||
|
||||
#### Leave Type
|
||||
|
||||
A type of leave (for example, Sick Leave, Maternity Leave etc.)
|
||||
|
||||
> Human Resource > Leave and Attendance > Leave Type
|
||||
|
||||
#### Salary Manager
|
||||
|
||||
A tool that will help creation of multiple Salary Slips for Employees.
|
||||
|
||||
> Human Resource > Salary and Payroll > Process Payroll
|
||||
|
||||
#### Salary Slip
|
||||
|
||||
A record of the monthly salary given to an Employee.
|
||||
|
||||
> Human Resource > Salary Slip
|
||||
|
||||
#### Salary Structure
|
||||
|
||||
A template identifying all the components of an Employees' salary (earnings) and tax and other social security deductions.
|
||||
|
||||
> Human Resource > Salary and Payroll > Salary Structure
|
||||
|
||||
#### Appraisal
|
||||
|
||||
A record of the performance of an Employee over a specified period based on certain parameters.
|
||||
|
||||
> Human Resources > Appraisal
|
||||
|
||||
#### Appraisal Template
|
||||
|
||||
A template recording the different parameters of Employee performance and their weightage for a particular role.
|
||||
|
||||
> Human Resources > Employee Setup > Appraisal Template
|
||||
|
||||
#### Attendance
|
||||
|
||||
A record indicating presence or absence of an Employee on a particular day.
|
||||
|
||||
> Human Resources > Attendance
|
||||
|
||||
---
|
||||
|
||||
### Manufacturing
|
||||
|
||||
#### Bill of Materials (BOM)
|
||||
|
||||
A list of Operations and Items with their quantities, that are required to produce another Item. A Bill of Materials (BOM) is used to plan purchases and do product costing.
|
||||
|
||||
> Manufacturing > BOM
|
||||
|
||||
#### Workstation
|
||||
|
||||
A place where a BOM operation takes place. It is useful to calculate the direct cost of the product.
|
||||
|
||||
> Manufacturing > Workstation
|
||||
|
||||
#### Production Order
|
||||
|
||||
A document signaling production (manufacture) of a particular Item with specified quantities.
|
||||
|
||||
> Manufacturing > Production Order
|
||||
|
||||
#### Production Planning Tool
|
||||
|
||||
A tool for automatic creation of Production Orders and Purchase Requests based on Open Sales Orders in a given period.
|
||||
|
||||
> Manufacturing > Production Planning Tool
|
||||
|
||||
---
|
||||
|
||||
### Website
|
||||
|
||||
#### Blog Post
|
||||
|
||||
A short article that appears in the “Blog” section of the website generated from the ERPNext website module. Blog is a short from of “Web Log”.
|
||||
|
||||
> Website > Blog Post
|
||||
|
||||
#### Web Page
|
||||
|
||||
A web page with a unique URL (web address) on the website generated from ERPNext.
|
||||
|
||||
> Website > Web Page
|
||||
|
||||
---
|
||||
|
||||
### Setup / Customization
|
||||
|
||||
#### Custom Field
|
||||
|
||||
A user defined field on a form / table.
|
||||
|
||||
Setup > Customize ERPNext > Custom Field
|
||||
|
||||
#### Global Defaults
|
||||
|
||||
This is the section where you set default values for various parameters of the system.
|
||||
|
||||
Setup > Data > Global Defaults
|
||||
|
||||
#### Print Heading
|
||||
|
||||
A title that can be set on a transaction just for printing. For example, you want to print a Quotation with a title “Proposal” or “Pro forma Invoice”.
|
||||
|
||||
> Setup > Branding and Printing > Print Headings
|
||||
|
||||
#### Terms and Conditions
|
||||
|
||||
Text of your terms of contract.
|
||||
|
||||
> Selling > Setup > Terms and Conditions
|
||||
|
||||
#### Unit of Measure (UOM)
|
||||
|
||||
How quantity is measured for an Item. For example (Kg, No, Pair, Packet) etc.
|
||||
|
||||
> Stock > Setup > UOM
|
||||
|
||||
@ -1,39 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Implementation",
|
||||
"_toc": [
|
||||
"docs.user.implement.strategy",
|
||||
"docs.user.implement.concepts"
|
||||
]
|
||||
}
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
We have seen dozens of ERP implementations over the past few years and we realize that successful implementation is a lot about intangibles and attitude.
|
||||
|
||||
**ERPs are not required.**
|
||||
|
||||
Like exercise.
|
||||
|
||||
Human body may seem like it does not require exercise today or even tomorrow, but in the long run, if you wish to maintain your body and its health, you should get on the treadmill.
|
||||
|
||||
In the same way, ERPs improve the health of your organization over a long run by keeping it fit and efficient. The more you delay putting things in order, the more time you lose, and the closer you get to a major disaster.
|
||||
|
||||
So when you start implementing an ERP, keep your sight on the long term benefits. Like exercise, its painful in the short run, but will do wonders if you stay on course.
|
||||
|
||||
---
|
||||
|
||||
## The Champion
|
||||
|
||||
ERP means organization wide change and it does not happen without effort. Every change requires a champion and it is the duty of the champion to organize and energize the entire team towards implementation. The champion needs to be resilient incase something goes wrong .
|
||||
|
||||
In many organizations we have seen, the champion is most often the owner or a senior manager. Occasionally, the champion is an outsider who is hired for a particular purpose.
|
||||
|
||||
In either case, you must identify your champion first.
|
||||
|
||||
Most likely it's **you!**
|
||||
|
||||
Lets Begin!
|
||||
@ -1,30 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Implementation Strategy"
|
||||
}
|
||||
---
|
||||
Before you start managing your Operations in EPRNext, you must first become familiar with the system and the terms used. For this we recommend implementation should happen in two phases.
|
||||
|
||||
- A Test Phase, where you enter dummy records representing your day to day transactions and a - Live Phase, where we start entering live data.
|
||||
|
||||
### Test Phase
|
||||
|
||||
- Read the Manual
|
||||
- Follow the Five-Day-Setup Module or the instructions given below.
|
||||
- Create your first Customer, Supplier and Item. Add a few more so you get familiar with them.
|
||||
- Create Customer Groups, Item Groups, Warehouses, Supplier Groups, so that you can classify your Items.
|
||||
- Complete a standard sales cycle - Lead > Opportunity > Quotation > Sales Order > Delivery Note > Sales Invoice > Payment (Journal Voucher)
|
||||
- Complete a standard purchase cycle - Material Request > Purchase Order > Purchase Receipt > Payment (Journal Voucher).
|
||||
- Complete a manufacturing cycle (if applicable) - BOM > Production Planning Tool > Production Order > Material Issue > Sales Return
|
||||
|
||||
> Tip: Use the 30-day free trial at [erpnext.com](https://erpnext.com) to take your test drive.
|
||||
|
||||
### Live Phase
|
||||
|
||||
Once you are familiar with ERPNext, start entering your live data!
|
||||
|
||||
- Clean up the account of test data or better, start a fresh install.
|
||||
- Setup all the modules with Customer Groups, Item Groups, Warehouses, BOMs etc.
|
||||
- Import Customers, Suppliers, Items, Contacts and Addresses using Data Import Tool.
|
||||
- Import opening stock using Stock Reconciliation Tool.
|
||||
- Create opening accounting entries via Journal Voucher and create outstanding Sales Invoices and Purchase Invoices.
|
||||
@ -1,70 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Introduction",
|
||||
"_toc": [
|
||||
"docs.user.intro.open_source",
|
||||
"docs.user.intro.try",
|
||||
"docs.dev.install",
|
||||
"docs.user.help"
|
||||
]
|
||||
}
|
||||
---
|
||||
## What is an ERP and why should I care?
|
||||
|
||||
(If you are already convinced you need an all-in-one system for your organization, you can skip this page.)
|
||||
|
||||
If you are running a small business that has a few employees, you understand that it's hard to manage the dynamic nature of doing businesses. You are already using a software like Accounting, and may be some more to manage your inventory and sales (or CRM).
|
||||
|
||||
An ERP brings all of this together in one place.
|
||||
|
||||
Small businesses are not so different from large ones. They contain most of the complexities of a large business along with many other constraints. Small businesses have to communicate with customers, do accounts, pay taxes, do payroll, manage timelines, deliver quality, answer questions, and keep everyone happy just like in large businesses.
|
||||
|
||||
Large businesses have the advantage of using advanced data systems to manage their process efficiently. Small businesses, on the other hand, typically struggle to keep things organized. They often use a mix of apps like spreadsheets, accounting software, web CRM etc to manage.The problem is, not everyone is on the same page. An ERP changes that.
|
||||
|
||||
---
|
||||
|
||||
## What is ERPNext?
|
||||
|
||||
ERPNext helps you to manage all your business information in one application and use it to manage operations and take decisions based on data.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Among other things, ERPNext will help you to:
|
||||
|
||||
- Track all Invoices and Payments.
|
||||
- Know what quantity of which product is available in stock.
|
||||
- Identify open customer queries.
|
||||
- Manage payroll.
|
||||
- Assign tasks and follow up on them.
|
||||
- Maintain a database of all your customers, suppliers and their contacts.
|
||||
- Prepare quotes.
|
||||
- Get reminders on maintenance schedules.
|
||||
- Publish your website.
|
||||
|
||||
And a lot lot lot more.
|
||||
|
||||
---
|
||||
|
||||
## Why Should I Use ERPNext?
|
||||
|
||||
ERPNext is a modern tool that covers not only accounting but also all other business functions, on an integrated platform. It has many benefits over both traditional accounting as well as ERP applications.
|
||||
|
||||
### Benefits over traditional accounting software:
|
||||
|
||||
- Do a lot more than just accounting! Manage inventory, billing, quotes, leads, payroll and a lot more.
|
||||
- Keep all your data safe and in one place. Don’t keep hunting for data when you need it across spreadsheets and different computers.
|
||||
-Manage everyone on the same page. All users get the same updated data.
|
||||
- Stop repetitive work. Don’t enter the same information from your word processor to your accounting tool. It's all integrated.
|
||||
- Keep track. Get the entire history of a customer or a deal in one place.
|
||||
|
||||
### Benefits over big ERPs
|
||||
|
||||
- $$$ - Saves money.
|
||||
- **Easier to configure:** Big ERPs are notoriously hard to setup and will ask you a zillion questions before you can do something meaningful.
|
||||
- **Easier to use:** Modern web like user interface will keep your users happy and in familiar territory.
|
||||
- **Open Source :** This software is always free and you can host it anywhere you like.
|
||||
@ -1,25 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Open Source"
|
||||
}
|
||||
---
|
||||
The source code is an Open Source software. It is open for anyone to understand, extend or improve. And it is free!
|
||||
|
||||
Advantages of an Open Source software are:
|
||||
|
||||
1. You can choose to change your service provider anytime.
|
||||
1. You can host the application anywhere, including your own server to gain complete ownership and privacy of the data.
|
||||
1. You can access a community to support you, incase you need help. You are not dependant on your service provider.
|
||||
1. You can benefit from using a product that is critiqued and used by a wide range of people, who have reported hundreds of issues and suggestions to make this product better, and this will always continue.
|
||||
|
||||
---
|
||||
|
||||
### Alternatives
|
||||
|
||||
There are many Open Source ERPs you can consider. Popular ones are:
|
||||
|
||||
1. OpenERP
|
||||
1. OpenBravo
|
||||
1. Apache OfBiz
|
||||
1. xTuple
|
||||
1. Compiere (and forks)
|
||||
@ -1,39 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label":"Getting Started with ERPNext"
|
||||
}
|
||||
---
|
||||
There are many ways to get started with ERPNext.
|
||||
|
||||
### 1. See the Demo
|
||||
|
||||
If you want to check out the user interface and **feel** the application, just see the demo at:
|
||||
|
||||
- [https://demo.erpnext.com](https://demo.erpnext.com)
|
||||
|
||||
### 2. Get a Free 30 day Trial at ERPNext.com
|
||||
|
||||
If you like the feel and want to set it up for your own company, you can take a 30 day free trial (no credit card details required) at ERPNext.com
|
||||
|
||||
ERPNext.com is managed by the organization (Web Notes) that publishes ERPNext. You can do a trial run with your own account by [signing up on the website](https://erpnext.com/pricing-and-signup).
|
||||
|
||||
You can also decide to host your application at ERPNext.com by buying the hosting plans. This way you support the organization that develops and improves ERPNext. You also get one-to-one functional (usage) support with the hosting plans.
|
||||
|
||||
### 3. Download a Virtual Machine
|
||||
|
||||
To avoid the trouble of installing an instance, ERPNext is available as a Virtual Image (a full loaded operating system with ERPNext installed). You can use this on **any** platform including Microsoft Windows.
|
||||
|
||||
[Click here to see instructions on how to use the Virtual Image](docs.download.html)
|
||||
|
||||
### 4. Install ERPNext on your Unix/Linux/Mac machine
|
||||
|
||||
ERPNext is reasonably easy to install on a Unix like operating system and requires:
|
||||
|
||||
1. MySQL database
|
||||
1. Apache Web Server
|
||||
1. Python
|
||||
1. Memcached
|
||||
|
||||
to be installed.
|
||||
|
||||
[More instructions on this page](docs.dev.install.html).
|
||||
@ -1,110 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Accounting Knowledge"
|
||||
}
|
||||
---
|
||||
|
||||
Chart of Accounts represents a tree like representation of all accounting heads, used to represent company's financial information. There are two types of accounts: Balance Sheet and Profit and Loss Statement accounts. Balance Sheet consists of Assets and Liabilities accounts and Profit and Loss Statement accounts consists of Incomes and Expenses.
|
||||
|
||||
**Assets:** Bank and Cash balances, outstanding amounts of customers and all other assets are recorded here.
|
||||
|
||||
**Liabilities:** All the company's liabilities like shareholder's capital, outstanding amount to be paid to suppliers, taxes to be paid to concerned to authorities are recorded under this group.
|
||||
|
||||
**Income:** Income from direct/indirect sales.
|
||||
|
||||
**Expenses:** All the expenses to run the business, like salaries, purchases, rent etc. are recorded here.
|
||||
|
||||
### Debit and Credit
|
||||
|
||||
Each of these accounts are either "Debit" or "Credit" type. Assets, Expenses are "Debit" accounts and Liabilities, Incomes are "Credit" accounts.
|
||||
|
||||
Accounting Entries
|
||||
|
||||
The balance of account can be increased / decreased, depending on account type and transaction type.
|
||||
|
||||
<table class="table table-bordered text-center">
|
||||
<thead>
|
||||
<tr class="active">
|
||||
<td>Account Type</td>
|
||||
<td>Transaction Type</td>
|
||||
<td>Effect on account balance</td>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Debit</td>
|
||||
<td>Debit</td>
|
||||
<td>Increases</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Debit</td>
|
||||
<td>Credit</td>
|
||||
<td>Decreases</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Credit</td>
|
||||
<td>Credit</td>
|
||||
<td>Increases</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Credit</td>
|
||||
<td>Debit</td>
|
||||
<td>Decreases</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
### Double Entry
|
||||
|
||||
This means that every accounting entry has two parts, one debit and one credit and must affect two separate accounts. If you add or deduct to one account, some other account somewhere else must also be affected. See the example below:
|
||||
|
||||
1. Company sells a laptop worth 50000 to Customer A and delivers that with an invoice.
|
||||
|
||||
As the company will receive a payment from customer, the customer is considered as an asset account. For booking income, company maintains an account called "Sales of Laptop". So, entries will be done in the following manner:
|
||||
|
||||
<table class="table table-bordered text-center">
|
||||
<thead>
|
||||
<tr class="active">
|
||||
<td>Account</td>
|
||||
<td>Debit</td>
|
||||
<td>Credit</td>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Customer A</td>
|
||||
<td>50000</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Sales of Laptop</td>
|
||||
<td></td>
|
||||
<td>50000</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
Customer A has made the payment, so customer balance should decreased based on the paid amount, which will increase "Cash" balance.
|
||||
|
||||
<table class="table table-bordered text-center">
|
||||
<thead>
|
||||
<tr class="active">
|
||||
<td>Account</td>
|
||||
<td>Debit</td>
|
||||
<td>Credit</td>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Customer A</td>
|
||||
<td></td>
|
||||
<td>50000</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Cash</td>
|
||||
<td>50000</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
@ -1,38 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Accounting Entries"
|
||||
}
|
||||
---
|
||||
The concept of accounting is explained with an example given below:
|
||||
We will take a "Tea Stall" as a company and see how to book accounting entries for the business.
|
||||
|
||||
- Mama (The Tea-stall owner) invests Rs 25000 to start the business.
|
||||
|
||||
|
||||
|
||||
|
||||
Analysis: Mama invested 25000 in company, hoping to get some profit. In other words, company is liable to pay 25000 to Mama in the future. So, account "Mama" is a liability account and it is credited. Company's cash balance will be increased due to the investment, "Cash" is an asset to the company and it will debited.
|
||||
|
||||
- The company needs equipments (Stove, teapot, cups etc) and raw materials (tea, sugar, milk etc) immediately. He decides to buy from the nearest general store "Super Bazaar" who is a friend so that he gets some credit. Equipments cost him 2800 and raw materials worth of 2200. He pays 2000 out of total cost 5000.
|
||||
|
||||
|
||||
|
||||
Analysis: Equipments are "Fixed Assets" (because they have a long life) of the company and raw materials "Current Assets" (since they are used for day-to-day business), of the company. So, "Equipments" and "Stock in Hand" accounts have been debited to increase the value. He pays 2000, so "Cash" account will be reduced by that amount, hence credited and he is liable to pay 3000 to "Super Bazaar" later, so Super Bazaar will be credited by 3000.
|
||||
|
||||
- Mama (who takes care of all entries) decides to book sales at the end of the every day, so that he can analyze daily sales. At the end of the very first day, the tea stall sells 325 cups of tea, which gives net sales of Rs. 1575. The owner happily books his first day sales.
|
||||
|
||||
|
||||
|
||||
Analysis: Income has been booked in "Sales of Tea" account which has been credited to increase the value and the same amount will be debited to "Cash" account. Lets say, to make 325 cups of tea, it costs Rs. 800, so "Stock in Hand" will be reduced (Cr) by 800 and expense will be booked in "Cost of goods sold" account by same amount.
|
||||
|
||||
At the end of the month, the company paid the rent amount of stall (5000) and salary of one employee (8000), who joined from the very first day.
|
||||
|
||||
|
||||
|
||||
### Booking Profit
|
||||
|
||||
As month progress, company purchased more raw materials for the business. After a month he books profit to balance the "Balance Sheet" and "Profit and Loss Statements" statements. Profit belongs to Mama and not the company hence its a liability for the company (it has to pay it to Mama). When the Balance Sheet is not balanced i.e. Debit is not equal to Credit, the profit has not yet been booked. To book profit, the following entry has to be made:
|
||||
|
||||
|
||||
|
||||
Explanation: Company's net sales and expenses are 40000 and 20000 respectively. So, company made a profit of 20000. To make the profit booking entry, "Profit or Loss" account has been debited and "Capital Account" has been credited. Company's net cash balance is 44000 and there is some raw materials available worth 1000 rupees.
|
||||
@ -1,16 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Attachment and CSV files"
|
||||
}
|
||||
---
|
||||
|
||||
#### How to Attach files?
|
||||
|
||||
When you open a form, on the right sidebar, you will see a section to attach files. Click on “Add” and select the file you want to attach. Click on “Upload” and you are set.
|
||||
|
||||
#### What is a CSV file?
|
||||
|
||||
A CSV (Comma Separated Value) file is a data file that you can upload into ERPNext to update various data. Any spreadsheet file from popular spreadsheet applications like MS Excel or Open Office Spreadsheet can be saved as a CSV file.
|
||||
|
||||
If you are using Microsoft Excel and using non-English characters, make sure to save your file encoded as UTF-8. For older versions of Excel, there is no clear way of saving as UTF-8. So save your file as a CSV, then open it in Notepad, and save as “UTF-8”. (Sorry blame Microsoft for this!)
|
||||
|
||||
@ -1,73 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "DocType"
|
||||
}
|
||||
---
|
||||
|
||||
|
||||
|
||||
ERPNext is a based on a “metadata” (data about data) framework that helps define all the different types of documents in the system. The basic building block of ERPNext is a DocType.
|
||||
|
||||
A DocType represents both a table in the database and a form from which a user can enter data.
|
||||
|
||||
Many DocTypes are single tables, but some work in groups. For example, Quotation has a “Quotation” DocType and a “Quotation Item” doctype for the Items table, among others. DocTypes contain a collection of fields called DocFields that form the basis of the columns in the database and the layout of the form.
|
||||
|
||||
<table class="table table-bordered text-left">
|
||||
<thead>
|
||||
<tr class="active">
|
||||
<td width="30%">Column</td>
|
||||
<td>Description</td>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Name</td>
|
||||
<td>Name of the record</td>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Owner</td>
|
||||
<td>Creator and Owner of the record</td>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Created on</td>
|
||||
<td>Date and Time of Creation</td>
|
||||
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Modified On </td>
|
||||
<td>Date and Time of Modification</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Docstatus</td>
|
||||
<td>Status of the record<br>
|
||||
0 = Saved/Draft<br>
|
||||
1 = Submitted<br>
|
||||
2 = Cancelled/Deleted
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Parent</td>
|
||||
<td>Name of the Parent</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Parent Type</td>
|
||||
<td>Type of Parent</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Parent Field</td>
|
||||
<td>Specifying the relationship with the parent (there can be multiple child relationships with the same DocType).</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Index(idx)</td>
|
||||
<td>Index (sequence) of the record in the child table.</td>
|
||||
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
#### Single DocType
|
||||
|
||||
There are a certain type of DocTypes that are “Single”, i.e. they have no table associated and have only one record of its fields. DocTypes such as Global Defaults, Production Planning Tool are “Single” DocTypes.
|
||||
|
||||
@ -1,201 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "DocType-Fields"
|
||||
}
|
||||
---
|
||||
|
||||
#### Field Columns
|
||||
|
||||
In the fields table, there are many columns. The columns of the field table are explained below:
|
||||
|
||||
<table class="table table-bordered text-left">
|
||||
<thead>
|
||||
<tr class="active">
|
||||
<td width="30%">Column</td>
|
||||
<td>Description</td>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Label</td>
|
||||
<td>Field Label (that appears in the form).</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Type</td>
|
||||
<td>Field Type</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Name</td>
|
||||
<td>Column name in the database, must be code friendly with no white spaces, special characters and capital letters.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>options</td>
|
||||
<td>Field settings:<br>
|
||||
For Select: List of options (each on a new line).<br>
|
||||
For Link: DocType that is “linked”.<br>
|
||||
For HTML: HTML Content
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Perm Level</td>
|
||||
<td>Permission level (number) of the field. You can group fields by numbers, called levels, and apply rules on the levels.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Width</td>
|
||||
<td>Width of the field (in pixels) - useful for “Table” types.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Reqd</td>
|
||||
<td>Checked if field is mandatory (required).</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>In Filter</td>
|
||||
<td>Checked if field appears as a standard filter in old style reports.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Hidden</td>
|
||||
<td>Checked if field is hidden.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Print Hide</td>
|
||||
<td>Checked if field is hidden in Print Formats.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Report Hide</td>
|
||||
<td>Checked if field is hidden in old style reports.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Allow on Submit</td>
|
||||
<td>Checked if this field can be edited after the document is “Submitted”.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Depends On</td>
|
||||
<td>The fieldname of the field that will decide whether this field will be shown or hidden. It is useful to hide un-necessary fields.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Description</td>
|
||||
<td>Description of the field</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Default</td>
|
||||
<td>Default value when a new record is created.<br>
|
||||
Note: “user” will set the current user as default and “today” will set today’s date (if the field is a Date field).</td>
|
||||
</tr>
|
||||
<tbody>
|
||||
<table>
|
||||
|
||||
|
||||
#### Field Types and Options
|
||||
|
||||
Here is a list of the different types of fields used to make / customize forms in ERPNext.
|
||||
|
||||
<table class="table table-bordered text-left">
|
||||
<thead>
|
||||
<tr class="active">
|
||||
<td width="30%">Type</td>
|
||||
<td>Description</td>
|
||||
<td>Options/Setting</td>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Data</td>
|
||||
<td>Single line text field with 180 characters</td>
|
||||
<td> </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Select</td>
|
||||
<td>Select from a pre-determined items in a drop-down.</td>
|
||||
<td>The “Options” contains the drop-down items, each on a new row</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Link</td>
|
||||
<td>Link an existing document / record</td>
|
||||
<td>Options contains the name of the type of document (DocType)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Currency</td>
|
||||
<td>Number with 2 decimal places, that will be shown separated by commas for thousands etc. in Print.</td>
|
||||
<td>e.g. 1,000,000.00</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Float</td>
|
||||
<td>Number with 6 decimal places.</td>
|
||||
<td>e.g. 3.141593</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Int</td>
|
||||
<td>Integer (no decimals)</td>
|
||||
<td>e.g. 100</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Date</td>
|
||||
<td>Date</td>
|
||||
<td>Format can be selected in Global Defaults</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Time</td>
|
||||
<td>Time</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td colspan="3" class="active">Text</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Text</td>
|
||||
<td>Multi-line text box without formatting features</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Text editor</td>
|
||||
<td>Multi-line text box with formatting toolbar etc</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Code</td>
|
||||
<td>Code Editor</td>
|
||||
<td>Options can include the type of language for syntax formatting.
|
||||
Eg JS / Python / HTML</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td colspan="3" class="active">Table (Grid)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Table</td>
|
||||
<td>Table of child items linked to the record.</td>
|
||||
<td>Options contains the name of the DocType of the child table. For example “Sales Invoice Item” for “Sales Invoice”</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td colspan="3" class="active">Layout</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Section Break</td>
|
||||
<td>Break into a new horizontal section.</td>
|
||||
<td>The layout in ERPNext is evaluated from top to bottom.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Column Break</td>
|
||||
<td>Break into a new vertical column.</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>HTML</td>
|
||||
<td>Add a static text / help / link etc in HTML</td>
|
||||
<td>Options contains the HTML.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td colspan="3" class="active">Action</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Button</td>
|
||||
<td>Button</td>
|
||||
<td>[for developers only]</td>
|
||||
</tr>
|
||||
<tbody>
|
||||
<table>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,14 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Engineer-to-Order Manufacturing"
|
||||
}
|
||||
---
|
||||
|
||||
Engineer-to-order manufacturing is a strategy where the product is designed and manufactured based on very specific customer requirements. Since the end product tends to be complex, customers may engage with the ETO company throughout the entire design and manufacturing phases, to ensure that their specifications are met. This strategy is used by construction, fabrication industry, etc.
|
||||
|
||||
Since most specifications like design, requirements, engineering changes etc are often tossed back and forth several times between the ETO company and the customer, either party can become confused if the exchange of product information is poorly managed. Managing and identifying parts for production is an important step.
|
||||
|
||||
Engineered-to-order products are often built from difficult to source parts, expensive parts and highly engineered components. Thus, acquiring the necessary product components can be a time consuming and costly endeavor, causing issues before and during production runs.
|
||||
|
||||
To manage ETO products maintain a consistent serial number records and create a Bill of Material for each product. Focus on the bill of materials rather then on the estimation and budgeting of the product.
|
||||
|
||||
@ -1,10 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Fiscal-Year"
|
||||
}
|
||||
---
|
||||
|
||||
A fiscal year is also known as a financial year or a budget year. It is used for calculating financial statements in businesses and other organisations. The fiscal year may or may not be the same as a calendar year. For tax purposes, companies can choose to be calendar-year taxpayers or fiscal-year taxpayers. In many jurisdictions, regulatory laws regarding accounting and taxation require such reports once per twelve months. However, it is not mandatory that the period should be a calendar year (that is, 1 January to 31 December).
|
||||
|
||||
A fiscal year usually starts at the beginning of a quarter, such as April 1, July 1 or October 1. However, most companies' fiscal year also coincides with the calendar year, which starts January 1. For the most part, it is simpler and easier that way. For some organizations, there are advantages in starting the fiscal year at a different time. For example, businesses that are seasonal might start their fiscal year on July 1 or October 1. A business that has most of its income in the fall and most of its expenses in the spring might also choose to start its fiscal year on October 1. That way, they know what their income will be for that year, and can adjust their expenses to maintain their desired profit margins.
|
||||
|
||||
@ -1,14 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Make-to-Order Manufacturing"
|
||||
}
|
||||
---
|
||||
|
||||
Make-to-order is a manufacturing process in which manufacturing starts only after a customer's order is received.
|
||||
|
||||
The company has some standard items but the product is only made when the customer places an order. This is true for furniture, for designer gift items etc.
|
||||
|
||||
Manufacturing after receiving customer's orders means to start a pull-type supply chain operation because manufacturing is performed when demand is confirmed, i.e. being pulled by demand.
|
||||
|
||||
In this type of manufacturing, production orders are linked to one or more sales orders.
|
||||
|
||||
@ -1,16 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Make-to-Stock Manufacturing"
|
||||
}
|
||||
---
|
||||
|
||||
Make-to-stock manufacturing is a system based on keeping stocks ready for customers in order to provide instant availability to customers. Products like FMCG goods and electronics are made and stocked. Here, the production cycle is completed before the sales orders are made.
|
||||
|
||||
This strategy is used by businesses to match production with consumer demand forecasts. The make-to-stock (MTS) method forecasts demand, to determine how much stock should be produced. If demand for the product can be accurately forecasted, the MTS strategy can be an efficient choice.
|
||||
|
||||
The main drawback to the make-to-stock (MTS) method is that it relies heavily on the accuracy of demand forecasts. Inaccurate forecasts will lead to losses stemming from excessive inventory or stockouts.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,84 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Format Using Markdown"
|
||||
}
|
||||
---
|
||||
|
||||
Markdown is a simple way of writing text to format your content. Markdown allows you easy ways to format.
|
||||
|
||||
1. Headings (h1 (largest), h2, h3, h4 and so on)
|
||||
1. Paragraphs
|
||||
1. Lists (numbered or bulleted)
|
||||
1. Hyper links (links to other pages)
|
||||
1. Images
|
||||
1. Code
|
||||
1. Embed HTML (HTML tags within your text)
|
||||
|
||||
#### Headings
|
||||
|
||||
Headings are specified by adding a `#` (hash) at the beginning of the line. The more the number of hashes, the smaller the heading:
|
||||
|
||||
# This is a large heading.
|
||||
|
||||
### This is a smaller heading.
|
||||
|
||||
#### Paragraphs
|
||||
|
||||
To start a new paragraph, just make sure that there is an empty line at the beginning and end of the paragraph.
|
||||
|
||||
To format text as **bold** or with _italics_ format as follows:
|
||||
|
||||
**This text** is **bold** and _this one_ is with _italics_
|
||||
|
||||
#### Lists
|
||||
|
||||
To define numbered lists, start your link with a number and a dot (.) and ensure there is a blank line before and after the list. The numbers are automatically generated so it does not matter what number you put:
|
||||
|
||||
1. list 1st item
|
||||
1. second item
|
||||
1. and so on
|
||||
1. and so forth
|
||||
|
||||
To define bulleted lists, start your items with a hyphen (-)
|
||||
|
||||
- item 1
|
||||
- item 2
|
||||
- item 3
|
||||
|
||||
To nest lists within one another, put four spaces to indent your inner list as follows:
|
||||
|
||||
1. item 1
|
||||
1. item 2
|
||||
- sub item 1
|
||||
- sub item 2
|
||||
1. item 3
|
||||
|
||||
#### Links (to other pages)
|
||||
|
||||
Links to other pages can be defined by adding your text in box brackets [] followed by the link in round brackets ()
|
||||
|
||||
[This is an external link](http://example.com)
|
||||
[A link within the site](my-page.html)
|
||||
|
||||
#### Images
|
||||
|
||||
Images can be added by adding an exclamation ! before the link.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Code
|
||||
|
||||
To add a code block, just leave a blank line before and after the block and make sure all code line are indented by four spaces:
|
||||
|
||||
This is normal text
|
||||
|
||||
This is a code block
|
||||
|
||||
#### HTML
|
||||
|
||||
You can embed any kind of HTML tags within your code. Any content written within HTML tags will not be formatted.
|
||||
|
||||
[Detailed description of the markdown format](http://daringfireball.net/projects/markdown/syntax)
|
||||
|
||||
|
||||
@ -1,19 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Knowledge Library",
|
||||
"_toc": [
|
||||
"docs.user.knowledge.fiscal_year",
|
||||
"docs.user.knowledge.accounting",
|
||||
"docs.user.knowledge.accounting_entries",
|
||||
"docs.user.knowledge.doctype",
|
||||
"docs.user.knowledge.doctype_fields",
|
||||
"docs.user.knowledge.attachment_csv",
|
||||
"docs.user.knowledge.markdown",
|
||||
"docs.user.knowledge.make-to-stock",
|
||||
"docs.user.knowledge.make-to-order",
|
||||
"docs.user.knowledge.engineer-to-order"
|
||||
]
|
||||
}
|
||||
---
|
||||
Knowledge Library contains definitions and explanations of various management concepts. This page is created for users who wish to elaborate their conceptual knowledge.
|
||||
|
||||
@ -1,30 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Bill of Materials"
|
||||
}
|
||||
---
|
||||
At the heart of the Manufacturing system is the **Bill of Materials** (BOM). The **BOM** is a list of all materials (either bought or made) and operations that go into a finished product or sub-Item. In ERPNext, the component could have its own BOM hence forming a tree of Items with multiple levels.
|
||||
|
||||
To make accurate Purchase Requests, you must always maintain correct BOMs. To make a new BOM:
|
||||
|
||||
> Manufacturing > Bill of Materials > New BOM
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
In the BOM form:
|
||||
|
||||
- Select the Item for which you want to make the BOM.
|
||||
- Add the operations that you have to go through to make that particular Item in the “Operations” table. For each operation, you will be asked to enter a Workstation. You must create new Workstations as and when necessary.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- Add the list of Items you require for each operation, with its quantity. This Item could be a purchased Item or a sub-assembly with its own BOM. If the row Item is a manufactured Item and has multiple BOMs, select the appropriate BOM.
You can also define if a part of the Item goes into scrap.
|
||||
|
||||
Workstations are defined only for product costing purposes not inventory. Inventory is tracked in Warehouses not Workstations.
|
||||
|
||||
> The “Full BOM” section will list all the Items of that BOM right up to the lower most child node. This table is automatically updated if any of the BOMs of the sub-Items are updated.
|
||||
@ -1,56 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Manufacturing",
|
||||
"_toc": [
|
||||
"docs.user.mfg.bom",
|
||||
"docs.user.mfg.planning",
|
||||
"docs.user.mfg.production_order"
|
||||
]
|
||||
}
|
||||
---
|
||||
The Manufacturing module in ERPNext helps you to maintain multi-level Bill of Materials (BOMs) for your Items. It helps you in Product Costing, planing your production via Production Plan, creating Production Orders for your manufacturing shop floors and planing your inventory by getting your material requirement via BOMs (also called Material Requirements Planning MRP).
|
||||
|
||||
### Types of Production Planning
|
||||
|
||||
Broadly there are three types of Production Planning Systems
|
||||
|
||||
- Make-to-Stock: In these systems, production is planned based on a forecast and the Items are then sold to distributors or customers. All fast moving consumer goods that are sold in retail shops like soaps, packaged water etc and electronics like phones etc are Made to Stock.
|
||||
- Make-to-Order: In these systems, manufacturing takes place after a firm order is placed by a Customer.
|
||||
- Engineer-to-Order: In this case each sale is a separate Project and has to be designed and engineered to the requirements of the Customer. Common examples of this are any custom business like furniture, machine tools, speciality devices, metal fabrication etc.
|
||||
|
||||
Most small and medium sized manufacturing businesses are based on a make-to-order or engineer-to-order system and so is ERPNext.
|
||||
|
||||
For engineer-to-order systems, the Manufacturing module should be used along with the Projects module.
|
||||
|
||||
#### Manufacturing and Inventory
|
||||

|
||||
You can track work-in-progress by creating work-in-progress Warehouses.
|
||||
|
||||
ERPNext will help you track material movement by automatically creating Stock Entries from your Production Orders by building from Bill of Materials.
|
||||
|
||||
|
||||
---
|
||||
|
||||
### Material Requirements Planning (MRP):
|
||||
|
||||
The earliest ERP systems were made for manufacturing. The earliest adopters were automobile companies who had thousands of raw materials and sub-assemblies and found it very hard to keep track of requirements and plan purchases. They started using computers to build the material requirements from forecasts and Bill of Materials.
|
||||
|
||||
Later these systems were expanded to include Finances, Payroll, Order Processing, and Purchasing and thus became the more generic Enterprise Resource Systems (ERP). More recently Customer Relationship Management (CRM) was added as a function and is now an integral part of ERP systems.
|
||||
|
||||
These days the term ERP is used to describe systems that help manage any kind of organization like education institutes (Education ERP) or Hospitals (Hospital ERP) and so on.
|
||||
|
||||
---
|
||||
|
||||
### Best Practice: Lean Manufacturing
|
||||
|
||||
The state of art manufacturing philosophy (the rationale behind the planning processes) comes from Japanese auto major Toyota. At the time when American manufacturers depended on MRP systems to plan their manufacturing based on their sales forecasts, they turned around the problem by discovering a leaner way of planning their production. They realized that:
|
||||
|
||||
The biggest cause of wastage in manufacturing is variation (in product and quantity).
|
||||
|
||||
So they standardized their products and sub-assemblies and sold fixed quantities based on what they produced or did not produce based on what they sold. This way, they had an extremely predictable and stable product mix. If they sold less than planned, they would simply stop production.
|
||||
|
||||
Their card signaling system kanban, would notify all their suppliers to stop production too. Hence they never used any of the complex material planning tools like MRP to play day-to-day material requirements, but a simple signaling system that said either STOP or GO.
|
||||
|
||||
They combined this system with neatly managed factories with well labeled racks.
|
||||
|
||||
Small manufacturing companies are usually make-to-order or engineer-to-order and can hardly afford to have a high level of standardization. Thus small manufacturing businesses should aim for repeatability by innovating processes and creating a common platform for products.
|
||||
@ -1,71 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Production Planning Tool"
|
||||
}
|
||||
---
|
||||
Production Planning Tool helps you plan production and purchase of Items for a period (usually a week or a month).
|
||||
|
||||
This list of Items can be generated from the open Sales Orders in the system and will generate:
|
||||
|
||||
- Production Orders for each Item.
|
||||
- Purchase Requests for Items whose Projected Quantity is likely to fall below zero.
|
||||
|
||||
To use the Production Planning Tool, go to:
|
||||
|
||||
> Manufacturing > Production Planning Tool
|
||||
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
#### Step 1: Select and get Sales Order
|
||||
|
||||
Select sales orders for MRP using filters (Time, Item, and Customer)
|
||||
|
||||
|
||||
|
||||
|
||||
Click on Get Sales Order to generate a list.
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
#### Step 2: Get Item from Sales Orders.
|
||||
|
||||
You can add/remove or change quantity of these Items.
|
||||
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
#### Step 3: Create Production Orders
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
#### Step 4: Create Material Request
|
||||
|
||||
Create Material Request for Items with projected shortfall.
|
||||
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
The Production Planning Tool is used in two stages:
|
||||
|
||||
- Selection of Open Sales Orders for the period based on “Expected Delivery Date”.
|
||||
- Selection of Items from those Sales Orders.
|
||||
|
||||
|
||||
The tool will update if you have already created Production Orders for a particular Item against its Sales Order (“Planned Quantity”).
|
||||
|
||||
You can always edit the Item list and increase / reduce quantities to plan your production.
|
||||
|
||||
> Note: How do you change a Production Plan? The output of the Production Planning Tool is the Production Order. Once your orders are created, you can change them by amending the Production Orders.
|
||||
@ -1,36 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Production Order"
|
||||
}
|
||||
---
|
||||
Production Order (also called as Work Order) is a document that is given to the manufacturing shop floor by the Production Planner as a signal to produce a certain quantity of a certain Item. Production Order also helps to generate the material requirements (Stock Entry) for the Item to be produced from its **Bill of Materials**.
|
||||
|
||||
The **Production Order** is generated directly from the **Production Planning Tool** based on Sales Orders. You can also create a direct Production Order by:
|
||||
|
||||
> Manufacturing > Production Order > New Production Order
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- Select the Item to be produced (must have a Bill of Materials).
|
||||
- Select the BOM
|
||||
- Select Quantities
|
||||
- Select Warehouses. WIP (Work-in-Progress) is where your Items will be transferred when you begin production and FG (Finished Goods) where you store finished Items before they are shipped.
|
||||
- Select if you want to consider sub-assemblies (sub-Items that have their own BOM) as stock items or you want to explode the entire BOM when you make Stock Entries for this Item. What it means is that if you also maintain stock of your sub assemblies then you should set this as “No” and in your Stock Entires, it will also list the sub-assembly Item (not is sub-components).
|
||||
|
||||
and “Submit” the Production Order.
|
||||
|
||||
Once you “Submit”, you will see two more buttons:
|
||||
|
||||
|
||||
|
||||
|
||||
1. Transfer Raw Material: This will create a Stock Entry with all the Items required to complete this Production Order to be added to the WIP Warehouse. (this will add sub-Items with BOM as one Item or explode their children based on your setting above).
|
||||
1. Update Finished Goods: This will create a Stock Entry that will deduct all the sub-Items from the WIP Warehouse and add them to the Finished Goods Warehouse.
|
||||
|
||||
> Tip: You can also partially complete a Production Order by updating the Finished Goods stock creating a Stock Entry.
|
||||
|
||||
When you Update Finished Goods to the Finished Goods Warehouse, the “Produced Quantity” will be updated in the Production Order.
|
||||
|
||||
@ -1,18 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Projects",
|
||||
"_toc": [
|
||||
"docs.user.projects.project",
|
||||
"docs.user.projects.task",
|
||||
"docs.user.projects.timelog"
|
||||
]
|
||||
}
|
||||
---
|
||||
Managing Projects
|
||||
|
||||
ERPNext helps you manage your Projects by breaking them into Tasks and allocating them to different people.
|
||||
|
||||
Purchasing and selling can also be tracked against Projects and this can help the company keep tabs on its budget, delivery and profitability for a Project.
|
||||
|
||||
Projects can be used to manage internal projects, manufacturing jobs or service jobs. For service jobs, Time Sheets can also be created that can be used to bill Customers if billing is done on a Time & Money basis.
|
||||
|
||||
@ -1,12 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Project"
|
||||
}
|
||||
---
|
||||
|
||||
## Project
|
||||
|
||||
The Project record maintains the details of your project and milestones that you have set. The Project record can be linked in Quotations, Sales Orders, Delivery Notes, Sales Invoices, Purchase Requests, Purchase Orders and Purchase Invoices. This way you can keep a track of all the activities that happen around this project.
|
||||
|
||||
|
||||
|
||||
@ -1,15 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Tasks"
|
||||
}
|
||||
---
|
||||
|
||||
## Tasks
|
||||
|
||||
Project is divided into Tasks and each Task is allocated to a resource. In ERPNext, you can also create and allocate a Task independently of a Project. If you define the start and end dates, it will add calendar events for the same and also show the task on the Gantt Chart that you can use for monitoring the Project.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,14 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Task"
|
||||
}
|
||||
---
|
||||
|
||||
## Tasks
|
||||
|
||||
Project is broken into Tasks and each Task is allocated to a resource. In ERPNext, you can also create an allocate a Task independently of a Project. If you define the start and end dates, it will add calendar events for the same and also show the task on the Gantt Chart that you can use for monitoring the Project.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,12 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Time Log"
|
||||
}
|
||||
---
|
||||
|
||||
## Time Sheets
|
||||
|
||||
You can create Time Sheets to track billable work to Customers. These Time Sheets can be tracked against Project and Tasks so that you can get reports on how much time was spent on each Task or Project.
|
||||
|
||||
|
||||
|
||||
@ -1,11 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Campaign"
|
||||
}
|
||||
---
|
||||
|
||||
A Campaign is a full-scale implementation of a sales strategy to promote a product or a service. This is done in a market segment of a particular geographical area, to achieve specified objectives.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,80 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Customer Master",
|
||||
"_title_image": "img/customers.png"
|
||||
}
|
||||
---
|
||||
A customer, who is sometimes known as a client, buyer, or purchaser is the one who receives goods, services, products, or ideas, from a seller for a monetary consideration. A customer can also receive goods or services from a vendor or a supplier for other valuable considerations.
|
||||
|
||||
You can either directly create your Customers via
|
||||
|
||||
> Selling > Customer
|
||||
|
||||
or upload it via the Data Import Tool.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
> Note: Customers are separate from Contacts and Addresses. A Customer can have multiple Contacts and Addresses.
|
||||
|
||||
### Contacts and Addresses
|
||||

|
||||
Contacts and Addresses in ERPNext are stored separately so that you can attach multiple Contacts or Addresses to Customers and Suppliers.
|
||||
|
||||
To add a Contact or Address directly from the Customer record, click on “New Contact” or “New Address”.
|
||||
|
||||
> Tip: When you select a Customer in any transaction, one Contact and Address gets pre-selected. This is the “Default Contact or Address”.
|
||||
|
||||
To Import multiple Contacts and Addresses from a spreadsheet, use the Data Import Tool.
|
||||
|
||||
### Integration with Accounts
|
||||
|
||||
In ERPNext, there is a separate Account record for each Customer, for each Company.
|
||||
|
||||
When you create a new Customer, ERPNext will automatically create an Account Ledger for the Customer under “Accounts Receivable” in the Company set in the Customer record.
|
||||
|
||||
> Advanced Tip: If you want to change the Account Group under which the Customer Account is created, you can set it in the Company master.
|
||||
|
||||
If you want to create an Account in another Company, just change the Company value and “Save” the Customer again.
|
||||
|
||||
### Customer Settings
|
||||
|
||||
You can link a Price List to a Customer (select “Default Price List”), so that when you select that Customer, the Price List will be automatically selected.
|
||||
|
||||
You can set “Credit Days” so that it is automatically set in the Sales Invoices made against this Customer.
|
||||
|
||||
You can set how much credit you want to allow for a Customer by adding the “Credit Limit”. You can also set a global “Credit Limit” in the Company master. Classifying Customers
|
||||
|
||||
ERPNext allows you to group your Customers and also divide them into Territories. Grouping will help you get better analysis of your data and identify which Customers are profitable and which are not. Territories will help you set sales targets for the respective territories.
|
||||
|
||||
### Customer Group
|
||||
|
||||
You can group your Customers so that you can get trend analysis for each group. Typically Customers are grouped by market segment (that is usually based on your domain).
|
||||
|
||||
> Tip: If you think all this is too much effort, you can leave it at “Default Customer Group”. But all this effort, will pay off when you start getting reports.
|
||||

|
||||
An example of a sample report is given below:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Territory
|
||||
|
||||
If your business operates in multiple Territories (could be countries, states or cities) it is usually a great idea to build your structure in the system. Once you group your Customers by Territories, you can set annual targets for each Item Group and get reports that will show your actual performance in the territory v/s what you had planned.
|
||||
|
||||
### Sales Person
|
||||
|
||||
Sales Persons behave exactly like Territories. You can create an organization chart of Sales Persons where each Sales Person’s target can be set individually. Again as in Territory, the target has to be set against Item Group.
|
||||
|
||||
### Sales Partner
|
||||
|
||||
A Sales Partner is a third party distributor / dealer / commission agent / affiliate / reseller who sells the companies products, for a commission. This is useful if you make the end sale to the Customer, involving your Sales Partner.
|
||||
|
||||
If you sell to your Sales Partner who in-turn sells it to the Customer, then you must make a Customer instead.
|
||||
@ -1,32 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Customer Group"
|
||||
}
|
||||
---
|
||||
|
||||
Customer Group is a category where you specify your customer group type. Your customers can be Individuals or they can be corporate(Company) customers. Your customers could also be government officials or non-profit organisations. ERPNext allows you to create your own Customer Group.
|
||||
|
||||
To create a new Customer Group, go to
|
||||
|
||||
> Selling > Customer Group
|
||||
|
||||
|
||||
#### Step 1: Click on Add Child
|
||||
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
#### Step 2: Name the Customer Group
|
||||
|
||||
|
||||
|
||||
|
||||
The new Customer Group will be added to the Customer Group Tree.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,16 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Discount"
|
||||
}
|
||||
---
|
||||
|
||||
|
||||
While making your sales transactions like a Quotation (or Sales Order) you would already have noticed that there is a “Discount” column. On the left is the “Price List Rate” on the right is the “Basic Rate”. You can add a “Discount” value to update the basic rate.
|
||||
|
||||
Since your taxes are calculated on Items, you must apply your discounts here so that you apply the tax on the discounted rate, which is the case for most taxes.
|
||||
|
||||
The second way to apply discount is to add it in your Taxes and Charges table. This way you can explicitly show the Customer the discount you have applied on the order. If you choose this method, remember that you will tax your Customer at the full rate, not the discounted rate. So this is not a good way to track discounts.
|
||||
|
||||
There is a third way to do it. Create an Item called “Discount” and make sure that all the taxes apply in the same way as the main Items. (This method is useful if only one type of tax is applicable on the sale). This way your “Discount” will appear as an expense. You will see a slightly higher income and expense but your profits will still remain the same. This method might be interesting where you want detailed accounting of your discounts.
|
||||
|
||||
> Note: The maximum Discount that can be applied on an Item can be fixed in the Item master.
|
||||
@ -1,35 +0,0 @@
|
||||
---
|
||||
{
|
||||
"_label": "Lead"
|
||||
}
|
||||
---
|
||||
To get the customer through the door, you may be doing all or any of the following:
|
||||
|
||||
- Listing your product on directories.
|
||||
- Maintaining an updated and searchable website.
|
||||
- Meeting people at trade events.
|
||||
- Advertising your product or services.
|
||||
|
||||
When you send out the word that you are around and have something valuable to offer, people will come in to check out your product. These are your Leads.
|
||||
|
||||
They are called Leads because they may lead you to a sale. Sales people usually work on leads by calling them, building a relationship and sending information about their products or services. It is important to track all this conversation to enable another person who may have to follow-up on that contact. The new person is then able to know the history of that particular Lead.
|
||||
|
||||
To create a Lead, go to:
|
||||
|
||||
> Selling > Lead > New Lead
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
ERPNext gives you a lot of options you may want to store about your Leads. For example what is the source, how likely are they to give you business etc. If you have a healthy number of leads, this information will help you prioritize who you want to work with.
|
||||
|
||||
> **Tip:** ERPNext makes it easy to follow-up on leads by updating the “Next Contact” details. This will add a new event in the Calendar for the User who has to contact the lead next.
|
||||
|
||||
### Difference between Lead, Contact and Customer
|
||||
|
||||
The difference is that a Lead is a potential Customer, someone who can give you business. A Customer is an organization or individual who has given you business before (and has an Account in your system). A Contact is a person who belongs to the Customer.
|
||||
|
||||
A Lead can be converted to a Customer by clicking on the “Create Customer” button. Once the Customer is created, the Lead becomes “Converted” and any further Opportunities from the same source can be created against the Customer.
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user