Saudi Aramco Invoice Requirements: Vendor Guide to IKTVA

Saudi Aramco enforces some of the most prescriptive invoice format rules of any buyer in the global energy sector. Every field on a vendor invoice is subject to strict validation, and a single formatting error will trigger an outright rejection, pushing payment back by weeks or longer.

The requirements are exacting down to individual characters. Invoice numbers must not exceed 16 digits. Purchase order numbers must begin with 65 for materials or 45 for services. The supplier name printed on the invoice must match the company's Commercial Registration exactly, with no abbreviations or variations. Totals must appear both numerically and written out in words. All supporting documents, including the Service Entry Sheet (SES) and Goods Receipt (GR), must be attached at the time of submission. Beyond Aramco's own rules, vendors must simultaneously comply with ZATCA e-invoicing standards, which impose a separate layer of tax compliance formatting on every transaction.

These requirements are scattered across Aramco's dense supplier onboarding PDFs, portal help pages, and procurement bulletins, making it difficult for vendors to piece together a complete picture of what a compliant invoice actually looks like. International contractors entering Aramco's supply chain for the first time are especially vulnerable to rejections they could have avoided with clearer guidance.

Mandatory Invoice Format Rules for Aramco Vendors

Saudi Aramco enforces prescriptive invoice format rules that function as hard validation gates — not guidelines. Many of these fields are checked automatically by Aramco's procurement systems before a human ever reviews your submission. An invoice that fails any single check is rejected outright, with no partial approval or manual override.

Here is every field-level requirement your invoices must satisfy.

Invoice Number

Your invoice number must be a maximum of 16 alphanumeric characters. No special characters, no spaces exceeding the limit. If your internal numbering system generates longer strings, you will need a truncated or separate numbering convention specifically for Aramco submissions.

Purchase Order Reference

Every invoice must reference the corresponding PO number. Pay close attention to the PO prefix:

Materials POs start with 65 (e.g., 6500012345)
Services POs start with 45 (e.g., 4500067890)

This distinction matters because Aramco uses the PO prefix to route invoices through entirely different approval workflows. A materials invoice cited against a services PO — or vice versa — will not reach the correct approvers and will stall or be rejected.

Supplier Name

The supplier name on your invoice must exactly match the name registered in three places simultaneously:

Your Commercial Registration certificate
The Aramco contract
The Aramco Supplier Master File

Even minor discrepancies will trigger rejection. This includes abbreviations ("Co." vs. "Company"), transliteration differences between Arabic and English renderings of your company name, and variations in legal entity suffixes. If your Commercial Registration reads "شركة المقاولات المتحدة" but your invoice header uses a slightly different English transliteration than what Aramco has on file, the invoice fails validation. Confirm your exact registered name with your Aramco procurement contact before your first submission.

Invoice Total — Numeric and Written

Your invoice total must appear both as a numeric figure and written out in words. For example:

SAR 142,500.00 (One Hundred Forty-Two Thousand Five Hundred Saudi Riyals Only)

This dual-expression requirement is a fraud prevention measure standard across Middle Eastern procurement but often unfamiliar to vendors from Western markets. Omitting the written amount is one of the most common rejection triggers for first-time international suppliers.

Currency

The invoice currency must match the PO currency exactly. If the purchase order is denominated in SAR, your invoice must be in SAR. If the PO specifies USD for an international contract, invoice in USD. A currency mismatch — even between equivalent amounts — results in automatic rejection.

Tax Breakdown

Your invoice must comply with the applicable VAT rate and display a clear tax breakdown showing:

Taxable amount (net)
VAT rate applied
VAT amount
Total including VAT

Saudi Arabia's standard VAT rate is 15%. The tax line items must be calculated correctly and presented as separate fields — bundling tax into a single gross figure without itemization does not satisfy the requirement.

These are not areas where close enough counts. Aramco's automated validation checks these fields against the Supplier Master File, the PO record, and ZATCA tax rules before the invoice enters the approval queue. A single non-conforming field sends the entire invoice back to you, resetting your payment timeline from day one.

Supporting Documents Every Aramco Invoice Needs

Every invoice you submit to Saudi Aramco must arrive with a complete package of supporting documentation. The invoice itself is only one piece of the puzzle. Missing or mismatched attachments are the single most common reason Aramco rejects vendor invoices, so understanding exactly what to include for your contract type is essential before you hit submit.

Services Invoices: The Service Entry Sheet

If you are invoicing for services rendered, your submission must include a Service Entry Sheet (SES). The SES is Aramco's formal confirmation that the contracted services were performed and accepted by the responsible department. It functions as your proof of delivery for intangible work.

The SES must be signed and approved by the designated Aramco representative before you create your invoice. Submitting an invoice against an unapproved SES will result in an automatic rejection. Verify that the SES number, PO reference, and line item descriptions on your invoice match the approved SES exactly. Even minor discrepancies between the two documents will trigger a hold.

Materials Invoices: The Goods Receipt

For materials and equipment invoices, the equivalent document is the Goods Receipt (GR). The GR confirms that physical delivery of materials occurred at the specified Aramco facility and that the goods passed any required receiving inspection. Your invoice must reference the correct GR number and align with the specific PO line items covered by that receipt.

A common mistake among vendors supplying multiple shipments against a single purchase order is referencing the wrong GR or bundling line items from different receipts into one invoice. Each invoice should correspond to a specific GR, with line items that match precisely.

Additional Documentation by Contract Type

Beyond the SES or GR, Aramco may require supplementary documents depending on your contract structure:

Delivery notes — Required when goods are shipped to multiple Aramco locations or when partial deliveries are made against a single PO line.
Inspection certificates — Mandatory for equipment, materials, or components subject to quality specifications. These must be issued by an Aramco-approved inspection authority.
Milestone completion certificates — For project-based contracts, each invoice typically corresponds to a defined milestone. The completion certificate, signed by the project manager, validates that the milestone deliverables were met. Vendors working on large-scale projects should review Saudi construction invoice requirements and progress billing for additional guidance on progress billing structures common in Aramco capital projects.
Timesheet summaries — For time-and-materials contracts, approved timesheets covering the invoiced period must accompany the submission. These should carry signatures from both the vendor's site supervisor and the Aramco contract representative.

The 6-Month Submission Deadline

Aramco enforces a 6-month submission window from the date of the SES (for services) or GR (for materials). Invoices submitted after this deadline incur additional processing costs and may require special approval from Aramco's finance department before they can enter the payment queue.

This deadline catches more vendors than you might expect. Organizations that batch invoices on a quarterly cycle, or those with lengthy internal approval workflows before issuing invoices, frequently find themselves pushing against or exceeding the 6-month limit. If your company processes Aramco invoices alongside a large volume of other clients, build a tracking system that flags SES and GR dates as they approach the 5-month mark. Waiting for an internal sign-off that arrives at month five leaves almost no buffer for corrections if Aramco returns the submission for revisions.

Treat incomplete documentation as a preventable failure. Before submitting any invoice, run through a checklist: SES or GR attached and approved, PO line items matching across all documents, supplementary certificates included where the contract requires them, and submission date within the 6-month window. That verification step takes minutes and can save weeks of back-and-forth with Aramco's accounts payable team.

How to Submit Invoices Through the Aramco SNC Portal

Every invoice you send to Saudi Aramco flows through a single channel: the Supplier Network Communication (SNC) portal. This is Aramco's proprietary vendor management platform, and it governs far more than invoicing. Purchase order acknowledgment, delivery scheduling, payment status inquiries, and all other commercial interactions between Aramco and its suppliers happen here. If you supply goods or services to Aramco, the SNC portal is where your procure-to-pay lifecycle lives.

Before you can submit a single invoice, you need an active SNC account. This account is tied directly to your vendor registration approval, which means you must first qualify under the appropriate supplier category — General Supplier, Small Local Supplier, or another classification that matches your business profile and scope of work. Registration itself is a prerequisite to invoicing; without it, the portal will not accept your submissions. International vendors entering the Aramco supply chain for the first time should factor this registration lead time into their project planning.

The Submission Workflow

Once your Aramco vendor registration is complete and your SNC portal access is active, the invoice submission process follows a structured sequence:

Upload your invoice and supporting documents. You submit the invoice file along with all required attachments — goods receipt confirmations, delivery notes, service entry sheets, or whichever documents apply to your transaction type. Everything goes through the portal in a single submission package.
Automated validation against PO data. The SNC system cross-references your invoice details against the corresponding purchase order stored in Aramco's ERP. It checks line items, quantities, unit prices, currency, tax calculations, and vendor identifiers. Any mismatch between your invoice and the PO triggers a rejection.
Rejection or approval. Invoices that fail validation are returned with specific error codes explaining the discrepancy. These codes tell you exactly what went wrong — whether it is a pricing variance, a quantity mismatch, a missing reference number, or an issue with your supporting documentation. Invoices that pass all validation checks move forward.
Payment processing queue. Approved invoices enter Aramco's payment cycle according to the agreed payment terms on your contract, which typically range from 30 to 90 days depending on the contract type and procurement category. You can track the status of each invoice through the portal, from submission through approval to payment release.

The automated validation step is where most rejections occur, and it is unforgiving. The system performs a literal match against PO data, so even minor discrepancies in unit pricing or item descriptions will cause a rejection. Vendors who have experienced repeated rejections should review their internal processes for transcribing PO details onto invoices — manual data entry errors are the most common root cause.

Meeting Both Aramco and ZATCA E-Invoicing Requirements

Vendors supplying to Saudi Aramco face a compliance challenge that catches many finance teams off guard: every invoice must satisfy two distinct sets of rules at the same time. Saudi Arabia's national FATOORA e-invoicing mandate, administered by the Zakat, Tax and Customs Authority (ZATCA), applies to all B2B transactions in the Kingdom. Aramco's proprietary SNC portal requirements layer additional prescriptive format rules on top of that national standard. Neither system substitutes for the other.

The two frameworks share common ground. Both require vendors to hold a valid VAT registration, display tax identification numbers on invoices, and calculate VAT amounts correctly at the applicable rate. The underlying financial data — line item totals, taxable amounts, VAT breakdowns, and vendor identification details — must be accurate and consistent regardless of which system processes the invoice.

Where they diverge is in format and submission channel. ZATCA's Phase 2 (Integration Phase) mandates that invoices be generated in a structured XML format and transmitted through certified ERP integration directly to the ZATCA platform. Aramco, by contrast, requires submission through its SNC portal using Aramco's own format validation rules, field naming conventions, and supporting document attachments. A ZATCA-compliant e-invoice submitted through the FATOORA platform does not fulfill Aramco's invoice requirements. Vendors who assume their ZATCA setup covers Aramco invoicing will find their invoices rejected or simply unprocessed.

The practical approach is to treat these as two parallel workflows that draw from a single source of truth. Your ERP or accounting system should maintain one authoritative invoice record with correct amounts, tax calculations, and vendor details. From that record, generate the ZATCA-compliant XML for submission to the national platform, and separately prepare the Aramco-formatted invoice for upload through SNC. Keeping both outputs tied to the same underlying data prevents discrepancies that could trigger audits or payment holds from either authority. For a detailed breakdown of ZATCA VAT invoice requirements for Saudi Arabia, including Phase 2 integration timelines and XML field specifications, that national standard serves as the baseline your Aramco invoices must also respect.

International vendors supplying to Aramco from outside Saudi Arabia should assess their ZATCA obligations carefully. If your company holds a Saudi tax registration — whether through a local entity, branch, or tax agent — FATOORA compliance applies to your transactions. If you invoice Aramco purely as a foreign supplier without Saudi tax registration, the ZATCA e-invoicing mandate may not apply directly to you, though Aramco's own SNC portal requirements remain fully in effect regardless of your tax residency status. Confirm your specific obligations with a qualified Saudi tax advisor, as ZATCA's enforcement scope continues to expand.

IKTVA Reporting: How Local Content Scores Affect Your Contracts

Every vendor supplying goods or services to Saudi Aramco must participate in the In-Kingdom Total Value Add (IKTVA) program, a mandatory local content initiative tied directly to Saudi Vision 2030's economic diversification goals. IKTVA is not optional and not cosmetic. Your IKTVA score determines whether you can compete for future Aramco contracts, making it one of the most consequential compliance obligations in your vendor relationship.

The program's impact on Saudi Arabia's industrial base has been substantial. According to Saudi Gazette, Saudi Aramco's IKTVA program has doubled its local procurement content from 35% in 2015 to 70%, with over 200,000 jobs created and more than $280 billion added to Saudi Arabia's GDP. Those numbers reflect the scale of what Aramco expects from its supply chain — and the reporting burden that comes with it.

What You Report: The 8 IKTVA Categories

Each year, vendors must submit an IKTVA report covering eight categories of local content contribution. At a practical level, here is what each category requires:

Workforce localization — The ratio of Saudi nationals to total employees working on Aramco-related projects. You need payroll records, employment contracts, and GOSI registration data to substantiate your numbers.
Local procurement — The percentage of your spending directed to Saudi-based suppliers. Every purchase order, invoice, and payment record for local vendors becomes evidence.
Training and development — Investments in upskilling Saudi employees, documented through training expenditure receipts, course completion records, and program enrollment data.
Technology transfer — Agreements and activities that bring proprietary technology, intellectual property, or technical expertise into Saudi Arabia. Formal technology transfer agreements and milestone reports serve as documentation.
Capital expenditure in Saudi Arabia — Spending on facilities, equipment, and infrastructure within the Kingdom, backed by asset registers and capital investment receipts.
Research and development — R&D activities conducted locally, supported by project documentation and expenditure records.
Exports from Saudi Arabia — Revenue generated by exporting Saudi-manufactured goods or services, documented through export invoices and customs records.
Supplier development — Efforts to develop local supplier capabilities, evidenced through mentorship program records and joint venture documentation.

Each category requires documented evidence, not self-reported estimates.

How Your IKTVA Score Affects Contract Eligibility

Aramco calculates an IKTVA score for every vendor based on their annual report submission. This score feeds directly into the procurement evaluation process. A strong IKTVA score improves your competitiveness when bidding on new work. A weak score does the opposite — vendors with low local content performance have reported being excluded from bid lists, regardless of their pricing or technical capability.

This mechanism means IKTVA is not a parallel compliance exercise you can treat separately from your core Aramco business. It is woven into the commercial relationship itself. Vendors who neglect IKTVA reporting or submit incomplete data risk losing access to one of the world's largest procurement pipelines.

The Documentation Burden Is Year-Round

IKTVA reporting requires third-party verification, which means you cannot assemble your submission from memory at year-end. Vendors must maintain detailed records continuously throughout the year:

Local procurement invoices with supplier registration details
Payroll data showing Saudi employee headcounts and compensation
Training expenditure receipts tied to specific development programs
Technology transfer agreements with progress documentation
Capital expenditure records for Saudi-based assets

This transforms invoice and financial document management from a transactional activity into a continuous compliance requirement. Every local procurement invoice you process, every payroll cycle you run, and every training receipt you file feeds into your IKTVA score — and by extension, into your ability to win future Aramco work.

Prepare for Tightening Requirements

Aramco's stated target is 75% local content by 2030, up from the current 70%. As that deadline approaches, IKTVA scoring thresholds will likely tighten, and the documentation standards applied during third-party verification will grow more rigorous. Vendors who build disciplined record-keeping practices now will be better positioned than those scrambling to meet higher bars later.

Why Aramco Invoices Get Rejected and How to Prevent It

Most Aramco invoice rejections trace back to five recurring issues. The format rules and document requirements are covered in detail earlier in this guide. Here, the focus is on the specific failure modes that trigger each rejection and the prevention steps to build into your workflow.

Supplier Name Mismatch

The most frequent rejection cause, and the hardest for international vendors to prevent. Arabic-to-English transliteration creates subtle variations that Aramco's matching logic treats as entirely different entities. A company registered as "Al-Jazeera" in one system might appear as "Al Jazirah" or "Aljazeera" in another. Abbreviations ("Co." vs. "Company") and legal entity suffix variations cause the same problem.

Before issuing any invoice, pull your current Supplier Master File entry from the SNC portal and verify that the supplier name on your invoice matches it character for character. For bilingual invoices, confirm that both the Arabic and English renderings align with your Commercial Registration and contract records.

Missing or Incorrect PO Reference

Three common errors: entering the wrong PO number, omitting the required prefix (65 for materials, 45 for services), or referencing a PO that has already been fully invoiced or closed. Each one routes the invoice into a dead end.

Cross-reference every PO number against the SNC portal before submission. Verify that the PO status is "open" and that remaining value covers your invoice amount. Include PO prefixes exactly as they appear in the system.

Missing Supporting Documents

The subtler version of this error is not a missing document but a mismatched one. The SES or GR may be attached, but if it references different PO line items than the invoice does, the system flags a discrepancy and rejects the submission.

Build a pre-submission checklist that maps each invoice line item to its corresponding SES or GR. Confirm that PO line item numbers match across all documents before submitting.

Invoice Total Discrepancy

Any difference between the numeric total and the total expressed in words triggers rejection, even a rounding discrepancy of a few halalas. Separately, an invoice total that exceeds the remaining value on the referenced PO will also be rejected outright. Use dual-entry verification: have one person enter the numeric amount and a second person independently write it in words, then compare. Before submission, check the remaining PO balance in the SNC portal.

Late Submission

Invoices submitted more than six months after the SES or GR date are rejected. Recovering payment for late submissions requires a separate escalation process that can add months to your timeline. Track SES and GR dates in a centralized log and set an internal 90-day target, which gives your team a three-month buffer for document preparation, review, and any corrections if Aramco returns the submission.

Building Automated Pre-Submission Validation

When your organization processes a high volume of Aramco invoices, manually checking every field against PO data, name registrations, and supporting documents becomes a bottleneck that introduces the very errors you are trying to prevent. Tired eyes miss transliteration discrepancies. Copy-paste errors corrupt PO references. Totals go unverified under deadline pressure.

This is where automated extraction and validation changes the workflow. Tools that can automate invoice data extraction and validation allow you to process purchase orders, SES documents, and goods receipts alongside your invoices, extracting the relevant field data into structured output. You can then programmatically cross-reference supplier names against your CR registration, verify PO numbers and remaining balances, confirm that line items on supporting documents match the invoice, and flag total discrepancies before anything reaches the SNC portal. For vendors dealing with Arabic and English documentation, automated extraction with multilingual support catches the transliteration mismatches that manual review routinely misses.

The result is a repeatable validation layer that sits between your invoice preparation and Aramco submission, catching the five rejection causes outlined above before they cost you payment cycles.