Module Customers Invoices: Difference between revisions

From Dolibarr ERP CRM Wiki
Jump to navigation Jump to search
(Add Chinese)
Tag: 2017 source edit
 
(75 intermediate revisions by 7 users not shown)
Line 1: Line 1:
<!-- BEGIN origin interlang links -->
<!-- You can edit this section but do NOT remove these comments
    Links below will be automatically replicated on translated pages by PolyglotBot -->
[[fr:Module_Factures_Clients]]
[[es:Módulo_Facturas_a_clientes]]
[[pt:Módulo_Faturas_de_Clientes]]
[[zh:客户发票模块]]
<!-- END interlang links -->
[[Category:Invoices]]
[[Category:Invoices]]
{{TemplateDocUser}}
{{TemplateDocUser}}
{{TemplateModEN}}
{{BasculeDevUserEn|
{{BasculeDevUserEn|
name=Invoice|  
name=Invoice|
num=30|
devdoc=[[Module Customers Invoices (developer)]]|
devdoc=[[Module Customers Invoices (developer)]]|
userdoc=This page|}}
userdoc=This page|}}
Line 8: Line 19:
= Introduction =
= Introduction =


The customer invoices module can be used to create or update customer invoices that contains several invoices lines. It's also this module you use to create payments on invoices. This module provides also features to generate documents for each invoice in a format like PDF.
The customer invoices module can be used to manage customer invoices (create, update, delete, list). Each invoice contains several invoice lines.  
This module is also used to create payments on invoices and has features to generate documents for each invoice in a format like PDF.
 
Suppliers invoices are managed by [[Module Suppliers Invoices]].


= Installation =
= Installation =
Line 21: Line 35:
= Create invoice =
= Create invoice =


There is no complete accountancy into Dolibarr. So you must stll have an accountancy software or use services of an accounter.
There is no complete accountancy in Dolibarr, at present. So, you must still use a third-party accounting software package of your choice or use the services of an accountant.


However, Dolibar can build for you customers invoices for all customers you have created before (see [[Module Third Parties]]).
However, Dolibar can create customer invoices for all the customers you have created before (see [[Module Third Parties]]).




You can create an invoice directly from a customer record, or from a command enclosed in the state "accepted", or from a service contract.
You can create an invoice directly from a customer record, from a command enclosed in the state "accepted", or from a service contract.




Line 33: Line 47:
If you create an invoice from a customer record, you can choose 4 types of invoices:
If you create an invoice from a customer record, you can choose 4 types of invoices:


* The standard invoice
* The "standard invoice"
This is a standard bill. There are no prerequisites.
This is a standard bill. There are no prerequisites.
* The "replacement invoice"
* The "replacement invoice"
A replacement bill can redo an invoice on which there would be mistakes and that nothing would have been done (before any payment).
A replacement bill can redo an invoice on which there are mistakes and where nothing has have been done before any payment.
We can create only one replacement invoice for each invoice. When you create a replacement invoice R, you choose the invoice F you want to replace. Once R is created, it is no more possible to do actions on F even if invoice status of F has not changed.
Only one replacement invoice can be created for each invoice. When you create a replacement invoice R, you choose the invoice F that you want to replace. Once R is created, it is no longer possible to do actions on F even if the invoice status of F has not changed.
If the replacement invoice R is deleted, the bill F resume its original condition and lifecycle of the invoice F can resume.
If the replacement invoice R is deleted, the bill F will resume its original state and continue its life cycle.
If the replacement invoice R is validated, the bill status of F goes automatically to abandoned. The cycle of life continues on the invoice R.
If the replacement invoice R is validated, the bill status of F automatically goes to abandoned. The life cycle continues on the invoice R.
* The "credit note"
* The "credit note"
We create several credit notes on for a same invoice.
You can create several credit notes for an invoice. A credit note is an invoice used to correct (reduce) a standard invoice. The amount of a credit note can be payed back, or you can convert it into a discount to reduce the amount owed by a customer.
* The "invoice deposit"
* The "invoice deposit"
You can create as many invoice deposit you want. They will be then used to reduce amount of other invoices.
You can create as many invoice deposits as you need. They will be then used to reduce the amount of other invoices.




'''Procedure'''
'''Procedure'''


Once an invoice created (in draft mode), you must include, in the bill, products or services already defined in Dolibarr or you directly enter the title, the rate of VAT, the unit price. For each line of the invoice you also set an amount and possibly a relative discount (percentage).
Once an invoice is created (in draft mode), you must include, in the bill, products or services already defined in Dolibarr or you can directly enter the title, the rate of VAT, the unit price. For each line of the invoice, you can also set an amount and possibly a relative discount (percentage).


Une fois la facture prête vous devez la valider. Attention cette opération est irréversible. Once your order ready you must validate it. Note this operation is irreversible. Quand vous validez la facture un numéro lui est attribué selon le modèle de numérotation que vous avez choisi dans la configuration du module Facture. Si une erreur est détectée après avoir validé la facture, il faudra soit faire une facture de remplacement, soit faire une facture d'avoir. When you validate the invoice number assigned by the numbering scheme that you chose in the module configuration Invoice. If an error is detected after confirming your order, you must either make a replacement bill or make an invoice have.
Once the invoice is ready you need to confirm it. Note this operation is irreversible.  


= PDF generation, printing =
When you post the invoice, an invoice number is assigned according to the numbering scheme you have chosen in the configuration of Invoices module.


When a document is generated, it is manufactured to a design chosen from a list selected in the Home Screen - Configuration - Modules - Invoice.
If an error is detected after validating the invoice, it will either make a replacement invoice or make a credit note.


= Enter payments =
To complete...


= Classer la facture =
'''Rules for VAT calculation'''


Une facture validée peut être définitivement classée à l'état:
* Rules to calculate VAT are explained on page [[VAT calculation and rounding rules]].
* Payé
Si la somme des paiements est supérieure ou égale au montant réclamé.
* Payé partiellement
Si la somme des paiements est supérieure à 0 mais strictement inférieure au montant réclamé.
* Abandonné
Si aucun paiement n'a eu lieu.


= Export invoice =
'''Revenue stamp'''


Dolibarr provide a generic tool to export your invoices data.
* Some countries (like Tunisia) must include a revenue stamp (a fixed amount for each invoice produced). A list of countries and amounts concerned are defined in the dictionary table [[Table_llx_c_revenuestamp]]. If the country of your company is included in this list, a new field "Revenue stamp" appears on screens and documents of invoices.
For this, you must use the Export assistant you can find in menu '''Tools - New export''' (if [[Module Exports En|Module Export]] has been enabled).


See page [[Module Exports En]] for more informations.
= Reduce total amount/remain amount to pay =
It is possible to reduce the total and / or the balance amount to pay on a bill, but it should make a distinction between discount and a reduction, although the two terms are somewhat amalgamated in places.


= Exemples de cas d'utilisations =
== Reduction ==
A 'reduction' is a relative reduction (percentage) of the selling price of one or more products or services detailed on the invoice. This reduction should be set line by line while editing the invoice and be between 0% and 100% (the discount percentage is then replaced by the words ''available''.


'''UCIN00: Erreur sur le contenu de la facture corrigée par facture remplacement'''
== Discount ==
A 'discount' is a reduction of the total invoice price. It can be defined in two ways depending on whether or not it is combined with another bill, that is to say, a payment already received or not.


'''Situation''':
=== Discount associated with payment already received ===
Je crée une facture.
Bills and have bills payment, awarded payments already received, can be converted into future '' reduction'' (incidentally we note the blurring of ''discount'' and ''reduced'' ). In this case the reduction, once assigned to the current invoice via the section ''Rebates'', is mentioned at the bottom of the document as a reference to the advance payments in question, which are so obviously the amount total bill to specify the balance due. This discount is NOT mentioned as a line in the invoice detail.
Je valide.
Je me rend compte de l'erreur après validation.


'''Actions correctives''':
=== Not associated with a payment already received delivery ===
Je classe la facture abandonnée pour motif 'Autre' (opération non obligatoire car automatique avec étape suivante).
It is also possible to define a discount that is not related to a payment already received. In this case, go to the customer record, customer tab, and define or fixed discounts (amount) or relative (percentage) attributed to that customer, and why (commercial gesture compensation due to late delivery, etc.). Once the rebates granted to the customer, they will be available when editing any bill the customer, under the heading ''discounts'' to the top. Unlike consecutive discounts for payments already received, they will be referred to as negative lines in the detail of the bill, and thus reduce the total amount thereof, before deducting payments may already collected. But these discounts are NOT associated with an invoice or have a deposit.
Je crée une nouvelle facture en choisissant '''Facture de remplacement''' et en selectionnant la facture remplacée comme facture.


== Summary ==
So there are three possibilities to reduce the price of an invoice:
* assign a '''reduction''' percentage on certain products / services detailed in the invoice, which will effectively define a'' total amount'' lower than normally expected.


'''UCIN00b: Erreur sur le client détecté avant envoi facture'''
* assign the customer '''overall discount''', is not associated with or have an invoice payment, which will be added as a line of negative amount will reduce the ' total amount ' of the invoice.


'''Situation''':
* Use a 'credit note or deposit' transformed into future reductions that advance payments have been received, thereby reducing the 'balance payable' but not the total amount of bill.
Je crée une facture.
Je valide.
Je me rend compte que la facture a été crée sur le mauvais client.


'''Actions correctives''':
= PDF generation, printing =
Je classe la facture abandonnée pour motif 'Autre' et je renseigne le motif "Erreur saisie sur mauvais client".
When a document is generated, it is generated according to the design chosen from a list selected in the Home Screen - Configuration - Modules - Invoice.
Je crée une nouvelle facture sur le bon client.


TODO: Faire confirmer par expert que possible si c'est fait avant envoi.
If you want the PDF to include bank account number or address for check payment (or both), this is what to do:
Si pas possible, interdire la possibilité et utiliser le cas suivant.
# Activate module Bank/Cash.
# Create the bank account for your company.
# Setup up [[Module Customers Invoices]] by going into menu Setup - Modules - Customers invoices then select into area "Payment modes", the account created at step 2, or address to use for check payments, and validate by clicking on "Modify" button..
You can now regenerate your invoice, you will see the bank number or address to use for check payment.


= Enter payments =
Payments can be done only on validated invoices.


'''UCIN00c: Erreur sur le client (ou facture saisie 2 fois) détecté après envoi facture mais avant paiement'''
If a credit note is available, you can use it to reduce the remain to pay.


'''Situation''':
= Close invoice =
Je crée une facture.
An invoice can be validated definitively classified in the state:
Je valide et l'envoie au client.
* Paid (If the sum of payments is greater than or equal to the amount claimed).
Je me rend compte que la facture a été crée sur le mauvais client ou facture en doublon avec une autre deja envoyée.
* Partially paid (If the sum of payments is greater than 0 but strictly less than the amount claimed).
 
* Abandoned (If no payment has occurred).
'''Actions correctives''':
Je crée un avoir sur la facture qui n'a pas encore de paiement du montant inverse exacte.
Je convertit l'avoir en réduction. L'avoir se retrouve ainsi "traité", je peux l'envoyer au client si je le désire.
Je retourne sur la fiche facture en erreur et j'applique la réduction issue de l'avoir.
Le du devient alors zéro et je la classe à '''Payée complètement''' (paiement de 0).
 
 
'''UCIN00d: Erreur sur le libellé client détecté après saisie de paiement'''
 
'''Situation''':
Je crée une facture sur le client de libellé X.
Je valide.
Je saisi les paiements.
Je classe la facture payée.
Je me rend compte que la facture a été crée sur le mauvais client et le client me demande une contrefacture sur l'ancien nom X et une nouvelle sur le nouveau nom Y.
 
'''Actions correctives''':
Je crée un avoir sur la facture en erreur avec toutes les lignes en inverse.
Je transforme l'avoir en réduction. L'avoir se retrouve ainsi "traité".
J'édite la fiche client pour corriger le libellé client X par Y.
Je crée la nouvelle facture sur le nouveau client Y en incluant toutes les lignes.
Je la valide.
J'inclut le paiement issue de l'avoir.
Le solde passe alors à 0 (aucun du).
Je peux classer la facture à '''Payée''' sans saisir d'autres réglements (le client a déjà payé).
 
 
'''UCIN01: Facturation et paiement intégral'''
 
'''Situation''':
Je crée une facture.
Je reçois l'intégralité des paiements.
 
'''Actions''':
Je saisis tous les paiement sur la facture. Le solde devient à 0.
Je peux classer la facture à '''Payée'''.
 
 
 
'''UCIN02: Facturation et paiement supérieur reçu'''
 
'''Situation''':
Je crée une facture.
Je reçois un paiement supérieur au montant réclamé.
 
'''Actions correctives''':
Je saisi le montant reçu.
Je clos la facture à l'état '''Payé'''.
Je crée un avoir du trop perçu.
 
 
'''UCIN03: Facturation et paiement intégral puis produit retourné'''
 
'''Situation''':
Je crée une facture.
Je reçois l'intégralité des paiements. Je les saisis et le solde devient 0.
Je clos la facture à l'état '''Payé'''.
Plus tard, je reçois un retour de produit suite à rétractation légale.
 
'''Actions correctives''':
Je saisi un avoir sur cette facture.
Cet avoir peut etre converti en réduction pour la prochaine facture ou rembourser en monétaire.


= Export invoice =
Dolibarr provide a generic tool to export your invoices data.
For this, you must use the Export assistant you can find in menu '''Tools - New export''' (if [[Module Exports En|Module Exports]] has been enabled).


'''UCIN03b: Facturation et paiement intégral puis erreur sur produit détecté'''
See page [[Module Exports En|Module Exports]] for more informations.


'''Situation''':
= Pre-defined invoices =
Je crée une facture.
In Dolibarr a bill designated as pre-defined is simply an invoice which we will reuse most of the data to issue additional invoices based on this information, thereby saving time to create a new invoice.
Je reçois l'intégralité des paiements. Je les saisis et le solde devient 0.
Je clos la facture à l'état '''Payé'''.
Plus tard, je découvre une erreur de produit.


'''Actions correctives''':
In the case of the implementation of contracts, invoices can be predefined set, corresponding to the recurring elements of the contract. This is very interesting. The only downside, the period specified for each element of the resulting bill covers the entire period of contract. It should relate to the billing month.
Je saisi un avoir sur cette facture qui contient le produit en erreur.
Je converti cet avoir en réduction.  
Je crée une nouvelle facture avec le bon produit. J'intègre l'avoir dans cette nouvelle facture.
Enventuellement si j'utilise le module stock, je corrige le stock en manuel.




'''UCIN04: Facturation et paiement partiel car anticipé (escompte)'''
= Related videos =


'''Situation''':
== Video on Billing and payments of customer invoice ==
Je crée une facture.
Je reçois un paiement du montant de la facture moins un escompte accordé pour paiement anticipé.


'''Actions''':
<youtube width="280">L54ECXnrmLw</youtube>
Je saisi le paiment reçu de la valeur reçue.
Je classe la facture à '''Payé partiellement''' et renseigne le motif "Le manque est un '''Escompte'''".


== Recuring invoices ==


'''UCIN06: Facturation et paiement partiel ou nul puis retour produit et attente correction anomalie ou erreur infine tolerable'''
<youtube width="280">44VTZafmYvY</youtube>


'''Situation''':
Je crée une facture.
Si je reçois un paiement partiel, je le saisi.
Je reçois un retour d'une partie des produits (retractation du client) ou ne reçois plus les quelques centimes manquant.
Eventuellement, le client attend un avoir pour payer la fin de la facture.


'''Action''':
Invoices:
Je saisi un avoir sur la facture.
(vocal in french but subtitles are available and review in this language)
J'envoie l'avoir.
Ensuite, je convertit cet avoir en reduction pour le client.
Je saisi eventuellement la suite des paiements reçus.
Eventuellement j'inclus l'avoir dans la liste des paiements de la facture (sinon il pourra etre inclus dans une autre facture).
Je classe la facture à l'état '''Payé'''.


TODO Controle a inclure en plus: Quand l'avoir est fait sur une facture au statut 'Réglement commencé', il faut mettre un message disant "Attention, ne créer un avoir sur une facture en cours de paiement que si le client a cessé le paiement et attend cet avoir pour poursuivre la suite ou parce que vous fermez la facture".
<youtube width="280">7BVKHt91jrI</youtube>
Ensuite il faut vérifier que le montant de l'avoir est inférieur au montant de la facture auquel il s'applique - montant déja reçu. Sinon, refuser création avoir.


Payments:
(vocal in french but subtitles are available and review in this language)


'''UCIN05: Facturation et paiement partiel car mauvais payeur'''
<youtube width="280">ii8kdfa9BxA</youtube>


'''Situation''':
= Use case examples =
Je crée une facture.
== Deposits ==
Je reçois un paiement partiel, je le saisi.
{{ExamplesCaseEn
Après une longue attente, la suite des paiements n'est pas reçue et j'abandonne tout espoir.
|name=UCIN01: Reception of a deposit then final invoice
|situation=Reception of a deposit then final invoice
|actions=I entered a deposit invoice for the amount received (and not for total amount to pay). I input payment received. Then I convert this invoice into a future reduction.  
Later, I create the complete invoice (but i can also do it before the deposit). I add into complete invoice the reduction. This reduce the remain to pay. I send or resend the entire invoice generated indicating that a deposit has been received.
}}&nbsp;


'''Actions''':
== Billing and payments ==
Je classe la facture à l'état '''Payé partiellement''' et renseigne le motif '''Mauvais payeur'''.
{{ExamplesCaseEn
|name=UCIN02: Billing and payment in full
|situation=I created an invoice. I receive full payment.
|actions=I take all the payment on the invoice. The balance goes to 0. I can sort the invoices paid.
}}


{{ExamplesCaseEn
|name=UCIN03: Billing and higher payment received
|situation=I created an invoice. I get a payment exceeds the amount claimed.
|actions=I enter the amount received. I closed the bill to the state pays. I have created one of the overpayment.
}}


'''UCIN07: Facturation et aucun paiement reçu car mauvais payeur'''
{{ExamplesCaseEn
|name=UCIN04: Billing and payment in full and returned product
|situation=I created an invoice. I receive full payment. I entered and the balance becomes 0. I closed the bill to the state pays. Later, I received a return of product due to legal withdrawal.
|actions=
I create a invoice with type "credit note" to correct original invoice.
This credit can be converted to reduce the next bill or refunded money.
}}


'''Situation''':
{{ExamplesCaseEn
Je crée une facture.
|name=UCIN05: Billing and payment in full and on product error detected
Après une longue attente, la suite des paiements n'est pas reçu et j'abandonne tout espoir.
|situation=I created an invoice. I receive full payment. I entered and the balance becomes 0. I closed the bill to the state pays. Later, I discovered an error in product.
|actions=
I create a invoice with type "credit note" to correct original invoice.
I convert this credit note into discount.
I create a new invoice with the correct product. I'm joining in to have this new bill. Eventually if I use the stock, I corrected the stock in hand.
}}


'''Actions''':
{{ExamplesCaseEn
Je classe la facture à l'état '''Abandonnée''' et renseigne le motif '''Mauvais payeur'''.
|name=UCIN06: Billing and payment for partial advance (discount)
|situation=I created an invoice. I receive a payment of the invoice amount less a discount granted for early payment.
|actions=I received before the payment of the value received. I file the bills paid and partly because the information "Lack is a discount.
}}


= Factures pré-définies =
{{ExamplesCaseEn
|name=UCIN07: billing and payment, partial or no return and then wait and product defect or error correction tolerable
|situation=I created an invoice. If I get a partial payment, I know. I get a return of some products (Revocation of client) or not getting more pennies missing. Optionally, the client waits for a credit pay the late bill.
|actions=I submitted a credit on the bill. I send the credit. Then I have to convert this reduction to the customer. I know eventually the result of payments received. Eventually I include having the list of payments invoice (otherwise it will be included in another bill). I fill the bill in the state Paid.
}}


Dans Dolibarr, une facture désignée comme pré-définie est simplement une facture dont on réutilise la plupart des données pour émettre d'autres factures sur base de ces informations, ce qui permet un gain de temps non-négligeable à la saisie
{{ExamplesCaseEn
|name=UCIN08: Billing and partial payment for deadbeat
|situation=I created an invoice. I get a partial payment, I know. After a long wait, after payment is received and abandon all hope.
|actions=I fill the bill in the state Paid partial information and the reason bad payer.
}}


Dans le cas de la mise en oeuvre des contrats, une facture prédéfinies peut être définie et correspondant aux éléments récurrents du contrat. Ceci est très intéressant.  
{{ExamplesCaseEn
Le seul bémol, la période indiquée pour chaque élément de la facture résultante couvre toute la période du contrat. Elle ne devrait porter que sur le mois de facturation.
|name=UCIN09: Billing and received no payment for deadbeat
|situation=I created an invoice. After a long wait, after payment is received and not abandon all hope.
|actions=I file the bill in the state Abandoned and informs the reason bad payer.
}}&nbsp;


Cette fonctionnalité s'active en ajoutant l'option cachée FACTURE_ENABLE_RECUR dans configuration - divers. Cette fonction est instable.
== Solving billing errors  ==
{{ExamplesCaseEn
|name=UCIN00 Error on the content of an invoice detected after validation.
|situation=I created an invoice. I valid. I realize the error on the contents (amount, description) after validation (see use case UCIN10 on error on client).
|actions=I close the invoice to abandoned with comment 'Other' (not necessary as this will be done automatically by next step). I create a new invoice by choosing replacement invoice and by selecting the invoice to replace.
}}


= Exemple de cas d'utilisation des factures pré-définies =
{{ExamplesCaseEn
|name=UCIN10a: Error detected on the client after validation but before payment
|situation=I created an invoice. I valid. I realized that the invoice has been created on the wrong client.
|actions=I fill the bill dropped to the ground 'Other' and I fill the ground "before failure on bad customer". I created a new bill on the right customer.
}}


'''UCRIN01: Création d'une facture pré-définie'''
{{ExamplesCaseEn
|name=UCIN10b: Error on the client (or invoice before 2 times) detected after sending invoice but before payment
|situation=I created an invoice. I validate and send the client. I realized that the invoice has been created on the wrong customer or invoice in duplicate with another already sent.
|actions=I create a credit invoice that has not yet paid the amount exact opposite. I have to convert the discount. The invoice is found to have "treated", I can send it to the customer if I wish. I returned on the card bill in error and I apply the discount after having. On the becomes zero and I Paid in full Class (payoff of 0). That the client has not received or the original invoice, the latter was canceled and closed by the credit. I reprocessed the invoice to the right customer.
}}


Il n'est pas possible de créer une facture récurrente en soi. Il s'agit d'une facture normale que l'on réutilise par la suite.
{{ExamplesCaseEn
|name=UCIN10c: Error on the client spelling detected after payment
|situation=I created an invoice to the client X. I validated it. I add payments and set the bills paid. I realized that the invoice has been created with the wrong spelling and the client asks me about the credit note (for old name X and an invoice for new name Y).
|actions=I create a credit note with all the lines in reverse. I transform it into reduction. The credit note is now "used" for customer X. I edit the customer record to correct X into Y. I create the new bill on the new client Y including all lines. I valid. I include the credit note. The balance then goes to 0 (none of). I can classify the new invoice paid without recourse to other regulations (the customer has already paid).
}}&nbsp;


'''UCRIN02: Transformation d'une facture normale en facture prédéfinie'''
== Predefined invoices ==
{{ExamplesCaseEn
|name=UCRIN01: Creating a predefined invoice
|situation=I want to create a predefined invoice
|actions=It is not possible to create a recurring invoice directly. It must be a draft standard invoice that is subsequently converted. So take a look at next use case.
}}


J'ouvre une facture existante. Je clique sur le bouton "Modifier en récurrente". J'entre un titre (par exemple, "Mise-à-jour trimestrielle") et éventuellement une note, qui pourrait être une explication de la raison de la répétition de cette facture. Ma facture est à présent une facture récurrente. Cela ne sera visible que si je demande l'affichage des factures récurrentes ou que je crée une nouvelle facture.


'''UCRIN03: Utilisation d'une facture prédéfinie pour la création d'une nouvelle facture'''
{{ExamplesCaseEn
|name=UCRIN02: Transformation of an invoice into a recurring invoice'''
|situation=Transformation of an invoice into a recurring invoice'''
|actions=I open or create a draft invoice. I click on the "'''Convert to predefined'''". I enter a title (eg "Last Updated quarterly") and possibly a note, which might be an explanation of the reason for the repetition of this bill. My bill is now a recurring invoice. This will be visible only if I request the display of recurring bills or I create a new invoice.
}}


Je crée une nouvelle facture ("Créer facture"), et j'utilise la boîte de sélection en bas de page pour sélectionner la facture récurrente que je veux utiliser comme gabarit (template). Ma nouvelle facture est pré-remplie, les modifications à apporter sont mineures.
{{ExamplesCaseEn
|name=UCRIN03: Using a predefined bill to create a new invoice
|situation=Using a predefined bill to create a new invoice
|actions=I create a new invoice ( "Create invoice"), and I'm using the selection box at bottom of page to select the Recurring Billing I want to use as a template (template).My new invoice is pre-filled, the modifications are minor.
}}

Latest revision as of 06:56, 23 August 2023

Invoice
Numero/ID of module 30
User doc. of module This page
Developer doc. of module Module Customers Invoices (developer)

Introduction

The customer invoices module can be used to manage customer invoices (create, update, delete, list). Each invoice contains several invoice lines. This module is also used to create payments on invoices and has features to generate documents for each invoice in a format like PDF.

Suppliers invoices are managed by Module Suppliers Invoices.

Installation

This module is included with the Dolibarr distribution, so there is no need to install it.

Configuration

To use this module, you must first enable it using an administrator account, via the menu option "Home - Setup - Modules".

Choose the tab where the module is listed. Then click on "Activate".

The module is now activated.

If a cog icon appears Cog circle.svg on module thumb or at end of the line of the module, click on it to access the setup page specific to the module.


The page Invoice configuration explains you how to setup the invoice module.

Create invoice

There is no complete accountancy in Dolibarr, at present. So, you must still use a third-party accounting software package of your choice or use the services of an accountant.

However, Dolibar can create customer invoices for all the customers you have created before (see Module Third Parties).


You can create an invoice directly from a customer record, from a command enclosed in the state "accepted", or from a service contract.


Types of bills

If you create an invoice from a customer record, you can choose 4 types of invoices:

  • The "standard invoice"

This is a standard bill. There are no prerequisites.

  • The "replacement invoice"

A replacement bill can redo an invoice on which there are mistakes and where nothing has have been done before any payment. Only one replacement invoice can be created for each invoice. When you create a replacement invoice R, you choose the invoice F that you want to replace. Once R is created, it is no longer possible to do actions on F even if the invoice status of F has not changed. If the replacement invoice R is deleted, the bill F will resume its original state and continue its life cycle. If the replacement invoice R is validated, the bill status of F automatically goes to abandoned. The life cycle continues on the invoice R.

  • The "credit note"

You can create several credit notes for an invoice. A credit note is an invoice used to correct (reduce) a standard invoice. The amount of a credit note can be payed back, or you can convert it into a discount to reduce the amount owed by a customer.

  • The "invoice deposit"

You can create as many invoice deposits as you need. They will be then used to reduce the amount of other invoices.


Procedure

Once an invoice is created (in draft mode), you must include, in the bill, products or services already defined in Dolibarr or you can directly enter the title, the rate of VAT, the unit price. For each line of the invoice, you can also set an amount and possibly a relative discount (percentage).

Once the invoice is ready you need to confirm it. Note this operation is irreversible.

When you post the invoice, an invoice number is assigned according to the numbering scheme you have chosen in the configuration of Invoices module.

If an error is detected after validating the invoice, it will either make a replacement invoice or make a credit note.


Rules for VAT calculation

Revenue stamp

  • Some countries (like Tunisia) must include a revenue stamp (a fixed amount for each invoice produced). A list of countries and amounts concerned are defined in the dictionary table Table_llx_c_revenuestamp. If the country of your company is included in this list, a new field "Revenue stamp" appears on screens and documents of invoices.

Reduce total amount/remain amount to pay

It is possible to reduce the total and / or the balance amount to pay on a bill, but it should make a distinction between discount and a reduction, although the two terms are somewhat amalgamated in places.

Reduction

A 'reduction' is a relative reduction (percentage) of the selling price of one or more products or services detailed on the invoice. This reduction should be set line by line while editing the invoice and be between 0% and 100% (the discount percentage is then replaced by the words available.

Discount

A 'discount' is a reduction of the total invoice price. It can be defined in two ways depending on whether or not it is combined with another bill, that is to say, a payment already received or not.

Discount associated with payment already received

Bills and have bills payment, awarded payments already received, can be converted into future reduction (incidentally we note the blurring of discount and reduced ). In this case the reduction, once assigned to the current invoice via the section Rebates, is mentioned at the bottom of the document as a reference to the advance payments in question, which are so obviously the amount total bill to specify the balance due. This discount is NOT mentioned as a line in the invoice detail.

Not associated with a payment already received delivery

It is also possible to define a discount that is not related to a payment already received. In this case, go to the customer record, customer tab, and define or fixed discounts (amount) or relative (percentage) attributed to that customer, and why (commercial gesture compensation due to late delivery, etc.). Once the rebates granted to the customer, they will be available when editing any bill the customer, under the heading discounts to the top. Unlike consecutive discounts for payments already received, they will be referred to as negative lines in the detail of the bill, and thus reduce the total amount thereof, before deducting payments may already collected. But these discounts are NOT associated with an invoice or have a deposit.

Summary

So there are three possibilities to reduce the price of an invoice:

  • assign a reduction percentage on certain products / services detailed in the invoice, which will effectively define a total amount lower than normally expected.
  • assign the customer overall discount, is not associated with or have an invoice payment, which will be added as a line of negative amount will reduce the ' total amount ' of the invoice.
  • Use a 'credit note or deposit' transformed into future reductions that advance payments have been received, thereby reducing the 'balance payable' but not the total amount of bill.

PDF generation, printing

When a document is generated, it is generated according to the design chosen from a list selected in the Home Screen - Configuration - Modules - Invoice.

If you want the PDF to include bank account number or address for check payment (or both), this is what to do:

  1. Activate module Bank/Cash.
  2. Create the bank account for your company.
  3. Setup up Module Customers Invoices by going into menu Setup - Modules - Customers invoices then select into area "Payment modes", the account created at step 2, or address to use for check payments, and validate by clicking on "Modify" button..

You can now regenerate your invoice, you will see the bank number or address to use for check payment.

Enter payments

Payments can be done only on validated invoices.

If a credit note is available, you can use it to reduce the remain to pay.

Close invoice

An invoice can be validated definitively classified in the state:

  • Paid (If the sum of payments is greater than or equal to the amount claimed).
  • Partially paid (If the sum of payments is greater than 0 but strictly less than the amount claimed).
  • Abandoned (If no payment has occurred).

Export invoice

Dolibarr provide a generic tool to export your invoices data. For this, you must use the Export assistant you can find in menu Tools - New export (if Module Exports has been enabled).

See page Module Exports for more informations.

Pre-defined invoices

In Dolibarr a bill designated as pre-defined is simply an invoice which we will reuse most of the data to issue additional invoices based on this information, thereby saving time to create a new invoice.

In the case of the implementation of contracts, invoices can be predefined set, corresponding to the recurring elements of the contract. This is very interesting. The only downside, the period specified for each element of the resulting bill covers the entire period of contract. It should relate to the billing month.


Related videos

Video on Billing and payments of customer invoice

Recuring invoices


Invoices: (vocal in french but subtitles are available and review in this language)

Payments: (vocal in french but subtitles are available and review in this language)

Use case examples

Deposits

UCIN01: Reception of a deposit then final invoice
Situation Reception of a deposit then final invoice
Actions I entered a deposit invoice for the amount received (and not for total amount to pay). I input payment received. Then I convert this invoice into a future reduction.

Later, I create the complete invoice (but i can also do it before the deposit). I add into complete invoice the reduction. This reduce the remain to pay. I send or resend the entire invoice generated indicating that a deposit has been received.

 

Billing and payments

UCIN02: Billing and payment in full
Situation I created an invoice. I receive full payment.
Actions I take all the payment on the invoice. The balance goes to 0. I can sort the invoices paid.
UCIN03: Billing and higher payment received
Situation I created an invoice. I get a payment exceeds the amount claimed.
Actions I enter the amount received. I closed the bill to the state pays. I have created one of the overpayment.
UCIN04: Billing and payment in full and returned product
Situation I created an invoice. I receive full payment. I entered and the balance becomes 0. I closed the bill to the state pays. Later, I received a return of product due to legal withdrawal.
Actions I create a invoice with type "credit note" to correct original invoice.

This credit can be converted to reduce the next bill or refunded money.

UCIN05: Billing and payment in full and on product error detected
Situation I created an invoice. I receive full payment. I entered and the balance becomes 0. I closed the bill to the state pays. Later, I discovered an error in product.
Actions I create a invoice with type "credit note" to correct original invoice.

I convert this credit note into discount. I create a new invoice with the correct product. I'm joining in to have this new bill. Eventually if I use the stock, I corrected the stock in hand.

UCIN06: Billing and payment for partial advance (discount)
Situation I created an invoice. I receive a payment of the invoice amount less a discount granted for early payment.
Actions I received before the payment of the value received. I file the bills paid and partly because the information "Lack is a discount.
UCIN07: billing and payment, partial or no return and then wait and product defect or error correction tolerable
Situation I created an invoice. If I get a partial payment, I know. I get a return of some products (Revocation of client) or not getting more pennies missing. Optionally, the client waits for a credit pay the late bill.
Actions I submitted a credit on the bill. I send the credit. Then I have to convert this reduction to the customer. I know eventually the result of payments received. Eventually I include having the list of payments invoice (otherwise it will be included in another bill). I fill the bill in the state Paid.
UCIN08: Billing and partial payment for deadbeat
Situation I created an invoice. I get a partial payment, I know. After a long wait, after payment is received and abandon all hope.
Actions I fill the bill in the state Paid partial information and the reason bad payer.
UCIN09: Billing and received no payment for deadbeat
Situation I created an invoice. After a long wait, after payment is received and not abandon all hope.
Actions I file the bill in the state Abandoned and informs the reason bad payer.

 

Solving billing errors

UCIN00 Error on the content of an invoice detected after validation.
Situation I created an invoice. I valid. I realize the error on the contents (amount, description) after validation (see use case UCIN10 on error on client).
Actions I close the invoice to abandoned with comment 'Other' (not necessary as this will be done automatically by next step). I create a new invoice by choosing replacement invoice and by selecting the invoice to replace.
UCIN10a: Error detected on the client after validation but before payment
Situation I created an invoice. I valid. I realized that the invoice has been created on the wrong client.
Actions I fill the bill dropped to the ground 'Other' and I fill the ground "before failure on bad customer". I created a new bill on the right customer.
UCIN10b: Error on the client (or invoice before 2 times) detected after sending invoice but before payment
Situation I created an invoice. I validate and send the client. I realized that the invoice has been created on the wrong customer or invoice in duplicate with another already sent.
Actions I create a credit invoice that has not yet paid the amount exact opposite. I have to convert the discount. The invoice is found to have "treated", I can send it to the customer if I wish. I returned on the card bill in error and I apply the discount after having. On the becomes zero and I Paid in full Class (payoff of 0). That the client has not received or the original invoice, the latter was canceled and closed by the credit. I reprocessed the invoice to the right customer.
UCIN10c: Error on the client spelling detected after payment
Situation I created an invoice to the client X. I validated it. I add payments and set the bills paid. I realized that the invoice has been created with the wrong spelling and the client asks me about the credit note (for old name X and an invoice for new name Y).
Actions I create a credit note with all the lines in reverse. I transform it into reduction. The credit note is now "used" for customer X. I edit the customer record to correct X into Y. I create the new bill on the new client Y including all lines. I valid. I include the credit note. The balance then goes to 0 (none of). I can classify the new invoice paid without recourse to other regulations (the customer has already paid).

 

Predefined invoices

UCRIN01: Creating a predefined invoice
Situation I want to create a predefined invoice
Actions It is not possible to create a recurring invoice directly. It must be a draft standard invoice that is subsequently converted. So take a look at next use case.


UCRIN02: Transformation of an invoice into a recurring invoice'
Situation Transformation of an invoice into a recurring invoice
Actions I open or create a draft invoice. I click on the "Convert to predefined". I enter a title (eg "Last Updated quarterly") and possibly a note, which might be an explanation of the reason for the repetition of this bill. My bill is now a recurring invoice. This will be visible only if I request the display of recurring bills or I create a new invoice.
UCRIN03: Using a predefined bill to create a new invoice
Situation Using a predefined bill to create a new invoice
Actions I create a new invoice ( "Create invoice"), and I'm using the selection box at bottom of page to select the Recurring Billing I want to use as a template (template).My new invoice is pre-filled, the modifications are minor.