In Odoo 10 Enterprise how would we exempt some customers without having to provide an exemption certificate? We may have many government customers who don't pay sales tax (cities, counties, states, military bases, etc.).
Also do we have Tax Exempt Certificate option for taxcloud in Odoo 10 enterprise?
Thanks,
Quick Answer: Yes, the Odoo TaxCloud implementation has automated exemption certificates on-board, but exempt purchasers will have to fill out the form once (17 fields, shouldn't take more than 2 minutes, once).
Developer Answer:
Please review our excellent developer-oriented exemption certificates implementation guide
Detailed Answer: This is less an Odoo question, and more a tax law question.
[Notice: This post should not be considered as "tax advice". You should direct questions of this nature to a licensed CPA or tax attorney.]
Exempt entities are required to provide retailers with
documentation (frequently exemption certificates) to substantiate
their claim for tax exempt treatment.
Retailers are required to collect applicable sales tax on all
sales, unless the purchaser qualifies as an exempt entity.
As a business decision, and as a convenience to exempt purchases, some retailers will allow a sale to proceed without obtaining an exemption certificate, but only because many states allow retailers up to 90 days after completing a sales to obtain the necessary documentation.
However, during audit the retailer will be held liable for all uncollected sales tax (including delinquent penalties, fines, and accrued interest) unless they provide the auditor with evidence of purchasers' exempt entity status (obtained within 90 days of sale).
Related
I am just trying out the open-API specs provided by tmforum https://www.tmforum.org/open-apis/ and cannot seem to figure out the difference and actual purpose of the financial account resource mentioned in account management API specs. Can someone please elaborate?
The financial account aggregates the amounts of one or more billing accounts owned by a given party. For example, as a customer, I may have multiple billing accounts (e.g. for broadband services for multiple properties) - the financial account is the aggregation of these billing accounts.
We use DoExpressCheckoutPayment API function to do payment authorization. The DoExpressCheckoutPayment response has ReceiptID field, which is empty if the payment was funded from a Paypal account or is filled if the payment was by credit card. Is the ReceiptID field also filled if the payment was by debit card? If so, how can we distinguish a receipt is that is for credit card from a receipt that is for debit card? Or is there some other way to distinguish debit card payments? We get a lot of fraudulent transactions with stolen credit cards. Since credit card payments are likely fraudulent and debit card payments are likely good, we would like to have a way to know whether a payment was from credit card or debit card to help us decide whether to accept the transaction or not.
Thanks
No, PayPal does not tell you how one of their accountholders is funding a payment. That information will not be available to you.
If you will permit me to editorialize for a minute, though:
That's a Good Thing, because the reality is much more complex than debit vs. credi. You don't want to try to second-guess all of these possibilities. Payments might be partially funded from multiple sources; have conditional aka backup funding; use "cards" that are neither the debit nor credit networks you are familiar with (e.g. hybrids like China Union Pay, virtual debit cards backed by who-knows-what, ...); various bank draft networks/mechanisms; PayPal lines of credit; etc. In general, PayPal is doing a LOT of sophisticated things to detect fraud and they deliver very low fraud rates for accountholder payments.
Also: if you are processing an accountholder payment (rather than a direct credit card payment), PayPal's seller protection policies replace whatever protections (usually not much!) you would receive from card networks for Card Not Present transactions. These protections do not depend upon what funding the accountholder uses and may be very useful to you. I recommend you read the policies and determine if you can align your business so that most or all of your sales can qualify for these protections.
If your usage cannot be eligible for PayPal Seller Protections, though, then while PayPal still runs their fraud detection they have a pretty limited set of facilities for you to layer on added fraud detection of your own. They will give you a limited amount of information about the accountholder, but as I noted above this does NOT normally include the account's funding source(s).
Balanced payments documentation is unclear about debits and credits. You have merchants, customers and accounts. It now says accounts are deprecated and to use customer. Can someone shed light on any corrections I have in my workflow:
Form with CC fields tokenizes card.
Create customer for buyer and add card.
Debit buyers card.
Create another Customer object.
Add a bank account to the Second customer object.
Credit Second Customer object
Do I need the merchant fields on the second customer object (dob, postal code, etc)?
Do I need to do underwriting to second customer object?
Your workflow is correct.
The Customer resource abstracts away from you the pain the Account resource had when dealing with underwriting a merchant. Underwriting is required as part of the KYC (Know Your Customer) operation requirements Balanced needs to follow. Each Customer has an attribute named is_identity_verified where you can know if the Customer's identity was verified. Ideally you want to make sure the identity is verified for each Customer to which you will be crediting. While you can still perform credits (I believe up to a certain limit) to Customers whose identity is not verified, you run the risk of increased fraud and there may eventually be consequences to your marketplace.
Also, feel free to stop by #balanced on IRC. You'll probably get much faster answers to your questions there directly from developers.
I work for a non-profit organisation and have created and online donations page. Recently this donations page has been used to validate stolen credit card details via the process known as Carding.
The way it works is that a slacker get hold of a whole bunch of credit details but doesn't know which numbers are good or not. So they go to a donations page and attempt a small donation ($5 or less) with the stolen card number. If the donations goes through then they can use the number for bigger purchases.
Carding can cost a non-profit a lot of money as most these "donations" will end being reversed and in some cases a charge back fee will be charged by the bank.
Has anyone else had experience with this? Also, what are some ways that I could stop it?
Off-topic, but I'll bite:
Don't accept "small" donations.
Don't accept "many" donations from the same IP address in a "short" time span.
Consider buying credit card fraud insurance.
What "small," "many," and "short" means is up to you.
If you're not doing this already, consider using PayPal exclusively for accepting credit cards.
With no programming skills required, our Donate button is an easy and affordable way to start accepting donations online.
Discounted rates for 501(c)(3) status
Your donors don't even need a PayPal account
Accept all major credit cards
Source
What they say about fraud protection:
If there's one thing people know about PayPal, it's how seriously we take security. Behind the scenes, we work to help keep you and your donors safe from fraud.
Automatic Fraud Screening
Guard your business with our relentless fraud screens, address (AVS) and card verification (CVV2) checks, and 128-bit encryption—all included at no extra charge.
PCI & CISP Compliance
PayPal adheres to international PCI (Payment Card Industry) and CISP (Cardholder Information Security Program) standards for data protection. These standards are designed to help protect your business from fraud and loss of data. Because we handle the payment card information, you don't have to worry about meeting compliance standards yourself or storing your customers' sensitive financial information.
Full disclaimer: I have no affiliation with PayPal or any credit card company. I do not run, or have any first-hand experience with, an e-commerce site, nonprofit site, or any other web site which accepts electronic payments. I am not a lawyer. I'm just a programmer.
My customer has revenues of 10.000 per week so I'm looking for a professional solution. I need a good payment gateway for my shop (Drupal Ubercart). I was considering to use Authorize.Net. Is it available in Europe ?
If you are in europe, please consider Ogone.
SagePay, Wirecard, and CyberSource are all good gateways in Europe. I've had really good experience with the support staff at Wirecard in particular.
For those that stumble upon this question, Authorize.net now supports UK and European businesses: http://www.authorize.net/en-GB/
I believe they're also adding support for Canadian businesses as well.
It is not available in Europe. It is only available for US based merchant accounts. You can take European credit cards through Authorize.Net but only if you have a US merchant account.
From their FAQ
At this time, we are only able to offer our services to U.S. based businesses, or merchants who have U.S. based merchant accounts.
Why don't you consider PayPal it is one of the widely most supported Payment Gateways, it works in Europe as you requested and from my knowledge is easily integrated/setup with ubercart.
In my opinion Authorize.net is the best payment gateway out there.
Also to quote their FAQ's:
Does Authorize.Net support
international transactions?Yes.
Merchants can submit transactions to
the payment gateway on behalf of
non-U.S. customers. To do so, the
merchant's bank account must be with a
financial institution located in the
United States, and the merchant must
be configured to accept the customer's
card type: Visa, MasterCard, American
Express, Discover, JCB, Diner's Club,
or EnRoute. The payment gateway will
submit the amount of the transaction
to the customer's card issuer, who
will then handle all currency
conversion to U.S. dollars. Since
default Address Verification Service
(AVS) settings may cause foreign
transactions to be declined, merchants
who plan to regularly accept
international transactions should make
sure that their AVS settings are
configured to meet their business
needs.
So this is the one I would choose and it is not very hard to implement.