e-Solutions
e-Invoice
The people who prepare, check and send invoices usually work across two screens. This work brings those steps inside your Microsoft Dynamics ERP processes: checking, sending, status tracking and recording an arriving invoice are handled in the same place.
The path of a document
Checked, sent, followed up.
An invoice records work that is already done, and all three steps belong to the same flow.
Checked
The detail is reviewed before the invoice goes out.
Sent
Selected invoices go out in a single action.
Followed up
Status is watched, and arriving invoices are recorded.
Starting point
An invoice is the last step of the work.
An invoice is not a task in its own right. It appears when an order, a delivery or a service is complete, yet in most organisations it is issued on a separate screen, under separate responsibility.
When the same information sits in two places, so does the discrepancy: the record in the ERP and the document that went out do not confirm each other, and the transaction behind an arriving invoice has to be found by hand.
So we start from the process that produces the invoice rather than from the invoicing screen: which record creates it, who checks it, and who watches its status once it has gone out?
Common situations
- The same invoice detail entered into both the ERP and the invoicing screen
- A check before sending that only one person can do
- Having to ask separately what became of an invoice that was sent
- Arriving invoices matched to their records by hand
- Several companies or branches followed one at a time
Workstreams
Invoice flow built inside the ERP.
Scope is agreed together, based on your current Dynamics setup and your invoicing process; regulatory detail is confirmed with the relevant specialists.
A check before sending
Invoice detail can be reviewed before the invoice goes out, and it is agreed which information passes through whose check.
Sending invoices together
Invoices are selected from a list and sent in a single action, rather than opened one screen at a time.
Status and arriving invoices
The status of a sent invoice is followed; invoices that arrive are taken in and recorded alongside the entry they belong to.
Several companies and branches
More than one company or branch is managed through a folder structure, so a chain of sites can be followed centrally.
Delivery approach
We move without pausing invoicing.
Invoicing is part of daily work, and the transition is planned around that.
Mapping the current flow
The processes that produce invoices, the control points and the responsibilities are mapped together.
Adapting the ERP side
Missing fields, checks and the links to the related records are arranged on the Dynamics side.
Going live with limited scope
Work starts with one company or one document type and is validated with real invoices.
Monitoring and support
After go-live the flow is monitored and the steps that do not work are addressed regularly.
Scope note
Regulatory detail is agreed at the start of the project
e-Invoicing runs inside a framework set by regulation, and that framework changes over time. This page is not an undertaking about compliance; it describes how the process is set up in your organisation.
Which documents fall inside the scope, where each step is carried out and what the finance side expects are agreed at the start of the project with the relevant specialists.
Let's talk about your invoice flow together with the ERP side.
Let's review your current invoicing process and your setup, and agree the scope and the sequence together.