← All guides · Freelancers & business
Team workspaces for agencies: running client e-invoicing as a shared operation
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
An agency's e-invoicing problem is not conversion — it is coordination: many clients, several countries, mandate dates moving per client, and knowledge that must not live in one bookkeeper's memory. Team workspaces are the organisational layer this product puts on top of the conversion engine: shared work for agencies, higher limits, with Pro's bulk conversion, country rule packs, monitored clients and accounting exports underneath.
What are team workspaces?
Team is the $49/month tier: as the product's About page puts it, 'Team ($49/month) adds team workspaces for agencies and higher limits' — on top of Pro's bulk conversion of up to 200 invoices per job, per-country rule packs, monitored clients whose acceptance is re-checked as mandates change, and exports to CSV, Xero and QuickBooks formats. The free tier converts one invoice; Team organises the whole client portfolio's invoicing.
The agency difference: portfolios, not invoices
A freelancer's invoicing is a list; an agency's is a matrix — clients × countries × channels × mandate dates, with several people touching it. The failure modes are organisational: two staff invoicing the same client differently, a mandate flip known to the person on leave, a Peppol ID recorded in someone's email. The conversion engine cannot fix those; a shared workspace is where they get fixed, by making the client truth — records, identifiers, verdicts, history — common property instead of private knowledge.
That is the honest scope of the Team tier. It does not convert 'better' — the free tier's single conversion is already the complete validation job. It makes the conversion operation survivable by a team: many hands, one set of facts, and a portfolio view of who needs what, by when, in which country.
One client record, used by everyone
The workspace's foundation is the shared client record: legal name, full address, country, size class for phased-mandate countries, VAT identifier, Peppol ID, channel preferences, and the client's current acceptance verdict. Every conversion for that client draws on the same record, so the identifier a colleague collected in March is the identifier on the invoice another colleague issues in October.
Agencies feel the return in exceptions: the bulk run's failure list stops containing mysteries ('whose client is this? what is their Polish size class?') because the record answers before the question forms. Onboarding becomes a team checklist with a completeness gate, not a favour one person does for the future. When staff change — the moment agency knowledge usually evaporates — the records stay, and invoicing continuity is a property of the workspace rather than of anyone's tenure.
Runs, roles and the monthly rhythm
With records shared, the billing run becomes a rhythm a team can execute: monitored clients reviewed for verdict flips; the run assembled and bulk-converted (up to 200 per job on the Pro engine, higher limits on Team); exceptions worked by rule and cleared against the shared records; exports pushed to Xero or QuickBooks and CSV for the clients' own accountants where the agency provides them; sends completed per channel, Peppol confirmations filed from the agency's Qvalia account.
Roles clarify naturally around the artefacts: whoever prepares the run owns the exception list; whoever owns the client relationship owns the record's accuracy; whoever sends owns the confirmations file. None of those ownerships require the same person — which is precisely the agency condition the workspace exists to serve. The process survives holidays, handovers and growth because it was never a person's memory wearing a process costume.
Multi-country portfolios and the mandate wave
Agencies serving EU clients hold the whole mandate map at once: Belgian clients structured-required since January 2026, Polish clients flipping through 2026, French clients' receiving duty from September 2026, German and Spanish phases across 2027–2028, Italian clients long settled, and the ViDA backstop behind the rest. Country rule packs apply each destination's layer; monitored clients keep each verdict current; the workspace shows the portfolio's position as a whole, so the quarter where eleven clients flip is visible as a capacity question months ahead.
That visibility is what an agency sells, whether it lists it or not: clients outsource invoicing pain to firms that absorb complexity calmly. An agency that can say — truthfully, from its own dashboard — 'all your EU invoices are structured, validated and tracked against every mandate date' has turned a regulatory wave into a service line. The workspace is the difference between that sentence as marketing and as operations.
When Team is the right tier — and when it is not
The tiers map to organisational shapes, and honesty about the mapping serves everyone. One person, a few clients, a monthly handful of invoices: the free tier's conversions plus disciplined records may genuinely suffice, with Pro added when bulk runs and monitoring start saving real hours. One person with fifty clients, or several people sharing any client load: the coordination problem has arrived, and Team is priced for it at $49/month — against the cost of one mandate surprise across a portfolio, a trivial figure.
What Team never replaces: the underlying disciplines. Records must still be collected accurately, identifiers verified, exceptions actually worked, confirmations actually filed. A workspace organises discipline; it does not substitute for it. Agencies that bring the discipline find the tier multiplies it across every client they will ever onboard — which is the entire business case, stated once and compounding monthly.
Setting up an agency workspace in 5 steps
- Centralise client records: one shared record per client with address, country, size class, VAT identifier and Peppol ID.
- Make onboarding a completeness gate — no record is 'ready to invoice' until the identifiers its invoices need are present.
- Run the monthly rhythm as a team: review monitored clients for flips, bulk-convert, work exceptions by rule.
- Assign artefact ownership per run: preparer owns exceptions, relationship owner owns record accuracy, sender owns confirmations.
- Review the portfolio view quarterly — upcoming flips by country are a capacity plan, not a surprise list.
Worked example: an agency's first mandate quarter
A six-person agency holds 34 EU clients. In January 2026 its workspace shows: 5 Belgian clients structured-required, 9 Polish clients split by size across the February and April phases, 3 Italian clients long settled, the rest voluntary or pre-phase. The team spends one meeting on the view: Peppol setup confirmed, Polish size classes verified with clients, templates audited through a rehearsal bulk run whose exception list exposes two stale client records.
The quarter then executes as routine: monthly runs, exceptions shrinking run over run, April's Polish flip passing without a single client email beginning 'unfortunately'. The agency's account lead summarises it to a prospect in one line — 'mandates are a dashboard for us, not a deadline' — and the line is true, which is what makes it sales material.
Frequently asked questions
What does Team add over Pro?
Team workspaces for agencies and higher limits, on top of everything in Pro: bulk conversion (up to 200 per job), country rule packs, monitored clients and Xero/QuickBooks/CSV exports. Pro is $19/month; Team is $49/month.
We are two people — do we need Team?
If you share clients, yes: the coordination problem starts with the second person, not the fiftieth client. Shared records and a portfolio view are the tier's substance.
Does Team change how invoices validate?
No — validation is identical across tiers; the free tier's single conversion is the complete job. Team organises the operation around the engine: records, runs, monitoring and roles.
Can the workspace track mandate dates for all our clients?
That is monitored clients' job — each client's acceptance verdict re-checked as mandates change — surfaced at portfolio level for the agency.
What is the biggest agency mistake Team prevents?
Knowledge evaporation: identifiers, size classes and channel details living in one person's email or memory. Shared records make continuity a property of the firm.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- Bulk invoice conversion: turning a whole billing run into validated e-invoices
- Monitored clients: tracking each client's e-invoicing mandate status as dates move
- Freelancers invoicing EU clients: the e-invoicing playbook
- Country rule packs: the per-country layer on top of EN 16931 validation
- Exporting converted invoices to Xero, QuickBooks and CSV