Administration: keep cases traceable instead of in circulation folders
Post intake, invoice checking, contract deadlines, HR records, procurement and reporting: in business administration the effort rarely arises during the actual work, but at the handovers in between. We map the route of a case with responsibility, deadline and filing, so that it is always clear where it sits, who is next in line and what has already been decided.
Business administration is the area where sloppiness shows up latest and costs most. An invoice that sits in a mailbox for weeks costs the early-payment discount. A notice period that existed only in one person's calendar extends a contract unintentionally by a full term. An approval given by email cannot be found years later. This page describes which workflows typically consume time in the administrative units of companies as well as in administrative organisations and associations, where that can be resolved with IT, and where the decision deliberately stays with people.

The case overview in invoice intake
Which administrative workflows consume the most time
Administrative work largely consists of passing cases along: something arrives, is reviewed, assigned to a responsibility, checked, approved, posted and filed. Each of these steps is short on its own. The chain becomes expensive where a case changes medium or where nobody knows who is currently holding it. In our reviews it is regularly the same six areas that account for the largest share of the working time consumed (project experience).
Post intake and assignment
Post arrives on paper, by email to a shared mailbox and through portals. Someone reviews it, prints it, puts it in a tray or forwards it. Whether a letter has arrived and who is handling it is known only to whoever has just asked. A single logged intake point with assignment to a responsibility is almost always the most effective first step.
Invoice checking and approval
Incoming invoices need a factual and an arithmetic check, often against the purchase order and the delivery note, followed by an approval based on value limits. If that runs through circulation folders and email chains, the turnaround drags on and the discount period expires before anyone could intervene.
Contract management and deadlines
Lease, maintenance, insurance and service contracts have terms, notice periods, price adjustment clauses and automatic renewals. If they sit in ring binders and the deadlines live in personal calendars, one person's presence decides whether action is taken in time.
HR records
Employment contracts, amendments, certificates, time records, holiday requests and training evidence are among the most sensitive documents in the building. They need storage with restricted access, clear responsibilities and a rule stating how long each type of document is kept.
Procurement and ordering
Requisition, obtaining quotes, order approval, goods receipt and invoice matching spread across several people and media. Without a continuous order number it later becomes impossible to say which invoice belongs to which order, or whether a service was ordered at all.
Reporting and enquiries
Figures for boards, management, advisory bodies or members' meetings are usually collated by hand from several sources. The effort repeats in every cycle, and anyone asking how a figure came about triggers a small investigation.
Circulation folders, email approvals, deadlines in a personal calendar
These three habits are so widespread in administrative units that they barely register any more. They have one thing in common: they work well as long as everyone is present and nobody asks questions. As soon as someone falls ill, a case escalates or an audit is due, traceability disappears. The overview below names the points we most often record in administrative projects and describes, without drama, what they cost day to day.
| Friction point | How it usually runs today | What it costs day to day |
|---|---|---|
| Circulation folder | The case physically travels from desk to desk | Nobody can say where it is; parallel handling is impossible |
| Approval by email | Consent sits in the body of a message, often without reference to the document | Cannot be found later; unclear whether the value limit was observed |
| Deadline in a personal calendar | Notice and review dates rest with a single person | During absence or after a handover the deadline passes unnoticed |
| Paper file in a cabinet | Contracts and amendments sit in binders, sometimes in several places | Enquiries take time; during audits the latest version cannot be evidenced |
| Shared mailbox | Incoming mail is reviewed by changing people | Cases are handled twice or not at all |
| Report pack assembled by hand | Figures are copied afresh from several sources for every meeting | Recurring effort, diverging versions, no verifiable origin |
Invoice intake sets the pace in administration
If we are to start with a single workflow in an administrative unit, it is almost always invoice intake. It is frequent, repeats in the same shape, involves several responsibilities and has a built-in deadline in the early-payment discount period. At the same time it demonstrates what sound digital case handling looks like: a single point of entry, a check with a clear brief, a documented approval, a handover to accounting and filing that can still be searched years later. The sequence below describes how an invoice run looks after the changeover.
One point of entry
All incoming invoices run through a defined entry point, whether they arrive on paper, as a file attachment or in a structured invoice format. Paper is scanned in one place, electronic invoices are taken over directly. Every document receives a sequential number and a timestamp on arrival, which makes handling time measurable.
Capturing the document data
Invoice number, invoice date, supplier, amounts, tax amounts and payment terms are read out and proposed for checking. Anything not recognised with confidence stays visible as an open field rather than quietly adopting a wrong figure. Staff correct once instead of retyping everything.
Matching to order and cost centre
Existing purchase orders and goods receipts are matched to the document, as are cost centre and account according to the rules you already use. Differences between order and invoice are flagged as such and move into separate handling rather than being lost in the normal run.
Factual check by the requesting side
The person who requested the service confirms that it was delivered. In doing so they see the document, the order and the history. Queries are noted on the case rather than handled by email, so that they later belong to the document instead of sitting in a mailbox.
Approval by value limit
Approval follows your authority rules: up to a defined amount the requesting side decides, above that the department head, and for larger amounts management or the board in addition. Who approved what and when is recorded on the case. For absences we set up a deputy so the run does not stall.
Handover and filing
The approved document goes to the accounting system or to your tax advisers along with the checked coding details. It is then filed unalterably, linked to the order, the check note and the approval. An enquiry about a single document becomes a search rather than a round of phone calls.
All incoming invoices run through a defined entry point, whether they arrive on paper, as a file attachment or in a structured invoice format. Paper is scanned in one place, electronic invoices are taken over directly. Every document receives a sequential number and a timestamp on arrival, which makes handling time measurable.
Invoice number, invoice date, supplier, amounts, tax amounts and payment terms are read out and proposed for checking. Anything not recognised with confidence stays visible as an open field rather than quietly adopting a wrong figure. Staff correct once instead of retyping everything.
Existing purchase orders and goods receipts are matched to the document, as are cost centre and account according to the rules you already use. Differences between order and invoice are flagged as such and move into separate handling rather than being lost in the normal run.
The person who requested the service confirms that it was delivered. In doing so they see the document, the order and the history. Queries are noted on the case rather than handled by email, so that they later belong to the document instead of sitting in a mailbox.
Approval follows your authority rules: up to a defined amount the requesting side decides, above that the department head, and for larger amounts management or the board in addition. Who approved what and when is recorded on the case. For absences we set up a deputy so the run does not stall.
The approved document goes to the accounting system or to your tax advisers along with the checked coding details. It is then filed unalterably, linked to the order, the check note and the approval. An enquiry about a single document becomes a search rather than a round of phone calls.
Deadlines belong to the case, not to one person's calendar
The second major lever in administration is contract management. Contracts are signed, filed and then usually touched again only once something has happened. Yet almost all of them carry at least one deadline: a notice period, an automatic renewal, a price adjustment date, a reporting duty or a review interval. We record the contracts once in a structured form, attach the document together with its amendments, and set the deadlines as reminders against a role, not a person. The prompt arrives early enough for a decision to still be possible, and it reaches the deputy as well.
- Contract overview with term, notice period and renewal rule
- Document and all amendments on the same record instead of in several binders
- Reminders against a role, so holidays and handovers do not lose a deadline
- Lead time chosen so that negotiation or a change of provider is still possible
- Annual overview of expiring contracts for budget planning
Where IT genuinely helps — and where people decide
Automate where the workflow follows rules
Administrative work consists of rule-based steps and of judgement calls. Drawing that line cleanly matters more than the extent of automation: force judgement into rules and you get results that are formally correct and substantively wrong.
Well suited to systems
- Included: Reading document data and proposing it for checking instead of retyping
- Included: Assigning cases to the responsible role according to fixed rules
- Included: Mapping and logging approval routes based on value limits
- Included: Monitoring deadlines and raising them as reminders in good time
- Included: Checking completeness: reporting missing details and missing attachments
- Included: Producing recurring reports from a shared data basis
Stays a matter of judgement
- Not included: Decisions with latitude, such as goodwill towards a supplier
- Not included: Special cases that occur a few times a year and differ every time
- Not included: Personnel decisions and everything attached to them
- Not included: Contract negotiations and assessing offers beyond the price
- Not included: Interpreting unclear or contradictory contract clauses
- Not included: Escalations where the relationship with the other side matters
Entry point for administrative units · net plus VAT
- The route recorded where the cases are actually handled
- Approval routes, value limits and deputies documented in writing
- Report with prioritised measures and an estimated price per measure
- Third-party licences and fees shown separately
Everything starts with the process analysis: we record one clearly defined administrative workflow — usually invoice intake or contract management — and lay out the actual route with all handovers, approvals and filing locations. For one workflow at a single site the analysis is 1,900 € net. Implementation afterwards begins at 4,900 € net per automation or interface and is set as a fixed price once the analysis is done. Ongoing support starts at 190 € net per month. All prices net plus VAT; the reasoning is on the pricing overview.
Prices as of September 2026. Ongoing services are booked individually and can be cancelled monthly; there is no minimum term.
Evidence, retention and data protection
In administration, traceability is not a convenience feature but the actual purpose of many steps. Who approved an invoice has to remain identifiable years later. Commercial records are subject to the retention duties under commercial and tax law; for keeping and retaining them electronically, the German principles for the proper keeping and retention of books, records and documents in electronic form (GoBD) apply. Personal data is additionally covered by the General Data Protection Regulation, and for the design of the systems the recommendations of the German Federal Office for Information Security (BSI) provide a workable guide. We implement all of this technically; the legal assessment in each individual case stays with your advisers and your data protection officer.
- Unalterable filing: once filed, documents cannot be quietly swapped out
- An audit trail on the case: who checked, approved, changed or rejected, and when
- A role and permission model that effectively restricts access to HR records
- A deputising rule that is documented and does not rely on shared login details
- A deletion policy: which document is kept for how long and then removed
- Ability to give information: the full history of a document or contract can be shown
- Processing and storage in Germany, with a data processing agreement and deletion periods
HR data needs its own access area
How a project runs in your administration
Recording the route
The process analysis starts at the workplaces: we look at how a case actually runs, where it waits, which lists and mailboxes serve as interim storage and what the exceptions are. The result is a written report with prioritised measures and estimated prices that you can also use without us.
Defining roles and approval routes
Before technology comes into play, we put in writing who handles which cases, up to what amount each person approves and who deputises during absences. This is the most common finding in administrative projects, because in many organisations it exists only verbally. The result goes into the process documentation.
Connecting the systems
So that documents are not captured twice, we connect the systems involved through interfaces — for example the document run with the accounting system, the order with goods receipt, or master data from the inventory system. Where the same details are maintained in several places, data integration settles which source will lead in future.
Automating the workflow
Process automation takes over the rule-based steps: assignment by responsibility, completeness checks, reminders for cases left sitting, forwarding after approval. Paper still in the way is replaced through document digitisation, so that the filing becomes searchable.
Rollout with the people involved
We test with real cases from your organisation, not with samples. Training and rollout then follows for the handling staff and for the approvers, each on their own section. The previous way of working stays available during the transition, so nobody is left grasping at air.
Operations and reporting
In ongoing operations we monitor the transfers we set up and get in touch when a run does not happen. On the resulting data basis, metrics and reporting can then be built up: turnaround times, open cases per responsibility, discount periods actually used.
The process analysis starts at the workplaces: we look at how a case actually runs, where it waits, which lists and mailboxes serve as interim storage and what the exceptions are. The result is a written report with prioritised measures and estimated prices that you can also use without us.
Before technology comes into play, we put in writing who handles which cases, up to what amount each person approves and who deputises during absences. This is the most common finding in administrative projects, because in many organisations it exists only verbally. The result goes into the process documentation.
So that documents are not captured twice, we connect the systems involved through interfaces — for example the document run with the accounting system, the order with goods receipt, or master data from the inventory system. Where the same details are maintained in several places, data integration settles which source will lead in future.
Process automation takes over the rule-based steps: assignment by responsibility, completeness checks, reminders for cases left sitting, forwarding after approval. Paper still in the way is replaced through document digitisation, so that the filing becomes searchable.
We test with real cases from your organisation, not with samples. Training and rollout then follows for the handling staff and for the approvers, each on their own section. The previous way of working stays available during the transition, so nobody is left grasping at air.
In ongoing operations we monitor the transfers we set up and get in touch when a run does not happen. On the resulting data basis, metrics and reporting can then be built up: turnaround times, open cases per responsibility, discount periods actually used.
Deputising that works when it matters
A deputising rule that consists of a shared password is not one. We set deputies up as a separate permission with a period and an audit trail. That keeps it visible who acted as a deputy — and cases no longer sit still because one person is out of the building.
Roles instead of individual permissions
Permissions are granted to roles, not to people. A change of responsibility then becomes an assignment rather than a bulk operation across twenty folders. That reduces the administrative effort when people join or leave and makes it evidenceable during audits who was allowed to access what.
Filing that supports enquiries
Documents, contracts and amendments sit in one place, linked to the case they came from. Searching happens by supplier, amount, period or contract number rather than by folder structure. Providing information to management, a board or an audit thus becomes a query.
Figures without a collection round
As soon as cases are handled in a structured way, reports arise as a by-product: open invoices by due date, cases per responsibility, turnaround times, contracts expiring next quarter. Preparing a meeting then consists of checking rather than collating.
Typical starting situations from administrative projects
Illustrative, anonymised scenarios from typical project sequences (project experience). No customer details and no guaranteed outcomes.
What we do not take on in administration
- No statutory case-handling procedures: we work on your own business administration, not on procedures carried out as part of public-law duties.
- No legal or tax advice: questions about retention duties, contract drafting or tax consequences belong with your advisers; we implement their requirements technically.
- No data protection officer role: we deliver the technical implementation and the documentation for it, but we do not take on the role of your data protection officer.
- No organisational consulting: who takes on which task and how your organisation is structured is your decision; we map the arrangement you have made.
- No assessment of staff: turnaround times and case counts do not support performance comparisons between employees, and we do not provide reports for that purpose.
- No promised savings: we estimate effort and impact per measure, but we do not commit to outcome figures.
Which building blocks apply in your case is decided by the report from the process analysis. Often it is process automation for the document run, interfaces to the accounting system and document digitisation for the filing. Where an ageing specialist application is in the way, the topic is legacy replacement; for dependable figures there is metrics and reporting. How other sectors benefit is shown on the industries overview, and where we work on site is listed under regions. The services page gives the full picture.
Which administrative case costs you the most time right now?
Describe in a few sentences how a case runs at your organisation — from arrival to filing. In the initial call we tell you frankly whether a process analysis is the right next step or whether the matter can be settled more briefly.
