infor.com
concierge
infor u
developer portal
Posts
Categories
Groups
Hubs
Developer
Healthcare
Hospitality
Public Sector
CloudSuites
Aerospace & Defense (LN)
Automotive (LN)
Chemicals (M3)
Corporate (FSM/HRT)
Distribution (Sx.e/CSD)
Distribution Enterprise (M3)
Engineering & Construction (LN)
Fashion (M3)
Food & Beverage (M3)
Healthcare (FSM/HRT)
Industrial (Syteline/CSI)
Industrial Enterprise (LN)
Manufacturing (M3)
Public Sector (FSM/HRT)
Solutions
Supply Chain Management (SCM)
Human Capital Management (HCM)
Events
Groups
Your Groups
User Groups
Migrated Forums
FSM/HCM/S3 - Infor Lawson 10.x
HCM/S3 - Learning and Development
HCM/S3 - Global HR
HCM/S3 - Talent Acquisition
HR Service Delivery
Human Capital Management (HCM) - EMEA
Infor Configuration Management for Service Industries
Lawson - Business Intelligence
Lawson - Financials
Lawson - Human Resources
Lawson - Supply Chain
Lawson - Supply Chain Management
Lawson - Technology
MSCM on Landmark
About
Community News
Email Community Support
Home
Groups
Pegasus - Partner Community
Tax point date problem
Legacy Contributor
I was wondering if anyone has experienced this before?
Clients use the invoicing mod in OPII.
they raise some manual invoices. 3 months later (or whenever), they go to run their VAT return & some of these invoices arent on it.
Upon investigation, the tax point date has moved on by exacly one month, meaning that say the invoice date is 16.3.11, the tax point date is 16.4.11
The clients are adamant that they havent gone in & changed this, either on purpose or by accident & they "need it sorted"!
I mean where can anyone start with that? Its not every invoice & theyre accusing Opera of changing the date by itself.
there is no bespoke & they cannot replicate this for us. Its "after the event" that they can show us. Ive had to dismiss this as user error & have asked them to keep an eye on things, but it does look a bit odd that in the last 10 years, its only started to happen since 16.2.11 (payroll upgrade time)
Many thanks
James
Find more posts tagged with
Component react.asset.postCommentThread had an error.
"https:\/\/us.v-cdn.net\u2026" is not a valid URL.
Important Links
Community Hubs
Discussion Forums
Groups
Community News
Popular Tags
CPQ: Ask a Colleague
FAQs, How-To, and Best Practices
Idea
Infor OS Portal
UI Design
CPQ: Tips and Tricks
Infor Homepages
Widget Development
Infor EPM Migration
Infor Ming.le