UDSKRIFT 🔗
WEBVTT
00:00:15.599 --> 00:00:31.280
Uncertainty about whether the process is really working, this podcast is really working, and I help businesses look your successful solution to the data, processes, and controls behind e-evoicing.
00:00:31.519 --> 00:00:36.079
Because validation does not always mean everything is correct.
00:00:36.799 --> 00:00:42.640
Today we are going to talk about the invoice journey your business may have never met.
00:00:43.439 --> 00:00:48.960
A business owner tells the finance team, we are ready for e-invoicing.
00:00:49.200 --> 00:00:56.880
Our accounting software has been upgraded, the connection is working, and invoices can be submitted.
00:00:57.200 --> 00:00:59.280
That sounds reassuring.
00:00:59.520 --> 00:01:03.600
But then somebody asks a very simple question.
00:01:06.799 --> 00:01:10.400
And suddenly the answer is not so simple.
00:01:10.719 --> 00:01:17.359
For one customer, the transaction may begin when a salesperson confirms an order.
00:01:17.599 --> 00:01:22.560
For another, it may begin when a branch collects a deposit.
00:01:22.879 --> 00:01:32.079
For a service business, the invoice may only be triggered when the operations team confirms that a job has been completed.
00:01:32.560 --> 00:01:38.480
For an online sales, information may first come through an e-commerce platform.
00:01:38.719 --> 00:01:43.599
For a refund, the process may begin when a customer complains.
00:01:44.079 --> 00:01:51.680
And for an employee reimbursement, the transaction may begin completely outside the finance department.
00:01:51.920 --> 00:01:57.920
Yet all these transactions may eventually end up in the same accounting system.
00:01:58.480 --> 00:02:00.719
That creates an important question.
00:02:01.200 --> 00:02:09.680
If you only map what happened inside your accounting software, are you actually mapping your e-invoice process?
00:02:10.159 --> 00:02:11.360
Maybe not.
00:02:11.759 --> 00:02:22.159
One of the assumptions I frequently see around e-invoicing is that the invoice journey begins when someone opens the accounting system.
00:02:23.039 --> 00:02:26.319
But usually it begins much earlier.
00:02:26.639 --> 00:02:31.919
An invoice is the final output of a chain of business events.
00:02:32.240 --> 00:02:34.800
Something happens commercially.
00:02:35.439 --> 00:02:38.719
That event triggers a need to build.
00:02:39.039 --> 00:02:45.439
Information is collected, somebody decides how the transaction should be handled.
00:02:45.759 --> 00:02:58.879
The information is reviewed, the e-invoice is submitted, the result is validated, and if something goes wrong, someone has to correct it and retain the supporting records.
00:02:59.199 --> 00:03:04.639
A simplified journey may look like this Transaction begins.
00:03:04.960 --> 00:03:21.680
Invoice trigger occurs, information is captured, treatment is determined, the documents is reviewed, the e-invoice is submitted, the result is validated, exceptions are corrected, records are retained.
00:03:22.000 --> 00:03:23.759
That sounds straightforward.
00:03:24.400 --> 00:03:29.840
But most businesses do not have just one version of that journey.
00:03:30.080 --> 00:03:34.400
They may have 10, 20, or many more.
00:03:35.520 --> 00:03:39.520
This is what we are describing exactly the problems.
00:03:39.840 --> 00:03:58.479
Standard sales, point of sales transactions, online sales, service billing, deposit, credit notes, employees claim, self-billing situations, and intercompany charges may all follow different paths before reaching finance.
00:03:58.719 --> 00:04:02.080
Think about your business as a road network.
00:04:02.319 --> 00:04:05.759
Your accounting system is the central station.
00:04:06.000 --> 00:04:10.479
But not every transaction reaches that station through the same road.
00:04:10.719 --> 00:04:23.920
One road may come from your sales team, another may come from a branch, another may come from your website, another may come from operations, another may come through a spreadsheet.
00:04:24.319 --> 00:04:29.680
And one may still depend on somebody sending a message to finance.
00:04:30.000 --> 00:04:39.600
If management maps only the main road, the business may look organized, but the side roads are still carrying traffic.
00:04:39.839 --> 00:04:49.759
And if one of those side roads is poorly designed, information may arrive late, incomplete, or through an unofficial route.
00:04:50.000 --> 00:05:03.600
That is why I like to say you cannot redesign the road network until you know where all the roads begin, where they lead and where the congestions occur.
00:05:03.920 --> 00:05:06.800
Let me give you a composite example.
00:05:07.120 --> 00:05:15.439
Imagine a company that sells products and also provides maintenance services through a head office and three branches.
00:05:15.759 --> 00:05:20.079
Management believes everything is controlled through the accounting system.
00:05:20.480 --> 00:05:27.279
But during an e-immode implementation discussion, they start tracing actual transactions.
00:05:27.439 --> 00:05:29.680
And this is what they discover.
00:05:30.240 --> 00:05:36.000
Branch staff collect customer information using separate spreadsheets.
00:05:36.319 --> 00:05:40.319
Sales representative approves special discounts through email.
00:05:40.639 --> 00:05:45.920
The service team tells finance when maintenance work has been completed.
00:05:46.079 --> 00:05:50.240
Deposits are identified based on bank notifications.
00:05:50.480 --> 00:05:54.879
Credit notes requests are sent through messaging applications.
00:05:55.199 --> 00:06:02.560
Online orders are downloaded from one platform and then uploaded into accounting software.
00:06:02.879 --> 00:06:13.839
Employees' reimbursement go through another process entirely, and certain overseas supplier payments are handled directly by management.
00:06:14.079 --> 00:06:16.079
Now notice something important.
00:06:24.560 --> 00:06:30.560
And it certainly
Load full transcript
did not control all the decisions made before the information reached finance.
00:06:30.959 --> 00:06:43.600
That means an e-invoice implementation project built only around the accounting system may be designed around an incomplete picture of how the business really operates.
00:06:43.920 --> 00:06:48.959
Once management sees this, different questions start appearing.
00:06:49.279 --> 00:06:52.879
Who decides when each document should be issued?
00:06:53.120 --> 00:06:57.040
Who checks whether customer's information is complete?
00:06:57.519 --> 00:07:01.199
How are special discounts communicated to finance?
00:07:01.439 --> 00:07:04.480
Who determines the treatment of deposits?
00:07:04.800 --> 00:07:07.199
How are credit notes authorized?
00:07:07.519 --> 00:07:12.480
Which transactions require further tax or technical clarification?
00:07:12.720 --> 00:07:17.279
And if an e-invoice is rejected, who owns the problem?
00:07:17.759 --> 00:07:25.519
Finance, the branch, sales, IT, management, this is where process mapping becomes useful.
00:07:25.759 --> 00:07:29.519
And I want to make an important distinction here.
00:07:30.319 --> 00:07:39.759
A useful process map is not simply a diagram showing which buttons somebody clicks in the accounting software.
00:07:40.000 --> 00:07:44.560
It needs to show the business process behind the transaction.
00:07:44.879 --> 00:07:50.399
For each important transaction, I want to understand where does it begin?
00:07:50.639 --> 00:07:53.040
What event triggers the invoice?
00:07:53.279 --> 00:07:55.360
Where does the data come from?
00:07:55.680 --> 00:07:57.120
Who captures it?
00:07:57.360 --> 00:07:58.639
Who checks it?
00:07:58.879 --> 00:08:00.240
Who approves it?
00:08:00.560 --> 00:08:08.560
Which system, spreadsheets, or form is involved, what happens when something is unusual?
00:08:08.879 --> 00:08:11.519
How are errors corrected?
00:08:11.839 --> 00:08:13.759
What evidence is retained?
00:08:13.920 --> 00:08:18.160
And how does management know whether the same problem keeps happening?
00:08:18.399 --> 00:08:22.480
The purpose is not to create an impressive flowchart.
00:08:22.639 --> 00:08:32.159
The purpose is to expose assumption, handovers, and missing responsibilities before they become implementation problems.
00:08:32.559 --> 00:08:38.320
And one area deserves particular attention is the handover.
00:08:38.639 --> 00:08:45.600
Many process weaknesses happen at the point where responsibilities move from one person to another.
00:08:45.919 --> 00:08:50.559
Sales may assume finance will verify the customer's information.
00:08:50.960 --> 00:08:54.240
Finance may assume sales has already checked it.
00:08:54.559 --> 00:08:59.919
Operation may assume that completing the work automatically triggers billing.
00:09:00.159 --> 00:09:04.879
Finance may be waiting for someone to send confirmation.
00:09:05.120 --> 00:09:10.639
A branch may assume head office is handling a rejected document.
00:09:12.159 --> 00:09:16.960
Head office may not even know the rejected happens.
00:09:17.360 --> 00:09:22.960
This is where information gets delayed or duplicated or changed or lost.
00:09:23.279 --> 00:09:27.759
And sometimes nobody is quite sure who owns the next step.
00:09:28.080 --> 00:09:37.840
So one simple principle is when responsibilities changes hand, the information and evidence must travel with it.
00:09:38.639 --> 00:09:40.720
There is another important point.
00:09:41.279 --> 00:09:48.320
When you map your process, do not start with what your SOP says people are supposed to do.
00:09:48.559 --> 00:09:51.039
Start with what they actually do.
00:09:51.919 --> 00:09:59.039
Ask someone in your team, show me the last transaction you process, then follow it.
00:09:59.360 --> 00:10:01.200
Which system did you use?
00:10:01.519 --> 00:10:03.039
Which spreadsheet?
00:10:03.360 --> 00:10:04.639
Which email?
00:10:04.960 --> 00:10:06.799
Which WhatsApp message?
00:10:07.120 --> 00:10:08.480
Who approves it?
00:10:08.720 --> 00:10:12.000
What did you do when information was missing?
00:10:12.240 --> 00:10:13.679
Who did you call?
00:10:13.919 --> 00:10:16.879
What happened if that person is on leave?
00:10:17.279 --> 00:10:24.080
This is often where reality becomes much more interesting than the procedure manual.
00:10:24.399 --> 00:10:31.600
You may discover that an approval written into the SOP is no longer performed.
00:10:31.840 --> 00:10:37.600
A spreadsheet may have quietly become an unofficial subsidiary system.
00:10:38.000 --> 00:10:42.399
One experienced staff member may resolve every exception.
00:10:42.639 --> 00:10:46.960
Different branches may have developed different practices.
00:10:47.279 --> 00:10:57.279
Finance may regularly correct information coming from other departments, and management approvals may still be given verbally.
00:10:57.600 --> 00:11:03.519
These are not necessarily signs that employees are careless.
00:11:03.759 --> 00:11:07.440
They are signs that the actual process has evolved.
00:11:07.679 --> 00:11:19.360
And if management has never mapped that evolution, the business may be designing its e-invoice implementation around a process that no longer exists.
00:11:19.600 --> 00:11:24.559
This is where my 3CE invoice implementation framework begins.
00:11:24.799 --> 00:11:27.039
The first stage is clarify.
00:11:27.200 --> 00:11:31.120
And the first strategy inside clarify is process mapping.
00:11:31.360 --> 00:11:45.600
Before writing new procedure, before organization-wide training, before adding more automation, you need to understand which transactions are affected, where does each invoice journey begin?
00:11:45.919 --> 00:11:52.399
Which departments influence the transaction, where does information change hands?
00:11:52.799 --> 00:12:01.519
Which systems are involved, which exceptions occur, and where does further clarification become necessary?
00:12:02.000 --> 00:12:10.320
Because otherwise you can very
efficiently document, automate and train people on an incomplete process.
00:12:10.799 --> 00:12:12.720
And that is not progress.
00:12:12.960 --> 00:12:17.279
It is simply making the incomplete process more consistent.
00:12:17.600 --> 00:12:24.240
So the principle at this stage is clarify the journey before creating consistency.
00:12:24.720 --> 00:12:27.279
Now let us make this practical.
00:12:28.240 --> 00:12:30.960
Here is today's clarity checked.
00:12:31.279 --> 00:12:37.120
Pick one transaction type in your business, preferably not the easiest one.
00:12:37.440 --> 00:12:40.559
Choose something that crosses departments.
00:12:40.879 --> 00:12:52.639
Maybe a deposit, a credit note, a service invoice, an online sales, a refund, an employee reimbursement, or a transaction handled by a branch.
00:12:52.799 --> 00:12:58.080
Then ask your team to trace one real example from the beginning to the end.
00:12:58.399 --> 00:13:00.320
Not the ideal process.
00:13:00.559 --> 00:13:01.919
A real transaction.
00:13:02.159 --> 00:13:05.679
Start with where did that transaction originate?
00:13:05.919 --> 00:13:09.519
Then ask, what actually triggered the billing?
00:13:09.759 --> 00:13:11.840
Where did the information come from?
00:13:12.080 --> 00:13:13.279
Who checks it?
00:13:13.519 --> 00:13:14.799
Who approved it?
00:13:15.120 --> 00:13:18.159
Which system or spreadsheet was used?
00:13:18.480 --> 00:13:21.759
Where did responsibility change hands?
00:13:22.559 --> 00:13:26.799
What would happen if the information was incomplete?
00:13:27.039 --> 00:13:31.200
How would an error come back to the originating person?
00:13:31.759 --> 00:13:37.120
And finally, could management reconstruct this entire journey six months later?
00:13:37.279 --> 00:13:45.279
If you cannot answer those questions clearly, you may have an invoice journey your business has never properly mapped.
00:13:45.519 --> 00:13:52.720
And this matters because one accounting system does not necessarily mean one invoice journey.
00:13:52.960 --> 00:14:04.480
A business can have one accounting platform but many transaction channels, many handovers, many manual steps, many exception routes, and many assumptions.
00:14:04.720 --> 00:14:11.039
So before you ask whether an e-invoice software is ready, ask a more fundamental question.
00:14:11.360 --> 00:14:16.639
Do we understand how the transaction reaches the software in the first place?
00:14:16.879 --> 00:14:20.879
Because you cannot access or control a journey you cannot see.
00:14:21.200 --> 00:14:37.919
If today's discussion has made you realize that different department branches or systems may be feeding information into your e-invoice process in different ways, that is precisely where process mapping becomes valuable.
00:14:38.559 --> 00:14:55.360
This is one of the areas I work through in my e-invoice implementation coaching, helping businesses clarify how transactions actually move through people, systems, and departments before trying to create consistency and control.
00:14:55.840 --> 00:15:05.360
And if you are not sure where your organization currently stands, you can begin with the 3CE Invoice Readiness Assessment.
00:15:05.679 --> 00:15:14.639
It provides an initial view of whether your implementation may require greater clarity, consistency or control.
00:15:15.360 --> 00:15:22.000
Because before you improve the process, you first have to see the entire invoice journey.
00:15:24.879 --> 00:15:28.559
Before you go, here is your clarity question.
00:15:28.799 --> 00:15:33.360
Is e-invoicing genuinely under control in your business?
00:15:33.440 --> 00:15:37.360
Or is your team simply fixing the problems as they appear?
00:15:37.759 --> 00:15:40.960
If you are not sure, start with my compliment.