What exports
- Jobs — with status, issues, prices and technician attribution
- Sales — retail transactions against drawer sessions
- Customers — records and contact details
- Finance — ledger transactions including deposits and receivables
- Reports — the figures behind the reporting screens
Exports are produced as CSV, which is what an accountant working in Excel actually wants. Software that cannot hand over a file becomes something the business works around.
The audit log
Sensitive changes append to an audit log recording the user, the change and the time. Entries are never rewritten or deleted.
The same append-only discipline runs through the product: the job pipeline moves forward only, and financial history is corrected by posting a reversing entry rather than by deleting the original. History is a record, not a current state somebody may have tidied.
On integrations and APIs
To be direct about a gap: Horus Repair does not currently offer a public REST API, webhooks, or built-in accounting and payment-processor integrations. Data movement today is via the export files described above.
This is stated plainly because discovering it after committing to a platform is worse than knowing it now.
Frequently asked questions
- Can I export my data out of Horus Repair?
- Yes. Jobs, sales, customers, finance and reports all export to CSV, so figures can go to an accountant or be worked on in Excel. Your data is not locked in.
- Does Horus Repair have a public API or webhooks?
- Not currently. There is no public REST API, no webhooks, and no built-in integrations with accounting software or payment processors. Data movement is via CSV export. This is a known gap rather than a hidden one.
- Is there a record of who changed what?
- Yes. Sensitive changes append to an immutable audit log capturing the user, the change and the timestamp. Entries are never rewritten or deleted, and the job timeline and financial ledger follow the same append-only discipline.