10 ms·
People would legitimately be surprised to learn how low tech ordering/invoicing/remittances remain in 2017 even for half billion dollar contracts. There's very
by Someone1234 10y ago
People would legitimately be surprised to learn how low tech ordering/invoicing/remittances remain in 2017 even for half billion dollar contracts.
There's very little automation, even EDI is the exception rather than the rule (particularly for one off orders), most are either still paper, fax, or insecure email.
Email remains pretty broken. You'll be lucky to get end to end encryption, and once it arrives it is hard to make assurances that the sender really sent it (or even the sender's domain).
People have tried to fix email but nothing as ambitious as TLS/HTTPS has been. And getting people to use a more secure platform built on top of HTTPS is likely a non-starter...
So what can be done? I legitimately don't know. Even snail mail can be "hacked" via sending a plausible sounding invoice to the right address at the right time.
- dahart 10y agoI'd be extremely surprised if half billion dollar contracts were automated in any way, that seems like a really bad idea.
- L_Rahman 10y agoAutomating the payment would be a really bad idea, but the workflow of receiving the contract/invoice, running it through internal systems, negotiation and legal could use some software help.
- dahart 10y agoAll my contract negotiation & signing over a few bucks has been done using cloud based encrypted services for years. Yes email is not encrypted, but I'm not sure what the problem is, or how this even relates to the article. This was a phishing scam over new deals. New deals can't generally be automated, shouldn't generally be automated, and the issue here involved human factors that are likely to always exist. The presumption that more computers and more encryption could fix what happened in this story seems misguided to me.
- javiramos 10y agoTotally agree.. This process is SO broken and frustrating.
- tyingq 10y agoI wonder how long a less greedy approach would have worked. I would guess a larger number of smaller invoices might have gone unnoticed for some time. This egregious approach lasted for 2 years.
- bitJericho 10y agoEmail uses tls. If both ends support it, it uses it. Most popular email providers support it. Also, dmarc signs emails the guaranteeing domains, and if you want email to be reliable, you must support dmarc.
- pas 10y agoMany providers won't throw out emails with invalid DKIM signatures. Many senders (!) specify too lax SPF rules. (Because feedback loops are not accessible/open/standardized enough.) And furthermore TLS only protects the email between hops. But yes, email is not the problem. The problem is of course human error and legacy systems that are not user friendly. If they were properly composable then there would be no need for occasional out-of-band channels for sending/receiving invoices - like email.
- jerf 10y ago"People have tried to fix email but nothing as ambitious as TLS/HTTPS has been. And getting people to use a more secure platform built on top of HTTPS is likely a non-starter..." Makes me wonder if it's time to metaphorically pack it in, and respecify the SMTP infrastructure on top of HTTP(S), precisely because that seems like the only way we're going to get cert security with email systems. As long as it's an optional add-on to SMTP it seems it just isn't going to be added on. (Of course SMTP wouldn't go anywhere right away; I'm talking about a real process with transition times and such, not a mystical one where this would one day replace SMTP in a big bang.) I mean, there's a loooot of i's to dot and t's to cross betwixt this little comment and an actual standard, but conceptually it doesn't seem too difficult. SMTP is conversational standard but it seems like we've probably got enough negotiation tech in HTTP to pull it off in a request/response manner nowadays.
- Xylakant 10y ago> Makes me wonder if it's time to metaphorically pack it in, and respecify the SMTP infrastructure on top of HTTP(S), precisely because that seems like the only way we're going to get cert security with email systems. Transport security is not the actual issue. SMTP over TLS has been around for a while and is fairly well functional. The problem is attaching an identity to the senders email. That's what S/MIME and GPG/PGP do, but the actual real-world problem here is that you need to somehow certify that the sender is the right person. So you can either have a centralized set of authorities (S/MIME) or Web of Trust (GPG/PGP). Neither option actually scales. Some countries started issuing certificates in their ID cards, but given that other countries don't even have ID cards, this is obviously not going to fix this either. HTTPS has the same problems in principle, but it only needs to certify a comparatively small number of entities (web servers) as opposed to actual users.
- jerf 10y ago"Transport security is not the actual issue." From what I hear from security folks, transport security is still an issue. You can negotiate up to TLS easily in SMTP, as long as you don't care about certificate validity. But without caring about certificate validity, MITM is still quite possible.
- javiramos 10y ago"People would legitimately be surprised to learn how low tech ordering/invoicing/remittances remain in 2017 even for half billion dollar contracts." Totally agree with this. I occasionally deal with relatively large contracts and it is amazing the amount of labor behind processing purchase orders, invoices, etc. Many companies locate their accounts payable/receivable departments in low-cost countries.
- jdmichal 10y agoIf email is broken for sending invoices, then the correct response is to stop sending invoices over email. Banks figured this out already: Stop sending things directly in email, and instead send notifications. Have the user log into the banking system to see the notification. So, host invoices on your own domain, and only send links to clients. Clients can confirm they are talking to the correct server when downloading the invoice. Same as they should be used to doing for any email with links regarding money.
- michaelt 10y agoBanks figured this out already: Stop sending things directly in email, and instead send notifications. Yeah, and it sucks and everyone hates it. That's all very well when you're sending someone a bank statement and you don't care if they bother to read it - but when you want to send someone an invoice, and you're keen that they read it and respond in a timely manner, you need a higher standard of customer service.
- abraae 10y agoMost of the world seems happy to click through to read a Facebook notification, so I don't know why someone who gets paid to do it would not click through to see an invoice. The main problem with clicking through is normally clunky authentication systems that make it not just a click through, but a painful dance before you finally get to the target resource.
- jessaustin 10y agoClicking through doesn't solve any problems. It's real easy to spam people with links to www.mybank.com.evil.com. Only training the user to navigate directly can even hope to avoid such attacks.
- gpawl 10y agoThere's no problem with showing a preview of non-secure content. As long as the recipient knows to visit the official secure server for official copies of important information.
- dbg31415 10y ago"People would legitimately be surprised to learn how low tech ordering/invoicing/remittances remain in 2017 even for half billion dollar contracts." People in finance / accounting hate tech. Broad statement, I know... but if it's not Excel or whatever old and busted reporting system they have been using for the last 20 years, you know they are going to hate it and raise a huge stink if anyone tries to even upgrade them. This has been true for every company I have ever worked with. You say, "You are on a version that's 12 years old, and riddled with bugs and security flaws. The software maker put out an end of life notice back in 2008 for this version and has a big warning sign saying that continuing to use it is very dangerous and opens you up to hackers. Also, even though we have backups, we have no idea how to re-install it should something fail... we don't even have documentation on what service packs it requires to run and we're terrified someone will accidentally run Windows Update on the machine it's on for fear of breaking something..." Their response, "The new version changes the color of the button I use, so I don't want it." Every time. Anyone work for an agency and have to track your time in the Project Management system and the Accounting systems? This is why. Old-ass, no-API systems that simply won't play nice with anything modern -- and the accountants who love them.
- shitgoose 10y agousers refuse to upgrade because they know, that the new version will change the navigation, button colors, move menu items to ribbons and so on. not to mention it will contain new bugs and "features". see, users and devs have different perspectives. for user the software is the tool to perform a profit-generating business task (create invoice etc). for devs the software is a way of self-expression and an opportunity to change things because they can. devs despise user and his little business problems as much as business despises tech with its constant desire to storm into the room and start breaking things that were working perfectly fine before.
- aeorgnoieang 10y agoSeems like there's an opportunity ripe for exploiting then! Figure out how much it's worth to these companies to provide just enough support to keep the software running – as-is – forever. Certainly that should be easier than also changing the UX or whatever. But how hard is this? I imagine it'd be a lot harder than one might naively expect. As evidence, consider how few (if any?) companies already do this. Maintaining software requires significant work; doing so for more than one version is even harder; doing so for a decade-old version that only one customer uses is probably just not profitable. But, as a dev myself, I emphatically don't "despise user and his little business problems". I may tho – honestly – tell 'business' people or users that I can't guarantee that I can fix bugs because, e.g. I can't purchase a license for the (version of the) software needed to work with the project source code. It's perfectly fine for people to run software unchanged forever! As it is also perfectly fine for those same people to have to rebuild their business or a portion thereof around some new software when the existing software system fails catastrophically and can't be recovered.
- JacobDotVI 10y agoRequiring people to be involved in spending of large sums is often a feature and not a bug. It's not infallible but neither are computerized financial systems (e.g. SWIFT)