For UAE retailers, e-invoicing creates a practical challenge that is different from the one faced by a typical B2B service company.

A retail business may process hundreds or thousands of consumer transactions through its point-of-sale system every day while also selling to companies, government entities, resellers, contractors or other business customers.

Those transactions do not all receive the same treatment under the current UAE Electronic Invoicing System.

The key distinction is not whether the sale passes through a POS terminal, whether the customer pays by cash or card, or whether the retailer prints a receipt.

Under the current UAE framework, transactions with consumers who are natural persons not conducting business are outside the mandatory Electronic Invoicing System. B2B and B2G business transactions, however, are generally within scope unless a specific exclusion applies.

For retailers with a mixture of consumer and business customers, this means the real implementation challenge is identifying the transaction correctly and ensuring that the POS, accounting system and e-invoicing process can handle the appropriate workflow.

This guide explains what retail and POS businesses should review before UAE e-invoicing becomes mandatory for their applicable transactions.

Are Retail Businesses Subject to UAE E-Invoicing?

A retail business is not automatically excluded from UAE e-invoicing simply because it operates physical shops or uses a POS system.

The applicable treatment depends on the type of transaction.

The Ministry of Finance’s Electronic Invoicing Guidelines distinguish transactions according to the nature of the supplier and buyer.

Under the current framework:

Transaction	Current e-invoicing treatment
Business selling to another business	Generally in scope
Business selling to a government entity	Generally in scope
Business selling to an individual consumer not conducting business	Outside the current mandatory scope
Government entity selling to a business	Generally in scope
Transactions involving a consumer not conducting business	Outside the current mandatory scope

The Ministry of Finance Guidelines state that supplies to or from natural persons who are not conducting business are outside the scope of Electronic Invoicing and that there is no obligation to issue an Electronic Invoice for a supply made to a consumer.

Ministerial Decision No. 244 of 2025 also provides that Business-to-Consumer transactions are not subject to the Electronic Invoicing System until a future date determined by ministerial decision. A person engaged exclusively in B2C transactions is likewise outside mandatory implementation until that future determination.

This distinction is particularly important for retailers because the same legal entity may process both excluded B2C transactions and in-scope business transactions.

Does This Mean Ordinary Retail Sales Do Not Need E-Invoices?

Under the current framework, an ordinary sale to an individual consumer who is not conducting business does not require an Electronic Invoice under the UAE Electronic Invoicing System.

For example, consider a supermarket selling groceries to an individual for personal use.

That sale is a B2C transaction and is currently outside mandatory Electronic Invoicing.

The same principle can apply to ordinary consumer purchases in businesses such as:

• Fashion retailers.
• Electronics stores.
• Supermarkets.
• Furniture shops.
• Pharmacies, subject to the applicable tax treatment.
• Automotive retailers.
• Building-material stores.
• Consumer e-commerce businesses.
• Other retail outlets.

However, being outside the Electronic Invoicing System does not mean that VAT invoicing requirements disappear.

VAT and e-invoicing are related but separate regulatory frameworks.

A VAT-registered retailer must continue to comply with the applicable VAT rules for tax invoices and its accounting records.

POS Receipt vs E-Invoice: What Is the Difference?

Retailers should avoid treating a POS receipt and a UAE Electronic Invoice as the same document.

A conventional POS receipt is normally designed for the customer to read.

A UAE Electronic Invoice is structured invoice data issued, exchanged and processed through the Electronic Invoicing System.

The Ministry of Finance makes clear that unstructured documents such as PDFs, scanned documents and other ordinary digital invoice formats do not themselves constitute Electronic Invoices.

The same principle applies to a normal POS printout.

A receipt printed from a cash register is not converted into a UAE Electronic Invoice simply because it contains:

• A receipt number.
• The retailer’s VAT TRN.
• Product descriptions.
• VAT.
• The total amount.
• A QR code or barcode.

Where a transaction falls within Electronic Invoicing, the applicable structured invoice process must be followed.

Where the transaction is B2C and currently outside that system, the retailer still needs to consider the separate VAT invoicing requirements.

Can a POS Receipt Be a Simplified VAT Tax Invoice?

Potentially, yes, where the relevant VAT conditions are satisfied.

Under Article 59 of the UAE VAT Executive Regulation, a simplified Tax Invoice may be issued where:

• The recipient is not registered for VAT; or
• The recipient is registered for VAT and the consideration for the supply does not exceed AED 10,000.

A simplified Tax Invoice must contain specified information including:

• The words “Tax Invoice”.
• The supplier’s name, address and TRN.
• The date of issue.
• A description of the goods or services.
• The total consideration.
• The VAT amount charged.

Therefore, a retail POS receipt may potentially perform the role of a simplified Tax Invoice if the applicable VAT conditions and information requirements are satisfied.

That is a VAT question.

It should not be confused with whether a transaction requires a structured Electronic Invoice under the separate e-invoicing framework.

What Happens When a Retail Customer Is a Business?

This is where the retail implementation becomes more important.

Consider a building-material retailer.

During the day, it sells to:

• Homeowners buying materials for personal renovations.
• Construction companies purchasing materials for projects.
• Independent contractors conducting business.
• Government departments.
• Other trading companies.

These customers may arrive at the same counter and pay through the same POS terminal.

But the transactions may not have the same e-invoicing treatment.

A sale to an individual consumer for personal use is currently outside Electronic Invoicing.

A sale to a company purchasing goods in the course of its business is generally a B2B Business Transaction and can fall within the Electronic Invoicing System.

A sale to a government entity can also be within scope.

The POS process therefore needs a practical way to distinguish relevant business transactions from ordinary consumer sales.

Example: One Retail Store, Three Different Customers

Consider a UAE electronics retailer.

Customer 1: Individual consumer

An individual buys a television for home use and pays by credit card.

This is an ordinary B2C transaction and is currently outside mandatory Electronic Invoicing.

The retailer should continue to meet its applicable VAT invoicing and record-keeping requirements.

Customer 2: UAE company

A company purchases five laptops for its employees and asks the retailer to invoice the business.

This is a business transaction.

If the retailer is subject to mandatory Electronic Invoicing under its applicable implementation phase, the transaction should be assessed and processed under the e-invoicing requirements.

Customer 3: Government entity

A government department purchases equipment from the retailer.

Goods and services supplied to Government Entities are generally within the Electronic Invoicing scope, subject to the applicable rules and exclusions.

The fact that all three transactions were entered through the same POS system does not determine their treatment.

The nature of the buyer and transaction matters more than the sales channel.

What If an Individual Is Buying for a Business?

Retailers should also be careful not to assume that every individual standing at a checkout counter is necessarily acting as a consumer.

The Ministry of Finance’s current guidance excludes supplies to natural persons who are not in Business.

A natural person can also conduct a business.

For example, an individual may purchase equipment in the course of operating a business rather than for personal use.

The facts of the transaction therefore matter.

Retailers do not need to turn every consumer checkout into an unnecessarily complicated compliance process, but they should establish a suitable workflow for customers who identify themselves as purchasing in a business capacity.

That workflow may involve collecting the appropriate business and tax information before the invoice is finalized.

Retailers With Both B2C and B2B Sales Need a Split Workflow

For a mixed retail business, one of the most useful implementation concepts is a transaction split.

The workflow might operate like this:

Consumer transaction

POS identifies the transaction as B2C.

↓

Normal retail/VAT invoice or receipt process applies.

↓

No UAE Electronic Invoice is required under the current B2C exclusion.

Business transaction

POS identifies that the purchaser is buying as a business.

↓

Required business-customer information is captured or retrieved.

↓

Transaction data passes into the applicable accounting/e-invoicing workflow.

↓

Structured Electronic Invoice is processed through the appointed ASP where the supplier is subject to mandatory implementation.

The precise technical architecture will vary between businesses.

The important requirement is that the system can distinguish transactions reliably instead of treating every POS sale in exactly the same way.

What Customer Information May Need to Change at the POS?

Consumer retail often works with little or no customer master data.

A shopper may purchase goods without creating an account.

B2B electronic invoicing is different.

The business needs sufficient information to correctly identify the buyer and populate the applicable structured invoice fields.

Depending on the transaction and invoice type, this can require information beyond what a conventional retail receipt captures.

Retailers should therefore assess whether their systems can maintain appropriate information such as:

• Legal customer name.
• Business address.
• Relevant tax identifiers.
• Electronic identifiers required by the framework.
• Country and location information.
• Other transaction-specific information required by the applicable specification.

The exact mandatory fields should be assessed against the current UAE electronic invoice specification and the type of transaction.

Do not collect all this information from every shopper

That would usually create unnecessary friction.

Instead, design a process that identifies when a sale is a business transaction.

For example, the POS may allow staff to select:

Individual / Consumer

or

Business / Government Customer

Where a business customer is selected, the system can then retrieve an existing business account or request the required information.

Business Customer Accounts Become More Important

Retailers with frequent corporate customers should consider maintaining reliable customer master records.

For example, a building-material supplier may regularly sell to the same:

• Construction companies.
• Maintenance businesses.
• Property-management companies.
• Interior-design firms.
• Contractors.

Rather than entering customer details manually at every sale, the POS can potentially retrieve the approved business record.

This reduces risks such as:

• Incorrect legal names.
• Wrong VAT TRNs.
• Duplicate customer accounts.
• Incomplete addresses.
• Typographical errors.
• Transactions assigned to the wrong customer.

The quality of that customer data becomes an important part of e-invoicing readiness.

Retail businesses with wholesale or distribution activities should also review MKCA’s E-Invoicing for Trading Companies in the UAE because inventory, B2B sales and customer-data issues often overlap.

Does Payment Method Affect E-Invoicing?

No general distinction should be made simply because a customer pays:

• Cash.
• Debit card.
• Credit card.
• Bank transfer.
• Digital wallet.
• Another payment method.

A cash B2B purchase does not automatically become a consumer transaction.

Likewise, a card payment does not automatically create an Electronic Invoice requirement.

The relevant question is the underlying transaction and the status in which the buyer is acting.

This is an important configuration point for POS systems because payment method and customer classification should not be treated as the same field.

What About E-Commerce and Online Retail?

The same scope principles apply to online retail.

Selling through:

• A website.
• Mobile app.
• Online marketplace.
• Physical POS.
• Telephone order.
• Click-and-collect system.

does not by itself determine whether the transaction is B2B or B2C.

A retailer operating an e-commerce platform should assess whether its checkout process can distinguish:

• Consumer customers.
• Business customers.
• Government customers where relevant.

For business customers, the online checkout or account-registration process may need to collect additional invoicing information.

Avoid forcing B2B data into free-text checkout fields

A company legal name or TRN entered into a delivery-notes box is difficult to validate and automate.

Where B2B online sales are material, structured customer fields are more reliable.

How Should Retailers Handle Returns and Refunds?

Returns are a major retail workflow and should be included in e-invoicing implementation testing.

A retailer may need to deal with:

• Full returns.
• Partial returns.
• Exchanges.
• Price reductions.
• Incorrectly billed items.
• Cancelled transactions.
• Refunds to the original payment method.
• Store credit.

For ordinary consumer transactions outside the current Electronic Invoicing scope, the retailer should continue to apply the relevant VAT and accounting requirements.

For an in-scope B2B transaction that was processed through the Electronic Invoicing System, an adjustment may require the appropriate Electronic Credit Note process.

The POS and accounting system therefore need to preserve a reliable link between:

• Original sale.
• Original invoice.
• Returned item.
• Refund.
• Credit note.
• Accounting entry.

Example: Business customer returns part of an order

A company purchases ten office chairs from a furniture retailer through a B2B transaction.

The relevant Electronic Invoice is issued.

The company later returns two chairs.

The retailer should not simply delete or overwrite the original invoiced transaction.

The adjustment should follow the applicable electronic credit-note, VAT and accounting process.

This needs to be tested before go-live because ordinary POS refund functionality may not automatically create the required structured e-invoicing adjustment.

Exchanges Need Particular Attention

Retail systems often process exchanges as:

1. Return old item.
2. Apply value against replacement.
3. Collect or refund the difference.

From a customer-service perspective, this can feel like one transaction.

From an accounting and invoicing perspective, the business may need to identify the underlying return and new supply correctly.

The retailer should test how its POS, ERP and ASP handle this scenario, especially for business customers.

Discounts and Promotions Should Also Be Tested

Retail businesses frequently use:

• Promotional discounts.
• Loyalty discounts.
• Coupon codes.
• Buy-one-get-one offers.
• Bundle pricing.
• Employee discounts.
• Store credits.

The existence of a promotion does not remove the need for accurate accounting and VAT treatment.

Before e-invoicing goes live, retailers should test representative promotions to confirm that:

• Invoice-line amounts are correct.
• Discounts are represented consistently.
• VAT is calculated correctly.
• Document totals reconcile.
• The structured invoice matches the accounting records.

Do not wait until a large promotional campaign is running to discover that an invoice integration cannot correctly process the pricing logic.

POS and Inventory Data Need to Reconcile

Retail systems frequently connect multiple applications.

A transaction may pass through:

POS → Inventory → ERP / Accounting → E-Invoicing Process

If those systems do not use consistent identifiers or values, differences can arise.

Examples include:

• POS uses one SKU while ERP uses another.
• VAT treatment differs between systems.
• Discounts are posted differently.
• Returns appear in POS but not accounting.
• Sales totals are grouped differently.
• Customer records are duplicated.

The retailer should document the source of truth for each important data element.

For example:

Data	Primary source
Product SKU	Inventory system
Product description	Product master
Selling price	POS
VAT classification	ERP / approved tax master
Customer legal data	Customer master
Payment	POS / payment gateway
Accounting entry	ERP
E-invoice status	ASP / integrated monitoring

The actual design depends on the retailer’s technology environment.

Do You Need to Replace Your POS System?

Not automatically.

UAE e-invoicing should not be treated as an automatic instruction to replace every POS platform.

A retailer should first determine whether the existing system can:

• Identify the transaction type.
• Capture or retrieve the required business-customer data.
• Provide reliable sales-line information.
• Maintain correct VAT treatment.
• Connect to the accounting environment.
• Exchange the necessary data with the e-invoicing workflow.
• Handle returns and credit notes.
• Support reconciliation.

If those requirements can be met through configuration or integration, a complete POS replacement may not be necessary.

A replacement may become reasonable where the existing system already has serious limitations in areas such as data quality, integration, VAT configuration, multi-branch control or accounting reconciliation.

The decision should be based on actual system gaps rather than a general assumption that e-invoicing requires new POS hardware or software.

Multi-Branch Retailers Need Additional Controls

Retail chains should pay particular attention to consistency across branches.

One branch should not classify the same type of customer differently from another.

Review:

• Customer classification.
• VAT codes.
• Product data.
• Invoice numbering.
• Return procedures.
• User permissions.
• Business-customer onboarding.
• Daily reconciliation.
• System updates.

Central master-data control can reduce branch-level inconsistencies.

Example: Corporate customer visits different branches

A construction company regularly buys materials from several branches of the same retailer.

Branch A creates:

ABC Construction LLC

Branch B creates:

ABC Const.

Branch C records the transaction as an anonymous cash customer.

That creates fragmented transaction history and can complicate B2B e-invoicing.

A centralized business-customer account can reduce that risk.

What About Retailers That Sell Only to Consumers?

This is an important distinction.

Under the current implementation decision, a person engaged exclusively in B2C transactions is not subject to mandatory Electronic Invoicing until a future date determined by the Minister.

A genuinely consumer-only retailer should therefore not assume that the current B2B/B2G mandatory implementation dates automatically require it to convert every retail receipt into an e-invoice.

However, the business should monitor Ministry of Finance announcements.

The B2C position can change through a future decision.

The company should also continue complying with existing VAT, accounting and record-keeping obligations.

What About a Retailer With Only a Small Number of B2B Sales?

The fact that B2B sales represent a small percentage of total transactions does not automatically convert them into B2C transactions.

A retailer may generate 99% of its sales from individual consumers but still have business customers.

Those business transactions should be identified and assessed under the Electronic Invoicing framework.

The retailer should therefore avoid assuming:

“We are mainly retail, so e-invoicing does not apply to us.”

A better question is:

“Do we conduct any in-scope Business Transactions, and if so, when does the Electronic Invoicing implementation framework apply to us?”

When Do Retail Businesses Need to Implement E-Invoicing?

The current mandatory implementation phases apply to Persons subject to the Electronic Invoicing System.

Under the framework, businesses with revenue equal to or exceeding AED 50 million fall within the first mandatory implementation phase, with the amended ASP appointment deadline of 30 October 2026 and mandatory implementation from 1 January 2027.

Businesses subject to the system with revenue below AED 50 million have a later implementation phase, including an ASP appointment deadline of 31 March 2027 and mandatory implementation from 1 July 2027.

The current B2C exclusion must be considered alongside those dates.

A business engaged exclusively in B2C transactions is currently outside mandatory Electronic Invoicing until a later decision.

Retailers with mixed B2C and business transactions should therefore assess their circumstances rather than applying the B2C exclusion to the entire business automatically.

Retail and POS E-Invoicing Readiness Checklist

Before implementation, review the following areas.

Transaction Scope

• Do we know which transactions are B2C?
• Do we process B2B sales?
• Do we sell to government entities?
• Do individuals sometimes buy in a business capacity?
• Can the POS distinguish those transaction types?

Customer Data

• Can business customers be created as structured customer accounts?
• Are legal names accurate?
• Are duplicate customer records controlled?
• Can applicable tax identifiers be maintained?
• Can required e-invoicing identifiers be provided?

POS Data

• Are product descriptions consistent?
• Are quantities correctly captured?
• Are discounts structured?
• Are VAT codes correct?
• Are transaction dates reliable?
• Can original sales be linked to returns?

Integration

• How does POS data reach accounting?
• Which system owns the customer record?
• Which system owns VAT classification?
• How will business transactions reach the ASP?
• How will e-invoice status return to finance users?

Exceptions

• Can failed transactions be identified?
• Can incorrect customer information be corrected?
• Can returned B2B items generate the appropriate adjustment?
• Have exchanges been tested?
• Have partial refunds been tested?

Reconciliation

• Can POS sales be reconciled to accounting?
• Can accounting invoices be reconciled to e-invoice activity?
• Are failed or unprocessed B2B invoices visible?
• Can branch totals be reconciled centrally?

If several of these questions cannot be answered, the retailer has an implementation gap even if its existing POS works well for ordinary consumer sales.

For a wider readiness process, review MKCA’s guide to preparing your business for e-invoicing in the UAE.

What Should Retailers Test Before Go-Live?

Testing should reflect actual store activity.

A practical test plan could include:

Scenario	What to verify
Normal consumer sale	Correct B2C treatment
B2B sale at POS	Correct business-customer workflow
Government customer	Correct transaction classification
Cash B2B purchase	Payment method does not cause misclassification
Corporate card purchase	Buyer is identified correctly
Business customer not in master data	Customer onboarding works
Full B2B return	Appropriate adjustment process
Partial B2B return	Credit and totals reconcile
Exchange	Return and new supply handled correctly
Discount	VAT and totals remain accurate
Multi-line order	Line data passes correctly
Foreign-currency scenario, where applicable	Currency data is handled correctly
Failed transmission	Finance can identify and resolve the exception

The objective is not simply to prove that one invoice can be transmitted.

It is to prove that normal retail exceptions can be handled without losing accounting control.

Common E-Invoicing Mistakes for Retail and POS Businesses

Mistake 1: Assuming all POS transactions are B2C

The sales channel does not determine the buyer’s status.

A business can purchase goods at the same counter as a consumer.

Mistake 2: Trying to e-invoice every consumer transaction immediately

Under the current framework, ordinary B2C transactions are outside mandatory Electronic Invoicing.

Do not create unnecessary implementation complexity by treating every consumer receipt as an in-scope e-invoice without a regulatory basis.

Mistake 3: Assuming B2C exclusion removes VAT obligations

It does not.

Retailers still need to comply with applicable VAT tax-invoice and record-keeping rules.

Mistake 4: Using payment method to classify transactions

Cash does not mean consumer.

Corporate card does not automatically prove the correct legal buyer.

Classify the underlying customer and transaction.

Mistake 5: Collecting business details only after checkout

If a transaction needs a business invoice, obtaining the required information after the POS sale is finalized can create manual corrections.

Design the workflow earlier in the checkout process.

Mistake 6: Ignoring returns

Returns and exchanges are routine in retail and must be included in implementation testing.

Mistake 7: Replacing the POS unnecessarily

First determine whether configuration and integration can solve the problem.

Mistake 8: Failing to reconcile POS and e-invoicing activity

An invoice can exist in one system but fail elsewhere.

Finance needs an exception and reconciliation process.

Practical Implementation Approach for a UAE Retailer

A sensible implementation can follow seven stages.

Step 1: Map your sales channels

List:

• Stores.
• Websites.
• Apps.
• Marketplaces.
• Wholesale counters.
• Corporate sales desks.

Step 2: Identify transaction types

Determine which channels generate:

• B2C.
• B2B.
• B2G.
• Mixed transactions.

Step 3: Review customer data

Identify where business-customer information is stored and whether it is complete.

Step 4: Review POS and VAT configuration

Check products, tax codes, discounts, returns and invoice logic.

Step 5: Design the B2B routing process

Determine how an in-scope sale will move from POS into the e-invoicing environment.

Step 6: Test realistic retail transactions

Include business sales, returns, exchanges and errors.

Step 7: Train store and finance teams

Retail employees do not need to become e-invoicing specialists.

They do need to know when a customer should be treated as a business customer and what information must be collected.

Finance teams need to understand the downstream invoicing, exception and reconciliation process.

Frequently Asked Questions About Retail E-Invoicing in the UAE

Do UAE retailers need to issue e-invoices to every customer?

No.

Under the current framework, supplies to natural-person consumers who are not conducting business are outside mandatory Electronic Invoicing.

B2B and B2G transactions are treated differently.

Are B2C transactions included in UAE e-invoicing?

Not under the current mandatory framework.

Ministerial Decision No. 244 of 2025 provides that B2C transactions are not subject to the Electronic Invoicing System until a future date determined by ministerial decision.

Is a POS receipt an e-invoice?

Not merely because it is generated electronically.

A UAE Electronic Invoice is structured invoice data processed through the Electronic Invoicing System.

A standard POS receipt is a different document.

Do retailers still need to issue VAT invoices to consumers?

Where VAT legislation requires a Tax Invoice, the applicable VAT requirements continue to apply.

The B2C e-invoicing exclusion does not remove existing VAT obligations.

Can a retail POS receipt be a simplified Tax Invoice?

It can potentially qualify if the relevant conditions in the VAT Executive Regulation are satisfied and the receipt includes the required information.

Article 59 permits simplified Tax Invoices in specified circumstances, including supplies to non-registered recipients and supplies not exceeding AED 10,000 where the recipient is VAT registered.

What if a company employee buys goods from our store?

The retailer should consider who the actual purchaser is and the capacity in which the person is acting.

If the purchase is a business transaction, it should not automatically be treated as B2C merely because an individual employee is physically present at the checkout.

Does paying cash make the transaction B2C?

No.

Payment method does not determine whether the buyer is acting as a consumer or business.

Does an online sale count as B2C automatically?

No.

An online customer may be a consumer or business.

The channel does not determine the transaction type.

Do we need to replace our POS system?

Not necessarily.

First assess whether the current POS can identify transaction types, provide the required data and integrate with the accounting and e-invoicing environment.

Should a retailer with mostly consumer sales prepare now?

If the business also conducts in-scope business transactions, those transactions should be assessed against the applicable implementation rules.

Consumer-only retailers should continue monitoring Ministry of Finance announcements because B2C implementation can be introduced at a future date.

How MKCA Can Help Retail and POS Businesses Prepare for E-Invoicing

For retailers, e-invoicing readiness is not simply a question of connecting a POS system to another application.

The business first needs to understand which transactions are in scope and how information moves from the checkout process into accounting.

MKCA can support businesses in areas such as:

• E-invoicing scope assessment.
• B2B and B2C transaction mapping.
• POS and accounting-process review.
• Customer-master-data assessment.
• VAT process review.
• Invoice and credit-note workflow assessment.
• Data-readiness review.
• ASP and implementation preparation.
• Testing and reconciliation planning.
• Finance-team readiness.

Retailers with substantial wholesale or business-customer activity can also review MKCA’s E-Invoicing for Trading Companies in the UAE.

Businesses preparing their retail systems and finance processes can explore MKCA’s E-Invoicing Services in the UAE.

Conclusion

UAE e-invoicing does not currently mean that every receipt generated by every retail POS must become an Electronic Invoice.

Ordinary B2C transactions with consumers who are not conducting business are outside the current mandatory Electronic Invoicing scope.

The challenge arises when the same retailer also sells to businesses or government entities.

Retail and POS businesses therefore need a reliable way to distinguish transaction types, maintain business-customer data, route in-scope transactions into the e-invoicing process and manage returns, credit notes and reconciliation correctly.

The right preparation does not start with replacing the POS.

It starts by mapping customers and transactions, identifying where business sales occur, reviewing data and VAT configuration, and testing how those sales will move through the complete invoicing workflow.