The e-invoicing journey for medium-sized companies differs fundamentally from that of small businesses. You don’t issue dozens of invoices a month — you issue thousands of them across multiple branches, distributed sales teams, and operational systems that don’t necessarily talk to each other. Here, technical integration and volume management become the real measures of a successful rollout, not merely the ability to issue a single compliant invoice. In this guide we explain how to build an e-invoicing system that can handle your volume, integrate with your existing systems, and stay aligned with e-invoicing requirements at every stage.
Why a medium-sized company differs from a small one in e-invoicing
The difference isn’t in the law. The rulings of the Zakat, Tax and Customs Authority (ZATCA) apply equally to everyone. The difference is in operations. A small business may be content with a standalone invoicing solution that issues its invoices and sends them to the Authority. A medium-sized company, however, faces three simultaneous pressures that make a standalone solution insufficient.
The first pressure is volume. Issuing thousands of invoices a month means that any slowdown or interruption in the connection to the Fatoora platform instantly turns into queues at points of sale and delays in serving customers. Reliability here isn’t a luxury — it’s a condition for keeping the business running.
The second pressure is distribution. Several branches, dozens of users, varying permissions, and possibly separate warehouses. All of this must flow into a single data source; otherwise your tax figures scatter and preparing a unified return becomes difficult.
The third pressure is integration. A medium-sized company usually has an accounting system, and may have an enterprise resource planning (ERP) system, an inventory system, or a human resources system. E-invoicing must fit in with these systems, not add a new isolated island that requires duplicate manual entry.
This difference translates into a completely different purchasing decision. A small business asks: does this solution issue a compliant invoice? A medium-sized company asks: can this solution handle my volume, integrate with my systems, and give me a unified view across my branches? The focus shifts from a single feature to a complete system.
The pillars of an e-invoicing system for medium volume
Before any technical decision, order your priorities around four pillars that govern the success of a large-scale rollout. These pillars are what distinguish a solution that withstands your volume from one that stumbles at the first peak season.
- Generation and connection reliability: Stable performance under high loads and no invoice lost on its way to the Authority.
- Unification across branches: Unified data and permissions in a single system, with consolidated reports at the enterprise level.
- Integration through APIs: Automatic connection with accounting, ERP, and inventory systems instead of duplicate entry.
- Governance and permissions: Controlling who issues, who approves, and who views reports, across all branches.
These pillars interact with one another. Weak API integration undermines unification because data arrives incomplete. Lax governance undermines reliability because any user can edit an issued invoice. So evaluate the solution as a whole, not as a list of separate features.
Architectural integration between systems
How branch invoices flow automatically from generation sources to the Fatoora platform via Qoyod
Technical integration: the backbone of medium volume
The core of the solution for a medium-sized company is integration through application programming interfaces (APIs). Instead of employees entering invoices twice — once in the operational system and once in the invoicing system — data flows automatically from its generation source to the invoicing system, and from there to the Fatoora platform. This automatic flow reduces human error, speeds up generation, and keeps your accounting figures matching what was reported to the Authority.
When evaluating any solution, ask about the quality of the integration APIs available: is the documentation clear? Does it support connecting points of sale, ERP systems, and online stores? Does it handle errors safely, such as retrying when the connection drops? Fragile integration loses you invoices, while robust integration makes volume a detail rather than a burden.
There are three common integration scenarios in medium-sized companies. The first is connecting branch points of sale so they issue their simplified invoices directly through the central system. The second is connecting an ERP or inventory system so sales and item movements are reflected in invoicing without manual entry. The third is connecting the online store so it issues its electronic invoices as soon as the order is completed. The more of these three paths the solution covers, the less you depend on manual entry.
Clearance and reporting: understand the difference
In Phase 2 you deal with two types of processing. The business-to-business (B2B) tax invoice is subject to Clearance: it must be approved by the Authority before being sent to the buyer. The simplified tax invoice for the consumer (B2C), however, is delivered to the customer immediately, then reported to the Authority within 24 hours. For a medium-sized company that mixes both types across its branches, your system must distinguish between the two paths automatically, so you neither wait for the clearance of a simplified invoice nor exceed the reporting deadline. Learn more about the types of electronic invoices before configuring your settings.
The common mistake here is treating every invoice the same way. A retail branch that issues hundreds of simplified invoices a day can’t tolerate waiting for clearance on every transaction, while a wholesale invoice to another company must not be delivered before clearance. Automatically distinguishing between the two paths by customer type is what preserves both the speed of the branches and their compliance.
The mandatory technical fields in Phase 2
Invoices in Phase 2 require technical fields that the system generates automatically according to the Authority’s specification (UBL 2.1). The most notable are:
- Cryptographic stamp: A digital signature via the Cryptographic Stamp Identifier (CSID) certificate issued when you onboard your business with the Fatoora platform.
- Universally Unique Identifier (UUID): A distinct number for each invoice that is never repeated.
- Previous invoice hash: A chain that links each invoice to the one before it to ensure the integrity of the sequence.
- Quick Response (QR) code: It carries the invoice data and the signature.
You don’t write these fields manually. A compliant system generates them for you, but it’s important to understand they exist so you can assess the readiness of any solution in front of you. Ask any provider for a practical demo that shows a fully populated invoice accepted by the Authority’s sandbox environment, not just a promise of compliance.
Volume management: from hundreds of invoices to thousands
Volume is what breaks weak solutions. A solution that runs smoothly with 200 invoices a month may collapse with 20,000. When managing volume, pay attention to three aspects.
The first aspect is peak-time performance. Sales seasons and events suddenly raise the number of invoices. Make sure your system generates and reports without noticeable delay even under the highest loads.
The second aspect is error handling. With thousands of invoices, a small percentage of rejections or interruptions turns into a significant number. The system must provide a clear log of rejected invoices, automatic retries, and alerts for the relevant teams.
The third aspect is consolidated reporting. You need a unified view: how many invoices were issued today across all branches? How many of them were reported successfully? What is the total sales tax? These figures feed the value-added tax return and prevent surprises at the end of the tax period.
Add to this an organizational dimension that many overlook: who monitors the reporting success rate daily? At medium volume, it isn’t enough for the system to work — someone or a team must own the responsibility of watching the status dashboard and handling rejections before they pile up. Defining this responsibility clearly is an integral part of volume management.
Numbers that govern your operations at scale
Four numbers by which you monitor e-invoicing performance across multiple branches
Unifying branches and permissions in a single system
Multiple branches are the most prominent feature of a medium-sized company, and they are the source of the greatest fragmentation if not managed well. Unification means that each branch issues its invoices under a single central system, with the same numbering and tax rules, and that management sees the full picture in real time.
Governance begins with defining roles. The branch cashier issues simplified invoices only. The branch manager views their branch’s reports and approves returns. The accountant at headquarters sees all branches and prepares the return. Senior management views the consolidated reports without editing permission. This separation of permissions protects your data and facilitates auditing.
Unification is directly reflected in the value-added tax return. When the invoices of all branches gather in a single source, preparing the return becomes a one-click operation instead of an exhausting manual assembly from scattered spreadsheets. And the less manual intervention there is, the lower the risk of an error that could cost you a fine or an audit.
The cost of not being ready for medium volume
Ignoring integration and volume management doesn’t show its effect on launch day — it shows weeks later when the burden accumulates. The cost comes from three sources.
The first source is operational cost. Duplicate entry devours working hours, and increases with every rise in volume, until you find an entire team working to reconcile figures that could have matched automatically.
The second source is compliance cost. Exceeding the reporting deadline for simplified invoices, or the failure to clear tax invoices without follow-up, exposes you to the Authority’s violations. And at large volume, a small recurring error swells quickly.
The third source is decision cost. When your figures are scattered and not real-time, management decisions are delayed or built on old data. A unified view is not an accounting luxury — it is a decision-making tool.
Security and the audit trail at scale
With thousands of invoices and dozens of users, security and the audit trail become a pillar no less important than generation itself. Every invoice carries a trace that must remain reviewable: who issued it, when, whether it was edited, and whether it was reported successfully.
The hash chain that Phase 2 mandates serves this purpose technically: it links each invoice to the one before it, so any tampering with the sequence is revealed. But internal governance complements it: precise permissions that prevent editing an issued invoice, an activity log that documents every action, and backups that protect your data. These are not secondary technical details — they are what protects you the day an Authority auditor requests your data.
Ask any provider about the audit trail: does it keep a complete trace of every invoice? Does it prevent unauthorized deletion? Does it export the data in a format acceptable for review? At medium volume, the absence of these safeguards turns from a nuisance into a real risk.
Preparing for Phase 2 and the waves
Phase 2 (linking and integration) began on January 1, 2023, in ordered waves ranked by the business’s revenue, with a notice period of about six months for each wave. Medium-sized companies usually fall in later waves after the large taxpayers, but don’t build your plan on guesswork. Rely on your business’s official notice from the Authority to determine your date precisely.
Before your wave’s date, carry out these steps in order:
- Onboard your business with the Fatoora platform and obtain the Cryptographic Stamp Identifier (CSID) certificate.
- Test the integration in the sandbox environment before production, especially the clearance path for tax invoices.
- Train the branch teams on both paths: clearance for B2B invoices and reporting within 24 hours for B2C invoices.
- Review your master data: tax registration numbers, customer data, sales items.
- Activate consolidated reports to monitor the reporting success rate from day one.
To make sure every item is covered before launch, use the readiness checklist in the e-invoicing readiness guide. And if you’re moving up from a small volume and want to understand the starting point, the small businesses guide clarifies the fundamentals you build on.
Managing change across teams and branches
The technical side is half the story. The other half is human. Rolling out e-invoicing at scale means changing the habits of dozens of employees across branches that may be geographically dispersed. A simple change plan cuts out a lot of the stumbling.
Start with a single pilot branch before rolling out. Choose a medium-sized branch, implement the system fully there, gather the feedback, then extend the successful experience to the rest. This gradual approach exposes problems early and builds the teams’ confidence.
Provide a quick reference for each role: a card for the employee at the point of sale, a guide for the branch manager, and a clear point of contact for any glitch. The less ambiguity there is, the fewer generation errors occur and the higher the reporting success rate from the first week.
Connect your branches and systems into a single invoicing system
Qoyod links e-invoicing with your accounting and the Fatoora platform via API, and manages your invoice volume and multiple branches with consolidated reports compliant with Phase 2.
Preparing the data and transitioning to the new system
Before invoices can flow, your master data must be clean. A medium-sized company accumulates years of customer and item data, much of it duplicated or incomplete. Moving to an integrated invoicing system is an opportunity to clean up this data, not to carry over its mess as is.
Start with the chart of accounts. Make sure sales items are linked to the correct accounts and the appropriate tax rates, because the electronic invoice reflects this linkage automatically. An item with a wrong tax rate generates faulty invoices en masse, and correcting them after issuance is costly.
Then review the customer data. A business-to-business tax invoice requires a valid tax registration number for the buyer. Incomplete data means invoices rejected at clearance. Set aside time to audit the customer record before launch, especially wholesale customers to whom you issue tax invoices.
Finally, unify invoice numbering and its rules across the branches. Leaving each branch with an independent numbering system makes tracking and auditing difficult. A central system with unified rules preserves the invoice sequence and facilitates the hash chain that Phase 2 mandates.
A practical scenario: a chain with five branches
Imagine a chain with five branches that together issue about 15,000 invoices a month, most of them simplified consumer invoices and some of them tax invoices for wholesale customers. Before integration, each branch issued its invoices in a separate point-of-sale system, then the accountant entered the figures manually into a different accounting system at the end of the month. The result: hours of duplicate entry, recurring discrepancies between branch and accounting figures, and a tax return prepared under time pressure.
After moving to an integrated system, every invoice is now issued from the branch and reported to the Authority in real time, and is automatically reflected in accounting. Distinguishing between the simplified and tax invoice became automatic based on customer type. And management now sees a unified dashboard: the daily invoice count, the reporting success rate, the total sales tax across the branches. Preparing the return turned from an exhausting monthly task into a quick review of ready figures.
The lesson from this scenario is clear: the gain didn’t come from a single feature, but from linking generation, reporting, and accounting into a single flow. This is the essence of what a medium-sized company needs, and it is what you should look for when choosing your solution.
How to choose the invoicing solution that fits your volume
When comparing solutions, turn the four pillars into practical questions you ask every provider. The answers reveal who is truly suited to medium volume.
- Does the solution support documented API integration with points of sale, ERP, and inventory systems?
- Does it automatically distinguish between the clearance path for tax invoices and reporting for simplified ones?
- Does it unify branch data and permissions in a single system with consolidated reports?
- How does it behave when the connection drops or the Authority rejects an invoice? Does it retry and log the status?
- Does it link invoicing directly to your accounting so it feeds the value-added tax return without duplicate entry?
- Does it offer a sandbox environment to test the integration before production?
Any provider that stumbles on these questions may suffice for a small business, but it puts you before a real risk at medium volume. Always ask for a practical demo, not theoretical promises.
Where Qoyod stands for the medium-sized company
The Qoyod accounting software is designed to handle the requirements of medium volume without losing its simplicity. It issues electronic invoices compliant with Phase 2, integrates with the Fatoora platform to perform clearance for tax invoices and reporting for simplified ones, and manages the cryptographic stamp, the unique identifier, the hash, and the Quick Response code automatically.
At the level of expanded operations, Qoyod unifies branch data and permissions in a single system, provides consolidated reports at the enterprise level, and integrates with your other systems via APIs. As for the teams handling the accounting and tax side, they find support in integrating invoicing with accounting without duplicate entry.
An important governance note: Qoyod generates value-added tax return data accurately, but filing the return and paying the tax remain through the Authority’s portal on your side. The system prepares the figures, and you approve and file. This division of roles preserves your legal responsibility while giving you at the same time the accuracy of the figures and the speed of preparation.
Return on operations, not just on paper
Before and after integrating and unifying e-invoicing in the medium-sized company
Before: fragmented manual invoicing
- Duplicate entry of the invoice in the operational system and the invoicing system
- Manual errors creeping into the tax return figures
- Scattered reports across branches that are hard to consolidate
- The risk of exceeding the 24-hour reporting deadline and accumulating rejections
After: unified automatic integration
- Automatic data flow via API straight from the generation source
- Zero duplicate entry and accuracy in the value-added tax figures
- A single consolidated report for all branches with a real-time central view
- Stable adherence to the reporting deadline within 24 hours
The real return for a medium-sized company is not measured only by avoiding fines, but by the working hours saved by eliminating duplicate entry, by the accuracy of figures that link your sales to your tax return, and by the unified view that gives management a decision built on real-time data instead of monthly manual assembly.
Add up these gains over a full year, and you’ll find that the value of integration and volume management exceeds the cost of the system itself. Here compliance turns from a burden imposed by the Authority into an operational tool that raises your efficiency and gives you greater confidence in every figure.
Frequently asked questions
Does a medium-sized company really need API integration?
How do we unify invoicing across multiple branches?
What is the difference between clearance and reporting in our daily practice?
When should we test the connection before our wave’s date?
Does Qoyod file the tax return on our behalf?
How do we handle high volume during peak seasons?
Try Qoyod free for 14 days with no credit card.
Also read in the fundamentals track
- Small businesses guide
- types of electronic invoices
- Readiness checklist
