I have a request to build a report that shows Revenue by State - for the purposes of taxes.
As an Organization we're very new with FO (only a few months in), and I'm more a SQL/PowerBI developer - I can reproduce the Revenue #s that FO puts out, using hte BYOD - and I can see the WorkLocation for a given transaction.
But, "purposes of taxes" makes me think this should be something built in - or at least configured, to come out of FO itself - not some dork writing SQL stored procs.
Any guidance?
The ST module works fine when it relates to ST transactions only. We have no issues here. The problem is that many US states require a total revenue for the period (both taxable and non-taxable). This is where the ST module falls short as it is only engaged on taxable transactions leaving the development community to build reports that will capture all sales for a location as required by the taxing authorities.
It really depends on what the business' definition of "purposes of taxes" means. F&O does have a Sales/Use tax module but is it being used? There are also a number of 3rd party API-based products that calculate Sales/Use tax (Vertex, CCH, AvaTax). Does the business need a way of calculating sales tax liability and/or remittances or do they just want it for reporting?
In general, F&O OOB reporting is pretty weak. I have a customer requesting the same type of report - Sales by State - and I've told them it would be best to develop it in Power BI because nothing OOB will meet their requirements.
Following as this has been a thorn for several of our clients.
André Arnaud de Cal...
291,979
Super User 2025 Season 1
Martin Dráb
230,848
Most Valuable Professional
nmaenpaa
101,156