I have seen one option in odoo accounting "Fiscal Position" under
Accounting => Configuration => Accounting => Fiscal Position
I have checked it's features but I am not really getting at which point of time it's really useful or we can implement it where.
Features are very useful that all about tax and account mapping.
I would like to know it's importance, because I think so it's useful feature in odoo.
In Germany it's a really important feature. For example if you're a german company and sell goods mostly nationallly but sometimes internationally you don't have to take VAT from the customer (internationally), because Germany has double tax agreements with other countries.
But you will configure your Odoo products for the most used case -> national selling. Odoo gets lots of configured data like default tax and default accounts from the chosen product. But selling a product internationally means you have to take other taxes and accounts (in Germany for example!).
You could either handle that manually by changing taxes and accounts in invoices or you can use fiscal positions! Letter one will handle it on a much faster way.
Here a german example:
Product "Software Odoo": default tax 19% VAT, default Account 8400 (german SKR03, don't ask ;-))
Fiscal Position "Not EU":
tax mapping: 19% VAT -> no tax
account mapping: 8400 -> 8120
Creating an invoice for a non EU partner and this fiscal position, will set/map the taxes and accounts on every new invoice line automatically.
Actually that's no programming question and answer, but i've taken too much effort to write this, so i hope it will help you a bit ;-)
Like #CZoellner said.
it's a way to configure odoo to change the taxs automaticly for a partner.
for example by default our taxes 19% but when we deal with import && export partner the taxes are not applicable so instead of removing this taxes manually because as you know when you select a product the taxes are loaded,
by defining the Fiscal position of partner this is don automaticly by odoo (19% tax --> 0% tax).
Related
I wish to make to rules/conditions regarding shipping and prices. I have tried several things so far, but with no result. The 2 rules are as following (The currency is Danish Crown - DKK):
When you buy products in the price interval 0-500 DKK, you have to
pay additionally 50 DKK for shipping.
When you buy products for (in total) over 500 DKK, there is free shipping.
So far, we have managed to make the second rule (free shipping when buying for more than 500 DKK). But how can I make the first rule?
Thanks in advance
EDIT:
I have 2 shipping companies to choose from. For each of them, there are some specific rules regarding weight.
I just need to make sure that (regardless of which shipping company it is) there will be added an additional 50 DK when the price is between 0 and 500 DKK. Above 500 DKK, the shipping is free.
I have hear from the some where the char of account is used based on the different country it means that the char of account used based on different different country and analytical account is used as in service type of products.
I don't know am i right or wrong.
Please clarify me in depth which situation we are using the chart of account and which is not and which situation we are using the analytical account in ODOO (Formally) and which is not.
In principle, accounts that made up the chart of accounts are taken into general ledger posting i.e used to prepare BS, P/L etc, while the analytical accounting are mainly used only for companies internal use and doesn't affect anything in real accounting.
The general accounting system is a legal obligation. It must conform to certain accounting principles and must represent a fair picture of the financial situation of the company by producing a balance sheet and a profit and loss statement. Its foundation is the Chart of Accounts, made up of eight classes. Classes 1-5 are balance sheet accounts and classes 6 and 7 (expenses and revenues) are used for the profit and loss statement. All journals and accounts post to the General Ledger.
The second accounting system used in some countries is called Analytical Accounting. Its main purpose is to track expense and revenue accounts by categories in order to derive profit and loss by activity. Its foundation is a separate Chart of Accounts made up of a single class (class 9). Its journals and accounts post to a separate ledger (the Analytical Ledger.)
Some European countries use two types of accounting systems. (The United States and most other countries use only one.)
The chart of accounting will differ from country to country. For example US uses Account receivable and Account payable accounts which is equal to Debtors and Creditors accounts in Indian accounting. So Odoo keeps the chart of account based on the country.
Chart of Accounts are real accounts used for legal Purpose but Analytic Accounts are Just like same but only for Analysis Purpose like Budget Management Purpose etc.
Is there a way to get the most recent amount of property tax paid using the Zillow API? I can obtain the assessed value - just not the amount paid in taxes.
This information is available on the Zillow website in the Tax History section when viewing a property's detail.
Sample property on Zillow - scroll down to Tax History
Zillow gives the year the Tax assessment and the Assessed Value of the home that year. It also provides a link to the county assessors website. Basically this means that you have to find out the Mill Levy amount and then calculate the monthly or yearly taxes from that number. In Colorado this is area by area levy found on the county assessors website, so it may differ in different parts of your city, state and much different between states.
To calculate the property tax, the authority will multiply the assessed value of the property by the mill rate and then divide by 1,000. For example, a property with an assessed value of $50,000 located in a municipality with a mill rate of 20 mills would have a property tax bill of $1,000 per year. ~Wikipedia
Seems like Zillow has this info on their website so they should be able to open that up in their API, but sadly they don't. Makes for a lot of extra work! Good Luck
I have searched and searched but to no avail... has anybody created a payroll module for a U.S. based company? It seems that most of what I've seen is that companies are using payroll companies to process their payroll, but I haven't found anybody using OpenERP 7 for hourly employees with the U.S. tax system (it's not a flat tax rate).
It seems like what I may have to do, is create tax table in PostgresQL for federal, state, and local taxes, then reference those tables in the deduction calculation. I read one article on using the vendors/ or suppliers module and implementing a tax structure from that, but then again, those are still flat rates. I have to believe someone else has done this for the U.S. payroll system, and probably done it better than I could as I am fairly new to OpenERP.
I am in the process of doing something similar for LedgerSMB. The thing is that doing this on an open source model is extremely painful business-model-wise. I am working on solutions to that part but that's outside the scope of your question.
In general many US taxes are set up in marginal rates with certain minimums and maximums. For example income tax withholding is a set of marginal rates within tax brackets. Same with FICA and FUMA, but FICA taxes are capped at a certain level, so a simple tax table with rates, minimums, maximums, etc. and then a way of handling deductions to determine the correct line may be sufficient.
But users of most open source ERP's use third party services for payroll.
I have worked in an ERP. How we did is just calculate the FIT in yearly for all the employee and subtract the withholding amount with multiples.
FIT => Taxable Wages Yearly - (No.of withholding(Exemption))
Do the process as per the revision based on single or married only for annually. No need to update all the tables.
Then,
Divided it based on the frequency from the employee table information
EX:
for monthly : FIT/12
for daily : FIT/365
For SIT you have to use based on the document in the state usine case function.
We create point of sale software for the mac, and are looking to revamp our tax engine. It's pretty simple now, with taxes consisting of a name, code and rate that can be applied to every product individually. While this is good enough for some people, we've had lots of requests to handle more advanced situations. Some examples are US City/County sales tax, Canadian compound (stacked) taxes, French ecotax and NYC luxury tax.
We've identified most of the characteristics that these taxes have and are leaning towards a sort of rule-engine based implementation. We don't have to support every case out there, but we want to be able to extend it if needed (to avoid another rewrite).
We're looking for advise from people who built something like this before, or examples of projects that try to solve the same in an elegant way.
My suggestion would be to use database tables for what they are good for (storing values) and rules for what they are good for (business logic). I would certainly not put things like tax rates or lists of jurisdictions in rules - those should be in tables. What I would use a rules engine for is defining the logic that determines which rate to apply to which transactions. So, for instance, if I buy a set of products online from a company based in State X that ships from State Y to three different locations, what tax rates apply to which parts of the transaction?
This combination of rules and database tables is very common - the rules make sure you look up the right things while the tables aid in reporting etc. For instance, the California DMV did this with vehicle registration fees - all the various fees are stored in a database while the rules that determine which fee applies to which car are managed in a rulebase.
If you try and put everything in rules you will not be able to report well and if you try and put everything in database tables you will end up with dozens of tables to manage all the exceptions and corner cases.
JT
I would recommend a set of database tables and joins.
Example:
Jurisdiction: list of states, counties, countries, cities, etc.
Product: obvious
Store: list of locations you sell from
StoreJurisdiction(StoreID, JurisdictionID): the list of Jurisdictions the store is
responsible to collect taxes for
ProductTaxCode(ProductID int, TaxCodeID int): the type of product for the purposes of taxes: basic, luxury, etc.
JurisdictionTaxCodeRate(JurisdictionID, TaxCodeID, InterestRate, RateType): for each applicable combination of Jurisdiction and Tax Code, provide the tax rate to be applied, and the type of rate (compound, simple, etc.).
To find the list of taxes to apply, all you need is an INNER JOIN of the store, its jurisdictions, the jurisdictiontaxcoderates for those Jurisdictions, and the product's tax codes.
You could define ProductTaxCode as a View so all products receive a default TaxCode unless a special one is provided. By abstracting TaxCode, you can have the same metadata about a product ("Food" for instance) apply to different regions in different ways. If a particular jurisdiction has its own definition of "food", you just add a jurisdiction-specific code and apply it to products as needed.
This may require some tweaking for Internet purchases, wholesale purchases, and other situations where the sale is somehow exempt from taxes or the customer is responsible for remitting them. It would also need tweaking for situations where the customer's location, rather than the store, decides the tax rate.
Other tweaks: here in Texas, for instance, we have a "tax-free" weekend where state and local taxes are not collected on some classes of products where the individual item's sale price is less than $100. The idea is to provide cheaper school supplies, clothing, etc. for children heading off to school for a new year. This sort of tweak could be implemented by having a date range table for each JurisdictionTaxCodeRate going off in the future as far as they can be planned.
Here is an example of a "home rule" city in the Denver, CO metropolitan area:
http://www.c3gov.com/pages/about/division_salestax.html
You, as a retailer, may also need to send the tax payments to different locations. For cities that are not "home rule" cities (which is a special term that probably only applies to Colorado, but then probably every state has some equally special term like it), you'll send all the tax payments to the state who will then deal them out to the relevant parties. Colorado has a feature where there are "special tax districts" that are permitted to collect sales taxes for certain benefits (on the example link, RTD is the public transportation district, and "Invesco Field" is the stadium where the Denver Broncos play).
To expand upon Mr Tallent's answer on this thread, you'll need to also include in the Jurisdiction table some way of representing that the taxes may go to different places.