OmniApproval™ - Accounting Approvals
by Viindoo
| Lines of Code | 2041 |
| Technical name | viin_approval_account |
| License | OPL-1 |
| Website | https://viindoo.com/apps/modules/19.0/viin_approval_account |
| Read description for | v 17.0 v 18.0 |
| Required Apps | Invoicing (account) Discuss (mail) Employees (hr) |
| Included Dependencies | Viindoo Base OmniApproval™: One platform. Every approval. Advanced HR Management OmniApproval™ - Analytic Accounting Approvals Safe IR Metadata Proxies |
| Extensions | OmniApproval™ - Salary Disbursement Approval OmniApproval™ - Employee Advance Management OmniApproval™ - Purchase Approvals OmniApproval™ - Quote & Order Approvals |
Approve the entry before it is posted
Journal entries, invoices, journals and accounts on the approval request - so an accounting approval carries the document it is about.
OmniApproval™ - Accounting Approvals (technical name viin_approval_account) is an Odoo 19.0 app for Odoo Community and Odoo Enterprise and Viindoo Cloud, built for accountant, chief accountant, auditor, administrator.
At a Glance
The facts of OmniApproval™ - Accounting Approvals, version 0.1.3, in one place. Published by Viindoo.
How It Works
Three screens.
The request carries the document
The entry, the journal and the amount - on the request itself.
Configured per type
Which accounting fields the request carries, and whether they are required.
In one queue
Accounting approvals sit with purchases, contracts and the rest.
What You Get
Journal entries, invoices and journal items on the approval request
Journal, account and move type as request fields
Field toggles per approval type, on header and lines
Amount and currency carried for threshold rules
Sequential approvers, minimums and deadlines from the engine
The accounting documents themselves are unchanged
More Screens
Everything below was taken on a database seeded with real business data, on this series - not a mock-up and not a screenshot from an older version.
Field toggles per type
What This App Does Not Do
Read this before you buy. Everything below is something the app deliberately leaves to another app or to you.
Blocking is the approval state applied to the document by the engine.
Approval is a decision; posting stays the accountant's action.
This is the accounting bridge to that engine.
The request carries the amount; the rule that routes it is configuration.
Works Well With
Apps from the same stack, built to fit this one:
Who Should Use OmniApproval™ - Accounting Approvals?
Accountant
Sends an entry for approval with the entry attached.
Chief accountant
Approves with the lines in view, not from a description.
Auditor
Finds who authorised an unusual entry, and when.
Administrator
Decides per type which accounting fields a request must carry.
Frequently Asked Questions
What does OmniApproval™ - Accounting Approvals do?
Journal entries, invoices, journals and accounts on the approval request - so an accounting approval carries the document it is about.
What does OmniApproval™ - Accounting Approvals not do?
It does not block posting by itself. Blocking is the approval state applied to the document by the engine. It does not write entries. Approval is a decision; posting stays the accountant's action. It needs OmniApproval. This is the accounting bridge to that engine. Thresholds live in the approval type. The request carries the amount; the rule that routes it is configuration.
Who is OmniApproval™ - Accounting Approvals for?
Accountant: Sends an entry for approval with the entry attached. Chief accountant: Approves with the lines in view, not from a description. Auditor: Finds who authorised an unusual entry, and when. Administrator: Decides per type which accounting fields a request must carry.
Which Odoo version and editions does it support?
Odoo 19.0 - Odoo Community, Odoo Enterprise, Viindoo Cloud. Upgrades to a newer Odoo series are a separate purchase for that series.
What does it depend on?
It installs on top of: viin_approval, viin_approval_analytic, account. Odoo installs them with it.
How do I set it up?
Three screens.
What works well with it?
OmniApproval (viin_approval): The engine this extends. Accounting Foundation (viin_account): The accounting layer it plugs into. Accounting Reports (to_account_reports): Where the approved entries end up.
Can I try it before buying?
Yes - the Live Preview button at the top of this page opens a working database.
How do I get support?
Write to apps.support@viindoo.com with your Odoo version and the technical name viin_approval_account; pre-sales questions go to sales@viindoo.com.
See OmniApproval™ - Accounting Approvals in Action
Live demo: v19demo-int.viindoo.com
Need help with OmniApproval™ - Accounting Approvals?
For questions, implementation support or a custom feature, contact Viindoo.
Pre-Sales & Partnership
sales@viindoo.comUpgrades to a newer Odoo series are a separate purchase for that series.
All Viindoo apps: Viindoo Apps
Technical Requirement
Changes log
0.1.2 - Latest on the 17.0 line
- Accounting fields are available on request lines as well as on the header.
OmniApproval™ - Accounting Approvals
For invoicing users, accountants, approvers and approval administrators.
Note
Extends OmniApproval™ - see its documentation for roles, approvers, snapshots and every other engine feature. This guide only describes what the accounting approval types add.
Note
Builds on Invoicing and OmniApproval™ Analytic, whose analytic distribution column the request lines keep.
Overview
A customer invoice, a payment to a vendor and a refund to a customer all move money. The module adds three approval types to every company that has an accounting chart loaded: Customer Invoice, Vendor Payments and Customer Refunds. An invoicing user submits the document for approval, an approver decides on it and the document is then processed as usual.
The request lines also gain Taxes and Financial Account columns, and the totals of the request take the taxes into account.
| Role | What they do | Access right to assign |
|---|---|---|
| Invoicing user | Prepares the customer invoice, the vendor payment or the refund and submits it for approval. | Accounting: Invoicing |
| Accountant | Checks the taxes and the financial accounts of the lines before the document goes on. | Accounting: Administrator, with Show Full Accounting Features |
| Approver | Decides on the requests that reach them. | Team Approver or Officer |
| Approval administrator | Adjusts the three approval types. | Administrator (Approvals) |
The Team Approver, Officer and Administrator rights are described in the Roles and Access Rights section of the OmniApproval™ guide.
Setup (for the Administrator)
- Go to Apps, search for OmniApproval™ - Accounting Approvals and click Activate. The module is installed on its own when the Invoicing and OmniApproval™ apps are both installed.
- Open Approval > Configuration > Approval Types. Each company with an accounting chart has the types Customer Invoice, Vendor Payments and Customer Refunds, ready to use.
- Give each person the access right of their role under Settings > Users & Companies > Users.
Each of the three types asks the employee's manager for the first approval step and names no approver. Who approves, and in how many steps, is yours to decide: add approvers to the type as described in the Approvers section of the OmniApproval™ guide. The approval steps run one after another.
What the accounting types add
Customer Invoice
Only a customer invoice or credit note in Draft can be submitted. The request is filled in from the invoice:
| On the invoice | On the request |
|---|---|
| Invoice number | Invoice Number |
| Customer and company | Customer and the company |
| Salesperson | Salesperson |
| Invoice date | Invoice Date |
| Journal | Invoice Journal |
| Currency | The currency of the request |
| Each line: product, section or note, unit of measure, quantity, label, analytic distribution, financial account | The same columns of the request lines, under Invoice Lines |
| Each line: unit price, discount, taxes | Unit Price, Disc.%, Taxes |
The invoice number, the unit price, the discount and the taxes only travel from the invoice to the request: the request never changes them on the invoice.
The discount is applied exactly as on the invoice and the taxes are computed on the discounted amount, so the Total of a line is its amount including taxes and the total of the request equals the total of the invoice.
Vendor Payments and Customer Refunds
Both types start from payments. Vendor Payments applies to outgoing payments to vendors and Customer Refunds to outgoing payments to customers. One request can carry several payments: each payment becomes a line under Payments, with its label, the vendor or the customer, the amount, the date, the reference and the Payment Journal.
The lines of the request can also point to the Vendor Bill Lines or the Customer Invoice Lines the payments settle.
Taxes and financial accounts on the request lines
The request lines show these columns when the approval type enables them:
- Taxes - the taxes of the line, shown to users holding the Invoicing access right.
- Financial Account - the account of the line, shown to users who have the accounting features enabled (the Show Full Accounting Features or Show Accounting Features - Readonly rights of the user form).
- Tax Amount, Subtotal and Total - the optional columns of the line list; Tax Amount is hidden until you tick it. With several currencies in use, Tax Amount in Currency is available as well.
Using the accounting approvals
Submitting an invoice (Invoicing user)
Invoice approvals always start from the invoice itself: the Customer Invoice type does not create invoices of its own. The usual process is to prepare the invoice in Draft first and to get it approved before confirming it.
- Open the draft invoice and click Actions menu (the gear icon) > Get Approved.
- Check the approval type and the invoice shown in the Submit for Approval window.
- Click Create Approval Request.
The request opens in Draft, with the invoice lines under Invoice Lines.
Click Submit to send it to the approvers. Approving, refusing and the other decisions work as described in the OmniApproval™ guide.
Submitting payments (Invoicing user)
Open the list of vendor payments (or of customer payments for a refund), select the payments, click Actions menu (the gear icon) > Get Approved, choose Vendor Payments or Customer Refunds, and click Create Approval Request. Then click Submit on the request.
Confirming the approved invoice (Invoicing user)
Once the request is approved, confirm the invoice with its usual Confirm button. Posting the invoice is not a change to what was approved: the request records no note.
Approval never blocks Confirm by itself. See the Business Documents section of the OmniApproval™ guide to add a block.
Cancelling or refusing a request
When a request is cancelled, refused or reset to Draft, the invoice or the payments it was submitted from stay as they are. See the Cancelling, Refusing and Resetting to Draft section of the OmniApproval™ guide.
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.