Identify missing approvals, documentation, and duplicates
Present the causes of discrepancies and bookings in a comprehensible manner
Prepare for complete handover to accounting or service providers
The process in detail
Trace request and order
Combine information with the appropriate process and source reference.
Assign delivery and proof of performance
To make connections and open questions visible for professional evaluation.
Reconcile invoice with order and service
Provide results, assumptions and required evidence in a comprehensible manner.
Identify missing approvals, documentation, and duplicates
Coordinate next steps with those responsible and obtaining the necessary approvals.
Present the causes of discrepancies and bookings in a comprehensible manner
Combine information with the appropriate process and source reference.
Prepare for complete handover to accounting or service providers
To make connections and open questions visible for professional evaluation.
Technical review and responsibility
Invoice verification, approval, and posting are carried out according to your responsibilities. Discrepancies will remain visible until they are clarified.
Source reference
Which documents, data, and versions support this statement?
Open points
What information, evidence, or decisions are still missing?
Permissions
Who is allowed to use the data and who releases the result?
Tracking
How are feedback and next steps documented?
Work steps and handovers
01Trace request and order
02Assign delivery and proof of performance
03Reconcile invoice with order and service
04Identify missing approvals, documentation, and duplicates
05Present the causes of discrepancies and bookings in a comprehensible manner
06Prepare for complete handover to accounting or service providers
Schematic sequence according to the respective concept documents.
Documents, review and approval
Creditor tracking from order to postingInformation in connection
RequirementAssign information
OrderMaking dependencies visible
DeliveryDocument assumptions
The invoiceClarify any open issues
ReleaseCheck results
BookingTrack approvals
Schematic example view. Content and responsibilities will be defined in the specific process.
Evidence chain and open questions
01Requirement
02Order
03Delivery
04The invoice
05Release
06Booking
Where did the invoice come from?Order and service
Is it justified?Evidence and verification
Has it been released?Responsibility and approval
Why was it booked that way?Rationale and history
Test fields and required documentation
Example of a technical testing and verification matrix
Test field
Test question
Next step
Requirement
Are the details regarding the "requirement" complete and supported by appropriate sources?
Assign source
Order
Is the information regarding "order" complete and supported by appropriate sources?
Technical review
Delivery
Is the information regarding "delivery" complete and supported by appropriate sources?
Clarify any questions
The invoice
Are the details regarding "invoice" complete and supported by appropriate sources?
Document release
Release
Is the information regarding "approval" complete and supported by appropriate sources?
Assign source
Booking
Is the information regarding "booking" complete and supported by appropriate sources?
Technical review
AIDACreditors Navigator · Application Concept
pilot
Your entry point: Creditors Navigator
A self-contained pilot with your specialists.
The task, sources, and technical evaluation criteria will be defined jointly. Reliable results will be derived from representative cases and your team's assessment.
01Task
02Data & Rights
03Technical examination
04Pilot evaluation
Application in everyday work
Illustrative representation of the application area.
Invoice verification, approval, and posting are carried out according to your responsibilities. Discrepancies will remain visible until they are clarified.
jointly define the scope of the pilot project
Select a recurring task and person responsible
Combine information with the appropriate process and source reference.
Coordinate representative data and access rights
To make connections and open questions visible for professional evaluation.
Define result quality and necessary evidence
Provide results, assumptions and required evidence in a comprehensible manner.
Evaluate the pilot together and decide on next steps
Coordinate next steps with those responsible and obtaining the necessary approvals.
From example to professionally reviewed application
01Select a recurring task and person responsible
02Coordinate representative data and access rights
03Define result quality and necessary evidence
04Evaluate the pilot together and decide on next steps
Jointly review data, results, and responsibility
Requirements & Orders
Goods receipt & delivery notes
Invoices & Receipts
AIDA
Pilot with agreed data and test criteria
Using existing systems
Verifiable proposal
Technical feedback
Next step
Measurement points for the pilot
Jointly agreed pilot assessment
Measuring point
Test question
Processing effort
How much time does the team need for technically usable preparation?
completeness
Have relevant sources, limitations, and evidence been taken into account?
Quality
What corrections and questions remain before use?
Traceability
Are the fundamentals, responsible parties, and approvals identifiable?
Total expenditure
What costs are involved in data, integration, and operation?
1 / 2
Illustrative application concept. Numbers, comparisons, and processes are examples and will be tested against your data and systems.
Where is this invoice located and what approval is missing?
Invoice information, receipts and approvals are distributed across emails, Excel spreadsheets, paper documents and systems.
This is where the AIDA application concept comes in: Transparently preparing the entire process from order and service provision to handover and accounting. The first step is a limited pilot project with your experts and approved data.
This is how the process can look
Consolidate invoice information from agreed sources
Assign order, service, and approvals to a process
Mark missing evidence, discrepancies, and possible duplicates
Prepare handover to accounting or service providers
These data and systems are being considered
Email, DMS, ERP, invoices, orders, performance records and approvals.
Which sources are connected and which actions are possible depends on the available interfaces, permissions, and the agreed project scope.
How to evaluate the pilot
Search and voting time; outstanding evidence; quality of handover.
We compare agreed-upon tasks before and during the pilot project. Reliable results are obtained using representative data and the professional evaluation of your team.
Clear responsibility in the process
Booking and payment are separate steps and follow the existing approval process. Integration with financial systems will be agreed upon within the project.