How do you keep track of outstanding invoices in your day-to-day work?
The work is done and the invoice has been sent. Then new tasks begin. You check the account between other work, look for an invoice number and wonder whether anyone has already followed up. Perhaps the customer has paid in the meantime or sent a question to someone else. An outdated list can lead to an incorrect reminder at just that point.
In a small business, follow-up often falls to the owner. In larger businesses, sales, the project team and accounting all need to know the current status. A list of invoices sent is not enough: what matters is the amount actually outstanding and the next permitted step.
Keep outstanding, promised and received payments separate.
An invoice may be partially paid, under review or already settled. A promise to pay does not change the payment received. Check the authoritative invoice and payment source immediately before a permitted contact. If the current status is unavailable, resolve that gap first.
The Creditreform payment indicator from August 2026 shows payment activity in B2B business across company sizes and sectors. Its analysis of overdue but settled invoices is not a statistic of all unpaid invoices or evidence of AloZen's effectiveness.
Calling a letter a “payment reminder” does not automatically mean it has no legal consequences. § 286 BGB sets out specific conditions for default. Have the content, timing and further measures for your business approved by a qualified professional. This page organizes the office process; it does not assess individual claims.
A traceable follow-up process instead of occasional reminders.
- Check the current case. Bring together the invoice, the agreed basis, the current outstanding balance and any responses received. Check payments and corrections before making contact; do not copy the original amount without checking.
- Use the approved contact procedure. Use the texts, timing and recipients approved for this case. There is no universal reminder schedule here. Avoid parallel messages from sales and accounting.
- Treat questions as work to be done. Did the invoice arrive? Is a purchase order reference missing? Does the customer say they have paid or dispute the claim? Clarify the specific information. Refer new installments, fees, legal action or disputed claims to the person responsible for the decision.
- Record the actual outcome. Schedule a follow-up for a promised payment according to your rules. Only a confirmed payment assigned to the correct invoice changes the payment status. An outstanding difference or disputed issue remains visible; do not turn it into a fictitious full settlement.
A practical checklist before sending:
Case: [invoice]. Payment source checked on: [time]. Actually outstanding: [balance]. Response received: [status]. Approved next contact: [rule/text]. Responsible for discrepancies: [role]. Check again before sending: [responsibility].
Lexware's guide from August 2026 describes reminders linked to the corresponding invoice created there and sending initiated manually. A link already sent does not update automatically if payment is made later. Such details matter when checking the system; a provider's logo is not enough. This does not establish that AloZen has a confirmed function in Lexware.
How AloZen handles the administrative follow-up.
As your digital employee, AloZen is intended to carry out the permitted office work: read the current status, prepare or send approved correspondence, clarify missing administrative details, associate responses with the right case and track the next check. A case stays connected across messages, work in software and waiting periods.
Within defined authority, routine work does not need a new decision each time. Unclear payment allocations, disputed claims or new obligations are passed on with the necessary information. Legal assessments and professional accounting decisions remain with qualified people in charge. Specific invoice access, sending and confirmed responses must be evidenced in the relevant system.
Understand the digital employeeCheck the invoicing and payment process as specific actions.
Example: An agency invoice has only been partially paid.
In the fictional agency project, an approved invoice for 1,200 Euro was issued. Before the planned contact, a payment of 800 Euro is clearly assigned to that invoice. That leaves 400 Euro outstanding, not the original total.
- Before contact
- The invoice management system confirms receipt of 800 euros and a remaining balance of 400 euros. The message follows the rule approved for this case.
- Customer enquiry
- The customer needs an internal purchase order reference. The existing, approved reference is shared; the invoice is not recreated or changed arbitrarily.
- Waiting
- The customer says they will pay the remaining balance. The case remains open, with a follow-up scheduled as agreed; no payment is recorded on that basis alone.
- Conclusion
- Only once receipt of the remaining 400 euros has been confirmed and matched to the invoice is the invoice marked as paid and the follow-up closed. If the customer disputes it, the matter remains open for resolution.
In a trades business, the same organised approach can keep several job invoices distinct. In a larger service company, a shared source prevents accounting and sales from following up independently. The specific system workflow and professional authorisations must be appropriate in each case.
Prepare payment follow-up as a reviewable office workflow.
Agencies and service businesses
Keep project status and administrative follow-up together.
Trades business office
Customers, office tasks and exceptions in day-to-day work.
Assign the follow-up
Define the outcome, sources and permitted contact.
Understand costs and requests
One complete task across multiple steps and channels.
Plan the evaluation
Check the actual process within the approved quote.
Sources and context.
Creditreform: Payment indicator, August 2026: B2B context based on overdue invoices that have been settled; not AloZen results. Lexware Office: Creating reminders, August 2026: Provider-specific workflow and limitations, not confirmation of an integration or legal guidance. BGB §286: Default: Official legal framework; not an assessment of an individual claim.
Sources checked on 30. September 2026. They explain the work context or features of other providers; they do not establish an AloZen integration, customer results or guaranteed effects.


