Design stage: there is no released app yet. This site separates what exists in the repository from what is planned. See status

Taxes, regions and compliance

Compliance themes

Compliance themes that matter by industry and region. Themes to verify, never claims of compliance.

Status labels: Built in the repository (checked files or tested library code; not a product you can run yet) Designed in a document, no code yet Planned: listed in the catalog, not built Not decided Not in the catalog yet (a gap) No claim made

Where does “What Simca does not claim” fit in Simca, in particular regarding buyers asking for attestations?

No claim C0202

The site claims no PCI, SOC 2, HIPAA, GDPR or EMV compliance and no audit or certification of any kind. Plan for: buyers asking for attestations; procurement forms; marketing temptation. No claim is made.

Open this answer on its own page

Where does “Payment-card rules” fit in Simca, thinking about provider responsibilities?

Designed C0203

Card acceptance has its own industry rules. The README's approach (phone Tap to Pay via a provider, no card scanning, no OCR) is designed to keep card data away from Simca. Plan for: provider responsibilities; receipts with card digits; manual entry. It is designed in a document and no code exists.

Open this answer on its own page

Which edge cases come up around “Tax documents”, with a focus on numbering?

Planned C0204

Receipts, invoices and credit notes that meet local rules. Only Peru has depth in the catalog. Plan for: numbering; cancellation; retention. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

What should owners check about “Data protection”, especially around consent?

Planned C0205

Laws about personal data differ by country. For Peru the catalog's LEGAL module plans: access, rectification, cancellation and objection requests handled offline; erasure that restricts retained tax data instead of deleting it; a personal-data inventory per element; income treated as sensitive data; breach-notification guidance; and a statement that the company holds no customer data. These are planned and the reading awaits a Peruvian lawyer. Plan for: consent; access requests; cross-border use is none by default. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

Where does “Record retention” fit in Simca, in particular regarding archive access?

Built (repo) C0206

How long sales and tax records must be kept varies by place and document. For Peru the repository researched the periods (not legal advice) and built retention clocks as tested code: a toss of tax-relevant data is refused until a date computed from the record's own date, books wait for a recorded liquidation plus five years, and a legal hold blocks every toss. The retention table is a signed, editable data pack whose status is draft, not reviewed by a lawyer. Plan for: archive access; no trusted time offline; the table's years are defaults, not facts. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

What should I plan for with “Age-restricted sales”, with a focus on underage refusal logging?

Planned C0207

Alcohol, tobacco and similar goods need age checks. The catalog has age prompts. Plan for: underage refusal logging; overrides; id scanning absent. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

What should owners check about “Food safety”, with a focus on recalls?

Planned C0208

Allergen, temperature and traceability rules for food businesses. Lots and expiry are in the catalog; formal food-safety plans are not. Plan for: recalls; allergen labels; temperature logs. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

How risky is “Pharmacy rules” to get wrong, thinking about controlled registers?

Gap C0209

Prescription and controlled-substance rules are strict. The catalog has lots and prescription flags only. Plan for: controlled registers; cold chain; insurer claims. It is a gap: the catalog does not cover it.

Open this answer on its own page

What should owners check about “Weights and measures”, especially around calibration stickers?

Gap C0210

Scales used for trade often need approval and calibration. Plan for: calibration stickers; rounding; tare. It is a gap: the catalog does not cover it.

Open this answer on its own page

Why does “Employment rules” matter for a small business, thinking about overtime?

Planned C0211

Wages, hours and tips are regulated; the catalog has basic labor items for Peru and payroll-adjacent exports. Plan for: overtime; tip pooling rules; contractor classification. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

Which edge cases come up around “Accessibility”, thinking about colour contrast?

Planned C0212

The catalog includes localization and accessibility items; this site targets WCAG 2.2 AA checks on its own pages but makes no claim about the app. Plan for: colour contrast; screen readers; large text. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

How risky is “Anti-money-laundering” to get wrong, thinking about thresholds?

No claim C0213

Money services and large-cash businesses face reporting duties. Simca provides no monitoring. Plan for: thresholds; identity capture; suspicious activity. No claim is made.

Open this answer on its own page

How risky is “Consumer protection” to get wrong, thinking about refund periods?

Planned C0214

Returns, warranties and price display rules. Plan for: refund periods; warranty terms; price accuracy. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

Where does “Transport rules” fit in Simca, in particular regarding document validity?

Planned C0215

Waybills, driver documents and vehicle rules for logistics. Plan for: document validity; cross-border; hours of service. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

What should I plan for with “Trade and export rules”, especially around customs codes?

Gap C0216

Import and export rules apply to wholesale and manufacturing. Not covered. Plan for: customs codes; licences; origin documents. It is a gap: the catalog does not cover it.

Open this answer on its own page

Which edge cases come up around “Removing a module: keep or toss the data”, considering secure erase not provided?

Built (repo) C0217

ADR-0005: when a customer unticks an element, its data is kept by default: archived, read-only and restored if the element is added again. Tossing is a separate, explicit choice that needs the element id typed, a verified backup first and, for books and personal data, an export, a retention check and a Spanish acknowledgement. There is no delete-all. Built as tested code in the core, Logistics, packaging and the launcher model; no screen. Deleted data is not securely erased. Plan for: secure erase not provided; whole-element granularity only; kept archives accumulate. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

What should I plan for with “Legal hold”, in particular regarding holds are local?

Built (repo) C0218

ADR-0007: a legal hold on one element or on everything blocks every toss until it is lifted, and lifting needs a typed confirmation. Both are written to the audit chain. Built as tested code. Plan for: holds are local; no trusted time offline; lifting is audited. It exists only as a file in the repository, not as a product feature.

Open this answer on its own page

What should I plan for with “Personal-data requests offline”, especially around tax data cannot simply be erased?

Planned C0219

Planned in the catalog's LEGAL module: a register of access, rectification, cancellation and objection requests with deadlines, a data-restriction flag on records, and erasure of non-tax personal data only. Not built; the legal reading awaits a Peruvian lawyer. Plan for: tax data cannot simply be erased; deadlines; minors. In the catalog it is a plan; no screen or product is built.

Open this answer on its own page

What should owners check about “Terms and privacy drafts for the product”, in particular regarding lawyer review pending?

Designed C0220

The repository holds Spanish and English drafts of the product's terms of use and privacy notice. Spanish governs. They state that acquisition is free, that data stays on the customer's computer, that deletion of tax data is limited by law and by Simca's retention table, and that Simca gives no tax or accounting advice. They are marked draft, not reviewed by a lawyer, and are not shown to customers. Plan for: lawyer review pending; owner identity and complaints channel undefined; fee wording to be re-confirmed. It is designed in a document and no code exists.

Open this answer on its own page

Which edge cases come up around “Showing you are above the profit threshold”, considering businesses with no net-profit books?

Not decided C0221

The fee depends on a profit threshold, but Simca has no telemetry, so the company cannot see sales or books. The repository recommends that the app compute a band locally from the books the user keeps and that the user may choose to export a small signed file with no ledger rows; a rolling three-month average, a grace period and a dispute path through an accountant's attestation are recommended. Not built, and not decided. Plan for: businesses with no net-profit books; income is sensitive data; which services are charged. It is not decided.

Open this answer on its own page