What it does
This module is a bridge between Stock Asset and Inventory Backdate. When a member of the stock back-date
group validates an asset allocation transfer at a past date, the assets the transfer generates are
dated at that past date. It installs automatically when both modules are installed, and it is
uninstalled together with the back-date modules.
Key Features
- An asset generated by a back-dated asset allocation transfer carries the back-date as its Date,
and as its First Accounting Date when its category sets accounting dates manually.
- A user outside the back-date groups who asks for a back-date is refused, and no asset is
generated.
- Without a back-date, the asset carries the date at which the transfer is validated.
Editions Supported
- Community Edition
- Viindoo Cloud
Stock Asset - Backdate: user guide
This guide is for accountants and warehouse users who enter a company's past stock transfers, and
for the administrator who grants the right to do so.
Note
Back-dating is not meant for routine use. It serves to enter a company's past data during the
initial deployment, and the back-date modules are uninstalled once that work is done.
What this module does
This module is the bridge between Stock Asset (to_stock_asset)
and Inventory Backdate (viin_stock_backdate). It
installs by itself when both are installed, and it is uninstalled together with the back-date
modules. It has no screen and no setting of its own.
When a member of the Stock Backdate Operations group validates an asset allocation at a past
date, each asset the transfer generates carries that back-date as its Date and as its
acquisition date. When the asset category dates the first accounting manually, the First
Accounting Date takes the back-date too; with any other setting of the category, the first
accounting date follows the category's own rule.
Validate an asset allocation at a past date
- Open the asset allocation transfer in Inventory > Operations > Transfers.
- Press Validate. Because you belong to the Stock Backdate Operations group, the dialog
Validate with a Back Date opens.
- Enter the real date and time of the transfer in Transfer Date. It cannot be in the future.
- Press Validate.
The assets are generated in Draft, dated at the back-date. Without a back-date, an asset carries
the date at which the transfer is validated.
Who can back-date
Trust is granted per person: the administrator adds each person to the Stock Backdate Operations
group. A user outside the back-date groups who asks for a back-date is refused, and no asset is
generated.
Back-date before a lock date
When the back-date falls before a lock date of the accounting, the accounting lock rule moves the valuation journal
entry of the transfer to the first open date. The asset keeps the back-date. The accountant
should check the dates of such assets and entries; nothing blocks the transfer.
This software and associated files (the "Software") may only be
used
(executed, modified, executed after modifications) if you have
purchased a
valid license from the authors, typically via Odoo Apps,
or if you
have
received a written agreement from the authors of the
Software (see the
COPYRIGHT file).
You may develop Odoo modules that use the Software as a library
(typically
by depending on it, importing it and using its
resources), but
without
copying any source code or material from the
Software. You may distribute
those modules under the license of your
choice, provided that this
license
is compatible with the terms of
the Odoo Proprietary License (For
example:
LGPL, MIT, or proprietary
licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell
copies of the
Software or modified copies of the Software.
The above copyright notice and this permission notice must be
included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT
SHALL THE
AUTHORS OR COPYRIGHT HOLDERS
BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING
FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE
SOFTWARE.