A fiscal device CRM integration connects a physical Armenian fiscal device with Lua CRM, so your team can send sales data to Armenian tax authorities and print compliant fiscal receipts from the same system where you manage customers and sales. For shops, service companies and other businesses in Armenia, the fiscal receipt is not optional paperwork: it is part of every eligible sale. When the CRM and the fiscal device live in separate worlds, staff type the same sale twice, receipts are forgotten during busy hours and managers cannot easily match what was sold with what was reported. This guide explains what the Armenian Fiscal Device integration is, what the Lua CRM integrations page says about it, what the official Armenian sources say about cash register receipts and how to prepare your process before you connect it.
Key takeaways
- The Armenian Fiscal Device integration lets you send sales data to Armenian tax authorities and print compliant fiscal receipts from Lua CRM.
- The Lua CRM integrations page lists it in the Fiscal & Compliance category, which connects physical fiscal devices.
- According to the State Revenue Committee, cash registers are mandatory for transactions involving cash or payment cards, including prepayments and partial payments.
- A fiscal device must be registered with the tax authority, which links the device to the commercial software the business uses.
- Follow the instructions in Lua CRM or contact the Lua CRM team to connect your device.
What is a fiscal device CRM integration?
A fiscal device, often called a cash register machine or HDM (ՀԴՄ) in Armenia, is the device that records eligible sales for the tax authority and prints the fiscal receipt that the customer receives. A CRM integration connects that device with your customer and sales software, so the sale you already recorded in the CRM can be reported and the receipt printed without retyping the details on a separate machine.
The Lua CRM integrations page lists a dedicated Fiscal & Compliance category. The category is described as a way to connect physical fiscal devices to report sales to Armenian tax authorities and print compliant fiscal receipts. The Armenian Fiscal Device entry is titled fiscal reporting and receipt printing, and its description says it sends sales data to Armenian tax authorities and prints compliant fiscal receipts. The integrations page does not list device models, setup steps or configuration options, so treat the instructions inside Lua CRM and the Lua CRM team as the source for those details.
What official sources say about fiscal receipts in Armenia
The rules come from Armenian tax legislation, and the State Revenue Committee (SRC) is the authority that explains and enforces them. In its key information on cash register operation rules, the SRC states that the use of cash registers is mandatory when conducting transactions involving cash or payment cards, including receiving prepayments or partial payments, for the sale of goods, providing services to the public or performing work.
The same SRC notice lists three basic rules: users must operate a cash register that meets the technical requirements set by government decision; they must provide a cash register receipt when receiving payment from a buyer for goods or from a customer for services; and the details printed on the receipt must accurately reflect the transaction and be easily readable. The SRC also notes that the most common violation is failing to provide a receipt, including one for an advance payment, and that violations are subject to fines.
Registration is the other official step. The national services gateway explains how to apply to register a cash register (HDM): after purchasing a cash register, a business registers it in the tax authority electronic reporting system in order to integrate the device with commercial software and ensure data exchange between the business and the tax authority. The service is provided by the SRC. Rules can change, so always check the current requirements with the SRC or your accountant.
Why connect fiscal receipts to your CRM
One record of the sale
When the sale is created in the CRM and the receipt is printed through the integration, the customer, the products or services and the fiscal receipt belong to the same story. Managers no longer compare a notebook, a cash register report and a CRM export to understand one day of sales.
Fewer forgotten receipts
Busy moments are when receipts are most often skipped. A process where the receipt is part of completing the sale in the CRM makes the correct step the easy step, especially for prepayments, which the SRC specifically mentions.
Less double entry
Typing the same amount and items into two systems wastes time and creates mistakes. Reducing manual entry also makes the receipt details more likely to match the transaction, which the SRC rules require.
Clearer reporting for owners and accountants
When sales and receipts are connected to customers, owners can see revenue by customer, product or team, and accountants get a cleaner picture of what was sold. For broader advice on keeping numbers under control, read our article on financial management for small businesses.
Who benefits most
| Business type | Typical situation | How the integration helps |
|---|---|---|
| Retail shops | Many small sales during the day, often by card | Sales recorded in the CRM can be reported and receipts printed without a second system |
| Service companies | Customers pay for completed work or visits | The receipt is tied to the customer and the service in one record |
| Businesses taking deposits | Prepayments and partial payments before delivery | Deposits follow the same receipt process as final payments |
| Teams with several cashiers | Different people close sales on different shifts | One shared process instead of personal habits |
| Owners and accountants | Need to match sales, payments and receipts | One place to review what was sold and reported |
How to prepare and connect the integration
The integrations page describes what the integration does but not the technical setup, so the steps below focus on preparation and on the official requirements you control.
- Check your obligations. Confirm with the SRC guidance or your accountant which of your sales require a fiscal receipt, including prepayments and partial payments.
- Prepare a registered fiscal device. Make sure the device meets the technical requirements and is registered with the tax authority, as described on the national services gateway.
- Clean up your products and services in the CRM. Use clear names and correct prices, because receipt details should accurately reflect the transaction.
- Decide when a receipt is printed. Agree on the moment in your sales process when the receipt is issued, for example when a payment is received, and who is responsible on each shift.
- Connect the device. Open the integrations area in Lua CRM and follow the Armenian Fiscal Device instructions there, or contact the Lua CRM team for help with your specific device.
- Test before going live. Run a few test sales with your accountant or a responsible manager and check that the printed receipts look correct.
- Train the team and review. Show every cashier the process, then review receipts against sales after the first week.
Fitting fiscal receipts into your sales workflow
The fiscal step works best as part of a complete flow from lead to payment. A customer inquiry becomes a deal, the deal becomes an order or a booked service, payment is received and the receipt is issued. If you collect online payments, the PayLink CRM integration covers sending payment links; the fiscal device integration covers fiscal reporting and receipt printing. Ask the Lua CRM team how the two work together for your case rather than assuming they are linked automatically.
Automation can support the human steps around the receipt, such as tasks for unpaid orders or reminders to close a sale at the end of the day. Our guide to CRM automation explains how to start with simple rules. Retailers can also combine receipt discipline with customer follow-up ideas from our retail store CRM guide.
Common mistakes to avoid
- Treating the integration as legal advice. The integration helps you report and print receipts; your obligations still come from the law and the SRC.
- Skipping receipts for prepayments. The SRC names missing receipts for advance payments as a common violation.
- Messy product names and prices. Unclear data in the CRM leads to unclear receipts.
- No owner for the process. Someone must check daily that sales and receipts match.
- Going live without a test. A few test sales prevent surprises on a busy day.