[MOV] accounting: restructuration of the accounting documentation
This commit improves the structure of the accounting documentation by
- reducing the levels necessary to reach the information
- grouping some docs
- moving content to their parent category page (content in all levels)
- renaming some sections to reflect the structure of the app better
task-3330093
closes odoo/documentation#4479
X-original-commit: c68cc154ed
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
|
After Width: | Height: | Size: 5.1 KiB |
@@ -0,0 +1,72 @@
|
||||
==============================
|
||||
Batch payments by bank deposit
|
||||
==============================
|
||||
|
||||
A **batch deposit** is a convenient way to group customer payments and deposit them into your bank
|
||||
account. The feature lets you list multiple payments and generate a detailed deposit slip with a
|
||||
batch reference. This reference can be used when reconciling to match bank statement lines with
|
||||
transactions in the batch deposit.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Go to :menuselection:`Accounting --> Configuration --> Settings --> Customer Payments` and tick
|
||||
:guilabel:`Batch Payments` to activate the feature.
|
||||
|
||||
Deposit multiple payments in batch
|
||||
==================================
|
||||
|
||||
Register payments
|
||||
-----------------
|
||||
|
||||
Before performing a batch deposit, it is necessary to register each transaction's payment. To do so,
|
||||
open the corresponding customer invoice and click :guilabel:`Register Payment`. In the pop-up
|
||||
window, select the :guilabel:`Journal` linked to your bank account and :guilabel:`Batch Deposit` as
|
||||
the :guilabel:`Payment Method`, and click :guilabel:`Create Payment`.
|
||||
|
||||
.. image:: batch/batch-payments.png
|
||||
:align: center
|
||||
:alt: Registering a customer payment as part of a batch deposit
|
||||
|
||||
Add payments to a batch deposit
|
||||
-------------------------------
|
||||
|
||||
To add payments to a batch deposit, go to :menuselection:`Accounting --> Customers --> Batch
|
||||
Payments`, and click :guilabel:`New`. Next, select the :guilabel:`Bank` and choose :guilabel:`Batch
|
||||
Deposit` as the :guilabel:`Payment Method`.
|
||||
|
||||
.. image:: batch/batch-customer-payment.png
|
||||
:align: center
|
||||
:alt: Filling out a new inbound batch payment form
|
||||
|
||||
Click :guilabel:`Add a line`. In the pop-up window, tick all payments to include in the batch
|
||||
deposit, then click :guilabel:`Select`.
|
||||
|
||||
.. image:: batch/batch-lines-selection.png
|
||||
:align: center
|
||||
:alt: Selecting all payments to include in the batch deposit
|
||||
|
||||
Once done, click :guilabel:`Validate` to finalize the batch deposit.
|
||||
|
||||
.. tip::
|
||||
Click :guilabel:`Print` to download a PDF file to include with the deposit slip.
|
||||
|
||||
Bank reconciliation
|
||||
-------------------
|
||||
|
||||
Once the bank transactions are on your database, you can reconcile bank statement lines with the
|
||||
batch payment. To do so, go to the :guilabel:`Accounting Dashboard` and click :guilabel:`Reconcile
|
||||
Items` on the related bank account. Go to the :guilabel:`Batch Payments` tab to select a specific
|
||||
batch and click :guilabel:`Validate` to finalize the process.
|
||||
|
||||
.. image:: batch/batch-reconciliation.png
|
||||
:align: center
|
||||
:alt: Reconciling the batch payment with all its transactions
|
||||
|
||||
.. note::
|
||||
If a specific payment could not be processed by the bank or is missing, remove the related
|
||||
payment before reconciling.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payments`
|
||||
- :doc:`batch_sdd`
|
||||
|
After Width: | Height: | Size: 7.4 KiB |
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 7.5 KiB |
|
After Width: | Height: | Size: 8.0 KiB |
|
After Width: | Height: | Size: 17 KiB |
@@ -0,0 +1,131 @@
|
||||
=======================================
|
||||
Batch payments: SEPA Direct Debit (SDD)
|
||||
=======================================
|
||||
|
||||
SEPA, the Single Euro Payments Area, is a payment-integration initiative of the European Union for
|
||||
simplification of bank transfers denominated in euros. With **SEPA Direct Debit** (SDD), your
|
||||
customers can sign a mandate that authorizes you to collect future payments from their bank
|
||||
accounts. This is particularly useful for recurring payments based on a subscription.
|
||||
|
||||
You can record customer mandates in Odoo, and generate `.xml` files containing pending payments made
|
||||
with an SDD mandate.
|
||||
|
||||
.. note::
|
||||
| SDD is supported by all SEPA countries, which includes the 27 member states of the European
|
||||
Union as well as additional countries.
|
||||
| `List of all SEPA countries
|
||||
<https://www.europeanpaymentscouncil.eu/document-library/other/epc-list-sepa-scheme-countries>`_.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Go to :menuselection:`Accounting app --> Configuration --> Settings`, activate
|
||||
:guilabel:`SEPA Direct Debit (SDD)`, and click on :guilabel:`Save`. Enter your company's
|
||||
:guilabel:`Creditor Identifier`. This number is provided by your bank institution, or the authority
|
||||
responsible for delivering them.
|
||||
|
||||
.. image:: batch_sdd/creditor-identifier.png
|
||||
:align: center
|
||||
:alt: Add a SEPA Creditor Identifier to Odoo Accounting
|
||||
|
||||
SEPA Direct Debit Mandates
|
||||
==========================
|
||||
|
||||
Create a mandate
|
||||
----------------
|
||||
|
||||
The :abbr:`SDD (sepa direct debit)` Mandate is the document that your customers sign to authorize
|
||||
you to collect money directly from their bank accounts.
|
||||
|
||||
To create a new mandate, go to :menuselection:`Accounting app --> Customers -->
|
||||
Direct Debit Mandates`, on :guilabel:`Create`, and fill out the form. Export the PDF file by
|
||||
clicking on :guilabel:`Print`. It is then up to your customer to sign this document. Once done,
|
||||
upload the signed file and click on :guilabel:`Validate` to start running the mandate.
|
||||
|
||||
.. important::
|
||||
Make sure that the **IBAN bank accounts details** are correctly recorded on the debtor’s contact
|
||||
form, under the :guilabel:`Accounting` tab, and in your own :doc:`Bank Account <../bank>` settings.
|
||||
|
||||
SEPA Direct Debit as a payment method
|
||||
-------------------------------------
|
||||
|
||||
SDD can be used as a payment method both on your **eCommerce** or on the **Customer Portal** by
|
||||
activating SDD as a **Payment Provider**. With this method, your customers can create and sign their
|
||||
mandates themselves.
|
||||
|
||||
To do so, go to :menuselection:`Accounting --> Configuration --> Payment Providers`, click on *SEPA
|
||||
Direct Debit*, and set it up according to your needs.
|
||||
To do so, go to :menuselection:`Accounting app --> Configuration --> Payment Acquirers`, click on
|
||||
:guilabel:`SEPA Direct Debit`.
|
||||
|
||||
.. important::
|
||||
Make sure to change the :guilabel:`State` field to :guilabel:`Enabled`, and to check
|
||||
:guilabel:`Online Signature`, as this is necessary to let your customers sign their mandates.
|
||||
|
||||
Customers using SDD as payment method get prompted to add their IBAN, email address, and to sign
|
||||
their SEPA Direct Debit mandate.
|
||||
|
||||
.. todo::
|
||||
Add link to future **Payment Provider** documentation.
|
||||
|
||||
Close or revoke a mandate
|
||||
-------------------------
|
||||
|
||||
Direct debit mandates are closed automatically after their :guilabel:`End Date`. If this field is
|
||||
left blank, the mandate keeps being **Active** until it is **Closed** or **Revoked**.
|
||||
|
||||
Clicking on :guilabel:`Close` updates the mandate’s end day to the current day. This means that
|
||||
invoices issued after the present day will not be processed with an SDD payment.
|
||||
|
||||
Clicking on :guilabel:`Revoke` disables the mandate immediately. No SDD payment can be registered
|
||||
anymore, regardless of the invoice’s date. However, payments that have already been registered are
|
||||
still included in the next SDD `.xml` file.
|
||||
|
||||
.. warning::
|
||||
Once a mandate has been :guilabel:`closed` or :guilabel:`revoked`, it cannot be reactivated.
|
||||
|
||||
Get paid with SEPA Direct Debit batch payments
|
||||
==============================================
|
||||
|
||||
Customer invoices
|
||||
-----------------
|
||||
|
||||
You can register SDD payments for invoices issued to customers who have an active SDD mandate.
|
||||
|
||||
To do so, open the invoice, click on :guilabel:`Register Payment`, and choose
|
||||
:guilabel:`SEPA Direct Debit` as payment method.
|
||||
|
||||
Generate SEPA Direct Debit `.XML` files to submit payments
|
||||
----------------------------------------------------------
|
||||
|
||||
`.xml` files with all SDD payment instructions can be uploaded to your online banking interface
|
||||
to process all payments at once.
|
||||
|
||||
.. note::
|
||||
The files generated by Odoo follow the SEPA Direct Debit **PAIN.008.001.02** specifications, as
|
||||
required by the SEPA customer-to-bank `implementation guidelines
|
||||
<https://www.europeanpaymentscouncil.eu/document-library/implementation-guidelines/sepa-credit-transfer-customer-psp-implementation>`_,
|
||||
which ensures compatibility with the banks.
|
||||
|
||||
To generate your `.xml` file of multiple pending SDD payments, you can create a batch payment.
|
||||
To do so, go to :menuselection:`Accounting app --> Customers --> Payments`, select the needed
|
||||
payments, then click on :guilabel:`Action`, and finally :guilabel:`Create a batch Payment`. Once
|
||||
you click on :guilabel:`Validate`, the `.xml` file is directly available for download.
|
||||
|
||||
.. image:: batch_sdd/xml.png
|
||||
:align: center
|
||||
:alt: Generate an .XML file for your SDD payments in Odoo Accounting
|
||||
|
||||
Finally, upload this file to your online banking interface to process the payments.
|
||||
|
||||
.. tip::
|
||||
You can retrieve all the generated SDD `.xml` files by going to
|
||||
:menuselection:`Accounting app --> Customers --> Batch Payments`.
|
||||
|
||||
.. seealso::
|
||||
* :doc:`batch`
|
||||
* :doc:`../bank`
|
||||
* `List of all SEPA countries
|
||||
<https://www.europeanpaymentscouncil.eu/document-library/other/epc-list-sepa-scheme-countries>`_
|
||||
* `Sepa guidelines
|
||||
<https://www.europeanpaymentscouncil.eu/document-library/implementation-guidelines/sepa-credit-transfer-inter-psp-implementation-guidelines>`_
|
||||
|
After Width: | Height: | Size: 22 KiB |
|
After Width: | Height: | Size: 9.2 KiB |
|
After Width: | Height: | Size: 5.6 KiB |
|
After Width: | Height: | Size: 5.1 KiB |
@@ -0,0 +1,148 @@
|
||||
======
|
||||
Checks
|
||||
======
|
||||
|
||||
There are two ways to handle payments received by checks. Odoo support
|
||||
both approaches so that you can use the one that better fits your
|
||||
habits.
|
||||
|
||||
1. **Undeposited Funds:**
|
||||
once you receive the check, you record a payment
|
||||
by check on the invoice. (using a Check journal and posted on the
|
||||
Undeposited Fund account) Then, once the check arrives in your
|
||||
bank account, move money from Undeposited Funds to your bank
|
||||
account.
|
||||
|
||||
2. **One journal entry only:**
|
||||
once your receive the check, you record a
|
||||
payment on your bank, paid by check, without going through the
|
||||
**Undeposited Funds**. Once you process your bank statement, you do
|
||||
the matching with your bank feed and the check payment, without
|
||||
creating a dedicated journal entry.
|
||||
|
||||
We recommend the first approach as it is more accurate (your bank
|
||||
account balance is accurate, taking into accounts checks that have not
|
||||
been cashed yet). Both approaches require the same effort.
|
||||
|
||||
Even if the first method is cleaner, Odoo support the second approach
|
||||
because some accountants are used to it (quickbooks and peachtree
|
||||
users).
|
||||
|
||||
.. Note::
|
||||
You may have a look at the *Deposit Ticket feature* if you deposit
|
||||
several checks to your bank accounts in batch.
|
||||
|
||||
Option 1: Undeposited Funds
|
||||
===========================
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
- Create a journal **Checks**
|
||||
|
||||
- Set **Undeposited Checks** as a default credit/debit account
|
||||
|
||||
- Set the bank account related to this journal as **Allow Reconciliation**
|
||||
|
||||
From check payments to bank statements
|
||||
--------------------------------------
|
||||
|
||||
The first way to handle checks is to create a check journal. Thus,
|
||||
checks become a payment method in itself and you will record two
|
||||
transactions.
|
||||
|
||||
Once you receive a customer check, go to the related invoice and click
|
||||
on **Register Payment**. Fill in the information about the payment:
|
||||
|
||||
- Payment method: Check Journal (that you configured with the debit and
|
||||
credit default accounts as **Undeposited Funds**)
|
||||
|
||||
- Memo: write the Check number
|
||||
|
||||
.. image:: checks/check02.png
|
||||
|
||||
This operation will produce the following journal entry:
|
||||
|
||||
+----------------------+-------------------+----------+----------+
|
||||
| Account | Statement Match | Debit | Credit |
|
||||
+======================+===================+==========+==========+
|
||||
| Account Receivable | | | 100.00 |
|
||||
+----------------------+-------------------+----------+----------+
|
||||
| Undeposited Funds | | 100.00 | |
|
||||
+----------------------+-------------------+----------+----------+
|
||||
|
||||
The invoice is marked as paid as soon as you record the check.
|
||||
|
||||
Then, once you get the bank statements, you will match this statement
|
||||
with the check that is in Undeposited Funds.
|
||||
|
||||
+---------------------+-------------------+----------+----------+
|
||||
| Account | Statement Match | Debit | Credit |
|
||||
+=====================+===================+==========+==========+
|
||||
| Undeposited Funds | X | | 100.00 |
|
||||
+---------------------+-------------------+----------+----------+
|
||||
| Bank | | 100.00 | |
|
||||
+---------------------+-------------------+----------+----------+
|
||||
|
||||
|
||||
If you use this approach to manage received checks, you get the list of
|
||||
checks that have not been cashed in the **Undeposit Funds** account
|
||||
(accessible, for example, from the general ledger).
|
||||
|
||||
.. Note::
|
||||
Both methods will produce the same data in your accounting at the
|
||||
end of the process. But, if you have checks that have not been cashed,
|
||||
this one is cleaner because those checks have not been reported yet on
|
||||
your bank account.
|
||||
|
||||
Option 2: One journal entry only
|
||||
================================
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
These is nothing to configure if you plan to manage your checks using
|
||||
this method.
|
||||
|
||||
From check payments to bank statements
|
||||
--------------------------------------
|
||||
|
||||
Once you receive a customer check, go to the related invoice and click
|
||||
on **Register Payment**. Fill in the information about the payment:
|
||||
|
||||
- **Payment method:** the bank that will be used for the deposit
|
||||
|
||||
- Memo: write the check number
|
||||
|
||||
.. image:: checks/check03.png
|
||||
|
||||
The invoice is marked as paid as soon as you record the check.
|
||||
|
||||
Once you will receive the bank statements, you will do the matching with
|
||||
the statement and this actual payment. (technically: point this payment
|
||||
and relate it to the statement line)
|
||||
|
||||
With this approach, you will get the following journal entry in your
|
||||
books:
|
||||
|
||||
+----------------------+-------------------+----------+----------+
|
||||
| Account | Statement Match | Debit | Credit |
|
||||
+======================+===================+==========+==========+
|
||||
| Account Receivable | X | | 100.00 |
|
||||
+----------------------+-------------------+----------+----------+
|
||||
| Bank | | 100.00 | |
|
||||
+----------------------+-------------------+----------+----------+
|
||||
|
||||
.. tip::
|
||||
You may also record the payment directly without going on the
|
||||
customer invoice, using the menu :menuselection:`Sales --> Payments`. This method may
|
||||
be more convenient if you have a lot of checks to record in a batch but
|
||||
you will have to reconcile entries afterwards (matching payments with
|
||||
invoices)
|
||||
|
||||
If you use this approach to manage received checks, you can use the
|
||||
report **Bank Reconciliation Report** to verify which checks have been
|
||||
received or paid by the bank. (this report is available from the **More**
|
||||
option from the Accounting dashboard on the related bank account).
|
||||
|
||||
.. image:: checks/check01.png
|
||||
|
After Width: | Height: | Size: 21 KiB |
|
After Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 12 KiB |
@@ -0,0 +1,79 @@
|
||||
=====================
|
||||
Follow-up on invoices
|
||||
=====================
|
||||
|
||||
A follow-up message can be sent to customers when a payment is overdue. Odoo helps you identify late
|
||||
payments and allows you to schedule and send the appropriate reminders, using **follow-up actions**
|
||||
that trigger automatically one or more actions according to the number of overdue days. You can send
|
||||
your follow-ups via different means such as email, post, or SMS.
|
||||
|
||||
.. seealso::
|
||||
- `Odoo Tutorials: Payment Follow-up <https://www.odoo.com/slides/slide/payment-follow-up-1682>`_
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
To configure a :guilabel:`Follow-Up Action`, go to :menuselection:`Accounting --> Configuration -->
|
||||
Follow-up Levels`. Several follow-up actions are available by default, and you can customize them
|
||||
any way you want or create new ones to trigger the following actions:
|
||||
|
||||
- Send an email;
|
||||
- :ref:`Send an SMS message <pricing/pricing_and_faq>`;
|
||||
- Print a letter;
|
||||
- :ref:`Send a letter <customer_invoices/snailmail>`;
|
||||
- Manual action (creates a task).
|
||||
|
||||
It is also possible to automatically send a reminder by enabling the :guilabel:`Auto Execute`
|
||||
option, within a specific :guilabel:`Follow-Up Action`.
|
||||
|
||||
.. tip::
|
||||
To send a reminder before the actual due date is reached, set a negative number of due days.
|
||||
|
||||
Follow-up reports
|
||||
=================
|
||||
|
||||
The overdue invoices you need to follow up on are available in :menuselection:`Accounting -->
|
||||
Customers --> Follow-up Reports`. From there, you can identify all the customers that have late
|
||||
unpaid invoices.
|
||||
|
||||
When you open a customer, you see all their unpaid invoices (overdue or not). The due dates of the
|
||||
late invoices appear in red. Select the invoices that are not late yet in the :guilabel:`Excluded`
|
||||
column to exclude them from the reminder you send.
|
||||
|
||||
It is up to you to decide how to remind your customer. You can select :guilabel:`Print Letter`,
|
||||
:guilabel:`Send By Email`, :guilabel:`Send By Post`, :guilabel:`Send By SMS`. Then, click on
|
||||
:guilabel:`Done` to view the next follow-up that needs your attention.
|
||||
|
||||
.. note::
|
||||
- The contact information available on the invoice or on the contact form is used to send the
|
||||
reminder.
|
||||
- When the reminder is sent, it is documented in the chatter of the invoice.
|
||||
- If it is not the right time for a reminder, you can specify the :guilabel:`Next Reminder Date`
|
||||
and click on :guilabel:`Remind me later`. You will get the next report according to the next
|
||||
reminder date set on the statement.
|
||||
|
||||
.. tip::
|
||||
Reconcile your bank statements right before launching your follow-up process to avoid sending a
|
||||
reminder to a customer that has already paid you.
|
||||
|
||||
Debtor's trust level
|
||||
--------------------
|
||||
|
||||
To know whether a customer usually pays late or not, you can set a trust level by marking them as
|
||||
:guilabel:`Good Debtor`, :guilabel:`Normal Debtor`, or :guilabel:`Bad Debtor` on their follow-up
|
||||
report. To do so, click on the bullet next to the customer's name and select a trust level.
|
||||
|
||||
.. image:: follow_up/debtors-trust-level.png
|
||||
:alt: Set debtor's trust level
|
||||
|
||||
Send reminders in batches
|
||||
-------------------------
|
||||
|
||||
You can send reminder emails in batches from the :guilabel:`Follow-up Reports` page. To do so,
|
||||
select all the reports you would like to process, click on the :guilabel:`Action` gear icon, and
|
||||
select :guilabel:`Process follow-ups`.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../general/in_app_purchase`
|
||||
- :doc:`../../../marketing/sms_marketing/pricing/pricing_and_faq`
|
||||
- :doc:`../customer_invoices/snailmail`
|
||||
|
After Width: | Height: | Size: 7.0 KiB |
@@ -0,0 +1,48 @@
|
||||
============================
|
||||
Forecast future bills to pay
|
||||
============================
|
||||
|
||||
In Odoo, you can manage payments by setting automatic **Payments Terms** and **follow-ups**.
|
||||
|
||||
Configuration: payment terms
|
||||
============================
|
||||
|
||||
In order to track vendor conditions, we use **Payment Terms** in Odoo. They allow keeping track of
|
||||
due dates on invoices. Examples of **Payment Terms** are:
|
||||
|
||||
- 50% within 30 days
|
||||
- 50% within 45 days
|
||||
|
||||
To create them, go to :menuselection:`Accounting --> Configuration --> Invoicing: Payment Terms` and
|
||||
click on :guilabel:`Create` to add new terms or click existing ones to modify them.
|
||||
|
||||
.. seealso::
|
||||
`Odoo Tutorials: Payment Terms
|
||||
<https://www.odoo.com/slides/slide/payment-terms-1679?fullscreen=1>`_
|
||||
|
||||
Once **Payment Terms** are defined, you can assign them to your vendor by default. To do so, go to
|
||||
:menuselection:`Vendors --> Vendors`, select a vendor, click the :guilabel:`Sales & Purchase` tab,
|
||||
and select a specific **Payment Term**. This way, every time you purchase from this vendor, Odoo
|
||||
automatically proposes the chosen Payment Term.
|
||||
|
||||
.. note::
|
||||
If you do not set a specific Payment Term on a vendor, you can still set one on the vendor bill.
|
||||
|
||||
Forecast bills to pay with the aged payable report
|
||||
==================================================
|
||||
|
||||
To track amounts to be paid to the vendors, use the **Aged Payable** report. To access it, go to
|
||||
:menuselection:`Accounting --> Reporting --> Partner Reports: Aged Payable`. This report gives you a
|
||||
summary per vendor of the amounts to pay, compared to their due date (the due date being computed on
|
||||
each bill using the terms). This report tells you how much you will have to pay within the following
|
||||
months.
|
||||
|
||||
Select bills to pay
|
||||
===================
|
||||
|
||||
You can get a list of all your vendor bills by going to :menuselection:`Vendors --> Bills`. To view
|
||||
only the bills that you need to pay, click :menuselection:`Filters --> Bills to Pay`. To view only
|
||||
overdue payments, select the :guilabel:`Overdue` filter instead.
|
||||
|
||||
You can also group bills by their due date by clicking :menuselection:`Group By --> Due Date` and
|
||||
selecting a time period.
|
||||
|
After Width: | Height: | Size: 15 KiB |
@@ -0,0 +1,147 @@
|
||||
==================
|
||||
Internal transfers
|
||||
==================
|
||||
|
||||
In Odoo, internal money transfers can be made in a few clicks. You need at least either two bank
|
||||
accounts, two cash journals, or one bank account and one cash journal.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
An internal transfer account is automatically created on your database based on your company's
|
||||
localization and depending on your country’s legislation. If needed, the default :guilabel:`Internal
|
||||
transfer account` can be modified by going to :menuselection:`Accounting app --> Configuration -->
|
||||
Settings` and then under the :guilabel:`Default Accounts` section.
|
||||
|
||||
.. note::
|
||||
At least two bank accounts are needed to make internal transfers. Refer to
|
||||
:doc:`Bank and cash accounts section <../bank>` to see how to add an additional bank
|
||||
account to your database.
|
||||
|
||||
Register an internal transfer from one bank to another
|
||||
======================================================
|
||||
|
||||
Let's say you have two bank accounts registered on your database and you want to transfer 1,000 USD
|
||||
from Bank A to Bank B.
|
||||
|
||||
Log an internal transfer
|
||||
------------------------
|
||||
|
||||
From the Accounting Dashboard, click on the drop-down selection button (:guilabel:`⋮`) on one of
|
||||
your banks. In the :guilabel:`New` column click on :guilabel:`Internal Transfer` and enter the
|
||||
information related to the transfer.
|
||||
|
||||
.. image:: internal_transfers/internal_transfer.png
|
||||
:align: center
|
||||
:alt: Fill in the information related to your internal transfer
|
||||
|
||||
.. note::
|
||||
Fill in the :guilabel:`Memo` field for automatic reconciliation.
|
||||
|
||||
:guilabel:`Save` and :guilabel:`Confirm` to register your internal transfer. The money is now booked
|
||||
in the transfer account and another payment is **automatically** created in the destination journal
|
||||
(Bank B).
|
||||
|
||||
Bank journal (Bank A)
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
|
||||
* - **Account**
|
||||
- **Debit**
|
||||
- **Credit**
|
||||
* - Outstanding Payments account
|
||||
-
|
||||
- $1,000
|
||||
* - **Internal transfer account**
|
||||
- **$1,000**
|
||||
-
|
||||
|
||||
Automated booking - Bank journal (BANK B)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
|
||||
* - **Account**
|
||||
- **Debit**
|
||||
- **Credit**
|
||||
* - Outstanding Receipts account
|
||||
- $1,000
|
||||
-
|
||||
* - **Internal transfer account**
|
||||
-
|
||||
- **$1,000**
|
||||
|
||||
.. note::
|
||||
There are one outstanding payment and one outstanding receipt pending in your two bank account
|
||||
journals, because the bank statement confirming the sending and receiving of the money has not
|
||||
been booked yet.
|
||||
|
||||
.. image:: internal_transfers/outstanding-payments-receipts.png
|
||||
:align: center
|
||||
:alt: Outstanding Payments/Receipts pending bank statement booking
|
||||
|
||||
.. _interbank/import-and-reconcile:
|
||||
|
||||
Manage and reconcile bank statements
|
||||
------------------------------------
|
||||
|
||||
The next step is to book the bank statements to finalize the transaction by creating,
|
||||
:doc:`importing <../bank/transactions>`, or :doc:`synchronizing <../bank/bank_synchronization>` your
|
||||
:guilabel:`Transactions lines`. Fill in the :guilabel:`Ending balance` and click on the
|
||||
:guilabel:`Reconcile` button.
|
||||
|
||||
.. image:: internal_transfers/transactions-line.png
|
||||
:align: center
|
||||
:alt: Transaction lines to be filled in prior to reconciliation
|
||||
|
||||
.. seealso::
|
||||
:doc:`../bank/reconciliation`
|
||||
|
||||
In the next window, choose counterparts for the payment - in this example, the outstanding payment
|
||||
account - then click :guilabel:`Validate`.
|
||||
|
||||
.. image:: internal_transfers/bank-reconciliation.png
|
||||
:align: center
|
||||
:alt: Reconcile your payment
|
||||
|
||||
Bank journal entry
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
|
||||
* - **Account**
|
||||
- **Debit**
|
||||
- **Credit**
|
||||
* - Outstanding Payment
|
||||
- $1,000
|
||||
-
|
||||
* - Bank Account (BANK A)
|
||||
-
|
||||
- **$1,000**
|
||||
|
||||
The same steps must be repeated once you receive the bank statement related to Bank B. Book and
|
||||
reconcile your bank statement lines.
|
||||
|
||||
Bank journal entry
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
|
||||
* - **Account**
|
||||
- **Debit**
|
||||
- **Credit**
|
||||
* - Outstanding Receipt
|
||||
-
|
||||
- $1,000
|
||||
* - Bank Account (BANK B)
|
||||
- **$1,000**
|
||||
-
|
||||
|
After Width: | Height: | Size: 56 KiB |
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 26 KiB |
@@ -0,0 +1,53 @@
|
||||
=========================
|
||||
Pay several bills at once
|
||||
=========================
|
||||
|
||||
Odoo offers the possibility of grouping multiple bills' payments into one, facilitating the
|
||||
reconciliation process.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`/applications/inventory_and_mrp/purchase/manage_deals/manage`
|
||||
- :doc:`/applications/finance/accounting/bank/reconciliation`
|
||||
|
||||
Group payments
|
||||
==============
|
||||
|
||||
To register the payment of multiple bills at once, go to :menuselection:`Accounting app -->
|
||||
Vendors --> Bills`. Then, select the bills you wish to register a payment for by **ticking** the
|
||||
boxes next to the bills. When done, either click :guilabel:`Register Payment` or
|
||||
:menuselection:`Action --> Register Payment`.
|
||||
|
||||
.. image:: multiple/register-payment-button.png
|
||||
:align: center
|
||||
:alt: Register payment button.
|
||||
|
||||
.. note::
|
||||
Payments can only be registered for :guilabel:`posted` bills.
|
||||
|
||||
When registering the payments, a **pop-up window** appears. From here, you can either create
|
||||
**separate payments** for each bill all at once by clicking :guilabel:`Create Payment`, *or* create
|
||||
one payment by combining **all** bills' payments. To **combine** all payments, tick the
|
||||
:guilabel:`Group Payments` box.
|
||||
|
||||
.. note::
|
||||
The :guilabel:`Group Payments` option only appears when selecting two or more bills.
|
||||
|
||||
.. image:: multiple/multiple-group-payments.png
|
||||
:align: center
|
||||
:alt: Group payments options when registering a payment.
|
||||
|
||||
When selecting :guilabel:`Group Payments`, the :guilabel:`amount, currency, date and memo` are all
|
||||
set automatically, but you can modify them according to your needs.
|
||||
|
||||
Partial group payments with cash discounts
|
||||
------------------------------------------
|
||||
|
||||
In case of **partial group payments with cash discounts**, you can follow the steps found on the
|
||||
:doc:`cash discount documentation page
|
||||
</applications/finance/accounting/customer_invoices/cash_discounts>`. Make sure to
|
||||
apply the :doc:`payment terms
|
||||
</applications/finance/accounting/customer_invoices/payment_terms>` to the **bills**
|
||||
*instead* of the invoices.
|
||||
|
||||
.. seealso::
|
||||
:doc:`/applications/finance/accounting/customer_invoices/payment_terms`
|
||||
|
After Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 36 KiB |
@@ -0,0 +1,49 @@
|
||||
:show-content:
|
||||
|
||||
===============
|
||||
Online payments
|
||||
===============
|
||||
|
||||
.. toctree::
|
||||
|
||||
online/install_portal_patch
|
||||
|
||||
To make it more convenient for your customers to pay the invoices you issue, you can activate the
|
||||
**Invoice Online Payment** feature, which adds a *Pay Now* button on their **Customer Portal**. This
|
||||
allows your customers to see their invoices online and pay directly with their favorite payment
|
||||
method, making the payment process much easier.
|
||||
|
||||
.. image:: online/online-payment-providers.png
|
||||
:align: center
|
||||
:alt: Payment provider choice after having clicked on "Pay Now"
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Make sure your :ref:`Payment Providers are correctly configured <payment_providers/configuration>`.
|
||||
|
||||
.. note::
|
||||
By default, ":doc:`Wire Transfer </applications/finance/payment_providers/wire_transfer>`" is the only
|
||||
Payment Provider activated, but you still have to fill out the payment details.
|
||||
|
||||
To activate the Invoice Online Payment, go to :menuselection:`Accounting --> Configuration -->
|
||||
Settings --> Customer Payments`, enable **Invoice Online Payment**, and click on *Save*.
|
||||
|
||||
Customer Portal
|
||||
===============
|
||||
|
||||
After issuing the invoice, click on *Send & Print* and send the invoice by email to the customer.
|
||||
They will receive an email with a link that redirects them to the invoice on their **Customer
|
||||
Portal**.
|
||||
|
||||
.. image:: online/view-invoice.png
|
||||
:alt: Email with a link to view the invoice online on the Customer Portal.
|
||||
|
||||
They can choose which Payment Provider to use by clicking on *Pay Now*.
|
||||
|
||||
.. image:: online/pay-now.png
|
||||
:alt: "Pay now" button on an invoice in the Customer Portal.
|
||||
|
||||
.. seealso::
|
||||
|
||||
- :doc:`/applications/finance/payment_providers`
|
||||
@@ -0,0 +1,57 @@
|
||||
===================================================
|
||||
Install the patch to disable online invoice payment
|
||||
===================================================
|
||||
|
||||
Following recent changes in Odoo 16, you might be warned that disabling the :guilabel:`Invoice
|
||||
Online Payment` setting will uninstall modules. If you want to disable the feature without
|
||||
uninstalling modules, follow the steps below to install the module **Payment - Account / Invoice
|
||||
Online Payment Patch**.
|
||||
|
||||
.. note::
|
||||
| If your Odoo database is created after the module **Payment - Account / Invoice Online Payment
|
||||
Patch** was released, you don't have anything to do.
|
||||
| To check if the module is already installed, go to :guilabel:`Apps`, remove the `Apps` filter,
|
||||
and search for `account_payment`. If the module **Payment - Account / Invoice Online Payment
|
||||
Patch** is present and marked as installed, your Odoo database is already up-to-date and you
|
||||
are able to disable the feature without side-effect.
|
||||
|
||||
Update Odoo to the latest release
|
||||
=================================
|
||||
|
||||
The possibility to disable the :guilabel:`Invoice Online Payment` setting without side-effect is
|
||||
made available through a new Odoo module; to be able to install it, you must make sure that your
|
||||
Odoo source code is up-to-date.
|
||||
|
||||
If you use Odoo on Odoo.com or Odoo.sh platform, your code is already up-to-date and you can proceed
|
||||
to the next step.
|
||||
|
||||
If you use Odoo with an on-premise setup or through a partner, you must update your installation as
|
||||
detailed in :doc:`this documentation page </administration/maintain/update>`, or by contacting your
|
||||
integrating partner.
|
||||
|
||||
Update the list of available modules
|
||||
====================================
|
||||
|
||||
New modules must be *discovered* by your Odoo instance to be available in the **Apps** menu.
|
||||
|
||||
To do so, activate the :ref:`developer mode <developer-mode>`, and go to :menuselection:`Apps -->
|
||||
Update Apps List`. A wizard will ask for confirmation.
|
||||
|
||||
Install the module Invoice Online Payment Patch
|
||||
===============================================
|
||||
|
||||
.. warning::
|
||||
You should never install new modules in your production database without first testing them in a
|
||||
duplicate or staging environment. For Odoo.com customers, a duplicate database can be created
|
||||
from the database management page. For Odoo.sh users, you should use a staging or duplicate
|
||||
database. For on-premise users, you should use a staging environment---contact your integrating
|
||||
partner for more information regarding how to test a new module in your particular setup.
|
||||
|
||||
The module should now be available in your :guilabel:`Apps` menu. Remove the ``Apps`` filter and
|
||||
search for ``account_payment``; the module :guilabel:`Payment - Account / Invoice Online Payment Patch`
|
||||
should be available for installation. If you cannot find the module after having updated the list
|
||||
of available modules, it means your Odoo source code is not up-to-date; refer to step one of this
|
||||
page.
|
||||
|
||||
Once the module is installed, disabling the feature will work as intended and will not ask you to
|
||||
uninstall installed applications or modules.
|
||||
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 7.7 KiB |
|
After Width: | Height: | Size: 4.9 KiB |
@@ -0,0 +1,61 @@
|
||||
=============
|
||||
Pay by checks
|
||||
=============
|
||||
|
||||
Once you decide to pay a supplier bill, you can select to pay by check. You can then print all the
|
||||
payments registered by check. Finally, the bank reconciliation process will match the checks you
|
||||
sent to suppliers with actual bank statements.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Activate checks payment methods
|
||||
-------------------------------
|
||||
|
||||
To activate the checks payment method, go to :menuselection:`Accounting --> Configuration -->
|
||||
Checks`, there you can activate the payment method as well as set up the :guilabel:`Check Layout`.
|
||||
Once activated the :guilabel:`Checks` setting, the feature is automatically setup for your
|
||||
:guilabel:`Outgoing Payments`.
|
||||
|
||||
.. note::
|
||||
Some countries require specific modules to print checks; such modules may be installed by
|
||||
default. For instance, the :guilabel:`U.S. Checks Layout` module is required to print U.S.
|
||||
checks.
|
||||
|
||||
Compatible check stationery for printing checks
|
||||
===============================================
|
||||
|
||||
United States
|
||||
-------------
|
||||
|
||||
For the United States, Odoo supports by default the check formats of:
|
||||
|
||||
- **Quickbooks & Quicken**: check on top, stubs in the middle and bottom;
|
||||
- **Peachtree**: check in the middle, stubs on top and bottom;
|
||||
- **ADP**: check in the bottom, and stubs on the top.
|
||||
|
||||
Pay a supplier bill with a check
|
||||
================================
|
||||
|
||||
Paying a supplier with a check is done in three steps:
|
||||
|
||||
1. registering a payment
|
||||
2. printing checks in batch for all registered payments
|
||||
3. reconciling bank statements
|
||||
|
||||
Register a payment by check
|
||||
---------------------------
|
||||
|
||||
To register a payment, open any supplier bill from the menu :menuselection:`Purchases --> Vendor
|
||||
Bills`.
|
||||
Once the supplier bill is validated, you can register a payment. Set the :guilabel:`Payment Method`
|
||||
to :guilabel:`Checks` and validate the payment.
|
||||
|
||||
Print checks
|
||||
------------
|
||||
|
||||
On your :guilabel:`Accounting Dashboard` in the :guilabel:`Bank` Journal, you can see the
|
||||
number of checks registered. By clicking on :guilabel:`Checks to print` you have got the possibility
|
||||
to print the reconciled checks.
|
||||
|
||||
To print all checks in batch, select all payments from the list view and click on :guilabel:`Print`.
|
||||
@@ -0,0 +1,86 @@
|
||||
=============
|
||||
Pay with SEPA
|
||||
=============
|
||||
|
||||
SEPA, the Single Euro Payments Area, is a payment-integration initiative of the European Union to
|
||||
simplify bank transfers denominated in euros. SEPA allows you to send payment orders to your
|
||||
bank to automate bank wire transfers.
|
||||
|
||||
SEPA is supported by the banks of the 27 EU member states, as well as:
|
||||
|
||||
EFTA countries:
|
||||
|
||||
- Iceland;
|
||||
- Liechtenstein;
|
||||
- Norway;
|
||||
- Switzerland.
|
||||
|
||||
Non-EEA SEPA countries:
|
||||
|
||||
- Andorra;
|
||||
- Monaco;
|
||||
- San Marino;
|
||||
- United Kingdom;
|
||||
- Vatican City State.
|
||||
|
||||
Non-EEA territories:
|
||||
|
||||
- Saint-Pierre-et-Miquelon;
|
||||
- Guernsey;
|
||||
- Jersey;
|
||||
- Isle of Man.
|
||||
|
||||
When paying a bill in Odoo, you can select SEPA mandates as a payment option. At the day's end,
|
||||
you can generate the SEPA file containing all bank wire transfers and send it to the bank.
|
||||
|
||||
By default, the file follows the SEPA Credit Transfer **'pain.001.001.03'** specifications. This is
|
||||
a well-defined standard among banks. However, for Swiss and German companies, other formats are used
|
||||
**'pain.001.001.03.ch.02'** for Switzerland and **'pain.001.003.03'** for Germany.
|
||||
|
||||
Once the payments are processed by your bank, you can directly import the account statement in
|
||||
Odoo. The bank reconciliation process will seamlessly match the SEPA orders you sent to your bank
|
||||
with actual bank statements.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Activate SEPA Credit Transfer (SCT)
|
||||
-----------------------------------
|
||||
|
||||
To pay suppliers with SEPA, you must activate the **SEPA Credit Transfer** setting. To do so, go to
|
||||
:menuselection:`Accounting --> Configuration --> Settings --> Vendor Payments: SEPA Credit Transfer
|
||||
(SCT)`. By activating the setting and filling out your company data, you will be able to use the
|
||||
SCT option when paying your vendor.
|
||||
|
||||
.. note::
|
||||
According to the localization package installed, the **SEPA Direct Debit** and **SEPA Credit
|
||||
Transfer** modules may be installed by default. If not, they need to be :ref:`installed <general/install>`.
|
||||
|
||||
Activate SEPA payment methods on banks
|
||||
--------------------------------------
|
||||
|
||||
From the accounting dashboard, click on the drop-down menu (:guilabel:`⋮`) on your bank journal and
|
||||
select :guilabel:`Configuration`. Click the :guilabel:`Outgoing Payments` tab, and, if not already
|
||||
present, add :guilabel:`SEPA Credit Transfer` under :guilabel:`Payment Method`.
|
||||
|
||||
Make sure to specify the IBAN account number (domestic account numbers do not work with SEPA) and
|
||||
the BIC (bank identifier code) in the :guilabel:`Journal Entries` tab.
|
||||
|
||||
Registering payments
|
||||
--------------------
|
||||
|
||||
You can register and vendor payments made with SEPA. To do so, go to :menuselection:`Accounting -->
|
||||
Vendors --> Payments`. When creating your payment, select :guilabel:`SEPA Credit Transfer` as the
|
||||
:guilabel:`Payment Method`.
|
||||
|
||||
The first time you pay a vendor with SEPA, you have to fill in the :guilabel:`Recipient Bank
|
||||
Account` field with the bank name, IBAN, and BIC (Bank Identifier Code). Odoo automatically verifies
|
||||
if the IBAN format is respected.
|
||||
|
||||
For future payments to this vendor, Odoo will automatically suggest you the bank account, but it
|
||||
remains possible to select a new one.
|
||||
|
||||
Once your payment is registered, do not forget to confirm it. You can also pay vendor bills from the
|
||||
bill directly using the :guilabel:`Register Payment` button at the top of a vendor bill.
|
||||
The form is the same, but the payment is directly linked to the bill and will be automatically
|
||||
reconciled with it.
|
||||
|
After Width: | Height: | Size: 7.2 KiB |
@@ -0,0 +1,61 @@
|
||||
=============================
|
||||
Trusted accounts (send money)
|
||||
=============================
|
||||
|
||||
To protect users from sending money to scammers, vendor bank account numbers must be marked as
|
||||
trusted before you can use them to make an outgoing payment.
|
||||
|
||||
To do so, open the vendor bank account and click on the :guilabel:`Send Money` toggle switch button.
|
||||
|
||||
.. image:: trusted_accounts/send-money-toggle.png
|
||||
:align: center
|
||||
:alt: Example of a vendor bank account with the "Send Money" toggle button switched to "trusted."
|
||||
|
||||
.. note::
|
||||
All accounts are initially marked as untrusted.
|
||||
|
||||
Phishing attacks
|
||||
================
|
||||
|
||||
A **phishing attack** is an online scam designed to trick individuals or companies into giving away
|
||||
sensitive information or money by sending out fraudulent communication. Fraudsters pretend to be
|
||||
legitimate companies and may use partial information to give credibility to their requests.
|
||||
|
||||
There are several types of phishing attacks, including **invoice fraud**. In this case, the
|
||||
fraudster pretends to be a genuine supplier following up on unpaid bills or sending a new invoice,
|
||||
but with different payment information than usual and with fake contact details.
|
||||
|
||||
To protect yourself from these types of phishing attacks, remain vigilant when you receive
|
||||
unexpected invoices or payment requests.
|
||||
|
||||
.. important::
|
||||
In case of doubt, **we recommend contacting the vendor by phone**. Make sure to call an official
|
||||
phone number by searching yourself, as the URLs, email addresses, and phone numbers written in
|
||||
the communication you received may be fake.
|
||||
|
||||
Elements to check
|
||||
-----------------
|
||||
|
||||
There are several elements you can check by yourself when you receive an outgoing payment request to
|
||||
a new account:
|
||||
|
||||
Communication style
|
||||
Fraudulent emails and invoices often use a different communication style, such as **different
|
||||
wording**, and may include **spelling and grammatical mistakes**. Examine and **compare** them
|
||||
with previous ones that you know to be authentic (e.g., payment instructions, language, company
|
||||
logo, etc.).*
|
||||
|
||||
Urgency
|
||||
Invoice frauds often use **urgent or threatening language** and change the **payment deadline**.
|
||||
Check if you really received a late payment reminder previously.
|
||||
|
||||
Type of account
|
||||
A company is unlikely to replace a bank account with a **money transfer service**.
|
||||
|
||||
Email and links domain names
|
||||
Double-check the **email address domain** (`example@domain.com`). However, be wary that fraudsters
|
||||
can make their email addresses look genuine or even hack email addresses from your vendor's
|
||||
employees or even someone within your own organization.
|
||||
|
||||
Hover over the links in your email and check that the URLs they redirect to are genuine. Your
|
||||
internet browser usually displays the link's target at the bottom left of the window.
|
||||
|
After Width: | Height: | Size: 4.8 KiB |