How the Product Fits Together

This reference explains how OxyAccounting keeps source documents, subledgers, the general ledger and reports connected.

Document and ledger boundaries

  • Sales and purchase documents share one document model, so an invoice, quotation, purchase order, credit note and supplier invoice behave consistently and number independently.
  • Every final business action posts through one ledger path. Nothing writes journal lines around it, so the ledger cannot disagree with the document that produced it.
  • A source record can produce its intended journal once, which protects against a repeated submission posting twice.
  • Reports read posted ledger or subledger data; they do not invent a second set of transaction values.
  • Reversals keep the original record and post the correcting effect required for an audit trail.

Company isolation

Every record belongs to one company, and that boundary is enforced on each request rather than left to the screen. Subscription features and user permissions are evaluated for the active company. Platform operations use a separate console, and accountant or operator entry into a company is explicit and audited.

Key integrations and boundaries

AreaBoundary
PayFastSubscription checkout, renewal and cancellation; not customer invoice collection.
EmailTransactional document and account email with delivery history.
BankingCSV statement import; no live bank feed.
SARSVAT201 and EMP201 preparation for manual eFiling; no direct filing.
RoxyPage-context product guidance; no access to your record contents.
Data exportRaw and portable archive; no universal or one-click accounting-package migration.

OxyAccounting Docs

Last reviewed 1 August 2026. OxyAccounting does not submit returns to SARS or replace professional accounting or tax advice.