NordFlux links your invoice issuance from service recording through invoice run and approval to dispatch and open items list. Recurring invoices, batch invoices and down payment invoices run according to your rules, not by reminder. You approve, the rest happens without you.
In many businesses, invoicing is the last step that no one ever has time for. Every day an invoice sits, the money stays with your customer instead of on your account.
Five building blocks that we implement individually or as an integrated workflow. Which ones are worthwhile for you depends on your invoice volume and the type of services you provide.
Recorded times, completed orders, delivery notes and tickets are automatically consolidated into billable line items instead of being manually pieced together at month-end. We pull the data from where it already exists: time tracking, inventory management, ticketing system or project software. What can't be clearly assigned lands on a review list instead of silently in the invoice.
Savings 1-2 days per month-end closeMaintenance contracts, leases, subscriptions and flat fees are generated from a contract record on the agreed date, with price adjustment, term end and cancellation date. The run alerts you before a due date is missed, not when a customer complains about the missing invoice. We store price escalation clauses and index adjustments as rules, not as notes.
Benefit no missed due datesIn project and construction work, invoicing follows progress, not the calendar. We map the payment schedule, pull progress from your system or from team approval and generate down payment invoices with clean reconciliation in the final invoice. Already-issued down payments are automatically deducted so the final invoice isn't a puzzle to calculate.
Savings 3-5 h per projectInstead of creating each invoice individually, a batch run prepares all due documents and presents them to you as a list for review. Exceptions like unusually high amounts, missing order numbers, or customers with payment holds are flagged before you approve. Only your approval triggers creation and dispatch; everything before is preparation.
Savings 2-4 h per runEach customer receives the invoice via the channel they demand: email, customer portal, vendor portal, or mail through a service provider. In parallel, the document is filed audit-trail secure, accounting receives it in the agreed format, and open items are updated. Who received the invoice and when is in the log, not in a colleague's email outbox.
Benefit Payment receipt becomes traceableInvoice issuance, invoice format and invoice receipt are three separate areas. We separate them intentionally because otherwise projects get bloated that could be finished individually in 30 days.
This page covers the path from service to finished invoice. Whether that invoice ultimately goes out as PDF, XRechnung or ZUGFeRD file is a separate question with its own standards and validation rules. Both work together, but are planned separately.
Incoming vendor invoices must be read, verified against the purchase order, approved and passed to accounting. That's the vendor side and technically has little in common with your invoice issuance. If your bottleneck is there, the incoming side is the right starting point.
ToolsWe choose the tool based on your system, not on partnership programs. If your business runs on Microsoft 365, Power Automate is often the shorter path; for mixed systems and custom interfaces, we use n8n, on request on a server in Germany. Both access your existing invoicing software instead of replacing it.
After the free initial analysis, you get a fixed price before you decide. The price doesn't change during the project, even if we misjudge along the way.
We walk through an actual month-end close with you and document where each line item comes from and who touches it. At the end, we know which invoice types are worth automating and which need manual work.
Prices, discounts, payment terms, approval limits and exceptions for individual customers are stored as rules and signed off by you. What automation must not decide, we define explicitly here.
The invoice run is built and tested against actual invoices issued using the previous month's data. We clarify any differences before a single invoice goes to a customer.
The first real run goes to you as a proposal list, you approve it, and then the process takes over. We're available through the first close and hand over documentation your team can work with themselves.
A clean invoice run speeds up dispatch, not your customers' payment behavior. If your real bottleneck is open items and chasing payments, dunning management starts right at this point.
In 60 minutes we review your invoice issuance and honestly tell you which parts are worth automating and which aren't. The initial analysis is free and non-binding; then you decide.
Automated invoice issuance means that invoice bases from your systems converge and the document is prepared at the push of a button instead of being created manually at the end of the month. Times, delivery notes, contracts and payment plans are consolidated into line items, the invoice run presents the documents, you approve. Dispatch, filing and updating of open items then run automatically. Your invoicing software typically remains the same.
Invoice issuance is the customer side: you issue invoices to your customers. Invoice receipt is the vendor side: vendor invoices arrive at you and must be read, verified, approved and posted. Technically, these are two separate processes with different systems and approval logic, which is why we treat them as two projects. Both can be built on the same basis if you later want both directions.
Not in most cases. We work with your existing system's interfaces or exports and add the steps before and after, rather than selling you new software. Whether direct integration is possible or an intermediate step is needed, we clarify this in the initial analysis on your specific system. If a switch really were the better way, we'd say that instead of building a workaround.
The e-invoicing requirement concerns the invoice format, automation concerns the path to get there. Under the transition provision in Section 27 Paragraph 38 of the German Sales Tax Act, sales can still be billed on paper or in another electronic format until December 31, 2026; for businesses with a total revenue of no more than 800,000 euros in the previous year, this is extended by another year. A cleanly automated invoice run makes the format switch considerably easier because invoice data is then structured. Your tax advisor can give you binding information on your specific case; this is not legal advice.
After the free initial analysis, you get a fixed price that depends on your starting system, the number of invoice types and your shipping channels. A monthly batch run from one system is different from down payment invoices from three sources with portal dispatch. The fixed price is set before you decide and doesn't change during the project. Ongoing costs only arise afterwards for operation and maintenance, clearly separated from the project price.
