[anonymouse008]

Change this from ERP to POS and you've scripted 9/10ths of the pains for many quick service restaurant chains.

Story time: people are dense as hell. This one idiot put in his personal SSN to open $XX/m a year POS account. This account currently manages just over a hundred locations, and this fool's TIN has just been raking in millions for a few years all because 'I needed to get us signed up!' And what's better!? They still can't get out of the wet paper bag, because otherwise "we'll someone might start selling candy or something unapproved" > we'll isn't that's what your franchise liaisons and agreements are for?! I'm just beside myself.

I'm so hyped on this because this one 'immovable problem' prevents me from having API access to my locations accounts. Everything just hurts. /rant

[bombcar]

I swear the only way to get an ERP or POS change to work is to start a competitor using the new solution and wait for them to acquire you.

And then live forever with two systems running side by side.

[invalidlogin]

Would you mind breaking down the situation in a little more detail? Not my field and I find your story interesting.

[cutemonster]

I also don't totally understand, what's a TIN for example (Taxpayer Identification Number?) and why is it making money? (Don't taxes go to the state?)

[curious_curios]

Yeah, it’s the identifier the government uses to attribute income for, and hence calculate the resulting taxes.

In this case it sounds like a midsize business is using some random guy’s number, so the tax authorities are under the impression there’s a guy pulling in millions personally, and a company with no income. Given that individuals and companies get taxed differently in many different jurisdictions concurrently this will be a mess to untangle.

[cutemonster]

Wow that's amazing, thanks for explaining