Exact Online
The invoice is in Exact, the agreement in an email. I bring them together so your employee can act with the full picture.
Review my software and processProcess example 01
An outstanding invoice overview and recent customer email.
A worklist with amounts, due dates and the corresponding agreement.
Process example 02
Order or invoice records plus a service request.
A file with relevant order lines, the customer question and missing information.
Process example 03
An agreed financial export and a list of open actions.
A summary referencing source rows, with a separate list of exceptions.
Take an email ordering 20 filters A-104 and five packs of seals. The draft contains the customer reference, article code, quantity, unit and requested delivery date. The seals stay open until the article and pack size are known. Each line links back to its source.
Your order desk checks the customer, article match, price and stock in the current administration. Before building, we check with your administrator whether your Exact edition supports the required order fields and an appropriate import or API route. We agree how approved data becomes an order and how duplicate orders are prevented. This is a workflow to design for your environment, not a ready-to-enable integration.
See the full wholesale order example, or read how to automate order processing with AI in any sector. Payment follow-up and service enquiries remain separate possible starting points.
We choose one recurring process and measure its current workload. I define the sources, matching rules and approval step, then build the preparation. We test ordinary cases and exceptions together. Your team receives the workflow, instructions and a manual fallback.
An emailed payment agreement appears beside the outstanding invoice. An employee reviews the draft before a reminder goes out.
Orders and payment overviews can be compared with the accounts. Differences become a checklist for an employee to investigate before anything is posted.
Purchase invoices into a booking proposal, matching payments to invoices and debtor follow-up (from Plus) are handled by Exact itself. I do not rebuild that. My work starts with the email or PDF Exact never sees, the comparison with a second source, the exception and the measurement. See what each package already does.
I can design the process and build a suitable workflow. First I check permissions, fields, the administration and the export or connection route. These examples are not a ready-made Tamboer integration. Automatic posting or executing payments is outside these examples.
We start with read access to the minimum required data. Every prepared result refers to its sources. Missing information triggers a review. Writing changes or sending messages requires a separate, explicit approval step. Access, logging and the fallback are part of the agreed design.
No. We start with the software and working methods you already use. A new subscription is only discussed if the chosen process requires it.
We first check whether an existing feature solves the task. Tamboer adds process design and preparation between systems where work still remains.
I can design the process and build a suitable workflow. First I check permissions, fields, the administration and the export or connection route. These examples are not a ready-made Tamboer integration. Automatic posting or executing payments is outside these examples.
These examples prepare work for review. Changes and external messages require human approval and a separately agreed route.
Bring one recurring task and the names of your systems to your free AI plan. We examine where preparation can help and what needs checking first.
With Joost
Start with a free AI plan: an AI plan for your whole business, three tailored examples and a demonstration. Bring one task that keeps returning.
Request your free AI plan