| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Sales (sale_management) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 1224 |
| Technical Name |
kw_fop |
| License | LGPL-3 |
| Website | https://kitworks.systems/ |
| Versions | 14.0 17.0 18.0 19.0 |
FOP Sales and Accounting
Single-install bundle for Ukrainian sole proprietor (FOP) sales and accounting workflow. Bundles three purpose-built modules: FOP Seller registry, FOP Invoice fields and templates, FOP Act of Work Performed printout.
Why this suite
Multi-FOP registry
Manage unlimited FOP entities in one database. Each seller is an independent record with its own identity, banks and tax set.
Per-FOP sequences
Each FOP gets its own invoice number sequence and a separate sale-invoice number sequence — auditable, never collide with company invoice sequence.
Per-FOP analytic
Every FOP becomes an analytic account under the dedicated "FOPs" plan. Slice your P&L per individual entrepreneur.
Ukrainian print forms
Rakhunok-Faktura (invoice), Vydatkova Nakladna (goods delivery note), Akt vykonanykh robit (act of work performed) — all in Ukrainian.
Default-tax automation
Switching the FOP seller on an invoice replaces line tax_ids with the seller's configured default tax set automatically.
Default-FOP setting
Pick a default FOP in standard Odoo Settings. New invoices pre-fill the seller, contract reference and amount-in-words helpers automatically.
Members of this suite
Installing this bundle pulls in three feature modules:
account.move with FOP-seller fields. Renders the Rakhunok-Faktura and Vydatkova Nakladna A4 print forms in Ukrainian, with amount-in-words via num2words.See it before you buy
Book a live demo and we will walk you through the multi-FOP workflow end-to-end — seller setup, invoice creation, Rakhunok and Akt printouts, per-FOP analytics.
Book a live demoMaintained by Kitworks Systems. Reach out at info@kitworks.systems for installation help, bug reports or custom integrations.
Please log in to comment on this module