A customer calls a Nigerian supplier about an invoice. Sales finds the copy it sent. Accounts finds a reference number. Everyone is looking at the same sale, but nobody can immediately explain what happened after it left the invoicing system.
It is a small question that can turn into a long search.
Nigeria’s e-invoicing system uses an Invoice Reference Number, or IRN, to identify an invoice. The NRS guidance describes how it brings together the business’s invoice number, its assigned service ID and an issuance datestamp.
The reference gives the team somewhere to start. The useful story is what comes next: which checks completed, what result was recorded for the submission, and what evidence shows the invoice reached the intended recipient. Commercial approval and payment have their own place in that story too.
Now imagine the submission screen stops responding. Instead of creating a replacement invoice, accounts keeps the original reference and asks the integration provider to check that operation. When the result is found, it goes back against the same sales record.
The next time the customer calls, the team can follow one trail from the original invoice to its recorded outcome. A colleague does not have to reconstruct events from separate inboxes and screenshots.
That is a useful habit to build early: keep the invoice, its e-invoicing reference and its processing history connected. A number makes a document easier to find. A clear history makes the answer easier to trust.
