Question 1

What is AURA Tax & Payroll OS?

Accepted Answer

MVP scope: AURA is a shared operating layer for U.S. hospitality and multi-property teams. Its context brings properties, employees, payroll and tips, tax and wage compliance, filing workflows, workforce or identity workflows, and reviewable audit evidence into one place.

Question 2

Who is AURA for?

Accepted Answer

MVP scope: AURA is for U.S. hospitality teams operating one or more properties, including multi-property teams that need a shared operating layer for property, employee, payroll, tip, compliance, and review workflows.

Question 3

What are AURA’s MVP goals?

Accepted Answer

MVP scope: the goal is to give hospitality teams one reviewable operating layer for properties, employees, payroll and tips, tax and wage compliance, filing workflows, workforce or identity workflows, and audit evidence. Filing support for Forms 941, 8027, 940, W-2, and 1099-NEC is planned; direct IRS filing and SHA-256 ACK generation are unavailable until an authorized integration exists.

Question 4

Which workflows does the AURA context cover?

Accepted Answer

MVP scope: the site and workspace context represent workflows around properties, employees, payroll and tips, tax and wage compliance, filing work, workforce or identity work, and reviewable audit evidence. A workflow being represented in AURA does not by itself mean that an external filing or verification service is connected.

Question 5

Are external filing and verification services connected?

Accepted Answer

Boundary: no. Direct IRS filing and SHA-256 ACK generation are unavailable until an authorized integration exists. AURA does not submit these filings, and the site or workspace should not be read as proof of an external filing or verification connection.

Question 6

Has AURA filed any tax forms?

Accepted Answer

Status clarification: this FAQ does not claim that any tax forms have been filed. AURA’s filing workflows and reviewable evidence are product-scope concepts, not a filing receipt, an acceptance notice, or proof of a completed government submission.

Question 7

What should I treat as planned rather than live?

Accepted Answer

Boundary: filing support for Forms 941, 8027, 940, W-2, and 1099-NEC is planned rather than available. Direct IRS filing and SHA-256 ACK generation are unavailable until an authorized integration exists. Do not treat roadmap language, a workflow label, or an illustrative status as proof of a live external integration, filed form, or completed identity verification.

Question 8

What does “reviewable audit evidence” mean in this context?

Accepted Answer

MVP scope: it means evidence that can be reviewed within the AURA operating layer as part of a workflow. It does not mean that a government agency, external filing service, or external verification service has independently confirmed the record.

The operating layer, clearly explained.

Know what is in scope.

The operating layer, clearly explained.

Know what is in scope.

What is AURA Tax & Payroll OS?MVP scope

Who is AURA for?MVP scope

What are AURA’s MVP goals?MVP scope

Which workflows does the AURA context cover?MVP scope

Are external filing and verification services connected?Boundary

Has AURA filed any tax forms?Status clarification

What should I treat as planned rather than live?Boundary

What does “reviewable audit evidence” mean in this context?MVP scope