Setting your business up for eInvoicing

The benefits of eInvoicing are becoming more and more enticing to businesses in these tricky times. Understanding the benefits is one thing but taking the next steps to getting started is a different story, at least that’s what businesses may believe. Here are steps, in straightforward terms, to set your business up for eInvoicing.

Look at your business

Define your objectives

There are a few things to do when getting started. The first is to define your objectives for implementing eInvoicing. These could be reducing manual processes, complying with partners’ eInvoicing requests, increasing cash flow or something else. Knowing these from the get-go will help keep your business on track.

Review your business processes

The next thing is to look at your business processes. Think about:
  • How many invoices are you processing?
  • Do you plan to send invoices, receive them, or both?
  • Do you exchange invoices with suppliers or customers who are overseas?
  • What are your current processes for receiving invoices, approving them, making payments, reporting and reconciling?
You can then use this information to tailor your eInvoicing solution to best suit you.

Get relevant internal departments involved

One internal department taking control over your eInvoicing project is not ideal. One, it prioritises the needs of one team over others, that’s not very collaborative. Two, there’s no transparency and understanding across the organisation about the project. There are three main departments that are generally involved in an eInvoicing project: Finance
  • They’ll be working directly with eInvoicing by switching from receiving paper or PDF invoices. They’ll be acting on the eInvoices that end up in your software so it’s important for them to have a say and understand how it works.
IT
  • eInvoicing works through your software so your IT team needs to be part of the process. They can help with a lot of the technical stuff working directly with your eInvoicing provider.
Management
  • Those involved in compliance and reporting or the handling of master data can benefit from eInvoicing. It gives these decision makers visibility of procurement and payment information.

Getting your software ready

Have a look at your software to see if they already provide Peppol eInvoicing as an option. If so, find out whether it would require and update or an additional cost. If your software isn’t ready, that’s not a problem, you can work with an eInvoicing service provider and Access Point like MessageXchange. They’ll be able to help you with all the file and connection protocol requirements to get you connected. All you generally need is the ability to import and/or export some sort of invoice file.

Testing messages

For businesses implementing e-invoicing there is some testing required before you can send and receive e-invoices. This is where help from your IT team will come in handy. One requirement is connectivity testing with your Access Point to ensure you can both exchange messages correctly. Testing is also performed on your file to ensure it is correctly structured.Need more help getting ready for eInvoicing? Ask our experts by getting in touch below.

Request a call

Chat with one of our experts

Just fill out your details below and we'll be in touch within one business day.

EDI adoption barriers and how to overcome them

EDI is pretty enticing when you look at its host of benefits:
  • cost savings
  • shortened procure-to-pay cycle
  • better data accuracy
  • less manual handling
  • better visibility into your supply chain
  • better customer service.
But as with any innovation, there are barriers that can get in the way of a business choosing to implement EDI. Here are some of those and how to overcome them.

Not understanding EDI and how it works

Simply put, EDI (electronic data interchange) is the exchange of business information directly between business software. Think of a purchase order being created in one company’s accounting package, and it ‘magically’ appears in the supplier’s software; no email, no PDF, no manual data entry. Well, it’s not magic, it’s EDI! Check out our whitepaper to learn all the basics. EDI can be pretty technical so this often makes it a little daunting for businesses. There’s also a sense of if you don’t have expertise you’ll have trouble implementing. The fact is, EDI providers, like MessageXchange, will always be there to clarify a lot about how it works and work with the relevant internal teams to make the process seamless.

Having unrealistic expectations

EDI requires clear expectations in terms of costs, timelines, internal operations and of suppliers. Rome wasn’t built in a day! When it comes to EDI, planning at the beginning is everything. This will give a clear direction for implementation and help assess how things are tracking compared to your targets. Keep these clear with your provider and hold them to it. The planning stage should also set clear expectations of who is responsible for what when EDI is implementation. Something else you can do is to get a clear understanding of price from your provider. All providers have different pricing models, make sure you find the one that suits your business most.

The capability of your supply chain

Your supply chain is critical to any EDI project. It can often make or break a project. So it can seem like a big barrier if you have difficulty getting suppliers onboard. But there are definitely ways around this. The number one thing to do when looking at onboarding suppliers is to segment them into groups and use this to stage your onboarding process. There’s no right or wrong way to segment your suppliers. It can be according to their readiness for EDI, maybe their size, whatever you like. As you’re onboard each segment it will give you an understanding of your progress. Another great way to get around suppliers not onboarding is by giving them options. If they’re already using EDI they can just integrate with your EDI solution. If they’re not using EDI, you can offer them a web portal solution, like Colladium. It makes it easier for suppliers, particularly smaller ones, to send and receive EDI messages all from a web browser.

Lack of resources

EDI is often linked with being costly and time intensive to set up but that’s changed a lot. These days businesses with no previous EDI experience are getting set up easily and quickly. EDI providers, like MessageXchange often step businesses through the whole process and even take care of critical parts. MessageXchange can create automated compliance testing solutions that test the EDI messages of suppliers on a portal to make sure it adheres to all EDI requirements. This saves you time and also saves your staff from having to contact suppliers one by one to organise testing. Need more help getting ready for EDI? Ask our experts by getting in touch below.

Request a call

Chat with one of our experts

Just fill out your details below and we'll be in touch within one business day.

Five automated checks in MessageXchange to get the invoices you need the first time around

Many large organisations have processes setup in their accounts payables systems to review invoices and approve them for payment. Often the rules are quite complex and can rely on certain information being present on the invoice for the process to run effectively. Introducing eInvoicing can appear to throw a spanner in the works here, but with MessageXchange, it can make it even easier in automating the presence and validity of the data. Have a look at these tips to help you get the invoice you need the first time around.

1. Ensure a purchase order number is present

If your invoice matching requires a purchase order number to be present, MessageXchange can check that it’s there before sending the invoice onto your software. If it’s not, MessageXchange can automatically reject the invoice and send feedback to the supplier with information as to why it was rejected. Another alternative is to still receive the eInvoice in your software but send a notification to the supplier to ask them to include the order number on their future eInvoices.

2. Ensure the purchase order number is correct

This can be done in a couple of ways – you can check that the order number has the same format of those you issue, like always 10 digits, or starting with certain numbers, or you can even share (automatically, of course) a list of your order numbers from your software, and MessageXchange will check that it matches, before sending the invoice onto you. We can even go one step further and check that the purchase order number and ABN combination are correct.

3. Only receive eInvoices from ABNs you know

Our customers can provide a list of their suppliers’ ABNs. When an eInvoice for the customer comes in, MessageXchange can check the sender ABN against this list. Again, if it matches, we’ll send it onto you. And if not, we can reject it and notify the supplier, or continue to send it onto you while notifying the supplier.

4. Check the BSB and account number

Some invoice approval processes check the BSB and account numbers on the invoice. You can check for correct formatting, or even ensure they match those you have on file. When an eInvoice comes through, MessageXchange can check for these to make sure you get only the eInvoices that you’ll be able to process.

5. Mandate attachments from certain suppliers

If you use an outsourced HR company, for example, and expect timesheets with your invoices, MessageXchange can check that eInvoices from certain ABNs always have an attachment. We can even go one further to specify that the attachment must always be an Excel sheet, for example.All of these checks, and more, can be implemented in your eInvoicing Gateway. These are just some examples, but the only real limitation is your imagination. Have a chat to our team today about how to make sure you get the invoices you want the first time around.

Request a call

Chat with one of our experts

Just fill out your details below and we'll be in touch within one business day.

eInvoicing with MessageXchange in a nutshell

If you’re just starting out with eInvoicing, or looking for an eInvoicing provider, the process can be pretty daunting and confusing. The good news is, this blog is just for you. Keep reading to find out the A to Z of eInvoicing with MessageXchange.

What is eInvoicing?

For those really new to eInvoicing, have a look at this whitepaper that explains in layman’s terms what eInvoicing is, how it’s used, its benefits and more.Ok, now you’re all up to speed with the basics…

It doesn’t matter what software you use for invoicing

The good news with our eInvoicing service is that it doesn’t matter what invoicing software you use. Our service is software-agnostic, which means we can connect to any software. In the diagram above, your software will be corners 1 or 4. We’ll handle all the nitty gritty between corners 1 and 3 (for sending invoices) and corners 4 and 2 (for receiving invoices) so you don’t have to worry about any added stress of finding new software. After all, we all know what a process and investment changing software can be.

Your software doesn’t support UBL files? No worries

Now that you’re all up-to-date with eInvoicing, you’ll know that UBL is the file format used between Access Points (corners 2 and 3) to exchange eInvoices. In reality, many software packages don’t support this file format. And this is something we’ve catered for. We can take your software’s native file format and translate, or map, this to and from the eInvoicing UBL file. For those non-technical people reading this – usually a software package exports an imports one specific file format, like XML or JSON.

MessageXchange provides both Access Point and SMP services

The introduction to eInvoicing whitepaper describes how the eInvoicing process works. When an eInvoice is received at the sender’s Access Point, it looks up where to send the eInvoice to. This lookup is done in an SMP, or service metadata publisher. So, when you register to receive eInvoices, you’ll need to register your ABN, NZBN or whatever identifier you use, in an SMP. MessageXchange provides this service for free for all its eInvoicing customers so it’s one less thing you need to worry about.

Options to suit every business

We offer a couple of different eInvoicing options, which should suit most, if not all businesses out there.

eInvoicing Connect

This is the perfect option if you want to get up and running quickly and cost-effectively. This product can be used for sending and receiving eInvoices, or just one or the other. It also caters for business response messages, which is sent from a recipient of an eInvoice to a sender to update them on the status of the eInvoice, for example, whether it’s been accepted, rejected, paid and more. We’ve got an existing integration with TechnologyOne CiAnywhere, but if you’re not using that software, you can connect to MessageXchange via SFTP or our AS2 to exchange UBL, XML or CSV files. We have a message implementation guide for our XML and CSV files so you can familiarise yourself with the structure. When it comes to pricing, get setup for as little as $950, which includes registration of one ABN or NZBN. Then it’s just $50 per annum (this covers the subscription to our Access Point) and $50 for a pack of 1,000 credits. One credit covers 1MB of data or part thereof of a single message, including attachments. eInvoicing Connect users get access to a portal, which allows you to view a log of the invoices you’ve sent and received and you can see your credit balance too. Find out more about eInvoicing Connect here.

eInvoicing Gateway

If you’re going to be an eInvoicing power user, or are looking at eInvoicing more strategically, our eInvoicing Gateway is for you. It’s got much more flexibility in that we can connect to any software using any secure connection protocol to exchange any file format (MessageXchange configures maps to translate your format to/from the UBL format). Plus, it’s got additional functionality. Our Gateways allow you to implement business rule validation, which can do things like reject an invoice if it doesn’t have the data you need. It can also enrich invoice data, like adding an internal vendor number based on the ABN it’s sent from, to make sure the invoice data your software receives is what you need. The data enrichment can also cater for outgoing invoices. This helps if your software doesn’t populate all the mandatory eInvoicing information, or the information that your customers require from you. Another benefit of our eInvoicing Gateways is it’s reporting and analytics functionality. Get access to custom reports based on any data in the invoices and even call on data from other sources. One case we’ve seen is top-level reporting on multiple business units. The functionality is all there, but how you use it is really up to your imagination and your business’ needs. Find out more about our eInvoicing Gateways here.

Onboarding suppliers

Yes, getting setup for eInvoicing is the thing we think about first, but onboarding your trading partners is what you’ll turn your attention to once that’s done. With our 20+ years in supply chain trading, we’ve got a few tips at the ready. We’ve developed a guide to help you engage and onboard your supply chain. Plus, we’ve got no- and low-cost solutions for your trading partners to send and receive eInvoices. Just ask us more.

Security is a top priority

We know invoice data is commercially sensitive and that’s why we do everything within our power to keep it secure. We’re ISO27001 accredited, we use encryption in transit and encryption at rest plus a range of other security, DR and BCP processes. Have a look here for more info.Ready to find out more? Have a chat with one of our eInvoicing experts.

Request a call

Chat with one of our experts

Just fill out your details below and we'll be in touch within one business day.

EDI best practices

EDI can be a big commitment, and following best practice from the get-go can save you time, money and hassles down the line. We’re pretty experienced helping customers implement EDI, so here are some pointers on how to get things right the first time.

Establish clear procedures

It’s important to have clear contact point for your trading partners to get in touch with you about EDI-related issues they may have. The last thing you want is a colleague who knows little or nothing about EDI being asked EDI questions and not knowing where to direct the question. Work out who will take care of EDI questions from suppliers and educate your team so they understand where to direct these enquiries. Another thing to think about having is a contingency plan if something goes wrong with your EDI. You need processes in place to be able to keep operating in the unlikely scenario of an issue.

Test, test, test

There’s nothing worse than sending EDI messages to your suppliers only for them to not receive it. Or even having suppliers sending you messages incorrectly. This can lead to stock not being on shelves and invoices not getting paid. Testing before going live can make the transition to EDI much more seamless. Organise a time to send and receive test EDI messages to and from your suppliers to ensure that you don’t run into any issues when you go live. If this sounds a bit too manual, you can use our message compliance testing (MCT) service on Colladium to automatically ensure the EDI messages you’ll receive follow the correct syntax and use the right fields.

Automate as many processes as possible

Before getting started with EDI, think about all the things you want automated – an EDI automation wish list so to speak. Think about all the areas that take up too much manual processing or add significant costs, for example not knowing if an order can be fulfilled, or not knowing when it’s going to be delivered. You can even look at the invoice payment process, which is often time consuming for your accounts team. EDI can automate matching purchase orders and other EDI documents with your invoices to ensure they are accurate and legitimate.

Be picky when choosing an EDI provider

It’ll come as no surprise that it’s important to have a list of things you expect from your ideal EDI provider. Have a think with your team about what you want in your provider. Think about:
  • if they meet your technical requirements
  • if their business aligns with yours
  • if they have the right experience
  • if their support model works for your business
  • if their pricing model suits you.
Need more help getting ready for EDI? Ask our experts by getting in touch below.

Request a call

Chat with one of our experts

Just fill out your details below and we'll be in touch within one business day.

Using EDI to improve supply chain efficiency

Improving efficiency is one way for businesses to help battle rising costs and inflation. One efficiency improvement businesses are turning to is EDI.

Reduce costs and errors

The big efficiency with EDI is there’s no need for emailing or paper, which has some obvious benefits. As your number of orders grow, so does manual processing and hence, the need for more hands on deck. EDI does a lot of the heavy lifting for you through automating a lot of your processes. Studies have shown EDI can reduce the cost of a financial transaction by up to 90% and exchanging an invoice through EDI can even cost less than a cent. Automation from EDI can stop those awkward moments where your customer asks why your invoice numbers are wrong or if a supplier delivers the wrong products. EDI can result in a reduction in transactions errors by up to 40%.

Faster delivery times from suppliers

For any businesses, one of their biggest nightmares is not receiving goods when they need it. Any way to make the procure-to-pay cycle shorter is always a benefit. EDI sends trade documents directly between your software and your partners’. No more emails and manual inputting. EDI automation can speed up business cycles by 61%.

Better supply chain visibility

The best way keep track of all processes in the supply chain is through data. Businesses using EDI can find out whether a supplier can complete a purchase order. If you use advanced shipping notices (ASNs) with your suppliers, you can find out what a supplier is sending you and how they’re sending it. This can help your warehouse teams plan ahead for deliveries, so you can save time and resources. In fact, using ASNs can reduce receiving costs by up to 40%. Have more questions? Ask our experts by getting in touch below.

Request a call

Chat with one of our experts

Just fill out your details below and we'll be in touch within one business day.

What rules the roost – EDI process or business- and software-process?

We often get companies come to us when they want to implement EDI. And one of the points of confusion is often around where EDI fits in with their business processes and software. They ask what comes first – is EDI the cart or the horse, the chicken or the egg?As a general rule, we say EDI should support your business processes, not rule them. We suggest companies map out their process, whether it be existing or what they want them to be, then insert EDI at points that it can help. For example, if you want to scan inventory in when it arrives, you’ll probably choose to use an advanced shipping notice to get the data into your software ahead of time and have your suppliers attach scannable SSCC labels to their shipments. If your software conducts two-, three- or four-way matching, you’ll need to make sure you exchange the relevant messages that are used in those checks. The other thing is, you don’t want to make your project bigger than Ben Hur – it’s ok to phase in different stages. Start with where it’s simple to bring EDI into the process. Then if there are other pain points down the track that can be resolved with EDI, then add them into the mix. A key reason for why projects can go awry is biting off more than one can chew. Different industries, and even different businesses or different software all operate in their own ways. And there’s good reason for that. It’s important that you get your processes in a place that suit your business needs. EDI should ideally be used to bring in automation and to reduce your team’s workload. Here at MessageXchange, our software can help with the EDI portion, but our powerful business process management layer can help fill gaps between EDI and your processes and software. MessageXchange is flexible enough, and smart enough, to cater to processes regardless of their complexity. For example, two-way matching can be conducted within MessageXchange itself by taking the EDI order and invoice and reconciling them against each other, then sending the result on. It can do the same with three-way matching by including the shipping notice too. It can even enhance the data in your message. For example, if you find it’s difficult for you or your suppliers to include a supplier number or GLN, MessageXchange can insert that into messages for you. Looking for more information on this topic? Get in touch with us below.

Request a call

Chat with one of our experts

Just fill out your details below and we'll be in touch within one business day.

Things to keep in mind when onboarding large amounts of suppliers

Onboarding suppliers to EDI can be costly and time consuming. A typical onboarding process will involve these steps:
  1. Engaging suppliers Letting them know you’ll be onboarding them to EDI.
  2. Getting them familiar with requirements (MIGs) All requirements are normally shared via a message implementation guide (MIG)
  3. Schedule in testing Set up a time and deadline for testing of messages to start
  4. Test Send and receive EDI messages from your suppliers to ensure they are sending the correct data.
  5. Go live!
If you’re onboarding large amounts of suppliers it’s important to keep things efficient. Here are some things to keep in mind.

Testing is the most time-consuming process

Testing is time consuming because it requires a lot of back and forth checking and communication with your suppliers. This takes time and puts more pressure on you to keep things moving along. A more efficient solution is to use a message compliance testing tool (MCT), like Colladium. It allows suppliers to test their EDI files, often through an online portal, without your team needing to check them. This means you don't have to wait for your EDI team to match up availability with theirs. In fact, your resources don’t need to be involved at all. This also allows the supplier to fix up any issues with their mapping or EDI file generation so that when they go live, you're not scrambling to resolve issues.

Make templates for your communications

This makes it easy for anyone in your team to communicate with suppliers consistently and accurately. The templates should include who your suppliers should contact, the expectations and requirements to onboard and their scheduled time for testing. Just be aware it is pretty normal for these templates to evolve over time as you and your suppliers learn. These templates can also be tailored to the supplier’s knowledge and readiness for EDI.

Communicate internally

It’s key that everyone within your business is on the same page when it comes to onboarding. A step by step process should be finalised and communicated to your EDI team. This process should establish the roles for each part of the process and who to contact. Have more questions? Ask our experts by getting in touch below.

Request a call

Chat with one of our experts

Just fill out your details below and we'll be in touch within one business day.

EDI mapping explained

In most industries, there’s an EDI standard – whether it be EDIFACT, GS1 XML, ANSI X12 or something else. While standards are fantastic because they make it easier for companies to trade with each other (because they don’t need to setup different messaging standards with each trading partner), ERP software generally doesn’t export the standards out of the box, if at all. Typically, software exports an XML or CSV document. So this is where mapping comes in.

What is mapping?

A mapping translates a file from one format to another. For example, if your software exports an XML file but your customer requires an EDIFACT message, the mapping process transforms the XML to EDIFACT. The way MessageXchange work allows the mapping process to also incorporate business rules. For example, it can be used to enrich data, perform calculations and more. This is particularly helpful for those companies whose software doesn’t export all the information that a customer requires. A mapping is setup once and then it just runs. There’s no intervention needed when a new message comes in, the whole process of mapping a file is automated.

When would I use it?

As I mentioned above, mapping is typically used when software isn’t able to export the file format required by a company’s trading partners. It’s the way to mediate between your software and that of your trading partners. It can even cater for your trading partners who have different requirements – logic can be setup to use certain mappings for certain customers. Mapping cover all message types too – so if you receive an order, the purchase order can be mapped from XML to EDIFACT, but the POR, ASN and INV can be mapped from EDIFACT to XML, for example.

What are the benefits of mapping?

It allows a company to easily comply with their trading partners’ requirements

There’s no changing your software or investing in additional staff or other resources to manage this.

It automates processes

It’s ‘set and forget’. It just runs.

It’s scalable

There’s no extra work to do if your message volumes increase. Once the mapping is setup, any new messages that are exchanged automatically go through this process. If you're needing help with your mapping get in touch with our EDI experts by filling in the form below.

Request a call

Chat with one of our experts

Just fill out your details below and we'll be in touch within one business day.

The art of writing MIGs

When you onboard suppliers it’s important for them to understand what the requirements are for the messages they need. A Message Implementation Guideline (MIG) refines a generic EDI standard such as UN/EDIFACT and details how it will be used for your company. In simple terms, it tells your suppliers what messages they need to send, what information the messages contain and how they’re formatted.Here are important things you need to know…

Choosing an EDI standard

There are different EDI message standards used around the world. Once you choose a standard it will be used as the base for your MIG. Here are a few of the common ones and where they’re most used:
UN/EDIFACT Standard coined by the United Nations and the most commonly used worldwide, and heavily used in the Australian retail supply chain industry.
ANSI X.12 Commonly used in North America
EANCOM Commonly used in the European retail industry
ODETTE Commonly used in the European automotive industry
EbXML Global standard developed by United Nations body for Trade Facilitation and Electronic Business Information Standards (UN/CEFACT) and Organization for the Advancement of Structured Information Standards (OASIS ).
TRADACOMS Commonly used in the UK retail industry
HIPAAhow Commonly used in the North American Healthcare industry
SWIFT Commonly used by financial institutions worldwide.
 

Choose the message types you want to use with your suppliers

This comes down to what your objectives are as a business. Here are some of the common messages and what they do:
  • Purchase order Sent from buyer to supplier to order goods or services
  • Purchase order change Sent from buyer to supplier if the original purchase order has changed
  • Purchase order acknowledgement Sent from the supplier to the buyer to acknowledge receipt of the order
  • Purchase order response Sent from the supplier to the buyer to let them know how much of the order can be fulfilled, and any discrepancies from the original order
  • Advance shipping notice (or despatch advice) Sent from the supplier to the buyer to let them know when and how the goods will be shipped
  • Invoice Sent from the buyer to the supplier for payment of the goods or services
  • Recipient created tax invoice (RCTI) Sent from the supplier to the buyer for payment of the goods or services
  • Remittance advice Sent from the buyer to the supplier to confirm payment
  • Price/sales catalogue Sent from the supplier to the buyer with up-to-date product and pricing information
  • Product activity data Sent from buyer to the supplier with the number of units sold and units on hand
  • Transport instruction Sent from a buyer to a transport supplier (and related parties) to communicate transport arrangements
  • Transport response Sent from a transport provider to confirm instructions
  • Functional acknowledgement An automated response sent from a receiver of an EDI message to confirm receipt of the message.

Find out what data your ERP system requires to process your message types

This is important because it’ll determine what fields and values you need from your partners. This includes things like:
  • character limits
  • whether only integers are allowed
  • if it needs to be number
  • how many decimal places
  • whether the field is dependent on another field (conditional)
  • whether a field is used for particular use cases only
  • how calculations are made.
From here you can provide a list of values that can be used, If not, all values in your chosen EDI standard. We have a range of MIGs from various companies you can check out here.

Putting your MIGs together

This is where you take everything from the previous steps and document it. Writing MIGs can involve a bit of work and so you can get an external party to help. This where an EDI provider, like MessageXchange, comes in. We can assist or lead the MIG writing process, developing it from scratch or upgrading your MIG. Find out more here. Have more questions? Ask our experts by getting in touch below.

Request a call

Chat with one of our experts

Just fill out your details below and we'll be in touch within one business day.

EDI documents explained: The retail industry

The retail industry has been using EDI for decades. It’s been proven to give retailers more visibility, better accuracy and truckloads of savings. And there are even benefits for suppliers too, especially those who fulfill large volumes of orders. The use of EDI is mature in the retail industry and covers basically all use cases of the procurement process. Let’s have a look at the different EDI message types that are used in the retail industry and why.

Purchase order

This is sent from a buyer (retailer) to its supplier. It will tell the supplier exactly what they want supplied. It will tell the supplier where to ship the goods to, and it might even tell them when the retailer expects the goods by. A purchase order typically starts the procurement process. In the EDI world, you might see a purchase order referred to as ORDERS (EDIFACT) or 850 (ANSI X12).

Purchase order response

A purchase order response is sent from the supplier to the buyer (retailer) to let them know whether or not they can fulfill what’s been requested on the order. Typically, there are three scenarios – the supplier accepts the order in full (if they can fulfill everything as requested), the supplier rejects the order in full (if they won’t fulfill any of the order), or the supplier proposes changes to the order. Changes on the order response are typically changes to the quantity, the price or the delivery date. In the EDI world, a purchase order response can be called ORDRSP (EDIFACT) or 855 (ANSI X12).

Purchase order change

A purchase order change comes after a purchase order or purchase order response. It’s sent from the buyer (retailer) to the supplier. As the name suggests, it can be used to make changes to the original purchase order. Or if the supplier sends a purchase order response, some retailers send a purchase order change to confirm the supplier’s changes (response).

Advanced shipping notice

This can sometimes be referred to as a despatch advice. It’s sent from the supplier to the buyer to let them know what’s being shipped and when. There are a couple of ways that retailers use a despatch advice. The first is a relatively simple one – it basically tells them how many of each product is being shipped, to where and when. It just gives retailers a bit of visibility. The second one is much more detailed. The retailer requires the supplier to tell them exactly what’s being shipped, how, to where and when. These ASNs have SSCC, or serial shipping container code, details on them. SSCCs are unique numbers that identify a unit. This can be a pallet, carton or something else. The supplier tells the retailer how many of each product are going into each pallet, for example, and what the corresponding SSCC number is. The retailer may also require the supplier to tell them the batch number, best before and expiry dates of the products in that pallet. The supplier then prints labels, with the SSCC number represented as a barcode and sticks it onto the pallet they’re sending. This information is sent to the retailer on the ASN ahead of the goods being sent. When the retailer receives the goods, they can scan the barcode to know exactly what’s on the pallet. In the EDI world, this message is called DESADV (EDIFACT) or 856 (ANSI X12).

Invoice

An invoice is sent from a supplier to a buyer to let them know what to pay them for the goods or services they’ve supplied. Unlike invoices that you might send and receive by email, EDI invoices don’t typically have bank details on them, because these are usually agreed on as part of the supplier agreement. The EDI invoices generally just outlines the total to be paid, the breakdown of what’s to be paid and sometimes the payment terms, although these can also form part of the supplier agreement. In the EDI world, you might see the invoice referred to as INVOIC (EDIFACT) or 810 (ANSI X12).

Product catalog

A product catalog gives the retailer details of the products you’ll be supplying to them. It can be as simple as supplying them with the GTIN or item number, product description and unit price. In the EDI world, this is called a PRICAT (EDIFACT) or 832 (ANSI X12).

Functional acknowledgement

Unlike the other message types we’ve discussed here, functional acknowledgements aren’t your typical procurement messages. These are usually handled behind the scenes. They tell the sender of the message whether it’s been received and if it’s A-OK or why it might have been rejected. In the EDI world, these are called CONTRL (EDIFACT) or 997 (ANSI X12).If you have any questions or need help getting started, just get in touch!

Request a call

Chat with one of our experts

Just fill out your details below and we'll be in touch within one business day.

Tips for writing a tender document to find an eInvoicing provider

Many organisations are starting to go through the process of finding an eInvoicing provider. Some, particularly larger, organisations need to go through a formal procurement process to find a supplier. Given eInvoicing is a new area for a lot of people, here are some tips to help you write your tender document.

Get to know the ins and outs of eInvoicing

The last thing you want is to be unprepared. Getting to know the basics of eInvoicing makes this process much easier. Make sure you get to know what eInvoicing is and how it works. Learn about the use cases, the benefits, what it will mean for each of your teams (like accounts payable, accounts receivable, IT and others), what it will mean for your customers and suppliers, find out how others have used it as a start.

Get to know what eInvoicing providers provide beyond just eInvoicing

Just like most industries, there are some eInvoicing providers who merely pass the invoice from A to B. But there are others who have capability to do much more. Here at MessageXchange, our powerful software can insert missing information, check the information you require is on the invoice and perform complex lookups, workflows, rules and more. This functionality is particularly useful for organisations who have complex business rules, automated payments and integrations with multiple systems.

Have a clear view of how eInvoicing will fit into your architecture and processes

For smaller organisations, it can be as simple as eInvoices coming in and out of your software. Even in this simple case, you’ll need to know how they will come in and out – through an API, can it drop and pickup files from an SFTP folder or does it need to use another method – and what format they will come in and out in – will it be an XML format, a CSV or something else? For larger organisations, accounts receivable invoices may come out of one system and accounts payable invoices may go into another. You may have a single integration point for any data coming from the outside world, rather than connect to your systems directly. Be very clear on what this process will look like for your company. On the accounts payable side, many organisations have automated matching against an order, or checking the vendor number or ABN or other data. Make sure you know how eInvoices will fit into this process.

Get familiar with your company’s IT policies for external vendors

Some companies require IT vendors to have backup, redundancy and service SLAs. Make sure you’re familiar with what your company requires so you can be clear about this in your tender.

Start writing!

  • Document your setup and key information like:
    • The software you use (and go into detail if your setup isn’t straightforward, for example if you have multiple systems)
    • Whether you want to send and/or receive eInvoices
    • How many eInvoices you expect to send and/or receive
  • Break it down into sections. Example:
    • Company information
    • Technical requirements
    • Business process requirements
    • Procurement requirements
    • Contract
    • Pricing
Interested in learning more about eInvoicing? Sign up to our newsletter

Newsletter

Sign up to get the latest eInvoicing updates

Stay up-to-date with industry news, useful blogs and whitepapers, expert tips and more.