Our support team received a lots of questions recently around how to handle invoices when using OFN.
We have two large groups who are starting to use OFN (including a former Food Assembly), but are stuck with the invoices issue. As the food assembly had a legally compliant solutions to invoices, they expect the same from the tool they are choosing.
So far our biggest users were either not invoicing in France, or not using online payment through the OFN, so not using OFN invoices was working fine.
In a nutshell, the biggest problem with invoices in France so far is that you don’t have sequential numbers (and cannot have traceability on all the order amendments). A lot more has been described around this problem & linked tech solutions here: Trace order amendments through invoice lines and generate legally compliant invoices
Also the former Food Assembly don’t invoice the customers but the producers, so they need a way to export the data and build invoices for the producers for the commission they take on those sales. AND the producers need a way for their customers to get an invoice as well, legally they have to… The Food Assembly was sending an invoice from the producers to the customers, and from the hub manager to the producers.
With this post, I’m not looking for OFN tech solutions as we agree that spree upgrade / make what we have great was our priority, and we are fine with it. I’m reaching here to see if we could find a hack / something else in the meantime.
So far with @MyriamBoure we have looked at the following info:
- See if there is a report that could give us enough info to import the data (manually) in another tool. While the Xero report has all line items info, it has not enough info on tax, and reverse for the tax report.
- Zapier ? We could extract in a Googlesheet the data needed, and then import them in an invoicing package through a csv.
From what we understand in UK you find a solution for this? @lin_d_hop do you think we could set-up a zoom so you can show us what you did? If it’s really complex and needs someone to be trained for, we are also ready to pay for it. And then we can share the load of documenting everything for the community.
- Waiting for the API to be documented, and see what we can use from there. But the timeframe is unknown, and our two users are starting their activity in March.
- Or they can do manually the invoices, every producer should do one invoice per customer, and the hub manager should do one invoice per producer… I guess it is not acceptable.
Also what do you think: are there other solutions that we might have forgotten? Do you have other ideas that would help us to propose solutions to these enterprises?
ping @Kirsten @sauloperez @nick @luisramos0 @maikel @Matt-Yorkley