InvoStaq’s cover photo
InvoStaq

InvoStaq

IT System Custom Software Development

Dublin, Co. Dublin 59 followers

The AI Data Quality & Anomaly Shield for B2B E-Invoicing

About us

Global mandates like EU ViDA and UAE ZATCA are permanently changing B2B commerce. The era of sending messy, unstructured PDF invoices is over. Today, if your invoice data is incorrectly formatted, the government and the Peppol network will instantly reject it—blocking your transaction and halting your cash flow. Enter Invostaq. We are the AI Data Quality & Anomaly Shield for B2B E-Invoicing. We ensure mid-market finance teams achieve "Zero-Touch Compliance" by stopping network rejections and government fines before an invoice ever leaves the accounting system. Instead of forcing CFOs to log into clunky external portals, Invostaq operates entirely headless. We sit silently behind the "Post" button inside major ERPs like Microsoft Dynamics 365 and Odoo. Our core products and capabilities include: 🔹 The Hybrid AI Syntax Guardian: We combine deterministic validation rules with Azure OpenAI. In under 200ms, our engine automatically maps messy ERP text to strict UN/CEFACT Peppol codes and auto-enriches missing VIES/VAT master data on the fly. 🔹 The Anomaly & Fraud Shield: We protect your Accounts Payable feed. Our AI scans historical ERP behaviors to instantly flag duplicate billing amounts and hijacked IBAN vendor fraud. 🔹 The Plain-English Copilot: When an invoice fails a strict network rule, we translate the cryptic "Error 400" XML codes into actionable, one-click prompts natively within your ERP. No manual data entry. No compliance guesswork. Just flawless data routing. We are currently launching Phase 1 pilots across the UAE and European markets. Are you a Microsoft Dynamics 365 or Odoo Integrator looking to seamlessly solve Peppol compliance for your SME clients? Let's partner. Send us a message or visit invostaq.com to learn more.

Website
https://invostaq.com
Industry
IT System Custom Software Development
Company size
2-10 employees
Headquarters
Dublin, Co. Dublin
Type
Privately Held
Founded
2026

Locations

Employees at InvoStaq

Updates

  • Eight months in, we still spend a surprising amount of time answering one Belgian question: are we actually in scope? It comes down to three yeses. Are you established in Belgium, or do you have a fixed establishment here? Being VAT-registered in Belgium without being established is not the same thing — foreign companies with only a VAT number fall outside. Are you a VAT taxpayer who is not exclusively exempt under Article 44? Businesses performing only exempt activities are out. Are you invoicing another Belgian-established VAT taxpayer? Domestic B2B is the whole scope. Three yeses and you are in, and have been since January. Structured Peppol invoicing, not a PDF by email, with the penalty regime live since 1 April. What stays out: B2C, cross-border B2B in either direction, non-established businesses, exempt-only taxpayers, flat-rate schemes. Two warnings from the field. First, "out of scope" is not "unaffected" — if your Belgian customers are in scope, your invoices still land in an AP process built around structured data. Second, cross-border is out only until the EU rules change at the end of the decade, so building a Belgium-only workaround is buying a problem. Not sure which column you're in? That's a short conversation, and worth having before your next invoice run. 👉 invostaq.com/contact #EInvoicing #Belgium #Peppol #VAT #Compliance #CFO #InvoStaq

    • No alternative text description for this image
  • There is one German e-invoicing obligation you may already be complying with by accident — and one you almost certainly aren't. Since 1 January 2025, every business in Germany must be able to receive structured e-invoices. Every business. No turnover threshold, no exemption for small companies, no carve-out for firms that only invoice consumers. That obligation is not on the horizon. It is eighteen months old. The good news is how little it takes to satisfy technically. If a supplier emails you an XRechnung XML or a ZUGFeRD PDF and it lands in a business inbox you actually monitor, you have met the receiving requirement. No portal, no platform, no project. The uncomfortable part is what happens next. Receiving a file is not the same as being able to read it, book it, and archive the structured original for the retention period. Plenty of German AP teams are technically compliant and operationally stuck — the XML arrives and someone opens the PDF view and types the numbers in by hand. And the issuing side is still ahead of you: 1 January 2027 above €800,000 of prior-year turnover, everyone else in 2028. So the honest question isn't "are we ready for 2027." It's "what does my team do today when a structured invoice arrives?" If the answer involves retyping, that is the project. 👉 invostaq.com/contact #EInvoicing #Germany #XRechnung #ZUGFeRD #AccountsPayable #CFO #InvoStaq

    • No alternative text description for this image
  • Most French e-invoicing projects are treated as a plumbing exercise. Pick a platform, connect it, done. But the invoice itself changes too — and that part lives in your ERP, not in your platform. Four mentions become mandatory on in-scope invoices: Your customer's SIREN. Not their VAT number, their nine-digit SIREN. Which means your customer master data has to carry it, for every customer, including the ones you onboarded in 2014. The delivery address, when the goods go somewhere other than the billing address. A field many ERPs hold but never print. The nature of the supply — goods, services, or both. A classification that has to be derivable per invoice, not guessed. The "option pour le paiement de la taxe d'après les débits" wording, where you have exercised that option. None of these are hard on their own. Together they are a data-quality project, and data-quality projects have lead times. A platform can transmit an invoice in a week. Filling in a SIREN you never collected for 4,000 customers takes rather longer. So if your readiness plan only names a platform, it is missing half the work. Twenty days is still enough to find the gaps — it is not enough to discover them on 1 September. 👉 invostaq.com/contact #EInvoicing #France #MasterData #FacturX #Compliance #CFO #InvoStaq

    • No alternative text description for this image
  • Eight months into the Belgian mandate, the most expensive misunderstanding is still the simplest one: what actually counts as an e-invoice. It is not "electronic." It is structured. For domestic B2B between Belgian-established VAT taxpayers, the compliant invoice is a structured file — Peppol BIS Billing 3.0 in UBL, built to the EN 16931 semantic standard — issued, transmitted and received in a form that can be processed automatically. Peppol is the default channel; you may agree another EN 16931-compliant format with a counterparty, but you still have to remain reachable over Peppol. Which means a PDF emailed to your customer is not an e-invoice. Neither is a scan, nor a spreadsheet someone exports and attaches. They may look electronic. They still require a human to retype the data at the other end — which is exactly what the law removed. The tolerance period for that ended on 31 March. Since 1 April the penalty regime applies: €1,500, then €3,000, then €5,000. If your team still describes invoicing as "we email the PDF," that sentence is the whole gap. It is usually days of work to close, not months. 👉 invostaq.com/contact #EInvoicing #Belgium #Peppol #EN16931 #Compliance #CFO #InvoStaq

    • No alternative text description for this image
  • Everyone plans the sending. Almost nobody plans the storing. In Germany that is the gap auditors will walk straight into. When you issue or receive a structured e-invoice, the structured file is the invoice. Not the PDF preview. Not the version your ERP rendered. Not the copy someone printed for the folder. So three things have to be true for eight years, the retention period for invoices since the 2025 change: You keep the original structured file, in the format you received it. Converting the XML into an image or deleting it after posting is not allowed. It stays unaltered and machine-readable, with integrity and authenticity intact for the whole period. For hybrid files like ZUGFeRD, the structured part is the record — and you keep the PDF as well if it carries tax-relevant detail that isn't in the XML, such as payment conditions or notes. Worth checking this week: ask whoever runs your archive what exactly gets stored when an e-invoice arrives. If the answer is "we save the PDF" or "it's in the DMS as an image," you have a finding waiting to happen — and it is far cheaper to fix now than in an audit. We review archiving alongside the invoicing flow, because passing one and failing the other still counts as failing. 👉 invostaq.com/contact #EInvoicing #Germany #GoBD #ZUGFeRD #Compliance #CFO #InvoStaq

    • No alternative text description for this image
  • Let's talk about the part nobody puts on the slide: what it actually costs to miss the French deadline. €50 for every invoice you issue outside an approved platform, or that doesn't meet the structured format. €500 for every e-reporting transmission you fail to send — and transaction data and payment data are counted separately. Each stream is capped at €15,000 a year. Miss your platform connection altogether and it escalates on its own track: a formal notice, then €500, then €1,000 every three months until you fix it. Now the part that should actually change your plan. The law includes a tolerance: no penalty if it's your first infringement in the current year and the previous three, and you correct it voluntarily or within 30 days of being asked. The DGFiP has also said sanctions won't be applied blindly from day one — they will look at whether a business can show a real, documented preparation effort. Read that again, because it tells you what to do with the next 20 days. You are not being graded on a perfect 1 September. You are being graded on being able to show you took this seriously before it. So write things down. Which platform, since when, who tested what, which entities are registered, what is still open and when it closes. We help clients build exactly that file — and the plan behind it. 👉 invostaq.com/contact #EInvoicing #France #FacturX #Compliance #CFO #InvoStaq

    • No alternative text description for this image
  • Most people picture e-invoicing as a portal you log into. It isn't. It's a network, and it looks like this. Four corners. You issue the invoice. Your access point sends it. Your customer's access point receives it. Your customer's system books it. No portal, no email, no PDF sitting in someone's inbox waiting to be typed in. The two access points speak the same protocol, so the invoice arrives structured and ready to process — in seconds. That is the model Belgium has been running on since January, and it is why the businesses that connected early stopped chasing "did you get my invoice?" almost overnight. From 1 January 2028, a fifth corner joins: invoice data flows to the tax authority in near real time as it crosses the network. Nothing you do manually. Everything you build now has to be ready for it. So when you choose a provider, don't only ask whether they can send an invoice today. Ask what happens at that fifth corner in 2028. We build these connections for a living, and we're happy to sketch yours in thirty minutes. 👉 invostaq.com/contact #EInvoicing #Belgium #Peppol #Compliance #CFO #InvoStaq

    • No alternative text description for this image
  • The most common objection we hear in Germany: "our customers want a readable invoice, not a data file." They can have both. That is the whole point of ZUGFeRD. One file. Open it and a person sees a normal PDF invoice — letterhead, line items, total. Feed the same file to an accounting system and it reads the structured XML embedded inside, compliant with EN 16931. Nobody has to choose. Nothing gets re-keyed. That matters because of where Germany is on the calendar. Receiving structured invoices has been mandatory since 1 January 2025, for every business, with no exemptions. Issuing becomes mandatory on 1 January 2027 above €800,000 of prior-year turnover, and for everyone in 2028. The window to keep sending PDFs by agreement closes at the end of this year. German teams that started with the hybrid format made the transition almost invisible to their customers. The ones waiting for a big-bang system change are the ones now running out of calendar. If you invoice into Germany and you are not sure which format your customers actually accept, that is a thirty-minute conversation — not a project. 👉 invostaq.com/contact #EInvoicing #Germany #ZUGFeRD #XRechnung #Compliance #CFO #InvoStaq

    • No alternative text description for this image
  • Twenty days before the French mandate, most readiness checklists stop at "we signed with a platform." Here is the step that gets skipped: your entry in the central directory. From 1 September, that record is how a supplier's platform finds yours. Legal identifier, routing ID, the platform you are registered with. It is, in every practical sense, your postal address for invoices. When it is wrong — an old SIREN, a stale routing ID, an entity registered under a platform you no longer use — the invoice does not bounce back with a friendly error. It simply never arrives. Your supplier believes they invoiced you. You believe they didn't. Both of you find out at the end of the payment term. So before the deadline, open your record and read it out loud against your own master data. Every entity, every establishment, every identifier. It takes ten minutes. Getting it wrong takes a quarter to unwind. We check these with clients every week. If you would rather have a second pair of eyes on yours 👇 👉 invostaq.com/contact #EInvoicing #France #FacturX #Compliance #CFO #InvoStaq

    • No alternative text description for this image
  • Every Belgian e-invoicing article talks about the fines. Almost none mention the discount. Belgium didn't only make e-invoicing mandatory — it also decided to help pay for it. Under Article 64ter CIR 92, self-employed people, liberal professions and SMEs can deduct 120% of what they spend on getting compliant. Every €1 spent reduces your taxable base by €1.20. What counts: your Peppol-compliant invoicing subscription, setup and configuration, network registration, consulting and training. What doesn't: depreciation on capitalised software. The window covers costs incurred between 2024 and the end of 2027. After that it's gone, and compliance goes back to being an ordinary expense. So the arithmetic is unusually friendly right now. Fines of €1,500 to €5,000 on one side. A 120% deduction on the other. And a system that gets your invoices paid faster in between. If you're still on the fence in Belgium — or you've already paid for a platform and nobody told your accountant — it's worth thirty minutes. 👉 invostaq.com/contact #EInvoicing #Belgium #Peppol #Tax #SME #CFO #InvoStaq

    • No alternative text description for this image

Similar pages