FolioU4Unit 4
As at
Sun 22 Nov 2026
Entries
19
Not yet
18
Page seal 350E, 255°18′. Drawn from the SHA 256 of this page’s source text350E
Page seal350E, 255°18′

E Invoicing Connection

Quality gate (target)
Fri 18 Dec 2026
First sale (target)
Mon 21 Dec 2026
Turnaround
Not yet: set from measured Bench runs, per rule set1

Unit 4, the E Invoicing Connection. Many countries now require invoices to be sent in a set electronic format, through a state platform or an approved provider. We map one invoicing system to the national format, write the steps to connect it, validate 20 real invoices, find the cause of each reject and write the fix. At launch this job runs in runbook mode: AI agents check the system's output, write each step and test the result; your own developer or software house applies each change; we do not log in to your systems. At launch, a second AI model from another company and a named reviewer under contract will check every job.2 Invoice Rescue finds and fixes the cause when a system is live and failing. Connection prices at launch run from 304 USD direct (Poland) to 792 USD direct (Saudi Arabia); full prices, once we can make the changes ourselves, run from 380 USD to 990 USD. Invoice Rescue is 232 USD at launch and 290 USD at full price.

Each country is its own rule set, with its own Bench gate. No rule set is on sale before its gate passes.3

Lines of this unit

LineLaunch priceLaunch price, through a partnerFull price, directFull price, wholesaleGate, target
E Invoicing Connection, Saudi Fatoora rule set792 USD472 USD990 USD590 USDFri 18 Dec 2026
E Invoicing Connection, Poland KSeF rule set304 USD198.40 USD380 USD248 USDFri 18 Dec 2026
E Invoicing Connection, Germany rule set552 USD360 USD690 USD450 USDSat 2 Jan 2027
E Invoicing Connection, UAE through an accredited provider552 USD360 USD690 USD450 USDSat 16 Jan 2027
E Invoicing Connection, France and Belgium rule set469.60 USD306.40 USD587 USD383 USD
Invoice Rescue, per system232 USD152 USD290 USD190 USDFri 18 Dec 2026

What we do, in every country

  • Map one system to the national format. The system can be custom built, legacy, an ERP, a point of sale system or Odoo Community.
  • Write the steps to connect it to the state platform, an accredited provider or a Peppol access point (Peppol is the shared European network for sending e invoices). At launch your developer applies them.
  • Validate 20 real invoices with the official validator.
  • Find the cause of every reject, write the fix for your developer to apply, and validate again.
  • Write the runbook: how the system sends, what to do when an invoice is rejected, and which version of the validator rules it was tested against.

What this unit is not

This is configuration work, not tax work. We give no VAT or tax advice. We file nothing in the client's name. The VAT treatment of each invoice stays with the client's own accountant, and the scope says so in writing.

We believe no licence is needed for technical integration work in Saudi Arabia, Poland, Germany or the UAE.4 If a country's page says otherwise, that rule set waits until a licensed partner in that country signs.

Saudi Arabia: Fatoora

  • The date. Taxpayers whose revenue subject to VAT passed SAR 187,500 in any year from 2022 to 2025 connect to Fatoora by 1 Feb 2027 (Wave 25, S11).
  • How onboarding works. The Fatoora portal issues a one time password that is valid for one hour (S62, a search result).5 We book that hour with the client in advance.
  • Arabic copy. Beside each XML invoice, the client gets an Arabic readable copy made with an Arabic PDF engine.
  • Who it is for. Custom, legacy and point of sale systems, reached through software houses and accountants. Odoo and SaaS users are offered Invoice Rescue instead.
  • Price. At launch, in runbook mode: 792 USD direct, 472 USD wholesale. Full price, once we can make the changes ourselves: 990 USD and 590 USD. This rule set has its own ratio: wholesale is 40 percent under direct.
  • Against the market. Not yet: public prices of 3 local Fatoora integration providers read and recorded with URL and date before the gate6
  • Bench gate. Fri 18 Dec 2026 (target), 50 cases from public sample invoices, the official validator rules and the sandbox. First sale Mon 21 Dec, to partners who came in through the opt in doors.7

Poland: KSeF

  • The date. The largest firms have issued through KSeF, the national e invoicing system, since 1 Feb 2026, and most other firms since 1 Apr 2026. Firms whose invoiced sales are up to PLN 10,000 a month join from 1 Jan 2027 (S37).
  • Who it is for. Custom and legacy systems, through system houses and tax advisers. Odoo partners get Invoice Rescue and Community edition gaps only, since Odoo's own localisation covers the standard format.
  • Price. At launch, in runbook mode: 304 USD direct, 198.40 USD wholesale. Full price, once we can make the changes ourselves: 380 USD and 248 USD. Poland is a Tier 3 country, so these are 55 percent of the Tier 1 price.
  • Bench gate. Fri 18 Dec 2026 (target), 50 cases. First sale Mon 21 Dec, to partners who came in through the opt in doors.7

Germany: XRechnung and ZUGFeRD

  • The date. Businesses with turnover above EUR 800,000 issue e invoices from 1 Jan 2027. All domestic business to business invoices follow from 1 Jan 2028 (S38).
  • The formats. XRechnung is a pure XML invoice. ZUGFeRD is a PDF with the XML inside it.
  • Who it is for. Custom and legacy systems, through system houses and tax advisers.
  • Price. At launch, in runbook mode: 552 USD direct, 360 USD wholesale. Full price, once we can make the changes ourselves: 690 USD and 450 USD.
  • Bench gate. Sat 2 Jan 2027 (target), 50 cases. First sale Mon 4 Jan 2027. 7

United Arab Emirates: provider connection

  • The date. Businesses with revenue under AED 50 million appoint an accredited provider by 31 Mar 2027 and go live on 1 Jul 2027. Under Cabinet Decision No. 173 of 2026, not implementing, including not appointing a provider, carries a penalty of AED 5,000 plus AED 5,000 a month, up to AED 50,000 in any 12 consecutive months (S12, rechecked 22 Nov 2026). RSM reads the penalty as starting from each group's compliance date, 1 Jul 2027 for this group, but the same page also calls a business without a provider before that date late (S12, read 22 Nov 2026).8
  • How we connect. Through one accredited provider, under a written API partner agreement.9
  • Arabic copy. An Arabic readable copy sits beside each XML invoice.
  • Price. At launch, in runbook mode: 552 USD direct, 360 USD wholesale. Full price, once we can make the changes ourselves: 690 USD and 450 USD.
  • Bench gate. Sat 16 Jan 2027 (target), 50 cases on the provider's sandbox, once the agreement exists. First sale Mon 18 Jan 2027. 7

Later: France and Belgium

France requires small and micro firms to issue e invoices from 1 Sep 2027 (S39). Belgium has required structured business to business e invoices since 1 Jan 2026 (S40). This rule set is planned to open with the French lane in May 2027 (target), at 469.60 USD direct and 306.40 USD wholesale at launch in runbook mode, and 587 USD and 383 USD at full price (Tier 2, 85 percent).10

Invoice Rescue

For a system that is already connected and failing. We find why invoices are rejected, write the mapping fix for your developer to apply, revalidate and write the runbook. Per system: 232 USD direct and 152 USD wholesale at launch in runbook mode; 290 USD and 190 USD at full price. Opens with each rule set's gate.

Free e invoicing proof

For partners: 5 sample invoices from the partner's system pass the official validator for one rule set, with a signed report. Offered only after that rule set's gate.11

How it is accepted

  • 20 invoices validate. 20 real invoices from the client's system pass the official validator for the rule set with no errors.
  • The connection answers. The platform, provider or access point accepts a test submission from the system.
  • Rejects closed. Every reject seen during the unit has a recorded cause and fix, and the invoice passes on resubmission.
  • Rule version recorded. The record names the validator rule file version the invoices were tested against.
  • Arabic copy matches, for Gulf rule sets: each Arabic copy carries the same invoice number, dates, amounts and tax lines as its XML.

Warranty

Proposed: we redo the work free until all 20 invoices validate.12

Runbook mode

The client's own developer or software house applies the changes from our runbook. We hold no write access to the client's system. At launch every order runs this way; we make changes ourselves only once insurance that covers AI agent work is in place.13 Runbook mode is the launch price, 20 percent under the full price.

Price

The firm's own prices, in US dollars. Unit 4 takes the tier of the rule set's country.

Rule setLaunch priceLaunch price, through a partnerFullFull wholesale
Saudi Fatoora792 USD472 USD990 USD590 USD
Poland KSeF (Tier 3)304 USD198.40 USD380 USD248 USD
Germany XRechnung and ZUGFeRD552 USD360 USD690 USD450 USD
UAE provider connection552 USD360 USD690 USD450 USD
France and Belgium (Tier 2)469.60 USD306.40 USD587 USD383 USD
Invoice Rescue, per system232 USD152 USD290 USD190 USD

Full: full price (once we can make the changes ourselves); Full wholesale: full price, wholesale (through a partner, once we can make the changes ourselves).

Payment is taken in full at order.14

What the buyer gives

  • Access to the invoicing system's export, or a developer who runs the changes.
  • 20 real invoices to validate, chosen by the client.
  • Registration on the platform or with the provider, done by the client. In Saudi Arabia, the client is present for the one hour password window.
  • The name of the client's accountant, who keeps the VAT treatment.

What the buyer gets back

  • The format mapping for the system.
  • A working connection, tested.
  • A validation report for 20 invoices, with the rule file version.
  • A runbook for sending and for rejects.
  • In Gulf rule sets, an Arabic readable copy of each invoice.
  • A signed Proof of Fix record.15

Who checks it

AI agents build the mapping, run the validator, write the runbook and test the result. At launch the client's developer applies each change, and we do not log in to the client's systems. A second AI model from a different company checks the work.16 At launch, a named reviewer under contract will review and sign every job.17 Is client data used to train AI? No, unless the client ticks a consent box that allows it.

Sources

The spec file

Version 0.1.0 · Status: draft

The machine readable spec of this unit. Download it and hash it yourself: the seal below is drawn from its SHA 256.

Acceptance tests in the spec

  1. 01invoices_validate_2020 real invoices from the client system pass the official validator for the rule set with no errors.official validator
  2. 02connection_acceptsThe platform, accredited provider or access point accepts a test submission from the client system.platform response
  3. 03rejects_closedEvery reject seen during the unit has a recorded cause and fix, and the invoice passes on resubmission.firm record
  4. 04rule_version_recordedThe record names the validator rule file version the invoices were tested against.firm record
  5. 05arabic_copy_matchesGulf rule sets only: each Arabic readable copy carries the same invoice number, dates, amounts and tax lines as its XML. Not applicable outside the Gulf rule sets.firm record
Seal of this unit’s spec file42A6

Spec U4 0.1.0, 42A6, 304°37′

42a6d89d 2339d2f0 b9e8ca1c 78a2867d 5c99de6c 2c82596f 4d2c682b 82fa45ed

Download the spec file

Not yet in place18

Nothing is on sale yet; each numbered mark on this page points to a condition below. Every condition, with its state, is on the status board.

  1. 1set from measured Bench runs, per rule set
  2. 2second model vendor connected; two contracted reviewers, target Mon 30 Nov 2026
  3. 3Bench gate passed and sealed, per rule set
  4. 4each country's authority page read and recorded before its gate
  5. 5portal manual read in full
  6. 6public prices of 3 local Fatoora integration providers read and recorded with URL and date before the gate
  7. 7Bench gate passed
  8. 8start of the penalty read in Cabinet Decision No. 173 of 2026 or on the FTA page
  9. 9written API partner agreement signed with an accredited provider; time and fee not yet known
  10. 10Bench gate date set and passed
  11. 11rule set gate passed
  12. 12warranty terms for Unit 4 set by the founder and printed before the first gate
  13. 13cover that includes AI agent work bound
  14. 14company formed and checkout live
  15. 15client record signing live in our record log
  16. 16second model vendor connected
  17. 17two contracted reviewers, target Mon 30 Nov 2026
  18. 18page read in full

Each item is also marked where it stands on this page.