---
title: "Comment by Steven Mock on \"Implementing ZATCA E-Invoicing in a Saudi Property Management SaaS\" | Hashnode"
description: "This is a good reminder that property software is never just rent collection — the tax rules change with the type of unit, and getting that wrong is expensive."
url: "https://hashnode.com/posts/implementing-zatca-e-invoicing-in-a-saudi-property-management-saas/69f38013909e64ad07f87429/comment/6aeec05e5cb054c02903282e"
---

[Discussion](https://hashnode.com/posts/implementing-zatca-e-invoicing-in-a-saudi-property-management-saas/69f38013909e64ad07f87429)

Comment [Implementing ZATCA E-Invoicing in a Saudi Property Management SaaS](https://hashnode.com/posts/implementing-zatca-e-invoicing-in-a-saudi-property-management-saas/69f38013909e64ad07f87429)

[Steven Mock](https://hashnode.com/@stevenmock)

[6d ago](https://hashnode.com/posts/implementing-zatca-e-invoicing-in-a-saudi-property-management-saas/69f38013909e64ad07f87429/comment/6aeec05e5cb054c02903282e)

This is a good reminder that property software is never just rent collection — the tax rules change with the type of unit, and getting that wrong is expensive. The mixed-use point stood out to me: residential exempt, commercial at 15%, and sales under a different regime altogether means the system has to know what each unit is before it can invoice correctly. Storing that as a unit field, rather than trying to fix invoices after the fact, is the right call. Compliance work like this is invisible when it works, and very visible when it doesn't.